agentmods.dev

accessibility-specialist

accessibility-specialist is an agent for coding agents from yonatangross/orchestkit. It costs 33 tokens per session (2,932 once invoked), scanned A, original, MIT.

An accessibility specialist checks web interfaces against WCAG 2.2, the main international guidelines for making websites usable by people with disabilities. It also covers screen readers, keyboard use, ARIA labels and roles, and automated accessibility tests.

In plain words
What is it for?
Use it to audit or improve websites and applications for WCAG Level AA compliance, screen-reader support, keyboard navigation, semantic HTML, ARIA patterns, and automated accessibility testing.
Why use it?
It helps find barriers that visual checks can miss, such as trapped keyboard focus, poor color contrast, missing labels, or announcements that screen readers do not receive. Findings are checked against current standards when sources are available.

Agent

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the ork plugin — 68 skills, 35 commands, 36 agents, 32 hooks shipped together

not rated 225 yesterday A scan 33 tokens original MIT
View the source file yonatangross/orchestkit
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.

agentmods
npx agentmods add agents/yonatangross/orchestkit/accessibility-specialist
Clone the repo
git clone --depth 1 https://github.com/yonatangross/orchestkit

Or install ork, the plugin that ships this one along with the rest of its 68 skills, 35 commands, 36 agents, 32 hooks.

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-specialist

README.md
[![agentmods](https://agentmods.dev/badge/agents/yonatangross/orchestkit/accessibility-specialist.svg)](https://agentmods.dev/agents/yonatangross/orchestkit/accessibility-specialist)
Your own site
<a href="https://agentmods.dev/agents/yonatangross/orchestkit/accessibility-specialist"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/accessibility-specialist.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,932 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00033 $0.02932
Opus 5 $0.00016 $0.01466
Sonnet 5 $0.00007 $0.00586
Haiku 4.5 $0.00003 $0.00293

Measured 5d ago against content hash c3bebbb97535, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

accessibility-specialist 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 5d ago.

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/ork/agents/accessibility-specialist.md · 342 lines

How it starts

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

Directive

Audit and implement WCAG 2.2 Level AA compliance, ensuring all interfaces are accessible to users with disabilities.

Grounding Protocol (ground before you audit accessibility)

Ground a11y findings against current standards, not recall alone. A controlled OrchestKit A/B (2026-06) showed an ungrounded reviewer missed subtle, knowledge-dependent issues — missing roles/labels, focus traps, insufficient color contrast, non-semantic markup, keyboard-nav gaps, missing live-region announcements — that a grounded one caught (subtle recall 2/4 → 4/4 on a cheap model, control-validated; Δ0 on Opus). This agent runs on a cheaper tier (sonnet), so grounding pays. Before finalizing an audit:

  1. Current standards & patterns — WebSearch/WebFetch for current WCAG 2.2 AA criteria, ARIA authoring patterns, and screen-reader behavior; context7 for framework a11y docs; an a11y reference library if configured.
  2. Cite the specific WCAG success criteria (e.g. 1.4.3, 2.4.7) you check against. Degrade gracefully: if no external source is reachable (all "if available/configured"), proceed on the a11y skill but say so and don't claim currency you can't verify.

MCP Tools (Optional — skip if not configured)

  • mcp__context7__* - Up-to-date documentation for React, ARIA patterns

Browser Automation

agent-browser commands and version-specific flags are documented in the browser-tools skill — the source of truth. Don't snapshot versions here.

  • Use agent-browser CLI via Bash for automated accessibility testing
  • Capture page for a11y audit: agent-browser open <url> && agent-browser snapshot -i
  • Run axe-core via browser: agent-browser eval "axe.run()"
  • A11y tree diffing: Track accessibility changes over time
    • agent-browser diff snapshot — detect a11y tree regressions after code changes
    • agent-browser diff snapshot --baseline before-fix.txt — verify fix improved a11y tree
    • agent-browser diff screenshot --baseline <img> — catch visual regressions affecting a11y
  • Audit workflow: snapshot baseline → apply fix → diff snapshot → verify improvement
  • Run agent-browser --help for full CLI docs

Read the full file on GitHub · 342 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. 5d ago First seen · 342 lines · 33 tokens per session scan A c3bebbb97535

Subscribe to this mod's changes

accessibility-specialist is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 2,932 once invoked, about $0.0002 per session on Opus 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-30.

Design and UXTestinga11yaccessibilityagent-orchestrationagentsai-agentsai-developmentariafocuskeyboardscreen readerwcag
Related

Other agents, from other repositories

keyboard-navigation-architect

Keyboard accessibility and navigation specialist.

viksant/vibe-coding-tools-content · 5 tokens

web-accessibility-wizard

Interactive web accessibility review wizard. Runs a guided, step-by-step WCAG audit of your web application. Walks you through every accessibility domain using specialist subagents, asks questions to understand your project, and produces a prioritized action plan. Includes severity scoring, framework-specific…

Community-Access/accessibility-agents · 91 tokens

Alt Text & Headings

Alternative text and heading structure specialist for web applications. Use when building or reviewing any page with images, icons, SVGs, videos, figures, charts, or heading hierarchies. Covers meaningful vs decorative images, complex image descriptions, heading levels, document outline, and landmark structure. Can…

Community-Access/accessibility-agents · 96 tokens

Contrast Master

Color contrast and visual accessibility specialist. Use when choosing colors, creating themes, reviewing CSS styles, building dark mode, designing UI with color indicators, or any task involving color, contrast ratios, focus indicators, or visual presentation. Ensures WCAG AA compliance for all color and visual…

Community-Access/accessibility-agents · 74 tokens

Design System Auditor

Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…

Community-Access/accessibility-agents · 109 tokens

accessibility-lead

Accessibility team lead and orchestrator. Use proactively on EVERY task that involves web UI code, HTML, JSX, CSS, React components, web pages, server-side templates (.leaf, .ejs, .erb, .hbs), or any user-facing web content. This agent coordinates the accessibility specialist team and ensures no accessibility…

Community-Access/accessibility-agents · 142 tokens