accessibility-compliance

1# Accessibility Compliance
2 
3Master accessibility implementation to create inclusive experiences that work for everyone, including users with disabilities.
4 
5## When to Use This Skill
6 
7- Implementing WCAG 2.2 Level AA or AAA compliance
8- Building screen reader accessible interfaces
9- Adding keyboard navigation to interactive components
10- Implementing focus management and focus trapping
11- Creating accessible forms with proper labeling
12- Supporting reduced motion and high contrast preferences
13- Building mobile accessibility features (iOS VoiceOver, Android TalkBack)
14- Conducting accessibility audits and fixing violations
15 
16## Detailed patterns and worked examples
17 
18Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
19 
20## Best Practices
21 
221. **Use Semantic HTML**: Prefer native elements over ARIA when possible
232. **Test with Real Users**: Include people with disabilities in user testing
243. **Keyboard First**: Design interactions to work without a mouse
254. **Don't Disable Focus Styles**: Style them, don't remove them
265. **Provide Text Alternatives**: All non-text content needs descriptions
276. **Support Zoom**: Content should work at 200% zoom
287. **Announce Changes**: Use live regions for dynamic content
298. **Respect Preferences**: Honor prefers-reduced-motion and prefers-contrast
30 
31## Common Issues
32 
33- **Missing alt text**: Images without descriptions
34…