accessibility-test-plan
owl-listener/designer-skills
Plan comprehensive accessibility testing with assistive technologies, WCAG criteria, and real user participation.
What is accessibility-test-plan?
Creates structured testing plans for evaluating digital accessibility across assistive technologies and WCAG standards. Use when organizing formal accessibility testing sessions with real users and AT devices—not for self-evaluation of designs.
- Define testing layers: automated tools, manual keyboard/screen reader/zoom testing, and assistive technology validation
- Build test matrices across key user flows covering VoiceOver, NVDA, zoom levels, high contrast, and reduced motion modes
- Organize WCAG criteria by principle (Perceivable, Operable, Understandable, Robust) and conformance level (A, AA, AAA)
- Establish participant recruitment criteria for users with relevant disabilities (vision, motor, cognitive, hearing)
- Create issue reporting templates with WCAG mapping, severity, affected AT, reproduction steps, and remediation guidance
How to install accessibility-test-plan
npx skills add https://github.com/owl-listener/designer-skills --skill accessibility-test-planHow to use accessibility-test-plan
- 1.Define the key user flows and features to test
- 2.Select assistive technologies to cover (screen readers, voice control, magnification, switch control)
- 3.Build a test matrix mapping flows against AT platforms and manual testing modes (keyboard, zoom, high contrast, reduced motion)
- 4.Organize WCAG criteria by principle and level, assigning to relevant test cases
- 5.Recruit participants with relevant disabilities and establish session protocols
- 6.Document reporting format: issue description, WCAG criterion, severity, affected AT, reproduction steps, remediation
Use cases
- Schedule accessibility testing with real assistive technology users before major product launches
- Plan multi-layer testing strategy combining automated scanning, manual keyboard/screen reader checks, and user sessions
- Organize testing across multiple AT platforms (VoiceOver, NVDA, TalkBack, Voice Control, Dragon) and zoom/contrast modes
- Build accessibility test matrices for key user flows to ensure WCAG coverage across all interaction patterns
- Document testing protocols and issue severity prioritization for accessibility remediation work
- Accessibility testers and QA specialists
- Product managers planning accessibility validation
- Design system teams scheduling comprehensive AT testing
- Development teams integrating accessibility into definition of done
- Organizations recruiting disabled users for participatory testing
accessibility-test-plan FAQ
Automated tools catch 30-40% of issues. This skill plans comprehensive testing including manual keyboard/screen reader checks, real assistive technology devices, and user testing with disabled participants—essential for catching interaction and usability issues automation misses.
Use this for formal testing programs with real AT users and multiple platforms. Use `accessibility-audit` for self-evaluation of design mockups or quick compliance checks.
The skill guides participant criteria by disability type (vision, motor, cognitive, hearing). Recruit through disability organizations, accessibility communities, user testing platforms with AT specialization, or internal employee networks.
Start with VoiceOver (Mac/iOS), NVDA (Windows), and keyboard-only navigation—these cover the majority of AT users. Add TalkBack (Android), Voice Control, magnification, and switch control based on your user base and product type.
Prioritize by user impact and frequency across AT platforms, not just WCAG level. An AA issue affecting all screen reader users ranks higher than an AAA issue affecting one edge case.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
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
Related skills
More from owl-listener/designer-skills and the wider catalog.
aesthetic-usability
Apply the Aesthetic-Usability Effect to build trust through visual consistency and polish.
affinity-diagram
Cluster qualitative research data into themed insights across multiple interviews and sources.
animation-principles
Apply animation principles—easing, staging, follow-through—to tune how a single UI motion feels.
card-sort-analysis
Analyze card sort results into proposed groupings and labels for information architecture.
case-study
Craft compelling portfolio case studies with narrative arc, process evidence, and measurable outcomes.
click-test-plan
Design first-click and click tests to measure findability and navigation clarity.