accessibility-test-plan
The accessibility-test-plan skill guides creation of comprehensive testing strategies that evaluate digital products across assistive technologies, WCAG compliance levels, and user interaction modes. Use this when planning accessibility validation for web or digital applications, combining automated tools, manual testing techniques, and real-world assistive technology scenarios to identify issues before launch.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/accessibility-test-plan && cp -r /tmp/accessibility-test-plan/prototyping-testing/skills/accessibility-test-plan ~/.claude/skills/accessibility-test-planSKILL.md
# 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
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.
Create QA checklists for verifying design implementation accuracy.
Establish design review gates with criteria, checklists, and approval workflows.
Plan and facilitate design sprints from challenge framing through prototype testing.
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Design team workflows covering task management, collaboration rituals, and tooling.