accessibility-test-harness

Design accessibility verification harnesses for web applications with WCAG criteria mapping.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill accessibility-test-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-test-harness
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/accessibility-test-harness
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill accessibility-test-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill creates an accessibility verification harness so teams can test keyboard access, screen-reader behavior, focus management, and color contrast without falsely assuming that automated scans alone prove accessibility.

Core Features & Use Cases

  • WCAG-pinned verification planning: Defines the target standard, scope, and criteria for each check so findings are traceable and audit-ready.
  • Automated and manual split: Separates axe-style component scans, E2E checks, CI contrast checks, and linting from manual keyboard and screen-reader review.
  • Evidence-driven reporting: Maps findings to WCAG criteria, assigns accessibility-specific severity, and records reproducible evidence for audits or complaints.
  • Use Case: A product team receives a keyboard-accessibility complaint on checkout and needs a repeatable pass that catches traps, unreachable controls, and broken dialog focus behavior.

Quick Start

Ask for an accessibility harness for the target app or journey, including the WCAG level, the screen-reader and browser matrix, and the automated and manual checks you want covered.

Frequently Asked Questions about accessibility-test-harness

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

FAQPage Schema
How do I set up a WCAG accessibility test harness for web applications?

Split accessibility checks into automated axe-style component scans and manual keyboard or screen-reader reviews, mapping all findings to specific WCAG criteria with evidence-based severity reporting for audit readiness.

What's the best way to automate keyboard and screen-reader testing in CI?

Wire component and E2E accessibility scans into CI for automated contrast and lint checks, while keeping manual keyboard journeys and screen-reader smoke tests as a separate verification split.

How do I map accessibility violations to WCAG criteria for audit reporting?

Apply a WCAG-pinned verification plan that records reproducible evidence, assigns accessibility-specific severity, and uses a baseline-and-ratchet violation policy to prevent regression in audit reporting.

Does automated accessibility scanning prove WCAG compliance for keyboard and focus management?

Automated scanning alone does not prove WCAG compliance for keyboard and focus management; an explicit automated-versus-manual split is required to catch focus traps, unreachable controls, and broken dialog focus behavior.

How do I prevent accessibility regressions when fixing keyboard traps and contrast issues?

Apply a baseline-and-ratchet violation policy that maps findings to WCAG criteria, ensuring existing keyboard traps and contrast issues are fixed without allowing new violations to enter the codebase.