Accessibility statement.
Last reviewed: 2026-04-21 · Target: WCAG 2.2 AA
ThatStupidComputer targets WCAG 2.2 AA compliance across every page. This is a working target, not a finished state. Known limitations are listed below. Accessibility concerns go to joseph.w.anady@icloud.com and are acknowledged within two business days.
What WCAG 2.2 AA means here
WCAG 2.2 AA is the Web Content Accessibility Guidelines version 2.2 at conformance level AA. It covers perceivability, operability, understandability, and robustness. Every page on this site is designed, built, and tested against these guidelines, including color contrast, keyboard operability, semantic structure, focus visibility, and screen reader compatibility.
Specific practices applied on every page: semantic HTML5 landmarks (header, nav, main, footer), one H1 per page, proper heading order, form labels associated with inputs, autocomplete attributes on every input that maps to a personal data type, skip link at the top of every page, focus indicators meeting contrast requirements, alt text on all meaningful images, aria-hidden on decorative content.
Known limitations
The decorative WebGL landscape background auto-loads on pages where the ozarks scene is active. It is marked aria-hidden and skipped by screen readers. Users with prefers-reduced-motion set see a static fallback without animation. Mobile devices skip the scene entirely. Complex canvas interactions, if added in the future, will receive keyboard controls before shipping.
The Engine Optimization Grader at /grader/ uses custom radio button styling. Current implementation is keyboard operable and screen reader labeled but the visual focus indicator could be improved. Planned for revision in the next build cycle.
Some portfolio detail pages use images without responsive srcset. They are lazy loaded and carry descriptive alt text, but loading them on cellular networks is slower than optimal. Planned for revision.
How we test
Every page is tested against the WCAG 2.2 AA checklist before launch and re-tested on every substantial update. Automated tools include axe DevTools and Lighthouse Accessibility. Manual tests include keyboard only navigation, screen reader rotor check with VoiceOver on macOS, and color contrast verification via WebAIM Contrast Checker.
Automated tests are run as part of the one hundred twenty six check quality gate that every site must pass before going live. Manual tests are performed by Joseph personally. Third party audits are available on request for clients who need independent verification.
Contact for accessibility issues
Accessibility problems encountered on this site can be reported by email to joseph.w.anady@icloud.com, by phone at (505) 512-3662, or by mail to 463 State Highway 76, Cassville, Missouri 65625. Reports are acknowledged within two business days and remediated as quickly as the complexity allows.
When reporting an issue, including the page URL, the specific difficulty encountered, the assistive technology used, and any workaround you found helps us fix the issue faster.
Updates to this statement
This statement is reviewed at least quarterly and updated whenever substantial accessibility work is performed on the site. The last reviewed date at the top of this page reflects the most recent review. Significant changes to accessibility approach are communicated in the Field Notes blog.