WCAG 2.2 Accessibility Audit
AIPexStudio/AIPex
Audits a live webpage against eight core WCAG 2.2 success criteria, combining accessibility-tree inspection, visual screenshots and keyboard navigation tests, with evidence in the report.
A skill your agent uses when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks.
Install Accessibility Testing
$ npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist accessibility-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/accessibility-testing .claude/skills/accessibility-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "accessibility-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/accessibility-testing into .claude/skills/accessibility-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/accessibility-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist accessibility-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/accessibility-testing .agents/skills/accessibility-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "accessibility-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/accessibility-testing into .agents/skills/accessibility-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist accessibility-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/accessibility-testing .cursor/skills/accessibility-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "accessibility-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/accessibility-testing into .cursor/skills/accessibility-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/accessibility-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist accessibility-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/accessibility-testing .gemini/skills/accessibility-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "accessibility-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/accessibility-testing into .gemini/skills/accessibility-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist accessibility-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/accessibility-testing .github/skills/accessibility-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "accessibility-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/accessibility-testing into .github/skills/accessibility-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist accessibility-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/accessibility-testing .opencode/skills/accessibility-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "accessibility-testing" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/accessibility-testing into .opencode/skills/accessibility-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
accessibility-testing- GitHub stars
- 74k
- Token cost
- ~432 tokens
- SKILL.md length
- 147 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks.
- Reviewing component libraries
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- CI pipelines that need repeatable accessibility checks
What it does
Accessibility Testing is an agent skill from thedaviddias/Front-End-Checklist. 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.
Its SKILL.md is about 430 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Frontend & Design, covering Accessibility. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Reviewing component libraries
- CI pipelines that need repeatable accessibility checks
Example prompts
- “/accessibility-testing”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Accessibility Testing loads about 432 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 147 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 147 words, ~432 tokens.
Download SKILL.mdSave it as
.claude/skills/accessibility-testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- accessibility-testing
- description
- 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.
- metadata.category
- testing
- metadata.priority
- high
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 30
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/testing/accessibility-testing
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/rules/testing/accessibility-testing
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/accessibility-testing of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Accessibility Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Accessibility Testing this skillthedaviddias/Front-End-Checklist | 74k | — | ~432 | Automated safety check: Pass | MIT | |
| WCAG 2.2 Accessibility AuditAIPexStudio/AIPex | 1.3k | — | ~4.7k | Automated safety check: Pass | MIT | |
| Vrtmarigold-ui/marigold | 146 | — | ~787 | Automated safety check: Pass | MIT | |
| Control UIcursor/plugins | 10k | 2 repos | ~1.2k | Automated safety check: Pass | None | |
| Accessibility Testingpetrkindlmann/qa-skills | 163 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Accessibility Testingnaodeng/awesome-qa-skills | 243 | — | ~665 | Automated safety check: Pass | Custom licence |
Similar skills
Vrt
marigold-ui/marigold
DST — Trigger the Visual-Regression-Tests (Chromatic) GitHub Actions workflow on the current or a given branch.
- Official
Control UI
cursor/plugins
Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI.
Accessibility Testing
petrkindlmann/qa-skills
Test for WCAG 2.2 AA compliance with axe-core + Playwright, keyboard navigation audits, screen reader testing, ARIA pattern validation, and legal compliance mapping (ADA, EAA, Section 508).
Accessibility Testing
naodeng/awesome-qa-skills
A skill your agent uses when you need to design accessibility testing against WCAG, keyboard navigation, and assistive technology scenarios; triggers include accessibility testing and a11y testing.
Create Component
Orange-OpenSource/Orange-Boosted-Bootstrap
Step-by-step workflow for creating a new SCSS and/or JavaScript component in OUDS Web.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Accessibility Testing
What does Accessibility Testing do?
A skill your agent uses when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Accessibility Testing is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks.
When should I use Accessibility Testing?
Accessibility Testing fits situations like: reviewing component libraries; CI pipelines that need repeatable accessibility checks.
How do I install Accessibility Testing in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a claude-code`. Or copy the skill folder (skills/accessibility-testing in thedaviddias/Front-End-Checklist) into .claude/skills/accessibility-testing in your project. Claude Code loads it when a task matches its description.
How do I install Accessibility Testing in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a codex`. Or copy the skill folder (skills/accessibility-testing in thedaviddias/Front-End-Checklist) into .agents/skills/accessibility-testing in your project. Codex loads it when a task matches its description.
Can I use Accessibility Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill accessibility-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/accessibility-testing, .gemini/skills/accessibility-testing, .github/skills/accessibility-testing and .opencode/skills/accessibility-testing in your project.
What does Accessibility Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Accessibility Testing is instructions for the agent only.
Does Accessibility Testing access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Accessibility Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Accessibility Testing use?
Accessibility Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Accessibility Testing use?
About 432 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Accessibility Testing?
Skills that share tags, products or a category with Accessibility Testing: WCAG 2.2 Accessibility Audit (AIPexStudio/AIPex, 1.3k stars), Vrt (marigold-ui/marigold, 146 stars), Control UI (cursor/plugins, 10k stars) and Accessibility Testing (petrkindlmann/qa-skills, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Accessibility Testing?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,388 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.