What the release gate checks.
- Every public page source is manifested or explicitly excluded.
- Critical routes are checked for structure, accessible names, reflow, zoom, color modes, and WCAG A and AA rules.
- Keyboard-only journeys cover diagnosis, application review, workshop selection, and artifact creation.
- Accessible text downloads are checked for filename, media type, content, contract version, and evidence boundary.
- Visual baselines cover mobile, tablet, desktop, dark mode, reduced motion, and forced-colors emulation.
A proxy is not a person.
We show incomplete evidence instead of turning an automated result into a broader claim.
Safari 27 on macOS 27
Safari and safaridriver are available, but Safari Remote Automation is disabled on the verification machine.
No Safari result is claimed. Enabling persistent remote automation requires explicit owner approval, and a human journey is still required.VoiceOver with Safari
VoiceOver is available on the verification machine.
Automated ARIA snapshots are a semantic proxy, not VoiceOver output.Windows High Contrast
Chromium forced-colors emulation passes structure and visual regression checks.
A real Windows High Contrast run is still required.NVDA with Chrome or Firefox on Windows
No compatible Windows and NVDA environment is available in this workspace.
No NVDA result is claimed.Make the next move easier to understand.
Orient before asking
Name where the person is, what this step is for, and what happens next before requesting effort.
Ask for one decision at a time
Keep each control focused on one choice and separate explanation from the action label.
Make labels predict the result
Use specific verbs and objects so links and buttons still make sense when read out of context.
Make recovery obvious
Explain what needs attention, preserve prior work, and return focus to the place where recovery starts.
Separate evidence from promise
State what an estimate, recommendation, or artifact can show and what it cannot prove.
Passing checks is not the same as universal access.
Automated checks and browser emulation can find regressions, but they do not prove that every person, assistive technology, browser, or operating system can complete every task.
- No automated tool can establish complete accessibility or usability.
- The current screen-reader journey validates semantic orientation, not speech quality or user comprehension.
- Production accessibility must be rechecked after deployment because the verified scope is local.
- New customer content and third-party integrations can introduce issues outside this receipt.