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
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).
Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use `presentation-deck`.