accessibility-reviewlisted

## What It Does Audits the UI against WCAG 2.2 A/AA. Combines (1) static scan for missing ARIA, missing alt text, and obvious focus issues with (2) axe-core results from the Playwright walk (Step 3 of the workflow). Every finding cites a WCAG 2.2 success criterion id — the design-test analog of WSTG ids in pentest. ## Use This When Use this for every design-test run. Driven by the live phase's axe-core output when available; static-only when the live phase is blocked. ## Inputs - Read `docs/instructions/design-system/accessibility.md` for declared a11y rules. - Read `references/wcag-mapping.md` to map findings to WCAG ids. - Read the axe-core results JSON from `runtime-checks.ts` if the live phase ran. ## Procedure Detection and mapping are deterministic — the LLM picks severity and writes findings; the scripts do the spotting. 1. Static scan: run `scripts/static-a11y-scan.sh [search-root]` → TSV of `<category>\t<file>:<line>\t<excerpt>`. Categories: `img-no-alt | button-no-name | anchor-no-name | input-no-label | outline-zero | positive-tabindex | missing-lang`. 2. Live axe results: when the Step 3 runtime walk produced an axe JSON, run `scripts/parse-axe-violations.sh <axe-results.json>` → TSV of `<route>\t<rule-id>\t<impact>\t<target>\t<help>`. Accepts either a full runtime-checks payload or a bare violations array. 3. For each axe rule emitted, run `scripts/map-axe-to-wcag.sh <rule-id>` to get its primary WCAG 2.2 success criterion id. Unmapped rules return `WCAG-