accessibility-compliance — Claude Code skill for accessibility
This skill guides accessibility audits and interface work involving keyboard navigation, screen readers, and forms. Use it when building against WCAG 2.2.
/plugin marketplace add wshobson/agents
/plugin install ui-design@claude-code-workflowsWhat accessibility-compliance does
The skill covers WCAG 2.2 interface work, from keyboard navigation and focus management to labeled forms and screen reader support. It also addresses mobile accessibility, reduced-motion and contrast preferences, text alternatives, and content that remains usable at 200% zoom.
It lists common issues and testing tools: axe DevTools, WAVE, and Lighthouse for automated checks; VoiceOver, NVDA/JAWS, and TalkBack for manual testing. More detailed patterns and examples are in references/details.md. Test with a keyboard and assistive technology.
Install it when you are building or auditing accessible interfaces. For projects with no accessibility work, its guidance may be unnecessary.
What it helps with
- audit an interface for accessibility issues
- add keyboard navigation to interactive components
- manage focus and trap it when needed
- connect form fields to labels
- support VoiceOver and TalkBack
Example prompts for the agent
- Audit this page for WCAG 2.2 accessibility issues.
- Add keyboard navigation and focus management to this component.
- Check the form labels and screen reader support.
How to install accessibility-compliance
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install ui-design@claude-code-workflowsThis installs the whole ui-design plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill accessibility-compliance -a claude-code3Manually: put the files in place
~/.claude/skills/accessibility-compliance/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-compliance/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill accessibility-compliance -a codex2Manually: put the files in place
.agents/skills/accessibility-compliance/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill accessibility-compliance -a cursor2Manually: put the files in place
.cursor/skills/accessibility-compliance/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents accessibility-compliance2Manually: put the files in place
.github/skills/accessibility-compliance/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/ui-design/skills/accessibility-complianceManually: put the files in place
.devin/skills/accessibility-compliance/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 accessibility-compliance
How do I install accessibility-compliance in Claude Code?
Run npx skills add wshobson/agents --skill accessibility-compliance -a claude-code. The listed Claude Code marketplace commands are another installation option.
What does accessibility-compliance do?
It guides WCAG 2.2 interface work and audits, including keyboard access, screen reader support, and accessible forms.
Which accessibility testing tools does the skill cover?
It lists axe DevTools, WAVE, and Lighthouse for automated checks, plus VoiceOver, NVDA/JAWS, and TalkBack for manual testing.
Source text
SKILL.md · MIT
--- name: accessibility-compliance description: Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences. --- # Accessibility Compliance Master accessibility implementation to create inclusive experiences that work for everyone, including users with disabilities. ## When to Use This Skill - Implementing WCAG 2.2 Level AA or AAA compliance - Building screen reader accessible interfaces - Adding keyboard navigation to interactive components - Implementing focus management and focus trapping - Creating accessible forms with proper labeling - Supporting reduced motion and high contrast preferences - Building mobile accessibility features (iOS VoiceOver, Android TalkBack) - Conducting accessibility audits and fixing violations ## 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 1. **Use Semantic HTML**: Prefer native elements over ARIA when possible 2. **Test with Real Users**: Include people with disabilities in user testing 3. **Keyboard First**: Design interactions to work without a mouse 4. **Don't Disable Focus Styles**: Style them, don't remove them 5. **Provide Text Alternatives**: All non-text content needs descriptions 6. **Support Zoom**: Content should work at 200% zoom 7. **Announce Changes**: Use live regions for dynamic content 8. **Respect Preferences**: Honor prefers-reduced-motion and prefers-contrast ## Common Issues - **Missing alt text**: Images without descriptions - **Poor color contrast**: Text hard to read against background - **Keyboard traps**: Focus stuck in component - **Missing labels**: Form inputs without associated labels - **Auto-playing media**: Content that plays without user initiation - **Inaccessible custom controls**: Recreating native functionality poorly - **Missing skip links**: No way to bypass repetitive content - **Focus order issues**: Tab order doesn't match visual order ## Testing Tools - **Automated**: axe DevTools, WAVE, Lighthouse - **Manual**: VoiceOver (macOS/iOS), NVDA/JAWS (Windows), TalkBack (Android) - **Simulators**: NoCoffee (vision), Silktide (various disabilities)
© Seth Hobson · MIT · wshobson/agents