# accessibility_tester

accessibility_tester is a Claude Code subagent that reviews interface evidence for accessibility requirements. It covers keyboard use, focus, semantics, contrast, and interaction.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/accessibility_tester.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/agenticorglab-accessibility-tester

## What it 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.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/accessibility_tester.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/accessibility_tester.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/accessibility_tester.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/accessibility_tester.md

## When to use it
- 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
- 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.

## Similar
- [accessibility-tester](https://affpapa.org/en/nevibecode/agents/accessibility-tester.md) — subagent · 346 installs
- [Accessibility Runtime Tester](https://affpapa.org/en/nevibecode/agents/accessibility-runtime-tester.md) — subagent · ★ 41430 repo stars
- [visual-regression-tester](https://affpapa.org/en/nevibecode/skills/visual-regression-tester.md) — skill · 351 installs
- [accessibility](https://affpapa.org/en/nevibecode/skills/web-quality-skills-accessibility.md) — skill · 72600 installs
- [gem-browser-tester](https://affpapa.org/en/nevibecode/agents/gem-browser-tester.md) — subagent · ★ 41430 repo stars
- [ui-ux-tester](https://affpapa.org/en/nevibecode/agents/ui-ux-tester.md) — subagent · ★ 26718 repo stars

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
