Verified:GitHub

accessibility-test-plan

Plan accessibility testing across assistive technologies and WCAG criteria.

38|5|Updated Feb 24, 2026

Search Tags:#automation #testing #accessibility #usability #wcag #manual-testing #assistive-tech

One-click install

npx skills add https://github.com/launchapp-dev/animus-cli --skill accessibility-test-plan-launchapp-dev

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: accessibility-test-plan
Source: https://github.com/launchapp-dev/animus-cli/tree/main/.claude/skills/accessibility-test-plan
Command: npx skills add https://github.com/launchapp-dev/animus-cli --skill accessibility-test-plan-launchapp-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a plan to create comprehensive accessibility testing across assistive technologies and WCAG criteria, helping teams verify usability for all users.

Core Features & Use Cases

Automated testing: Axe, Lighthouse, WAVE tools; Catches 30-40% issues; Run on every page/state; Integrate into CI/CD pipeline.
Manual testing: Keyboard-only navigation; Screen reader walkthrough; Zoom to 200% and 400%; High contrast mode; Reduced motion mode.
Assistive technology testing: Screen readers (VoiceOver, NVDA, TalkBack); Voice control and Dragon; Switch control; Screen magnification.
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

Quick Start

Create an accessibility testing plan covering assistive technologies for your next release.

Frequently Asked Questions about accessibility-test-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a WCAG compliance testing plan for web and mobile apps?▼

Automated accessibility testing catches 30-40% of issues, making it necessary but insufficient. It must be paired with manual testing, such as keyboard-only navigation and screen reader walkthroughs, to ensure comprehensive coverage.

How do I test accessibility with screen readers like VoiceOver and NVDA?▼

Accessibility testing should be integrated into CI/CD pipelines to run automated checks continuously. Testing early and including it in the definition of done prevents compliance gaps before launch.

What is the best way to document accessibility testing results for remediation?▼

User testing with disabilities focuses on real tasks rather than compliance checkboxes. It involves recruiting participants with varied disabilities to test with their own devices and settings, prioritizing issues by actual user impact.

How do I build an accessibility test matrix for keyboard and high contrast modes?▼

Manual accessibility testing includes keyboard-only navigation, screen reader walkthroughs, zoom to 200% and 400%, high contrast mode, and reduced motion mode. These checks verify operability and perceivability for users with diverse needs.