Use when implementing or auditing WCAG 2.2 AA or AAA accessibility: ARIA patterns, keyboard navigation, focus management and screen readers. Includes mobile VoiceOver and TalkBack, accessible forms, reduced motion, contrast and common violation fixes.
Installs into .claude/skills of the current project.
Are you the author of Accessibility Compliance?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/monoes-accessibility-compliance)
---
name: accessibility-compliance
description: "Use when implementing or auditing WCAG 2.2 AA or AAA accessibility: ARIA patterns, keyboard navigation, focus management and screen readers. Includes mobile VoiceOver and TalkBack, accessible forms, reduced motion, contrast and common violation fixes."
tags: ["design","frontend","accessibility","audit","ui"]
tools: ["monodesign_detect","monodesign_fix"]
license: MIT
source: https://github.com/wshobson/agents
source_path: "plugins/ui-design/skills/accessibility-compliance"
source_commit: 4236bb91f8395b0435f1d8b8baf9e8e4c69a8620
---
# 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)