Borrowing it
Nothing to install: this file belongs to wri/wri-design-systems. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wri/wri-design-systems/main/.claude/skills/a11y-checker/SKILL.mdgit clone --depth 1 https://github.com/wri/wri-design-systemsWrote 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.
[](https://agentmods.dev/skills/wri/wri-design-systems/a11y-checker)<a href="https://agentmods.dev/skills/wri/wri-design-systems/a11y-checker"><img src="https://agentmods.dev/badge/skills/wri/wri-design-systems/a11y-checker/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.
<a href="https://agentmods.dev/skills/wri/wri-design-systems/a11y-checker"><img src="https://agentmods.dev/badge/skills/wri/wri-design-systems/a11y-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00050 | $0.01438 |
| Opus 5 | $0.00025 | $0.00719 |
| Sonnet 5 | $0.00010 | $0.00288 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
a11y-checker 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When running the accessibility checker on any codebase, follow this multi-tiered guide to ensure compliance with universal WCAG standards as well as library-specific rules.
1. Universal Accessibility Standards (Any Web Project)
Apply these rules to any kind of project (plain HTML, native React, or other UI libraries):
Accessible Names & Interactive Elements
- Discernible Text: Every clickable control (buttons, links, inputs) must have a discernible text label.
- Icon-Only Actions: If a button contains only an icon or image, it must receive an
aria-labeloraria-labelledbyattribute (e.g.,<button aria-label="Close dialog">or<IconButton aria-label="Delete item" />). - Images and SVGs:
- Standalone SVGs used as controls must have
role="img"and anaria-label. - Decorative icons or illustrations must have
aria-hidden="true"oralt=""so they are ignored by screen readers.
- Standalone SVGs used as controls must have
Forms & Input Controls
- Explicit Associations: Native HTML form controls must have a
<label>explicitly linked using thefor(orhtmlForin React) andidattributes. - Accessible Placeholders: A
placeholderis not an accessible label. A proper visible label oraria-labelmust always be provided. - Validation Signals: Error states must never rely on color changes alone. Set
aria-invalid="true"and programmatically link the input to its validation error message usingaria-describedby="error-message-id".
Layout & Landmark Structures
- Semantic HTML: Use correct semantic tags (
<header>,<nav>,<main>,<footer>,<aside>,<section>) instead of generic<div>wrappers. - Multiple Landmarks: If a page has multiple navigation regions, distinguish them using unique
aria-labelattributes (e.g.,<nav aria-label="Main navigation">and<nav aria-label="Footer navigation">).
Keyboard Navigation & Focus Management
- Focus Path: Every interactive element must be reachable using the
Tabkey. Custom non-interactive elements that trigger actions (e.g., a clickablediv) must havetabindex="0". - Keyboard Triggers: Custom interactive elements must handle
EnterandSpacekey presses using keydown/keyup event handlers. - Visible Focus: Never suppress the browser's default focus outlines (
outline: noneoroutline: 0) unless you are explicitly defining custom, highly-visible CSS focus indicator styles (e.g. using:focus-visible). - Overlay Focus Traps: Modals, slide-out panels, and dropdown menus must trap keyboard focus inside them while open, and must restore focus to the triggering element upon closure.
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 · 118 lines · 50 tokens per session scan A 76b3ba66cd15
a11y-checker is a skill published in the GitHub repository wri/wri-design-systems (3 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 1,438 once invoked, about $0.0003 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…