A frontend accessibility audit guide for WCAG, the international standard for making websites usable by people with disabilities. It checks semantic HTML, keyboard operation, focus, contrast, alternative text, forms, ARIA, screen readers, and reduced motion.

Use it while building or changing a web or React Native interface, or before shipping a screen. It helps check buttons and headings, tab order, focus rings, labels, error messages, color contrast, image descriptions, and motion settings.

It helps find barriers that can prevent keyboard users, screen-reader users, and people with low vision from using an interface. It gives a WCAG 2.1 AA baseline for reviewing user-facing screens.

a11y — Skill for Claude Code and Codex by byerlikaya

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 byerlikaya/claude-starter-kit --skill a11y

Clone the repo

git clone --depth 1 https://github.com/byerlikaya/claude-starter-kit

Made for: Claude Code, Codex.

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/byerlikaya/claude-starter-kit/a11y/github.svg)](https://agentmods.dev/skills/byerlikaya/claude-starter-kit/a11y)

Your own site

<a href="https://agentmods.dev/skills/byerlikaya/claude-starter-kit/a11y"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/a11y/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/byerlikaya/claude-starter-kit/a11y"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/a11y.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 806 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.00043	$0.00806
Opus 5	$0.00022	$0.00403
Sonnet 5	$0.00009	$0.00161
Haiku 4.5	$0.00004	$0.00081

Measured 11d ago against content hash 1a66062ee7ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

a11y 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 11d 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.

claude-starter/skills/a11y/SKILL.md · 47 lines

How it starts

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

Trigger phrases: "a11y", "accessibility", "WCAG", "screen reader", "keyboard navigation", "contrast", "ARIA", "keyboard only", "with a keyboard", "keyboard focus", "without a mouse", "focus ring", "tab order", "alt text", "color blind", "colour blind", "voiceover", "talkback", "reduced motion"

Goal: make the interface usable by everyone, including keyboard, screen reader, and low vision. Baseline target: WCAG 2.1 AA. Stack-agnostic (web/React/RN); do a web search when needed for framework-specific APIs.

Checklist

Semantic HTML: button/a/nav/main/h1..h6 correct; no div-buttons
Keyboard: every interaction reachable via Tab, sensible order, visible focus ring
Focus management: focus moves on modal/route change, focus trap correct
Contrast: text ≥ 4.5:1, large text ≥ 3:1
Alt text: alt on meaningful images; alt="" on decorative images
Forms: every input has a label; error message programmatically linked (aria-describedby)
ARIA: only when needed; wrong ARIA is worse than no ARIA; role/name/state correct
Motion/animation: respect prefers-reduced-motion
Language: <html lang> correct (coordinate with i18n)

How

Start with semantics — the right element solves 80%. Use button instead of role="button"+div.
Navigate with the keyboard — drop the mouse, run the whole flow with Tab/Shift-Tab/Enter/Escape; is focus visible and its order sensible.
Naming — does every interactive element have an accessible name (aria-label on visual-only icon buttons).
Contrast — check color pairs against the ratio; don't convey meaning by color alone (add an icon/text).
Dynamic content — notify the screen reader via a live region (aria-live); manage modal focus.
Automated + manual — tools like linters/axe are the baseline; but manual keyboard+reader testing is essential (tools don't catch 100%).

Read the full file on GitHub · 47 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.

11d ago First seen · 47 lines · 43 tokens per session scan A 1a66062ee7ca

Subscribe to this mod's changes

a11y is a skill published in the GitHub repository byerlikaya/claude-starter-kit (22 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 806 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.

Frontend agent-skills agents ai-agents anthropic automation boilerplate

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…

sangrokjung/claude-forge · 183 tokens

frontend-code-review

Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.

sangrokjung/claude-forge · 42 tokens

accessibility-a11y

WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.

travisjneuman/.claude · 26 tokens

flutter-development

Cross-platform development with Flutter and Dart for iOS, Android, Web, Desktop, and embedded. Use when building Flutter apps, implementing Material/Cupertino design, or optimizing Dart code.

travisjneuman/.claude · 41 tokens

electron-desktop

Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.

travisjneuman/.claude · 38 tokens

generic-react-ux-designer

Professional UI/UX design expertise for React applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design…

travisjneuman/.claude · 69 tokens