Summary
Run the agreed accessibility verification on representative pages so release decisions are based on rendered behavior, not source review alone.
Why this matters to users
Users do not benefit from code that looks correct in review but fails in the browser. This verification pass is what turns accessibility work from a best effort into a release-quality outcome.
Outcome we want
A release-readiness checkpoint that confirms high-risk user journeys work on representative pages with both automated and manual verification.
Scope
- Automated checks on the representative page matrix
- Keyboard-only verification
- Screen-reader verification for high-risk flows
- Release summary of unresolved known risks
Out of scope
- Net-new remediation work that belongs in earlier phases
Conditions of satisfaction
Summary
Run the agreed accessibility verification on representative pages so release decisions are based on rendered behavior, not source review alone.
Why this matters to users
Users do not benefit from code that looks correct in review but fails in the browser. This verification pass is what turns accessibility work from a best effort into a release-quality outcome.
Outcome we want
A release-readiness checkpoint that confirms high-risk user journeys work on representative pages with both automated and manual verification.
Scope
Out of scope
Conditions of satisfaction