Profile My skills Saved My plugins Edit profile Submit a skill

AI agent skills for accessibility audits

Accessibility skills push an agent past the automated third — contrast and alt text — into the part that needs judgment: focus order, what a screen reader actually announces, whether a custom control has the semantics of the native one it replaced. A good one cites the WCAG criterion it is checking so the finding is arguable. Be suspicious of any that report a passing score; automated checks cannot certify a page.

People land here searching for “claude code accessibility skill”, “agent skill wcag audit”, “a11y review skill”.

199 accessibility audits skills Refine in search →

How to install a accessibility audits skill

  1. Compare the skills. Read the accessibility audits skills below — each page shows the full SKILL.md, its safety verdict, and the capabilities it declares.
  2. Install it. Run npx skillmds@latest add <owner>/<name>. The CLI writes the skill into every agent directory it detects, or use --agent to pin one.
  3. Use it. Restart your agent. It loads the skill on demand the next time you ask for something that matches — you do not have to name the skill.

What makes a good accessibility audits skill?

Accessibility skills push an agent past the automated third — contrast and alt text — into the part that needs judgment: focus order, what a screen reader actually announces, whether a custom control has the semantics of the native one it replaced. A good one cites the WCAG criterion it is checking so the finding is arguable. Be suspicious of any that report a passing score; automated checks cannot certify a page.

Every skill listed here is a plain SKILL.md file in the format Anthropic documents for Agent Skills, read unchanged by Cursor, OpenAI Codex and 60+ agents. Each passes a safety review before it is publicly listed; the verdict and declared capabilities are on every skill's page.

Frequently asked questions

What is an agent skill for accessibility audits?

Accessibility skills push an agent past the automated third — contrast and alt text — into the part that needs judgment: focus order, what a screen reader actually announces, whether a custom control has the semantics of the native one it replaced. A good one cites the WCAG criterion it is checking so the finding is arguable. Be suspicious of any that report a passing score; automated checks cannot certify a page.

Does an accessibility skill replace manual testing?

No. Automated checks catch roughly a third of real issues; keyboard navigation and screen-reader testing catch the rest. A good skill is explicit about that boundary rather than reporting a clean pass.

Which agents can use these accessibility audits skills?

Any agent that reads SKILL.md files: Claude Code, Claude.ai, Cursor, OpenAI Codex, Windsurf, OpenCode and 60+ others. The format is not vendor-specific, so the same file works everywhere — each agent just keeps its skills in a different directory, listed at /agents.

Are these accessibility audits skills free?

Yes. Searching, reading and installing skills on SkillMD is free and needs no account. Individual skills carry their own licence, shown on each skill's page.