Accessibility Test Plan
- 951 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
accessibility-test-plan is a QA planning skill that generates layered WCAG accessibility test plans for developers who must validate automated, manual, assistive-technology, and real-user coverage before release.
About
accessibility-test-plan is a skill from owl-listener/designer-skills that creates comprehensive accessibility testing plans across four layers. Automated testing uses Axe, Lighthouse, and WAVE, catching roughly 30-40% of issues and integrating into CI/CD on every page state. Manual testing covers keyboard-only navigation, screen reader walkthroughs, 200% and 400% zoom, high contrast, and reduced motion. Additional layers address assistive technology checks and real-user validation against WCAG criteria. Developers reach for accessibility-test-plan when preparing release QA, audit remediation, or CI accessibility gates for web applications.
- Creates comprehensive test plans covering automated, manual, assistive technology, and user testing with disabilities
- Maps every key user flow against keyboard-only, VoiceOver, NVDA, zoom 200%, high contrast, and reduced motion
- Organizes WCAG criteria by Perceivable, Operable, Understandable, and Robust principles with A/AA/AAA levels
- Produces reports that include description, WCAG criterion, severity, assistive tech affected, reproduction steps, and re
- Integrates Axe, Lighthouse, and WAVE automated checks that typically catch 30-40% of issues
Accessibility Test Plan by the numbers
- 951 all-time installs (skills.sh)
- +43 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #433 of 1,888 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill accessibility-test-planAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 951 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you plan WCAG accessibility testing before release?
Generate structured accessibility test plans that combine automated, manual, assistive technology, and real-user testing layers.
Who is it for?
Frontend developers and QA engineers shipping accessible web apps who need structured WCAG coverage beyond automated scans alone.
Skip if: Backend-only API projects, teams with no UI surface, or developers seeking automatic code fixes without a test plan.
When should I use this skill?
The user needs an accessibility test plan, WCAG audit prep, or CI accessibility coverage before shipping a UI.
What you get
Layered accessibility test plan with automated, manual, assistive-tech, and user-testing steps mapped to WCAG.
- accessibility test plan document
- CI a11y check list
By the numbers
- Automated a11y tools catch approximately 30-40% of issues
Files
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
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.698k164k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.486k29.4k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst382k15.8k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k470
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.284k66.9k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.282k109kFAQ
What tools does accessibility-test-plan include for automation?
accessibility-test-plan recommends Axe, Lighthouse, and WAVE for automated runs on every page state, noting they catch approximately 30-40% of issues and should integrate into CI/CD pipelines.
What manual checks does the accessibility test plan cover?
accessibility-test-plan adds keyboard-only navigation, screen reader walkthroughs, 200% and 400% zoom, high contrast mode, and reduced motion testing alongside assistive technology and real-user layers.
Is Accessibility Test Plan safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.