analyze-accessibility

analyze-accessibility is a command for Claude Code from Matt-Dionis/claude-code-configs. It costs 5 tokens per session (975 once invoked), scanned A, original, MIT.

A command that checks interface components for accessibility problems and produces a report with suggested fixes. Accessibility means making software usable with assistive technology and keyboards.

In plain words
What is it for?
Use it to audit components against common WCAG 2.1 AA expectations and identify specific accessibility improvements.
Why use it?
It can reveal issues with semantics, labels, keyboard navigation, focus indicators, forms, images, and ARIA attributes before users encounter them.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to audit components against common WCAG 2.1 AA expectations and identify specific accessibility improvements.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/matt-dionis/claude-code-configs/analyze-accessibility
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/Matt-Dionis/claude-code-configs

Made for: Claude Code.

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 analyze-accessibility

README.md
[![agentmods](https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/analyze-accessibility/github.svg)](https://agentmods.dev/commands/matt-dionis/claude-code-configs/analyze-accessibility)
Your own site
<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/analyze-accessibility"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/analyze-accessibility/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 analyze-accessibility

Your own site · 80×15
<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/analyze-accessibility"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/analyze-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 975 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.00005 $0.00975
Opus 5.5 $0.00002 $0.00390
Sonnet 5.5 $0.00001 $0.00195
Haiku 4.5 $0.00001 $0.00097

Measured 1mo ago against content hash cc7cec9a5566, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyze-accessibility 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 1mo 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.

configurations/ui/shadcn/.claude/commands/analyze-accessibility.md · 172 lines

How it starts

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

Analyze components for accessibility issues and provide recommendations.

Instructions

  1. If no path specified, analyze all components in components/ui/
  2. Check for common accessibility issues
  3. Verify WCAG 2.1 AA compliance
  4. Provide specific recommendations for fixes
  5. Generate accessibility report

Checks to Perform

HTML Semantics

  • Proper heading hierarchy (h1 → h2 → h3)
  • Semantic HTML elements used appropriately
  • Lists use ul/ol with li elements
  • Buttons vs links used correctly

ARIA Implementation

  • Required ARIA attributes present
  • ARIA roles used appropriately
  • aria-label or aria-labelledby for interactive elements
  • aria-describedby for additional context
  • Live regions for dynamic content

Keyboard Navigation

  • All interactive elements keyboard accessible
  • Tab order is logical
  • Focus indicators visible
  • Escape key closes modals/popups
  • Arrow keys work in menus/lists

Forms

  • All inputs have associated labels
  • Required fields marked with aria-required
  • Error messages associated with inputs
  • Form validation accessible

Images & Media

  • Images have alt text
  • Decorative images have empty alt=""
  • Videos have captions/transcripts
  • Audio has transcripts

Color & Contrast

  • Text contrast ratio ≥ 4.5:1 (normal text)
  • Text contrast ratio ≥ 3:1 (large text)
  • Focus indicators have sufficient contrast
  • Information not conveyed by color alone

Motion & Animation

  • Respects prefers-reduced-motion
  • Animations can be paused/stopped
  • No flashing content (seizure risk)

Automated Testing

Install and run automated tools:

# Install testing dependencies
npm install -D @axe-core/react jest-axe

# Run axe-core tests
npx axe <url>

# Use React Testing Library
npm test -- --coverage

Manual Testing Checklist

  1. Keyboard Only Navigation
    • Disconnect mouse
    • Navigate using Tab, Shift+Tab, Enter, Space, Arrows, Escape
    • Verify all features accessible

Read the full file on GitHub · 172 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. 1mo ago First seen · 172 lines · 5 tokens per session scan A cc7cec9a5566

Subscribe to this mod's changes

analyze-accessibility is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 975 once invoked, about $0.0000 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-09-03.