accessibility-fix · accesslint — Claude Code skill: what it does, how to install
accessibility-fix repairs web accessibility violations against WCAG 2.2: baselines issues, edits files, verifies the result. Applies mechanical fixes automatically and leaves TODOs for judgment calls.
no license 1,200 installs ★ 124 updated 2026-08-25
npx skills add AccessLint/skills --skill accessibility-fix -a claude-codeWhat accessibility-fix does
The skill runs a three-step loop: audit to capture the violation set, edit code to address each one (add attributes, labels, roles), then re-audit to confirm targeted violations are gone and no new ones appeared. It accepts a findings worklist from accessibility-scan, accessibility-inspect, or accessibility-audit, or scans a target directly—URL, files, or a directory.
For live-DOM checks it calls audit_live, for static HTML and JSX it uses audit_html. The first requires a debuggable Chrome instance: the skill launches a headless one or attaches to an open browser. Authenticated sessions need a manually started headed browser, sign-in, then a port passed to the audit.
It applies only those changes where a concrete fix directive is given. Where visual or contextual judgment is needed (alt text, link text), it drops a TODO comment with the rule ID. Content is never invented.
What it helps with
- repair WCAG violations from an audit report
- add missing alt attributes and aria-label
- apply mechanical a11y fixes to JSX components
- verify edits introduced no new violations
- batch-remediate accessibility issues across files
Example prompts for the agent
- Fix accessibility violations in
src/components/Header.jsx - Apply the fixes from
audit-report.json - Make
app/views/checkout.htmlWCAG-compliant
How to install accessibility-fix
1Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-fix -a claude-code2Manually: put the files in place
~/.claude/skills/accessibility-fix/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-fix/
1Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-fix -a codex2Manually: put the files in place
.agents/skills/accessibility-fix/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-fix -a cursor2Manually: put the files in place
.cursor/skills/accessibility-fix/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install AccessLint/skills plugins/accesslint/skills/accessibility-fix2Manually: put the files in place
.github/skills/accessibility-fix/SKILL.md1Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-fix -a gemini-cli2Platform CLI
gemini skills install https://github.com/AccessLint/skills --path plugins/accesslint/skills/accessibility-fixManually: put the files in place
.devin/skills/accessibility-fix/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add AccessLint/skills --skill accessibility-fix -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-fix
How to install accessibility-fix in Claude Code?
Run npx skills add AccessLint/skills --skill accessibility-fix -a claude-code. The skill will appear in ~/.claude/skills/accessibility-fix/SKILL.md.
What does accessibility-fix do?
It repairs web accessibility violations against WCAG 2.2 by running an audit baseline, editing code to add attributes and roles, then verifying the outcome. Mechanical changes are applied as given; where context is needed, it leaves a TODO with the rule ID.
Can I fix accessibility without running a separate audit first?
Yes. Pass a URL, file, or directory—the skill will baseline it before applying fixes. Or hand it a findings list from accessibility-scan or accessibility-audit and it skips the baseline step.
Similar skills
All skills for Frontend and UI →accessibility-fix by other authors comes first.