a11y-deep

Use @axe-core/playwright in a script that serves the built dist folder statically, visits every generated page with Playwright Chromium, and runs AxeBuilder with WCAG 2.x tags. Exit non-zero when any violation is found so the GitHub Actions job fails.

No. Lighthouse runs only about 66 of axe's 125 rules as a weighted average, so pages can score 0.95+ while failing audits. Even a full axe pass detects roughly 57% of issues by volume, so manual keyboard and screen reader testing remains necessary.

Five of the six new A/AA criteria require human judgment: consistent help, redundant entry, focus not obscured, dragging movements, and accessible authentication. Only target size is automated in axe-core 4.13, and it ships disabled by default so it must be enabled explicitly.

No. In axe-core 4.13 the target-size rule is tagged wcag22aa but ships disabled. Enable it explicitly via the rules option in AxeBuilder, for example options({ rules: { 'target-size': { enabled: true } } }).

Reserve a WCAG-EM 2.0 audit for when the site makes a public conformance or accessibility statement. It defines scope, explores the site, selects representative plus random sample pages, evaluates every applicable criterion, and produces the report the public statement quotes.

Islands hydrated with client:visible or client:idle render interactive-looking controls before JavaScript attaches, so keyboard users can reach dead controls. ClientRouter announces the page title on navigation, so every page needs a unique descriptive title and focus must be managed after view transitions.