What is the accessibility-compliance skill?
The accessibility-compliance skill is a SKILL.md in the ui-design plugin of the wshobson/agents repository. It guides an AI coding agent through WCAG 2.2 Level AA or AAA work, ARIA patterns, keyboard and focus handling, forms, reduced motion and mobile screen reader support.
WCAG 2.2 sits in the first line of the description for this wshobson/agents skill. It belongs to the ui-design plugin and covers mobile accessibility, inclusive design patterns and assistive technology support, built to help users with disabilities.
The SKILL.md itself is compact. Most of the detail lives in four reference files, and the main file lists when to use it, best practices, common issues and testing tools.
When the skill applies
- Implementing WCAG 2.2 Level AA or AAA.
- Building screen reader accessible interfaces.
- Adding keyboard navigation, focus management and focus trapping.
- Creating forms with proper labels.
- Supporting reduced motion and high contrast.
- Mobile accessibility with VoiceOver and TalkBack.
- Auditing and fixing violations.
Practices and testing tools
Eight best practices lead with semantic HTML over ARIA, keyboard first design and keeping focus styles. Content should work at 200% zoom. Named testing tools include axe DevTools, WAVE, Lighthouse, VoiceOver, NVDA, JAWS and TalkBack.
Who the accessibility-compliance skill is for
Best for
- Teams building to WCAG 2.2 who want an agent that remembers focus order, labels and live regions.
- Reviewing custom controls that recreate native behaviour badly, a common issue the skill lists.
- Related pages: fixing-accessibility and web-accessibility-skill.
Not for
- A certified audit. The skill guides code, and its own advice is to test with real users.
- Replacing automated scanners. It names axe DevTools, WAVE and Lighthouse. Related page: web quality audit.
Use it with UiChemy
Accessible markup helps the pages you ship from a design tool. After UiChemy converts a Figma file with Figma to WordPress, review the Elementor or Gutenberg output, and use Composer to adjust it visually. Click Get Started on uichemy.com.
How to install Accessibility Compliance Skill: WCAG 2.2 for Agents
gh skill install wshobson/agents accessibility-complianceCheck GitHub CLI
The
gh skillcommand requires GitHub CLI 2.90 or later. Rungh --versionand upgrade first if your version is older.Install the skill
Run
gh skill install wshobson/agents accessibility-complianceand select your coding tool when prompted. The README says this reads the skill from GitHub without cloning the repository.Or install the whole plugin
Inside Claude Code run
/plugin marketplace add wshobson/agents, then/plugin install ui-design@claude-code-workflows. This adds the ui-design plugin that contains the skill, with its agents, commands and hooks.Invoke it
Try a prompt such as: use accessibility-compliance to audit this form component. Name the file so the agent reviews real markup.
Check that it loaded
Ask the agent to review a modal dialog. It should check focus trapping, keyboard dismissal, labels, focus order and live region announcements, and cite the matching WCAG guidance.
Key features
- WCAG 2.2 targetsSupports Level AA or AAA compliance work on interfaces, as named in the use list.
- Screen reader supportGuidance for building interfaces that assistive technology can read, with ARIA patterns in a dedicated reference file.
- Keyboard and focusKeyboard navigation, focus management and focus trapping, plus the rule never to remove focus styles.
- Accessible formsInputs get proper labels, because missing labels are one of the listed common issues.
- Reduced motion and contrastHonors prefers-reduced-motion and prefers-contrast settings.
- Mobile accessibilityiOS VoiceOver and Android TalkBack support is covered in mobile-accessibility.md.
- Eight best practicesSemantic HTML, testing with real users, keyboard first, visible focus, text alternatives, 200% zoom, live regions and honoring preferences.
- Common issue listMissing alt text, poor contrast, keyboard traps, missing labels, auto-playing media, custom controls, missing skip links and wrong focus order.
- Named testing toolsaxe DevTools, WAVE and Lighthouse for automated checks, VoiceOver, NVDA, JAWS and TalkBack for manual ones, NoCoffee and Silktide for simulation.
Frequently asked questions
What is the accessibility-compliance skill?
It is a SKILL.md in the ui-design plugin of the wshobson/agents repository. It helps an AI coding agent implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns and assistive technology support, and it points to reference files for detail.
How do I install the accessibility-compliance skill?
Run gh skill install wshobson/agents accessibility-compliance and pick your coding tool when prompted. GitHub CLI 2.90 or later is required. The plugin route is /plugin marketplace add wshobson/agents followed by /plugin install ui-design@claude-code-workflows.
Which WCAG level does it target?
The use list mentions WCAG 2.2 Level AA or AAA compliance. Detailed pattern documentation lives in references/details.md, which SKILL.md says to read when its navigation tier is not enough. Choose your target level in your prompt.
Does it cover mobile accessibility?
Yes. It lists iOS VoiceOver and Android TalkBack support, and a reference file called mobile-accessibility.md holds the details. Manual testing with VoiceOver, NVDA, JAWS and TalkBack is named among its testing tools.
Does the skill replace automated testing?
No. It names axe DevTools, WAVE and Lighthouse as automated tools and lists manual screen reader testing too. Its best practices also say to include people with disabilities in user testing, which no skill replaces.
Which AI coding agents can use the skill?
The repository README describes support for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Google Antigravity and Pi through different install routes. Skills-only installs ask which coding tool you use, so pick yours at the prompt.
What license does the skill use?
GitHub lists the wshobson/agents repository as MIT licensed, and the accessibility-compliance skill sits inside its ui-design plugin. Confirm the license in the repository before copying the folder into a product of your own.