accessibility-a11y — Claude Code skill: what it does, how to install
accessibility-a11y — a skill for Claude Code and Codex guides WCAG 2.2 compliance and interface accessibility checks. Activates during UI component development, accessibility reviews, or CI/CD test integration.
MIT 161 installs ★ 114 updated 2026-11-10
npx skills add travisjneuman/.claude --skill accessibility-a11y -a claude-codeWhat accessibility-a11y does
The skill provides reference patterns for building accessible web applications conforming to WCAG 2.2 AA and AAA levels. It covers modal dialogs, accessible forms with error notifications, keyboard navigation, and live regions for dynamic updates.
Guidance relies on semantic HTML before ARIA, explicit focus handling, and screen reader testing with VoiceOver and NVDA. A built-in contrast reference defines minimum ratios, including 4.5:1 for standard text and 3:1 for large text or graphical widgets under WCAG AA.
Because automated test suites detect only around 30% of accessibility flaws, this setup enforces manual keyboard-only verification for all interactive elements.
What it helps with
- audit UI components against WCAG 2.2 AA and AAA requirements
- implement keyboard focus trapping for custom modal dialogs
- verify color contrast ratios across typography and UI elements
- integrate automated accessibility audits into CI/CD pipelines
Example prompts for the agent
- Review this checkout form for WCAG 2.2 AA compliance and missing labels
- Add accessible focus management and keyboard handling to the modal component
- Check color contrast ratios for our primary button styles
How to install accessibility-a11y
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill accessibility-a11y -a claude-code2Manually: put the files in place
~/.claude/skills/accessibility-a11y/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-a11y/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill accessibility-a11y -a codex2Manually: put the files in place
.agents/skills/accessibility-a11y/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill accessibility-a11y -a cursor2Manually: put the files in place
.cursor/skills/accessibility-a11y/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install travisjneuman/.claude skills/accessibility-a11y2Manually: put the files in place
.github/skills/accessibility-a11y/SKILL.md1Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill accessibility-a11y -a gemini-cli2Platform CLI
gemini skills install https://github.com/travisjneuman/.claude --path skills/accessibility-a11yManually: put the files in place
.devin/skills/accessibility-a11y/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add travisjneuman/.claude --skill accessibility-a11y -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about accessibility-a11y
How to install accessibility-a11y in Claude Code?
Run npx skills add travisjneuman/.claude --skill accessibility-a11y -a claude-code in your terminal.
What does accessibility-a11y do?
It guides the assistant through WCAG 2.2 standards, ARIA specifications, keyboard focus rules, and automated testing integrations.
What reference topics are included in the skill?
It includes implementation patterns for dialogs and forms, an ARIA quick reference, common anti-patterns, and an audit checklist.
Source text
SKILL.md · MIT
--- name: accessibility-a11y description: WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing --- # Accessibility (a11y) ## Overview This skill covers building accessible web applications that work for everyone, including people using screen readers, keyboard-only navigation, switch devices, and other assistive technologies. It addresses WCAG 2.2 compliance at AA and AAA levels, correct ARIA usage, focus management, color contrast, reduced motion support, and automated testing integration. Use this skill when building new UI components, reviewing existing interfaces for accessibility compliance, fixing a11y audit findings, or integrating automated accessibility testing into CI/CD pipelines. --- ## Core Principles 1. **Semantic HTML first** - Native HTML elements (`<button>`, `<nav>`, `<dialog>`) provide accessibility for free. ARIA is a repair tool for when semantics are insufficient, not a replacement for proper HTML. 2. **Keyboard is the baseline** - If it doesn't work with a keyboard alone, it doesn't work. Every interactive element must be focusable, operable, and have visible focus indicators. 3. **Test with real assistive technology** - Automated tools catch ~30% of accessibility issues. The rest require manual testing with screen readers (VoiceOver, NVDA) and keyboard-only navigation. 4. **Progressive enhancement** - Build the accessible version first, then layer on visual enhancements. Never hide content from assistive technology that sighted users can see. 5. **No information by color alone** - Color can reinforce meaning but never be the sole indicator. Use icons, text labels, and patterns alongside color. --- ## Reference files Detailed material is in separate files so this overview stays short. Read only the file whose topic matches the task; each one is self-contained. Paths are relative to the folder that holds this `SKILL.md` (in the full toolkit install, `~/.claude/skills/accessibility-a11y/`). | Topic | File | Covers | | --- | --- | --- | | Key Patterns | [`references/key-patterns.md`](references/key-patterns.md) | Pattern 1: Accessible Modal Dialog; Pattern 2: Accessible Form with Error Handling; Pattern 3: Keyboard Navigation for Custom Widgets; Pattern 4: Live Regions for Dynamic Content; Pattern 5: Automated Accessibility Testing | | ARIA Quick Reference | [`references/aria-quick-reference.md`](references/aria-quick-reference.md) | 13 lines | | Anti-Patterns | [`references/anti-patterns.md`](references/anti-patterns.md) | 14 lines | | Checklist | [`references/checklist.md`](references/checklist.md) | 17 lines | ## Color Contrast Quick Reference | Text Size | WCAG AA | WCAG AAA | |---|---|---| | Normal text (< 18px / 14px bold) | 4.5:1 | 7:1 | | Large text (>= 18px / 14px bold) | 3:1 | 4.5:1 | | UI components & graphical objects | 3:1 | 3:1 | | Decorative / disabled elements | No requirement | No requirement | --- ## Related Resources - **Skills:** `performance-engineering` (intersection of performance and a11y), `growth-engineering` (accessible onboarding) - **Rules:** `docs/reference/checklists/ui-visual-changes.md` (visual change accessibility checks) - **Rules:** `docs/reference/stacks/react-typescript.md` (React component patterns)
© travisjneuman · MIT · travisjneuman/.claude