Agent skill · vasilyu1983
qa-testing-accessibility
Builds accessibility testing workflows for WCAG 2.2 audits and CI gates. Use when adding axe-core or Lighthouse checks, calibrating gate policy, or planning screen-reader testing.
What it needs
About 12k tokens when loaded.
What this skill does
QA Testing (Accessibility) Accessibility testing automation, CI gating, and audit methodology for web and mobile. Use this skill to decide what to automate, what requires manual testing, and how to build a sustainable accessibility quality gate. Key distinction: software-ui-ux-design covers accessible design. This skill covers accessible testing — tooling, CI gates, screen reader protocols, and conformance evidence. Quick Start 1. Add axe-core to existing component or E2E tests to catch common detectable issues early. 2. Establish a baseline before enabling blocking gates on legacy codebases. 3. Set a team-defined CI policy: a common starter is block on critical/serious, warn on moderate, but tune it per product risk and remediation maturity. 4. Plan manual audit for what automation cannot judge reliably: context, usability, cognitive load, and assistive-technology behavior. 5. Run screen-reader verification on critical user flows before release. Workflow 1. Gather the target surfaces, WCAG scope, and platform constraints. 2. Cover what automation can reliably detect first. 3. Add manual keyboard and screen-reader checks for critical journeys. 4. Turn findings into CI gates, remediation work, and verification evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vasilyu1983/qa-testing-accessibility