What problem does it solve? Verifying that a web UI is accessible requires many manual checks across keyboard navigation, screen readers, and user preference modes, and regressions are easy to miss. This Skill provides a structured, repeatable testing workflow with checklists and reporting guidance so accessibility verification is consistent and traceable. ## Core Features & Use Cases - Ordered Test Workflow: Runs automated scans first, then keyboard-only journeys, screen reader smoke passes, and zoom/reflow/reduced-motion/forced-colors checks. - Reusable Smoke Checks: A companion CHECKS.md file provides repeatable keyboard, screen reader, and preference-mode smoke steps. - Structured Regression Reporting: Produces reports covering scope, tools, pass/fail results, reproduction steps, and residual risk. - Use Case: After shipping a new checkout form, run this Skill to confirm every control is keyboard-reachable, errors are announced to screen readers, and the flow remains usable at 200 percent zoom. ## Quick Start Use the web-a11y-testing skill to verify the accessibility of the updated checkout page and report any failures with reproduction steps.