OpenParable
Skip to content
← Back to skills

Accessibility Testing

Testing & Quality
accessibility-testing

Accessibility Testing is an Agent Skill for testing & quality published in the thedaviddias/Front-End-Checklist repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/thedaviddias/Front-End-Checklist/blob/HEAD/skills/accessibility-testing/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/accessibility-testing, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Include accessibility testing

Automated accessibility testing catches 30-50% of WCAG violations before code reaches users—reducing legal risk and improving usability for everyone.

Quick Reference

  • Use jest-axe for component-level accessibility testing
  • Integrate @axe-core/playwright or cypress-axe for E2E a11y tests
  • Run accessibility tests in CI/CD to catch regressions early
  • Test specific WCAG rules like color-contrast individually

Check

Review this test suite for accessibility testing coverage using axe-core, jest-axe, or similar tools.

Fix

Add automated accessibility testing to detect WCAG violations in components and pages.

Explain

Explain how to implement automated accessibility testing and what issues it can detect.

Code Review

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