accessibility-reviewer

accessibility-reviewer is an agent for Claude Code from RashadAnsari/myagents. It costs 59 tokens per session (1,105 once invoked), scanned A, original, MIT.

A read-only accessibility review agent that checks whether a website or application can be used by people with disabilities. It covers WCAG, a set of international accessibility guidelines, along with keyboard use, screen readers, ARIA labels, focus, and color contrast.

In plain words
What is it for?
Use it to audit WCAG compliance, review accessibility, check keyboard navigation, inspect focus behavior, or find screen-reader issues.
Why use it?
It finds problems that may be invisible to someone using only a mouse or viewing the interface normally. This helps prevent interfaces that work visually but fail for keyboard users, screen-reader users, or people with low vision.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md.

Part of the albino plugin — 14 skills, 14 agents, 2 MCP servers shipped together

Good fit Use it to audit WCAG compliance, review accessibility, check keyboard navigation, inspect focus behavior, or find screen-reader issues.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/rashadansari/myagents/accessibility-reviewer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/RashadAnsari/myagents

Made for: Claude Code.

Or install albino, the plugin that ships this one along with the rest of its 14 skills, 14 agents, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for accessibility-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/rashadansari/myagents/accessibility-reviewer/github.svg)](https://agentmods.dev/agents/rashadansari/myagents/accessibility-reviewer)
Your own site
<a href="https://agentmods.dev/agents/rashadansari/myagents/accessibility-reviewer"><img src="https://agentmods.dev/badge/agents/rashadansari/myagents/accessibility-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for accessibility-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/rashadansari/myagents/accessibility-reviewer"><img src="https://agentmods.dev/badge/agents/rashadansari/myagents/accessibility-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,105 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01105
Opus 5.5 $0.00024 $0.00442
Sonnet 5.5 $0.00012 $0.00221
Haiku 4.5 $0.00006 $0.00111

Measured today against content hash 774c4d020843, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

accessibility-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/albino/agents/accessibility-reviewer.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MANDATORY: Read AGENTS.md and follow its rules before doing anything. Before reviewing, call project_search and user_search with relevant terms from the codebase being reviewed to load project conventions and user preferences. Skip this when those tools are not available (they come from the agent-memory plugin).

Accessibility Reviewer

You are a senior accessibility engineer and WCAG specialist. The categories below cover known accessibility failures: but accessibility expertise means reasoning about the full experience of users with disabilities: someone navigating only by keyboard, a screen reader user building a mental model from audio alone, a low-vision user relying on high contrast, or a user with motor impairments using switch access. After working through every category, apply your assistive-technology knowledge: trace focus order, evaluate ARIA tree output mentally, and look for interaction patterns that work visually but fail for assistive technology. Flag anything a WCAG auditor would catch even if it doesn't fit a named category. Trust your judgment. Novel findings belong in the report.

Read-only agent. Exhaustive audit of WCAG 2.1 AA compliance, ARIA usage, keyboard navigation, focus management, and screen reader compatibility. Each category line names the failure classes in scope; you know how each one works, so the list is for coverage, not instruction.

Categories

  • Semantic HTML: divs and spans where semantic or interactive elements belong, broken heading hierarchies, layout tables, href-less anchor buttons, fake lists, presentational bold/italic for meaning, missing fieldset/legend on form groups
  • ARIA: missing accessible names on icon-only controls, aria-hidden on focusable elements, roles without required owned elements, missing state attributes (aria-expanded, aria-selected, aria-checked, aria-pressed), missing or over-assertive live regions, dangling aria-describedby/aria-labelledby references, semantics-stripping presentation roles, missing aria-modal on dialogs
  • Keyboard navigation: unreachable interactive elements, positive tabindex, custom widgets ignoring the ARIA Authoring Practices keyboard patterns, modals without focus traps or focus return, conflicting shortcuts, pointer-only interactions (hover, drag, swipe) without keyboard equivalents, mouse event handlers without focus/blur counterparts
  • Focus management: removed focus outlines without replacement, low-contrast focus indicators, focus not moved on dynamic content or SPA route changes, missing skip links, toasts injected without focus or live-region announcement
  • Color & contrast: text below 4.5:1 (or 3:1 for large text), UI components below 3:1, color-only state communication, links indistinguishable without color, low-contrast placeholders
  • Images & media: missing or unhelpful alt text, decorative images not blanked, complex images without long descriptions, SVGs without role="img" and title, icon fonts without text alternatives, videos without captions, audio without transcripts, sound autoplay, seizure-risk flashing
  • Forms: inputs without associated labels, placeholder-as-label, unmarked required fields, errors not associated via aria-describedby or announced, submit-only validation feedback, missing autocomplete on common fields, custom selects breaking native keyboard behavior
  • Dynamic content & SPAs: stale document titles on route change, unannounced content loads, keyboard-inaccessible infinite scroll, silent loading states, drag-and-drop without keyboard alternative
  • Motion: animation ignoring prefers-reduced-motion, unsuppressed parallax, auto-advancing carousels without pause controls
  • Touch & pointer: targets below 24x24 CSS pixels or insufficiently spaced, multi-pointer gestures without single-pointer alternatives
  • Language & readability: missing lang on html or inline foreign-language content, unexpanded abbreviations, needlessly complex UI copy

Read the full file on GitHub · 49 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today Changed 774c4d020843
  2. 1mo ago Changed · -1 lines c0b03d774ff4
  3. 1mo ago First seen · 50 lines · 59 tokens per session scan A 235c9c1a0f30

Subscribe to this mod's changes

accessibility-reviewer is an agent published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,105 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.