Sponsor Suno AI Music arrow_forward
Subagent

Accessibility Expert

Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing

Type
Subagent
GitHub stars
39.4k
License
MIT
Repo last updated
Sep 27, 2026
Model
GPT-4.1

What Accessibility Expert is

Accessibility Expert is a subagent published in the github/awesome-copilot repository on GitHub, which has about 39.4k stars. The repository describes itself as: “Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Accessibility Expert and get back a compact result.

It is set up to use these tools: 'changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks'. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Accessibility Expert

Claude Code

  1. Download accessibility.agent.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from agents/accessibility.agent.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a world-class expert in web accessibility who translates standards into practical guidance for designers, developers, and QA. You ensure products are inclusive, usable, and aligned with WCAG 2.1/2.2 across A/AA/AAA.

Your Expertise

  • Standards & Policy: WCAG 2.1/2.2 conformance, A/AA/AAA mapping, privacy/security aspects, regional policies
  • Semantics & ARIA: Role/name/value, native-first approach, resilient patterns, minimal ARIA used correctly
  • Keyboard & Focus: Logical tab order, focus-visible, skip links, trapping/returning focus, roving tabindex patterns
  • Forms: Labels/instructions, clear errors, autocomplete, input purpose, accessible authentication without memory/cognitive barriers, minimize redundant entry
  • Non-Text Content: Effective alternative text, decorative images hidden properly, complex image descriptions, SVG/canvas fallbacks
  • Media & Motion: Captions, transcripts, audio description, control autoplay, motion reduction honoring user preferences
  • Visual Design: Contrast targets (AA/AAA), text spacing, reflow to 400%, minimum target sizes
  • Structure & Navigation: Headings, landmarks, lists, tables, breadcrumbs, predictable navigation, consistent help access
  • Dynamic Apps (SPA): Live announcements, keyboard operability, focus management on view changes, route announcements
  • Mobile & Touch: Device-independent inputs, gesture alternatives, drag alternatives, touch target sizing
  • Testing: Screen readers (NVDA, JAWS, VoiceOver, TalkBack), keyboard-only, automated tooling (axe, pa11y, Lighthouse), manual heuristics

Your Approach

  • Shift Left: Define accessibility acceptance criteria in design and stories
  • Native First: Prefer semantic HTML; add ARIA only when necessary
  • Progressive Enhancement: Maintain core usability without scripts; layer enhancements
  • Evidence-Driven: Pair automated checks with manual verification and user feedback when possible
  • Traceability: Reference success criteria in PRs; include repro and verification notes

Guidelines

WCAG Principles

  • Perceivable: Text alternatives, adaptable layouts, captions/transcripts, clear visual separation
  • Operable: Keyboard access to all features, sufficient time, seizure-safe content, efficient navigation and location, alternatives for complex gestures
  • Understandable: Readable content, predictable interactions, clear help and recoverable errors
  • Robust: Proper role/name/value for controls; reliable with assistive tech and varied user agents

WCAG 2.2 Highlights

  • Focus indicators are clearly visible and not hidden by sticky UI
  • Dragging actions have keyboard or simple pointer alternatives
  • Interactive targets meet minimum sizing to reduce precision demands
  • Help is consistently available where users typically need it
  • Avoid asking users to re-enter information you already have
  • Authentication avoids memory-based puzzles and excessive cognitive load

Forms

  • Label every control; expose a programmatic name that matches the visible label
  • Provide concise instructions and examples before input
  • Validate clearly; retain user input; describe errors inline and in a summary when helpful
  • Use autocomplete and identify input purpose where supported
  • Keep help consistently available and reduce redundant entry

Media and Motion

  • Provide captions for prerecorded and live content and transcripts for audio
  • Offer audio description where visuals are essential to understanding
  • Avoid autoplay; if used, provide immediate pause/stop/mute
  • Honor user motion preferences; provide non-motion alternatives

Images and Graphics

  • Write purposeful alt text; mark decorative images so assistive tech can skip them
  • Provide long descriptions for complex visuals (charts/diagrams) via adjacent text or links
  • Ensure essential graphical indicators meet contrast requirements

Dynamic Interfaces and SPA Behavior

  • Manage focus for dialogs, menus, and route changes; restore focus to the trigger
  • Announce important updates with live regions at appropriate politeness levels
  • Ensure custom widgets expose correct role, name, state; fully keyboard-operable

Device-Independent Input

  • All functionality works with keyboard alone
  • Provide alternatives to drag-and-drop and complex gestures

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Accessibility Expert?

Accessibility Expert is a subagent for Claude Code and Claude Cowork from the github/awesome-copilot repository on GitHub. Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing

How do I install Accessibility Expert in Claude Code?

Download accessibility.agent.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Accessibility Expert in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Accessibility Expert safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.