test-accessibility

Installation
SKILL.md

Accessibility tests

Three layers, each catching what the others cannot: a rule engine scans every state a user can reach, browser checks drive the keyboard and read the accessibility tree, and a short screen reader pass covers what only a person can judge. Success is a gate that fails on new WCAG A and AA violations, browser checks shown to fail on a seeded bug, and a recorded manual pass for the flows that matter.

What each layer can decide

Layer Decides Cannot decide
Rule engine (axe-core, pa11y, Lighthouse) Missing names, labels and alt; invalid ARIA; contrast of plain text on solid backgrounds; duplicate ids in ARIA references; page language; target size Anything that needs interaction, intent or judgment: focus order and visibility, traps, Escape, focus return, missing error wiring, announcements, reflow, motion, alt text quality
Browser checks (key presses, accessibility tree, viewport and media emulation) Tab reaches every control in order, visible focus, dialog focus management, accessible description of a field, live regions, 320 px reflow, reduced motion Whether the experience makes sense when heard
Manual screen reader pass What is announced, in what order, and whether it is usable Regressions between passes
Installs
1
First Seen
8 days ago
Security Audits