What is audit-accessibility?

A checklist for reviewing React components for accessibility, meaning whether people with disabilities can use them with screen readers, keyboards, high-contrast settings, or other assistive tools.

Use it to audit component markup, ARIA attributes, headings, forms, dialogs, tabs, selects, focus handling, motion, contrast, and forced-colors support.

It helps find missing labels, incorrect keyboard behavior, poor contrast, weak focus indicators, and other barriers before release.

audit-accessibility — Skill for Claude Code by annondeveloper/ui-kit

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.

Any agent

npx skills add annondeveloper/ui-kit --skill audit-accessibility

Clone the repo

git clone --depth 1 https://github.com/annondeveloper/ui-kit

Made for: Claude Code.

Or install ui-kit, the plugin that ships this one along with the rest of its 5 skills, 2 agents, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/annondeveloper/ui-kit/audit-accessibility/github.svg)](https://agentmods.dev/skills/annondeveloper/ui-kit/audit-accessibility)

Your own site

<a href="https://agentmods.dev/skills/annondeveloper/ui-kit/audit-accessibility"><img src="https://agentmods.dev/badge/skills/annondeveloper/ui-kit/audit-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/annondeveloper/ui-kit/audit-accessibility"><img src="https://agentmods.dev/badge/skills/annondeveloper/ui-kit/audit-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 504 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.

Model	Per session	Once invoked
Fable 5.1	$0.00058	$0.00504
Opus 5.5	$0.00023	$0.00202
Sonnet 5.5	$0.00012	$0.00101
Haiku 4.5	$0.00006	$0.00050

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

Security

Grade A, and why

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

plugins/claude-code/skills/audit-accessibility/SKILL.md · 51 lines

What it actually says

UI Kit Accessibility Audit

Audit the following code for accessibility: $ARGUMENTS

Checklist

Semantic HTML

Uses native HTML elements where possible (<button>, <dialog>, <details>, <select>)
Headings follow logical hierarchy (h1 > h2 > h3)
Lists use <ul>/<ol> for groups of items
Forms use <label> with htmlFor association

ARIA

Interactive elements have accessible names (aria-label, aria-labelledby, visible text)
Dynamic content uses aria-live regions
Custom widgets follow WAI-ARIA APG keyboard patterns
aria-expanded, aria-selected, aria-checked used correctly
Decorative elements have aria-hidden="true"

Keyboard

All interactive elements are focusable
Tab order follows visual order
Escape closes overlays (Dialog, Drawer, Popover)
Arrow keys navigate within composite widgets (Tabs, Select, RadioGroup)
Enter/Space activates buttons and toggles

Visual

Text contrast ≥ 4.5:1 (WCAG AA)
UI element contrast ≥ 3:1
Focus indicators visible (2px solid outline, offset)
No information conveyed by color alone
@media (forced-colors: active) support

Motion

prefers-reduced-motion respected
Motion level cascade: OS > prop > CSS > provider > default
No auto-playing animations without user control
motion={0} disables all animation

Touch

Touch targets ≥ 44px (@media (pointer: coarse))
No hover-only interactions
-webkit-tap-highlight-color: transparent set

Report findings with severity (Critical/Warning/Info) and specific fix recommendations using UI Kit components and conventions.

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.

1mo ago First seen · 51 lines · 58 tokens per session scan A 8b63784cc25f

Subscribe to this mod's changes

audit-accessibility is a skill published in the GitHub repository annondeveloper/ui-kit (0 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 504 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.

Frontend cloudflare-workers mcp mcp-server

add-provider

Add a new storage or service provider to the core package. Use when implementing a new backend for StorageService (e.g., a new database) or a new service provider (e.g., a new LLM backend).

cyanheads/mcp-ts-core · 47 tokens

add-export

Add a new subpath export to the @cyanheads/mcp-ts-core package. Use when creating a new public API surface that consumers import from a dedicated subpath (e.g., @cyanheads/mcp-ts-core/newutil).

cyanheads/mcp-ts-core · 50 tokens

mcp-migration

Diagnose and carry out the migration of an MCP server to the 2026-07-28 specification — the revision that made the transport stateless, formalized OAuth 2.1, and deprecated the logging, sampling, and roots capabilities. Use this skill whenever someone mentions migrating, upgrading, or checking an MCP server against…

AlpayC/mcp-migration-check · 162 tokens

gw1-build-assistant

Use when the user asks about Guild Wars 1 (the original 2005 game, not GW2) — designing or reviewing skill bars, decoding or producing template codes (strings like "OgCjkurIrSuXaXPXBYihygvlYcA"), hero team composition, skill lookups or comparisons, or pasting a paw-ned2 team blob ("pwnd0001..."). Use the gw1-mcp tools…

Graphmaxer/gw1-mcp · 127 tokens

design-mcp-server

Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.

cyanheads/mcp-ts-core · 62 tokens

add-tool

Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.

cyanheads/mcp-ts-core · 35 tokens