accessibility-test-plan — Claude Code skill: what it does and setup
Plans accessibility testing sessions with assistive technology and real users. Useful when preparing user flows for WCAG compliance.
npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a claude-codeWhat accessibility-test-plan does
The skill outlines a four-layer verification strategy. It starts with automated scans via Axe, Lighthouse, and WAVE, which catch roughly 30-40% of flaws in CI/CD pipelines. Next, it structures manual checks for keyboard navigation, high contrast, and 200% to 400% zoom levels, followed by assistive tech runs on VoiceOver, NVDA, TalkBack, and Dragon.
The final tier schedules task-based sessions with people who rely on assistive hardware and software. Each discovered issue is mapped to a standard report structure containing WCAG criteria across levels A, AA, and AAA, affected software, reproduction steps, and remediation advice.
This tool does not audit code directly. If you need to evaluate an interface yourself, use accessibility-audit; this skill focuses strictly on structuring test protocols and organizing participant research.
What it helps with
- plan accessibility testing sessions with assistive technology users
- map test coverage against WCAG A, AA, and AAA criteria
- generate a testing matrix for VoiceOver, NVDA, and TalkBack
- standardize issue reporting with remediation steps and severity
Example prompts for the agent
- Create an accessibility test plan for our checkout flow covering VoiceOver and NVDA.
- Generate a WCAG AA testing matrix for keyboard navigation and 400% zoom.
How to install accessibility-test-plan
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a claude-code2Manually: put the files in place
~/.claude/skills/accessibility-test-plan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-test-plan/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a codex2Manually: put the files in place
.agents/skills/accessibility-test-plan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a cursor2Manually: put the files in place
.cursor/skills/accessibility-test-plan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills accessibility-test-plan2Manually: put the files in place
.github/skills/accessibility-test-plan/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path prototyping-testing/skills/accessibility-test-planManually: put the files in place
.devin/skills/accessibility-test-plan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -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-test-plan
How to install accessibility-test-plan in Claude Code?
Run npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a claude-code. The agent adds the skill configuration to your environment.
What does accessibility-test-plan do?
It builds a testing protocol covering automated tools, screen reader passes, and sessions with disabled users. Every flow is tied back to WCAG principles.
Can accessibility-test-plan audit my design directly?
No, it only outlines test plans and participant protocols. For inspecting design systems or UI assets directly, the author recommends accessibility-audit.
Source text
SKILL.md · MIT
--- name: accessibility-test-plan description: Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems). --- # Accessibility Test Plan You are an expert in planning comprehensive accessibility testing. ## What You Do You create testing plans that systematically evaluate accessibility across assistive technologies and WCAG criteria. ## Testing Layers ### 1. Automated Testing - Axe, Lighthouse, WAVE tools - Catches approximately 30-40% of issues - Run on every page/state - Integrate into CI/CD pipeline ### 2. Manual Testing - Keyboard-only navigation - Screen reader walkthrough - Zoom to 200% and 400% - High contrast mode - Reduced motion mode ### 3. Assistive Technology Testing - Screen readers: VoiceOver (Mac/iOS), NVDA (Windows), TalkBack (Android) - Voice control: Voice Control (Mac/iOS), Dragon - Switch control - Screen magnification ### 4. User Testing with Disabilities - Recruit participants with relevant disabilities - Include variety (vision, motor, cognitive, hearing) - Test with their own devices and settings - Focus on real tasks, not compliance checkboxes ## Test Matrix For each key user flow, test across: keyboard only, VoiceOver, NVDA, zoom 200%, high contrast, reduced motion. ## WCAG Criteria Checklist Organize by principle (Perceivable, Operable, Understandable, Robust) and level (A, AA, AAA). ## Reporting For each issue: description, WCAG criterion, severity, assistive tech affected, steps to reproduce, remediation. ## Best Practices - Test early and continuously, not just before launch - Automated testing is necessary but not sufficient - Test with real assistive technology users - Include accessibility in definition of done - Prioritize by user impact, not just compliance level
© Owl-Listener · MIT · Owl-Listener/designer-skills
