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.