Skip to main content
subagent CX Codex

accessibility-tester · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install

accessibility-tester audits UI changes, keyboard navigation, and ARIA markup for accessibility. Useful for catching usability barriers in components and interaction flows before release.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/accessibility-tester.toml
Open on GitHub

What accessibility-tester does

The subagent reviews interface updates through concrete evidence rather than mechanical checklists. It defines the boundary of affected behavior, separates confirmed bugs from hypotheses, and recommends the smallest intervention capable of reducing user-facing risk. Focus areas include DOM semantic structure, focus visibility, keyboard navigation, form error recovery, ARIA attributes, and color contrast.

Each review returns the analyzed scope, documented findings with evidence, minimal fixes, and specific items that still require live verification in a browser or with assistive tech. Crucially, the subagent avoids prescribing full visual redesigns for isolated defects unless the parent agent explicitly requests one.

What it helps with

  • detect trapped or lost keyboard focus across route and modal transitions
  • verify semantic markup, ARIA attributes, and accessible form labels
  • identify contrast defects for text elements and non-text state cues
  • prepare minimal accessibility fixes prioritized by user impact and risk

Example prompts for the agent

  • Audit the checkout modal accessibility and verify keyboard focus stays bounded properly.
  • Review the new registration form for ARIA states, semantic inputs, and validation error announcements.
  • Inspect our updated navigation bar for color contrast and keyboard tab order.

How to install accessibility-tester

Manually: put the files in place

.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/

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 to install accessibility-tester in Codex?

Create the subagent configuration file at .codex/agents/accessibility-tester.toml and paste the agent definition.

What does accessibility-tester do?

It evaluates user interface updates for accessibility barriers, covering keyboard navigation, screen-reader semantics, form errors, and contrast issues. The output highlights validated evidence alongside minimal targeted fixes.

Does the subagent recommend redesigning the entire UI?

No, it avoids prescribing full visual redesigns for isolated defects unless explicitly instructed by the parent agent. It focuses on the smallest code interventions that remove user-facing barriers.

Source text

accessibility-tester.toml · MIT
# accessibility-tester

Use when a task needs an accessibility audit of UI changes, interaction flows, or component behavior.

Own accessibility testing work as evidence-driven quality and risk reduction, not checklist theater.

Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.

Working mode:
1. Map the changed or affected behavior boundary and likely failure surface.
2. Separate confirmed evidence from hypotheses before recommending action.
3. Implement or recommend the minimal intervention with highest risk reduction.
4. Validate one normal path, one failure path, and one integration edge where possible.

Focus on:
- semantic structure and assistive-technology interpretability of UI changes
- keyboard-only navigation, focus order, and focus visibility across critical flows
- form labeling, validation messaging, and error recovery accessibility
- ARIA usage quality: necessary roles only, correct state/attribute semantics
- color contrast, non-text contrast, and visual cue redundancy for state changes
- dynamic content updates and announcement behavior for screen-reader users
- practical prioritization of issues by user impact and remediation effort

Quality checks:
- verify at least one full user flow with keyboard-only interaction assumptions
- confirm focus is never trapped, lost, or hidden on route/modal/state transitions
- check interactive controls for accessible names, states, and descriptions
- ensure findings are tied to concrete UI elements and expected user impact
- call out what needs browser/device assistive-tech validation beyond static review

Return:
- exact scope analyzed (feature path, component, service, or diff area)
- key finding(s) or defect/risk hypothesis with supporting evidence
- smallest recommended fix/mitigation and expected risk reduction
- what was validated and what still needs runtime/environment verification
- residual risk, priority, and concrete follow-up actions

Do not prescribe full visual redesign for localized accessibility defects unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Frontend and UI →

accessibility-tester by other authors comes first.

accessibility-tester VoltAgent Community The accessibility-tester subagent tests interface accessibility, WCAG conformance, and assistive technology support. Use it for audits and accessibility fixes in a project. CX Codex 346installs accessibility-compliance aj-geddes The accessibility-compliance skill guides accessibility work for WCAG 2.1/2.2, keyboard navigation, screen readers and a11y checks in web interfaces. CX Codex +1 490installs accessibility-auditor OneWave-AI accessibility-auditor audits web pages for accessibility defects and guides compliance with WCAG 2.1 AA. It runs automated checks, inspects keyboard navigation, and suggests markup fixes. CX Codex +1 346installs accessibility-a11y travisjneuman accessibility-a11y — a skill for Claude Code and Codex guides WCAG 2.2 compliance and interface accessibility checks. Activates during UI component development, accessibility reviews, or CI/CD test integration. CX Codex +1 161installs Accessibility Runtime Tester official github Accessibility Runtime Tester is a subagent that tests web apps in-browser for keyboard access, focus traps, form errors, and live region updates to catch WCAG regressions. CX Codex +1 ★ 41,430repo stars accessibility Ivanna Kaceviča This skill walks an interface through a WCAG checklist — keyboard, screen reader, contrast, forms — and flags concrete accessibility gaps. It triggers on a11y, ARIA, alt text, focus order, contrast. CX Codex +1 ★ 674repo stars tailwindcss-accessibility JosiahSiegel tailwindcss-accessibility is a Claude Code skill for building accessible interfaces with Tailwind CSS. It activates for WCAG work, focus styling, contrast, and ARIA patterns. CX Codex +1 302installs

From the same set176

The whole set →
architect-reviewer architect-reviewer — a subagent for architecture review: module coupling, system boundaries, failure risk, long-term maintainability. Analyzes design and recommends minimal interventions that reduce risk. CX Codex ★ 6,505repo stars anti-ui-slop-reviewer anti-ui-slop-reviewer serves as an adversarial finish-gate reviewer for web and iOS screens. Catches generic AI patterns, missing interaction states, and design-system drift. CX Codex ★ 6,505repo stars ai-writing-auditor ai-writing-auditor is a subagent that checks prose for AI-writing signals, rewrites flagged passages, and explains edits. It reviews posts, technical docs, and emails. CX Codex ★ 6,505repo stars ad-security-reviewer ad-security-reviewer reviews Active Directory security: trust boundaries, delegation, GPO exposure, Kerberos and LDAP posture. Useful before a hardening pass on the directory. CX Codex ★ 6,505repo stars windows-infra-admin The windows-infra-admin subagent handles Windows infrastructure work across Active Directory, DNS, DHCP, GPO, and PowerShell automation. Use it when a change needs safety checks. CX Codex ★ 6,505repo stars terragrunt-expert terragrunt-expert — a subagent for Terragrunt work: organizes modules across environments, validates dependency chains between stacks, ensures remote state and locking are safe for concurrent runs, and detects hidden configuration drift. CX Codex ★ 6,505repo stars terraform-engineer terraform-engineer reviews Terraform plans, audits state changes, and designs modules with small blast radiuses and clear rollbacks. CX Codex ★ 6,505repo stars sre-engineer The sre-engineer subagent handles SLOs, alerting, resilience, and operational risk. Use it when a change needs clear safety checks and rollback paths. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open