Accessibility Test Plan
Produce a WCAG-oriented accessibility test plan with automated, manual, assistive-tech, and user-testing layers before release or redesign sign-off.
Overview
Accessibility Test Plan is an agent skill most often used in Ship (also Launch, Grow) that creates systematic WCAG and assistive-technology testing plans for key user flows.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill accessibility-test-planWhat is this skill?
- Four testing layers: automated (Axe, Lighthouse, WAVE), manual, assistive technology, and user testing with disabilities
- Notes automated tools catch roughly 30–40% of issues—manual and AT coverage required
- Test matrix across keyboard-only, VoiceOver, NVDA, zoom 200%, high contrast, and reduced motion per flow
- WCAG checklist organized by Perceivable, Operable, Understandable, Robust and levels A/AA/AAA
- Issue template: WCAG criterion, severity, affected assistive tech, repro steps, remediation
- 4 testing layers (automated, manual, assistive technology, user testing)
- Automated tools catch approximately 30–40% of issues
- WCAG principles: Perceivable, Operable, Understandable, Robust
Adoption & trust: 572 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to ship UI changes but have no structured plan to test keyboard, screen readers, zoom, or WCAG criteria beyond a quick Lighthouse score.
Who is it for?
Solo builders and tiny teams launching SaaS, marketing sites, or mobile web who need professional a11y QA without a dedicated accessibility program.
Skip if: Pure backend or CLI projects with no user interface, or teams that only want a one-line “run axe” command with no manual AT coverage.
When should I use this skill?
Create accessibility testing plans covering assistive technologies and WCAG criteria.
What do I get? / Deliverables
You receive a documented test matrix, WCAG-aligned checklist, and reporting format so issues are found and tracked before users with disabilities hit blockers in production.
- Flow-by-flow accessibility test matrix
- WCAG criteria checklist by level
- Issue report template with severity and remediation fields
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Shipping is when you must prove keyboard, screen reader, zoom, and contrast behavior—not just visual polish—so this skill shelves under Ship testing. Outputs structured test matrices and issue reports for QA workflows rather than visual design or infra monitoring.
Where it fits
Draft a pre-release matrix for checkout and onboarding with NVDA and keyboard-only columns filled in.
Attach WCAG issue summaries to enterprise or government RFP responses after a structured audit pass.
Turn recurring a11y support tickets into added rows in the test matrix for the affected flows.
Hand the plan to your agent while implementing shadcn or custom components so states get tested, not just happy paths.
How it compares
Produces a full QA plan and matrix—not a single automated audit script or design mockup skill.
Common Questions / FAQ
Who is accessibility-test-plan for?
Builders and designers shipping customer-facing UIs who need WCAG-aware test documentation and assistive-technology coverage guidance for their agents.
When should I use accessibility-test-plan?
In Ship (testing) before a release or redesign; in Launch when proving compliance for distribution or enterprise deals; in Grow when revisiting flows after analytics show drop-off for assistive-tech users.
Is accessibility-test-plan safe to install?
It describes testing methodology only; confirm vendor trust via the Security Audits panel on this Prism catalog page before adding the skill to your agent.
SKILL.md
READMESKILL.md - Accessibility Test Plan
# 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