Skip to content
Back to skills

Accessibility Test Plan

ASecurity

Create accessibility testing plans covering assistive technologies and WCAG criteria.

  • 158 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
designgotestingci/cd

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add NVlabs/Skill2Env --skill accessibility-test-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Accessibility Test Plan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Accessibility Test Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nvlabs-accessibility-test-plan/badge)](https://www.skillsdirectory.com/skills/nvlabs-accessibility-test-plan)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: accessibility-test-plan
description: Create accessibility testing plans covering assistive technologies and WCAG criteria.
---
# 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…