accessibility-scan — Claude Code skill: accessibility checks
Scans one live page for mechanically detectable WCAG 2.2 issues and reports their DOM locations. Run it after a UI change to review the page.
npx skills add AccessLint/skills --skill accessibility-scan -a claude-codeWhat accessibility-scan does
The skill runs @accesslint/core against a live page over CDP. Its report groups findings by impact and gives a DOM selector; when source mapping is available, it also points to a file and line. Evidence can include a contrast ratio or a missing attribute.
Before scanning, the skill ensures Chrome is available for debugging. Give it a page URL, a target name from accesslint.config.json, or no argument to use the config’s default target. If there is no default target or config file, provide a URL.
It reports findings without editing the project. After making fixes, run the scan again to check the page. Keyboard and screen-reader checks are handled by the separate accessibility-inspect skill, not this scan.
What it helps with
- find WCAG 2.2 issues on a live page
- locate a finding by DOM selector and source line
- check for contrast and missing-attribute problems
- rescan a page after a UI change
Example prompts for the agent
- Scan the
devtarget for accessibility issues and list the findings. - Check this page and connect each issue to its selector and source file when available.
- Scan the page at the URL I provide; report findings without editing code.
How to install accessibility-scan
1Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-scan -a claude-code2Manually: put the files in place
~/.claude/skills/accessibility-scan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-scan/
1Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-scan -a codex2Manually: put the files in place
.agents/skills/accessibility-scan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-scan -a cursor2Manually: put the files in place
.cursor/skills/accessibility-scan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install AccessLint/skills accessibility-scan2Manually: put the files in place
.github/skills/accessibility-scan/SKILL.md1Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-scan -a gemini-cli2Platform CLI
gemini skills install https://github.com/AccessLint/skills --path plugins/accesslint/skills/accessibility-scanManually: put the files in place
.devin/skills/accessibility-scan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-scan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about accessibility-scan
How do I install accessibility-scan in Claude Code?
Run npx skills add AccessLint/skills --skill accessibility-scan -a claude-code. The skill file is installed at ~/.claude/skills/accessibility-scan/SKILL.md.
What does accessibility-scan do?
It checks one live page for mechanically detectable WCAG 2.2 issues and reports DOM selectors, with source file locations when available. It does not edit code.
Can I run accessibility-scan without a page URL?
Yes, if accesslint.config.json has a default target. Otherwise, pass a page URL.
