accessibility_tester — Claude Code subagent: audit and setup
accessibility_tester is a Claude Code subagent that reviews interface evidence for accessibility requirements. It covers keyboard use, focus, semantics, contrast, and interaction.
no license ★ 776 updated 2026-11-12
.claude/agents/accessibility_tester.mdWhat accessibility_tester does
The accessibility_tester subagent examines supplied interface material against accessibility requirements related to WCAG, assistive technology, keyboard use, visual presentation, and interaction. It can work from an audit request plus markup, components, screenshots, browser output, design tokens, or user-flow notes.
It returns a Markdown report with the review scope, assumptions, evidence, and areas that were not tested. Each finding includes affected users, observed behavior, severity, reproduction steps, a fix direction, and a way to verify the result. Automated signals, code-review observations, and manual checks stay separate. Incomplete evidence does not support a WCAG conformance claim.
What it helps with
- check keyboard navigation and focus behavior
- spot semantic and form-access issues
- review contrast, media, and changing content
- turn findings into reproducible fixes and verification tests
Example prompts for the agent
- Audit the interface for accessibility using the markup and screenshots in
ui_evidence. - Review keyboard navigation, focus, forms, and dynamic states across this user flow.
- Write a Markdown report that separates automated signals, code-review findings, and manual checks, with reproduction steps.
How to install accessibility_tester
Manually: put the files in place
.claude/agents/accessibility_tester.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/accessibility_tester.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/accessibility_tester.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about accessibility_tester
How do I install accessibility_tester in Claude Code?
Place the subagent file at .claude/agents/accessibility_tester.md.
What does accessibility_tester do?
It reviews supplied interface evidence against accessibility requirements and produces a Markdown report with findings, user impact, reproduction steps, remediation guidance, and verification tests.
What evidence can accessibility_tester review?
It can use markup, components, screenshots, browser results, design tokens, and documentation of a user flow.