accessibility-test-plan
Create accessibility testing plans covering assistive technologies and WCAG criteria.
npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- What You Do
- Testing Layers
- 1. Automated Testing
- 2. Manual Testing
- 3. Assistive Technology Testing
- 4. User Testing with Disabilities
- Test Matrix
- WCAG Criteria Checklist
- Reporting
- Best Practices
What does the accessibility-test-plan skill do?
Create accessibility testing plans covering assistive technologies and WCAG criteria.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.