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.
npx skills add LeahyCC/claude-skills --skill wcag-accessibilitygit clone --depth 1 https://github.com/LeahyCC/claude-skillsWrote 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/leahycc/claude-skills/wcag-accessibility)<a href="https://agentmods.dev/skills/leahycc/claude-skills/wcag-accessibility"><img src="https://agentmods.dev/badge/skills/leahycc/claude-skills/wcag-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.
<a href="https://agentmods.dev/skills/leahycc/claude-skills/wcag-accessibility"><img src="https://agentmods.dev/badge/skills/leahycc/claude-skills/wcag-accessibility.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.00064 | $0.03779 |
| Opus 5 | $0.00032 | $0.01889 |
| Sonnet 5 | $0.00013 | $0.00756 |
| Haiku 4.5 | $0.00006 | $0.00378 |
Grade A, and why
wcag-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 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WCAG 2.2 AA Accessibility
Comprehensive accessibility guidance for web applications targeting WCAG 2.2 Level AA conformance.
Architecture Overview
[Component Authoring]
├── Semantic HTML (landmarks, headings, lists)
├── ARIA attributes (roles, states, properties)
├── Keyboard interaction (focus, tab order, shortcuts)
└── Visual design (contrast, spacing, motion)
↓
[Automated Testing]
├── axe-core / jest-axe (unit)
├── Lighthouse CI (integration)
└── pa11y (page-level)
↓
[Manual Testing]
├── Keyboard-only navigation
├── Screen reader walkthrough (VoiceOver, NVDA)
└── Zoom to 200% / reflow check
↓
[Continuous Compliance]
├── CI gate (axe failures block merge)
├── Design token enforcement (contrast-safe palette)
└── Periodic audit (quarterly full review)
Quick Reference
| Need to... | See |
|---|---|
| Fix color contrast failures | Color Contrast |
| Add keyboard support to custom components | Keyboard Navigation |
| Choose correct ARIA roles and landmarks | Semantic HTML |
| Build accessible forms with validation | Forms and Inputs |
| Write good alt text, handle media | Images and Media |
| Handle animations and motion safely | Motion and Animation |
| Set up page lang, titles, reflow, zoom | Page Structure |
| Fix links, nav consistency, predictability | Links and Navigation |
| Support drag alternatives, touch targets | Pointer and Touch |
| Handle timeouts, auth, CAPTCHAs | Timing and Authentication |
| Set up automated a11y testing | Testing and Auditing |
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 2.7 KB
- resources/color-contrast.md 4.8 KB
- resources/forms-and-inputs.md 5.6 KB
- resources/images-and-media.md 5.0 KB
- resources/keyboard-navigation.md 6.1 KB
- resources/links-and-navigation.md 7.7 KB
- resources/motion-and-animation.md 5.2 KB
- resources/page-structure.md 7.8 KB
- resources/pointer-and-touch.md 8.5 KB
- resources/semantic-html.md 6.5 KB
- resources/testing-and-auditing.md 8.5 KB
- resources/timing-and-authentication.md 11 KB
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 · 312 lines · 64 tokens per session scan A 9c4c5717f5f1
wcag-accessibility is a skill published in the GitHub repository LeahyCC/claude-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 3,779 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
wes-bos-sick-picks
Research-first workflow for building frontend UI components (any framework), in the spirit of Wes Bos. Use when designing or implementing a UI component, layout, interaction, or CSS/HTML feature and you want a modern, accessible, best-practice solution rather than a first guess. Researches pitfalls and platform…
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…
micro-interactions
Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles…
elevation-and-depth
Elevation — subtle shadows and layering — communicates visual hierarchy by lifting elements above the surface. Combined with border-radius, it creates the tactile quality of cards, modals, and interactive surfaces. Use when designing cards, dropdowns, modals, tooltips, or any floating UI element.
loading-states-and-perceived-performance
Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…