wcag-audit-patterns — Claude Code skill: install and audit
Audits web interfaces against WCAG 2.2 with automated checks and manual verification. Use it to find violations and build accessible patterns.
/plugin marketplace add wshobson/agents
/plugin install accessibility-compliance@claude-code-workflowsWhat wcag-audit-patterns does
This skill guides WCAG 2.2 reviews across A, AA, and AAA conformance levels. It uses the POUR principles to inspect whether people can perceive content, operate the interface, understand it, and use it with assistive technology. It covers issues such as missing alt text, keyboard access, form labels, contrast, and heading order.
Automated testing detects 30-50% of issues, so the skill calls for manual checks as well. Detailed patterns and worked examples live in references/details.md. Its guidance starts with semantic HTML and treats ARIA as a later option when native elements do not fit.
Install it when you need to fix WCAG violations or create accessible components. It is a poor fit for an audit limited to automated scans.
What it helps with
- find interactive controls that lack keyboard access
- fix functional images with missing alt text
- add labels to form fields
- check interface color contrast
- correct an invalid heading hierarchy
Example prompts for the agent
- Audit this page against WCAG 2.2 and group the findings by severity.
- Check the registration form for keyboard navigation, field labels, and error messages.
- Make this custom widget accessible, starting with semantic HTML.
How to install wcag-audit-patterns
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install accessibility-compliance@claude-code-workflowsThis installs the whole accessibility-compliance plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill wcag-audit-patterns -a claude-code3Manually: put the files in place
~/.claude/skills/wcag-audit-patterns/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wcag-audit-patterns/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill wcag-audit-patterns -a codex2Manually: put the files in place
.agents/skills/wcag-audit-patterns/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill wcag-audit-patterns -a cursor2Manually: put the files in place
.cursor/skills/wcag-audit-patterns/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents wcag-audit-patterns2Manually: put the files in place
.github/skills/wcag-audit-patterns/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/accessibility-compliance/skills/wcag-audit-patternsManually: put the files in place
.devin/skills/wcag-audit-patterns/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about wcag-audit-patterns
How do I install wcag-audit-patterns in Claude Code?
Run npx skills add wshobson/agents --skill wcag-audit-patterns -a claude-code. The skill is placed at ~/.claude/skills/wcag-audit-patterns/SKILL.md.
What does wcag-audit-patterns do?
It guides WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Why does wcag-audit-patterns require manual testing?
Automated checks detect 30-50% of issues. Manual review is needed for cases such as keyboard interaction and interface clarity.
Source text
SKILL.md · MIT
--- name: wcag-audit-patterns description: Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns. --- # WCAG Audit Patterns Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies. ## When to Use This Skill - Conducting accessibility audits - Fixing WCAG violations - Implementing accessible components - Preparing for accessibility lawsuits - Meeting ADA/Section 508 requirements - Achieving VPAT compliance ## Core Concepts ### 1. WCAG Conformance Levels | Level | Description | Required For | | ------- | ---------------------- | ----------------- | | **A** | Minimum accessibility | Legal baseline | | **AA** | Standard conformance | Most regulations | | **AAA** | Enhanced accessibility | Specialized needs | ### 2. POUR Principles ``` Perceivable: Can users perceive the content? Operable: Can users operate the interface? Understandable: Can users understand the content? Robust: Does it work with assistive tech? ``` ### 3. Common Violations by Impact ``` Critical (Blockers): ├── Missing alt text for functional images ├── No keyboard access to interactive elements ├── Missing form labels └── Auto-playing media without controls Serious: ├── Insufficient color contrast ├── Missing skip links ├── Inaccessible custom widgets └── Missing page titles Moderate: ├── Missing language attribute ├── Unclear link text ├── Missing landmarks └── Improper heading hierarchy ``` ## Detailed patterns and worked examples Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. ## Best Practices ### Do's - **Start early** - Accessibility from design phase - **Test with real users** - Disabled users provide best feedback - **Automate what you can** - 30-50% issues detectable - **Use semantic HTML** - Reduces ARIA needs - **Document patterns** - Build accessible component library ### Don'ts - **Don't rely only on automated testing** - Manual testing required - **Don't use ARIA as first solution** - Native HTML first - **Don't hide focus outlines** - Keyboard users need them - **Don't disable zoom** - Users need to resize - **Don't use color alone** - Multiple indicators needed
© Seth Hobson · MIT · wshobson/agents