Name: accessibility-compliance
Author: wshobson

Imported from wshobson/agents (plugins/ui-design/skills/accessibility-compliance/SKILL.md) via skills.sh. Install upstream with npx skills add wshobson/agents --skill accessibility-compliance. Copyright stays with the author.

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

Use Semantic HTML: Prefer native elements over ARIA when possible
Test with Real Users: Include people with disabilities in user testing
Keyboard First: Design interactions to work without a mouse
Don't Disable Focus Styles: Style them, don't remove them
Provide Text Alternatives: All non-text content needs descriptions
Support Zoom: Content should work at 200% zoom
Announce Changes: Use live regions for dynamic content
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)

Install accessibility-compliance and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "wshobson-agents-accessibility-compliance", "kind": "skill", "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.", "publisher": "wshobson", "version": "1.0.0", "capabilities": { "domains": [ "legal" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/wshobson/agents", "path": "plugins/ui-design/skills/accessibility-compliance/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/wshobson/agents/accessibility-compliance", "key": "wshobson/agents/plugins/ui-design/skills/accessibility-compliance/SKILL.md" } }, "instructions": "# Accessibility Compliance\n\nMaster accessibility implementation to create inclusive experiences that work for everyone, including users with disabilities.\n\n## When to Use This Skill\n\n- Implementing WCAG 2.2 Level AA or AAA compliance\n- Building screen reader accessible interfaces\n- Adding keyboard navigation to interactive components\n- Implementing focus management and focus trapping\n- Creating accessible forms with proper labeling\n- Supporting reduced motion and high contrast preferences\n- Building mobile accessibility features (iOS VoiceOver, Android TalkBack)\n- Conducting accessibility audi", "cost": { "context_tokens": 522 } }

accessibility-compliance

About