Guide · Agent skill
How to use the Accessibility Compliance agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Accessibility Compliance skill is a set of instructions that gives an AI coding agent a checklist-style guide for building websites and apps that people with disabilities can use. It covers WCAG 2.2 success criteria, keyboard navigation, focus management, ARIA roles and labels, screen reader support on iOS and Android, and reduced-motion or contrast preferences. This guide explains what the skill does, how to install it, how to trigger it, and where its limits are, so you can use it on your next interface review or build.
Accessibility Compliancewshobson/agents · MIT Download the skill Quick start
- 1Download the ZIP. Get the accessibility-compliance skill ZIP from this page.
- 2Unzip into a skills folder. Extract it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Confirm the files. Check that SKILL.md and the references folder are present.
- 5Ask for an accessibility task. Describe the component or screen and the problem, such as an audit or a screen reader fix.
- 6Test the result. Run axe DevTools, WAVE or Lighthouse, then check with VoiceOver, NVDA, JAWS or TalkBack.
What the skill makes the agent do
Once installed, the agent has accessibility guidance loaded into its context. When you ask for help with an interface, it can review code or designs for common accessibility problems and suggest fixes. It can also help you implement features such as accessible forms, focus trapping for modals, live regions for dynamic content, and mobile support for VoiceOver and TalkBack.
When deeper detail is needed, the skill points to reference files with worked examples, including files on ARIA patterns, WCAG guidelines, and mobile accessibility.
- Reviews code or designs for common accessibility issues and suggests fixes
- Explains WCAG 2.2 Level AA and AAA criteria in the context of your work
- Gives ARIA role, state and property guidance, with the reminder to prefer native HTML first
- Covers keyboard navigation, focus order and focus trapping
- Covers mobile touch target sizing and screen reader support on iOS and Android
- Honours reduced-motion and contrast preferences
Install the Accessibility Compliance skill
Download the skill ZIP from this page. Unzip it into your personal skills folder, ~/.claude/skills/, so it is available in every project. To limit it to one project, unzip it into that project's .claude/skills/ folder instead.
If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload
Check the files after installing
The unzipped skill should contain SKILL.md at its core, plus a references folder. SKILL.md holds the main instructions and the description the agent uses to decide when to load the skill. The references folder holds the detailed files the agent reads when it needs more depth.
- SKILL.md
- references/aria-patterns.md
- references/details.md
- references/mobile-accessibility.md
- references/wcag-guidelines.md
Trigger the skill with natural requests
You do not need a special command. The skill's description says it applies when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences. Describe your task in those terms and the agent can pick the skill up.
Be specific about the component, platform and standard you care about. Naming WCAG 2.2 Level AA, VoiceOver or a particular component type gives the agent more to work with.
- Audit this login form for accessibility problems and suggest fixes
- Add keyboard navigation and focus trapping to this modal dialog
- Review this navigation component for ARIA issues and screen reader support
- Check this mobile screen for VoiceOver and TalkBack problems
- Make this carousel respect prefers-reduced-motion
Testing your work
The skill lists testing tools but does not run them. For automated checks it names axe DevTools, WAVE and Lighthouse. For manual testing it names VoiceOver on macOS and iOS, NVDA and JAWS on Windows, and TalkBack on Android. Run these yourself against your interface.
The skill also recommends testing with people with disabilities, which no automated check replaces.
- Automated: axe DevTools, WAVE, Lighthouse
- Manual: VoiceOver (macOS/iOS), NVDA/JAWS (Windows), TalkBack (Android)
Requirements and safety notes
The skill lists no requirements. It does not run scripts and does not use the network. It consists of instruction and reference files only, so it does not run commands on your machine or contact outside services.
Because it is guidance, its suggestions still need checking. Review any code the agent writes and test it with assistive technology before you rely on it.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
What people use it for
- Auditing a login or checkout form for missing labels and poor focus order
- Adding keyboard navigation and focus trapping to a modal dialog
- Reviewing a mobile screen for VoiceOver and TalkBack support
- Checking touch target sizes and spacing in a button group
- Adding reduced-motion and contrast handling to animated or themed components
Frequently asked questions
Is the Accessibility Compliance skill free?
The skill is published under the MIT licence, as listed on this page. The source does not mention pricing, so check the repository for licence terms.
What does the accessibility-compliance skill require?
The skill lists no requirements. It does not run scripts and does not use the network, and it consists of instruction and reference files.
How do I install the accessibility-compliance skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or a project's .claude/skills/ folder. In the Claude apps, you can upload it under Settings → Capabilities → Skills.
Can this skill scan my live website for accessibility errors?
No. The skill names tools such as axe, WAVE and Lighthouse but does not run them. You need to run those tools yourself against your site.
Does this skill make my product legally compliant?
No. It gives guidance, not a formal compliance sign-off, and it does not replace testing with real users with disabilities or a professional audit.
How does it compare with running axe or WAVE?
Axe, WAVE and Lighthouse check your interface automatically. This skill helps the agent write and review code with accessibility in mind and suggests fixes, so the two approaches complement each other.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Front-end developers who want accessibility considerations built into their coding help, and designers or product teams preparing an audit, will get useful checklists and fixes from this skill. Teams that need a formal compliance sign-off, automated scanning of a live site, or testing with users with disabilities should use a professional audit and the testing tools directly.
Download the skill