wcag-audit
Skill2 starsChanged 8 days agoMITView on GitHub
WCAG 2.2 AA audit checklist, severity rubric, and stack adaptation for accessibility review. Use when the user asks about accessibility, a11y, WCAG, screen readers, keyboard navigation, focus management, ARIA, contrast, semantic HTML, alt text, or form labels, or audits a component, page, or template for accessibility, in any stack, even if WCAG is not mentioned by name. Not loaded just because a project has UI code.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- christopherlouet/wcag-audittheir own version, first seen Mar 18, 2026
- HeleneKassandra/claude-a11y-skilltheir own version, first seen Mar 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- HeleneKassandra/claude-a11y-skill★ 4same name
- christopherlouet/wcag-audit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- auditSkill
- backup-patternsSkill
- bash-patternsSkill
- depsSkill
- django-patternsSkill
- docker-patternsSkill
- drf-patternsSkill
- engineering-fundamentalsSkill
- fastapi-patternsSkill
- git-patternsSkill
- go-patternsSkill
- graphql-patternsSkill
- investigateSkill
- javascript-patternsSkill
- logging-patternsSkill
- referenceSkill
- metaSkill
- monitoring-patternsSkill
- next-app-router-patternsSkill
- nuxt-patternsSkill
- opentofu-patternsSkill
- prSkill
- python-patternsSkill
- react-patternsSkill
- report-formatSkill
- security-patternsSkill
- slop-patternsSkill
- storybook-patternsSkill
- tailwind-patternsSkill
- test-patternsSkill
- typescript-patternsSkill
- unslopSkill
- vps-provisioningSkill
- vue-patternsSkill
- writeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
When the W3C publishes a new WCAG version, reconcile this skill against the per-criterion Understanding pages.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
WCAG 2.2 AA audit
Target: WCAG 2.2 Level AA. Includes all Level A. Does not include AAA unless explicitly requested.
How to apply
- Go through the references in order.
- Skip criteria that do not apply to the scope (e.g. no forms -> skip form labeling).
- Record what was checked, what passed, what failed.
- Note items that require runtime or user testing. Axe settles some against a running page, such as contrast (1.4.3), where the project runs it; screen reader and keyboard behavior still need a person.
For accessibility work, validate against WCAG 2.2 AA explicitly. Do not claim compliance without checking it against this list; an unaudited claim of conformance is a fabrication.
Severity rubric
failure: a direct Level AA violation that will block certification or cause a usable defect.warning: likely to cause issues in some assistive tech configurations, or violates A level and relied on by AA.info: best practice not required at AA, or a pattern likely to regress if not fixed now.
Reference files
| File | Covers |
| reference/anti-patterns.md | Severity-labeled anti-patterns: non-semantic interactives, contrast, missing labels |
| reference/perceivable.md | 1.1, 1.3, 1.4 (alt, semantics, contrast, reflow, text spacing) plus contrast tooling and APCA status |
| reference/operable.md | 2.1, 2.4, 2.5 (keyboard, focus, target size, drag) plus SPA focus management and 2.2 new criteria examples |
| reference/understandable.md | 3.2, 3.3 (consistent nav, errors, labels) plus 3.3.7 / 3.3.8 cognitive accessibility implementations |
| reference/robust.md | 4.1.2 / 4.1.3 (name/role/value, status messages) plus First Rule of ARIA and APG patterns |
| reference/cannot-be-verified.md | Items requiring runtime / AT testing, plus React / Django template / plain HTML stack notes |
References
- WCAG 2.2 spec: https://www.w3.org/TR/WCAG22/
- Understanding WCAG 2.2: https://www.w3.org/WAI/WCAG22/Understanding/
- How to Meet WCAG 2.2 (Quick Reference): https://www.w3.org/WAI/WCAG22/quickref/
- ARIA Authoring Practices Guide (APG): https://www.w3.org/WAI/ARIA/apg/
- W3C Using ARIA (Notes): https://www.w3.org/TR/using-aria/
- WebAIM: https://webaim.org/
- MDN Accessibility: https://developer.mozilla.org/en-US/docs/Web/Accessibility
Version notes
Checked: 2026-09-26 against https://www.w3.org/TR/WCAG22/ and https://www.w3.org/TR/using-aria/
- WCAG 2.2 (Recommendation, updated 2024-12-12): current target; 4.1.1 Parsing obsolete; WAI-ARIA 1.2 still current. WCAG 3.0 remains a Working Draft.
WCAG evolves:
- WCAG 3 is in early-draft form at the time of writing and will not replace WCAG 2.2 conformance until after a long sunset period.
- APCA contrast research continues outside the W3C; treat any "use APCA instead of WCAG ratio" claim as out of scope until the W3C ships normative guidance.
- When the W3C publishes a new WCAG version, reconcile this skill against the per-criterion Understanding pages.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.