Accessibility Audit (WCAG 2.2 AA)

Move a web app from "we think it is accessible" to "every WCAG 2.2 AA criterion has a recorded pass, fail, or not-applicable with evidence" without sacrificing accuracy, developer trust, or the re-verification loop.

Start every run

1. Read references/wcag-checklist.md for the criteria list and which test proves each one.
2. Read references/manual-testing.md before any keyboard, screen-reader, or zoom check.
3. Read references/operations.md for install commands, the URL list format, and report locations.
4. Inspect current state: the previous report in a11y/reports/, open accessibility issues in the tracker, the component library in use, and whether authenticated pages need a storage-state file.
5. Confirm authorization. Scanning and reporting are in scope by default. Changing production code, design tokens, or shared components requires the current request to say so; a scan request alone does not authorize fixes.

Non-negotiable rules

• Automated tools find roughly 30 to 40 percent of WCAG failures. Never report "passes WCAG" from an axe run alone; every criterion needs a manual result or an explicit not-applicable.
• Test the representative page set: home, login, one form with validation, one data table, one modal or dialog, one page with media, one error