Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-09 | ✗→✓ | ▲ Improved | -21% | 0% |
| case-14 | ✗→✓ | ▲ Improved | -71% | 0% |
| case-01 | ✓→✓ | ＝ Same ✓ | -10% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | -4% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | 33% | 0% |
Automated accessibility testing catches 30-50% of WCAG violations before code reaches users—reducing legal risk and improving usability for everyone.
Review this test suite for accessibility testing coverage using axe-core, jest-axe, or similar tools.
Add automated accessibility testing to detect WCAG violations in components and pages.
Explain how to implement automated accessibility testing and what issues it can detect.
Inspect component tests, E2E suites, and CI workflows for automated accessibility coverage. Flag critical pages or shared components that ship without axe-based checks, and note issues that still require manual keyboard or screen reader validation.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/testing/accessibility-testing
Other measured skills in the registry, with their headline benchmark lift.