a11y-reviewlisted

# Accessibility Review Accessibility is a verify-phase audit, the same shape as `security-review`: define the conformance target, run the automated layer, walk the manual checks, triage each finding to fix or accept-with-rationale. Automated tools (axe-core) catch ~30–40% of issues; the rest require a keyboard and screen-reader walkthrough. A page that passes axe but fails keyboard nav is not accessible. ## When to use - Reviewing a UI change (new page, component, form, interaction) before merge. - A feature touches focus order, dynamic content, media, or color-only signaling. - Hitting a conformance requirement (WCAG 2.1/2.2 AA is the legal/commercial default; AA is the target here unless stated). - An automated a11y scan (axe, Lighthouse) surfaced findings to triage. **Not for:** general code-quality review (use `code-review`); machine-detectable lint/style (use `linting`); runtime behavior bugs (use `debugging`). a11y-review is the human-judgment + tool-assisted audit layer. ## Steps ### 1. Confirm the conformance target and scope WCAG 2.2 AA is the default (covers 2.1 AA + new criteria). AAA is opt-in and only for specific surfaces. Scope: which pages/components are in this review? A full-site audit is different from a single-PR review — state the boundary. ### 2. Run the automated layer axe-core (or Lighthouse a11y audit) catches the machine-detectable class: missing alt text, empty buttons, insufficient contrast (ratio < 4.5:1 for text), duplicate IDs, missing