Accessibility Testing Guide
Guides an agent to set up and review automated accessibility checks (axe-based) in tests and CI.
- Repository
- thedaviddias/Front-End-Checklist
- Stars
- 74,632
- Licence
- MIT
- Files
- 2 files
What it does
Once installed, the agent can review component libraries, page flows and CI pipelines for automated accessibility checks, such as jest-axe or @axe-core/playwright tests. It explains how to add these checks and flags critical pages or shared components that lack them. It also points out that automated tools only catch structural and attribute-level problems, so keyboard, screen reader and manual UX testing are still needed.
Great for
- Front-end teams wanting accessibility checks in their test suites and CI
- Developers reviewing whether component or end-to-end tests cover accessibility
- Anyone who needs a starting point for axe-based testing before manual audits
Skip it if
- Full accessibility compliance audits: the skill states automated tests miss many issues and do not replace keyboard or screen reader testing
- Teams not using JavaScript test frameworks, since the examples focus on jest-axe, Playwright and Cypress
Try asking
- “Review my Playwright test suite and tell me where axe accessibility checks are missing”
- “Set up jest-axe for our React component library and show me an example test”
- “Add an accessibility step to our GitHub Actions CI pipeline”
- “Explain what automated accessibility testing can and cannot catch on our checkout flow”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 2 original files, the MIT licence and an attribution note.
accessibility-testing.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip accessibility-testing.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip accessibility-testing.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Point the agent at specific component directories or test files so its review is targeted.
- Ask it to note which issues still need manual keyboard or screen reader checks, since automated tests will not cover them.
- Check references/rule.md for framework-specific code examples before applying changes.
What's inside
- references/rule.md
- SKILL.md
Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.