mcpField
A
accessibility-test-plan

accessibility-test-plan

github.com/owl-listenerTesting & quality3.1k2.1k installsUpdated 8w ago
Repository

About accessibility-test-plan

An accessibility-testing planning skill for teams evaluating products across WCAG criteria and assistive technologies. It organizes automated, manual, assistive technology, and user testing into practical test coverage and reporting.

Key features

  1. 01Plans automated and manual tests
  2. 02Covers assistive technology testing
  3. 03Builds test matrices for user flows
  4. 04Organizes WCAG criteria by level
  5. 05Reports reproduction and remediation details

Use cases

  1. 01Planning accessibility checks before launch
  2. 02Defining coverage for key user flows
  3. 03Including disabled participants in testing
  4. 04Tracking accessibility tests continuously

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill accessibility-test-plan

After installing, type/accessibility-test-planin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported