Skip to content
UXClaim
Accessibility

Web Accessibility Plugin

23 cite-backed accessibility skills covering ARIA patterns, WCAG 2.2, keyboard interaction, and cognitive design for Claude Code and Gemini CLI.

View source More in Accessibility

What it does

Web Accessibility Plugin provides 23 evidence-based skills that teach LLMs to write accessible code from the start. Rather than relying on AI guessing, each skill encodes actual rules from WAI-ARIA Authoring Practices Guide, WCAG 2.2, and accessibility practitioners—all cited and hallucination-free.

How it works

The plugin works within Claude Code, Codex CLI, and Gemini CLI to guide code generation toward accessibility best practices. Skills cover APG widget patterns (accordions, comboboxes, dialogs, tabs), foundations like focus management and form accessibility, testing strategies, content guidance, and cognitive design considerations.

Use cases

  • Building interactive components: Get ARIA patterns right—knowing when to use native HTML vs ARIA roles
  • Auditing existing code: Run automated scanning and interpret results with axe-core, pa11y, and Lighthouse
  • Content teams: Write alt text, link labels, and error messages that work for all users
  • Avoiding hostile patterns: Detect and prevent carousels, infinite scroll, and other UX patterns that harm disabled users

Who benefits

Product designers, developers, content creators, and QA practitioners who want accessibility built in rather than bolted on. Teams serious about WCAG 2.2 compliance and inclusive design.

Frequently asked questions

How do I install the web accessibility plugin?
Add the marketplace with `/plugin marketplace add xrnavigation/agent-skills`, then install with `/plugin install a11y@agent-skills`. Alternatively, install directly with `/plugin install xrnavigation/web-a11y-plugin`.
What does the accessibility plugin actually prevent?
It stops LLMs from over-using ARIA, skipping keyboard interaction, ignoring focus management, and generating markup that fails screen readers. Every skill includes cited references so guidance is based on standards, not hallucinations.
Does the plugin work with Gemini or just Claude?
The plugin works with Claude Code, Codex CLI, and Gemini CLI. It follows the open Agent Skills standard so it's compatible across multiple AI platforms.
What's the difference between native HTML and ARIA?
The first rule of ARIA is: use native HTML first. Native elements like `<button>`, `<dialog>`, and `<details>` already have accessibility built in. ARIA is a fallback for complex patterns that HTML can't express. The plugin teaches this distinction.
Can the plugin help with alt text and link labels?
Yes. The plugin includes skills for accessible content writing, including a W3C decision tree for alt text (decorative vs informative vs functional), link text guidance, and error message clarity.
How do I audit my code for accessibility issues?
The `a11y-audit` skill guides you through automated scanning with axe-core, pa11y, and Lighthouse. The `testing-strategy` skill helps you decide what to test automatically vs manually vs with assistive technology.
What are hostile patterns and why should I avoid them?
Hostile patterns are UX features that harm disabled users—carousels, infinite scroll, hover-only interactions, auto-play, and CAPTCHAs. The plugin detects these and prevents recommendations for accessibility overlays (accessiBe, UserWay), which mask problems instead of solving them.
Does the plugin cover cognitive accessibility?
Yes. The plugin includes cognitive accessibility skills covering error handling, consistent navigation, timeout management, progress indicators, and neurodivergent user experience—explaining why design decisions like timeouts cause real distress.

Glossary

ARIA (Accessible Rich Internet Applications)
A set of attributes that add accessibility information to HTML. Used when native HTML can't express complex interactions. The first rule: use native HTML before ARIA.
APG (ARIA Authoring Practices Guide)
WAI's official guide for implementing ARIA patterns correctly. Covers 23+ widget patterns like tabs, comboboxes, and menus with tested keyboard and screen reader behavior.
WCAG 2.2 (Web Content Accessibility Guidelines)
W3C's international standard for web accessibility. Organized by four principles: Perceivable, Operable, Understandable, and Robust (POUR). Levels: A, AA, AAA.
Focus management
Controlling where keyboard focus lands during interactions. Includes focus trapping in modals, restoration after closing, and skip navigation links.
Assistive technology (AT)
Software or hardware that helps people with disabilities interact with content—screen readers, voice input, eye trackers, switch controls.

More in Accessibility

All →
Accessibility

A&T Claude Skills

Reusable Claude Code skills for accessibility audits, WCAG compliance checking, and web development workflows

automateandtweak
Accessibility

a11y-skills

Claude Skills for accessibility auditing, code review, and WCAG 2.2 compliance across web, mobile, and documents.

joedevon