Accessibility
I build this site to WCAG 2.2 AA and add AAA-level checks where they help. That is a target backed by tests, not a blanket certification.
Every change runs through accessibility linting, unit-level axe checks, and browser scans in Playwright. A regression can stop the build.
Automation only catches part of the problem. Keyboard use, focus after navigation, zoom and text spacing, screen readers, and the open states of dialogs still need hands-on review.
The work is not finished. If you hit a barrier, email ckellyreif@gmail.com. Tell me what happened and what you were trying to do, and I will fix it.
What I check
- WCAG 2.2 A and AA axe scans run across English and Spanish routes, both color themes, and responsive viewports.
- Lighthouse accessibility score of 100, enforced as a continuous-integration gate.
- Keyboard paths, visible focus, skip links, reduced motion, and forced-colors behavior have automated coverage.
- Semantic landmarks, one H1 per page, labelled controls, and live-region announcements are checked in the application.
- Text colors target the AAA 7:1 contrast ratio in both light and dark themes. Control borders are checked separately at 3:1.
VoiceOver with Safari, NVDA with Chrome, the complete keyboard matrix, and a formal WCAG conformance review are still open work. The public claim stays at AA until that work is complete.