a11y-scanlisted

# A11y Scan ## Purpose Run accessibility tooling (axe-core, Pa11y, Lighthouse) against the pages a change touches, classify findings by WCAG conformance level, and emit a markdown report with severity-tagged remediations. Designed for the `accessibility-reviewer` agent and any frontend PR that touches user-facing surface. ## Scope - Targets pages affected by the diff (or an explicit `--pages` glob). - Runs axe-core for rule-based scanning, Pa11y for HTML_CodeSniffer rules, and Lighthouse for the broader a11y category score. - Cross-references findings against WCAG 2.2 success criteria and classifies each as Level A (must), AA (should — most regulated baselines), or AAA (nice-to-have, rarely required). - Emits a markdown report; does NOT auto-fix. Remediation is dispatched to `frontend` / `accessibility-reviewer`. ## When to use - Before merging any PR that touches a user-facing page, component, or design-system primitive. - After a design-system version bump, against representative pages, to catch regressions. - For regulated projects (EU EAA-2025, ADA Title II, Section 508), on every release as a compliance gate. ## When NOT to use - For backend-only changes — no DOM, no findings. - For purely internal admin tools where the operator has explicitly scoped a11y out of policy (rare; surface this for explicit human approval first). - As a substitute for manual screen-reader testing — automated tools catch ~30-40% of WCAG issues. Manual testing covers