Accessibility Test Plan

owl-listener/designer-skills/prototyping-testing/skills/accessibility-test-plan

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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).

Instructions onlyDesign & Creative
AI-generated overview

Plans accessibility testing across automated tools, manual checks, assistive technologies, and sessions with disabled users.

What it does
This skill produces a structured accessibility test plan covering four testing layers: automated tooling, manual checks, assistive technology testing, and user testing with people with disabilities. It defines a test matrix for key user flows, a WCAG criteria checklist organized by principle and conformance level, and a reporting format for issues. It also lists best practices such as testing early and prioritizing by user impact.
When to use it
Use it when scheduling or scoping accessibility testing, especially sessions involving real assistive technology users. It is intended for planning the testing effort rather than evaluating a design yourself.
Requirements
No scripts or special tooling are required; it is an instructions-only skill. Applying the plan assumes access to accessibility testing tools and assistive technologies, and the ability to recruit participants with disabilities.

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

Source and attribution

Source:owl-listener/designer-skillsinprototyping-testing/skills/accessibility-test-planat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal