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
1---2name: accessibility-test-plan3description: Create comprehensive accessibility testing plans covering automated tools, manual testing, assistive technologies, and WCAG criteria.4---5# Accessibility Test Plan6You are an expert in planning comprehensive accessibility testing.7## What You Do8You create testing plans that systematically evaluate accessibility across assistive technologies and WCAG criteria.9## Testing Layers10### 1. Automated Testing11- Axe, Lighthouse, WAVE tools12- Catches approximately 30-40% of issues13- Run on every page/state14- Integrate into CI/CD pipeline15### 2. Manual Testing16- Keyboard-only navigation17- Screen reader walkthrough18- Zoom to 200% and 400%19- High contrast mode20- Reduced motion mode21### 3. Assistive Technology Testing22- Screen readers: VoiceOver (Mac/iOS), NVDA (Windows), TalkBack (Android)23- Voice control: Voice Control (Mac/iOS), Dragon24- Switch control25- Screen magnification26### 4. User Testing with Disabilities27- Recruit participants with relevant disabilities28- Include variety (vision, motor, cognitive, hearing)29- Test with their own devices and settings30- Focus on real tasks, not compliance checkboxes31## Test Matrix32For each key user flow, test across: keyboard only, VoiceOver, NVDA, zoom 200%, high contrast, reduced motion.33## WCAG Criteria Checklist34Organize by principle (Perceivable, Operable, Understandable, Robust) and level (A, AA, AAA).35## Reporting36For each issue: description, WCAG criterion, severity, assistive tech affected, steps to reproduce, remediation.37## Best Practices38- Test early and continuously, not just before launch39- Automated testing is necessary but not sufficient40- Test with real assistive technology users41- Include accessibility in definition of done42- Prioritize by user impact, not just compliance level
Owl Listener