← ClaudeAtlas

wcag-compliance-reporterlisted

Use after an accessibility scan across many pages (pa11y-ci, axe over a sitemap, Lighthouse batch) when the team needs a shareable conformance report. Groups violations by WCAG 2.2 success criterion and level, flags pages that were not scanned and writes a summary plus per-page detail.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# wcag-compliance-reporter ## Overview WCAG 2.2 has 77 success criteria (SC) split across three conformance levels: 25 at A, 24 at AA, 28 at AAA ([wcag-spec][wcag-tr]) - for a total of 49 SC at the AA level (which is the typical legal / contractual target in the US, EU, UK). [wcag-tr]: https://www.w3.org/TR/WCAG22/ Per [wcag-conformance][wcag-conf]: [wcag-conf]: https://www.w3.org/WAI/WCAG22/Understanding/conformance > "**Level AA**: 'satisfies all the Level A and Level AA success > criteria'" > > "All success criteria at a claimed level must be satisfied with no > exceptions." That binary verdict ("conforms or doesn't") makes per-tool output ("axe found 17 violations in 5 pages") hard to act on - the team needs to know **which SC at which level on which page** is failing the conformance claim. This skill builds that report. ## When to use - A multi-page scan has produced output from one or more of: axe-core (via `@axe-core/cli` or `axe-puppeteer`), pa11y (via `pa11y-ci`), Lighthouse (via `lighthouse-batch`), WAVE, IBM Equal Access. - A stakeholder asks "are we WCAG 2.2 AA conformant?" and wants a document, not a CLI dump. - The team is preparing an accessibility audit / VPAT / ACR. - A PR introduces UI changes and the team needs a "before vs after" on conformance. If only one tool is in use, the tool's native HTML report may suffice; this skill is for **aggregation** across multiple tools or multiple pages. ## How to use 1. **Gather scan output** from