← ClaudeAtlas

a11y-violation-gatelisted

Use when a project has accessibility debt and a zero-violations gate would block every PR. Builds a CI ratchet that fails only on new WCAG violations a PR introduces, with pre-existing ones baselined per rule and page, from axe-core, pa11y, Lighthouse, WAVE or IBM Equal Access results.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# a11y-violation-gate ## Overview A binary "all or nothing" a11y gate blocks every PR on a project with accumulated debt, so teams disable it. The **ratchet pattern** fixes this: the gate fails only on **new** violations vs. a stored baseline. Existing violations are grandfathered; fixes shrink the baseline. This skill builds that gate, aggregating outputs from any combination of the five scanners covered by `axe-a11y` (axe-core, pa11y, Lighthouse a11y, WAVE, IBM Equal Access). Sibling gates with the same architecture: `data-quality-gate`, `visual-baseline-gate`, `contract-compatibility-gate`, `perf-budget-gate`. ## When to use - The project has a11y debt and the team wants to gate against regressions while paying down the debt over time. - Multiple a11y scanners run in CI; the team wants one verdict. - Per-rule or per-page severity tiering matters (e.g. block on serious/critical, warn on moderate). If the project is a11y-clean already, prefer a strict scanner- native gate (e.g. `axe-core` configured to fail on any violation) without ratchet - simpler. ## Step 1 - Run the scanners and unify their outputs Each scanner emits its own report shape (axe-core `violations[]`, pa11y `issues[]`, Lighthouse `categories.accessibility.audits`, WAVE `categories`, IBM Equal Access `results[]`). Normalize every finding to one unified record: ```json { "scanner": "axe", "rule_id": "color-contrast", "wcag_sc": "1.4.3", "page_url": "/dashboard", "selector": "button.prim