Access commitment
Build access into the public front door
We aim to apply WCAG 2.2 AA practices and improve through testing and feedback. We do not claim full conformance without independent verification.
Current measures
Implemented in this preview
- Semantic landmarks and one logical page heading
- Skip link and keyboard-reachable navigation
- Visible focus styles and Escape-to-close menus
- Contrast-reviewed brand tokens
- Accessible labels, hints, inline errors, and error summaries
- Reduced-motion support
- Text alternatives for semantic diagrams
- Responsive layouts from 320px and zoom-friendly text
- No required information baked only into images
Keyboard and forms
Native behavior first
Menus use buttons, links, details, and focus management. Forms associate errors with controls, move focus to the error summary, preserve typed values on validation failure, and state loading, unavailable, error, and confirmed-success states.
Alternative formats
Ask for a reasonable format
If a resource or process is difficult to use, contact us for a plain-text explanation or another reasonable format. Availability depends on the source and current capacity.
Known limitations
What still needs human review
- No independent accessibility audit has been completed.
- Third-party Impact Hack Google Forms have their own accessibility behavior.
- Screen-reader and mobile-browser combinations beyond the automated test matrix require manual review.
- Legal and policy language may still benefit from plain-language user testing.
Feedback
Report an access barrier
Last reviewed: 2026-08-03. We aim to handle accessibility feedback through the general-contact target, but complex remediation may take longer.