Implement WCAG 2.2 compliant interfaces with mobile

Accessibility compliance

by wshobson · MIT license · ★ 39,857 on GitHub · updated Sep 21

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…

---
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)

Overview

Master accessibility implementation to create inclusive experiences that work for everyone, including users with disabilities.

Manual install (npx, ZIP)

Claude Codenpx skills add wshobson/agents --skill accessibility-compliance -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wshobson/agents/tar.gz/4236bb91f839 \
  | tar -xz -C ~/.claude/skills --strip-components=4 agents-4236bb91f839/plugins/ui-design/skills/accessibility-compliance

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/77a366b607fa9ad220c3/accessibility-compliance.zip" -OutFile "$env:TEMP\accessibility-compliance.zip"; Expand-Archive "$env:TEMP\accessibility-compliance.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.3 KB
references/4 files · 49.0 KB

Read the files here

wshobson/4236bb95 files

SKILL.md2.3 KB

SKILL.md

Show the full text52 lines

accessibility-compliance/SKILL.md52 lines · 2.3 KB

PreviewCode

Outline

RawView on GitHub

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)

1	---
2	name: accessibility-compliance
3	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.
4	---
5
6	# Accessibility Compliance
7
8	Master accessibility implementation to create inclusive experiences that work for everyone, including users with disabilities.
9
10	## When to Use This Skill
11
12	- Implementing WCAG 2.2 Level AA or AAA compliance
13	- Building screen reader accessible interfaces
14	- Adding keyboard navigation to interactive components
15	- Implementing focus management and focus trapping
16	- Creating accessible forms with proper labeling
17	- Supporting reduced motion and high contrast preferences
18	- Building mobile accessibility features (iOS VoiceOver, Android TalkBack)
19	- Conducting accessibility audits and fixing violations
20
21	## Detailed patterns and worked examples
22
23	Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
24
25	## Best Practices
26
27	1. Use Semantic HTML: Prefer native elements over ARIA when possible
28	2. Test with Real Users: Include people with disabilities in user testing
29	3. Keyboard First: Design interactions to work without a mouse
30	4. Don't Disable Focus Styles: Style them, don't remove them
31	5. Provide Text Alternatives: All non-text content needs descriptions
32	6. Support Zoom: Content should work at 200% zoom
33	7. Announce Changes: Use live regions for dynamic content
34	8. Respect Preferences: Honor prefers-reduced-motion and prefers-contrast
35
36	## Common Issues
37
38	- Missing alt text: Images without descriptions
39	- Poor color contrast: Text hard to read against background
40	- Keyboard traps: Focus stuck in component
41	- Missing labels: Form inputs without associated labels
42	- Auto-playing media: Content that plays without user initiation
43	- Inaccessible custom controls: Recreating native functionality poorly
44	- Missing skip links: No way to bypass repetitive content
45	- Focus order issues: Tab order doesn't match visual order
46
47	## Testing Tools
48
49	- Automated: axe DevTools, WAVE, Lighthouse
50	- Manual: VoiceOver (macOS/iOS), NVDA/JAWS (Windows), TalkBack (Android)
51	- Simulators: NoCoffee (vision), Silktide (various disabilities)
52