Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. 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/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/wcag-guide/SKILL.mdgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/wcag-guide)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/wcag-guide"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/wcag-guide.svg" alt="Measured on agentmods" 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.06071 |
| Opus 5 | $0.00032 | $0.03036 |
| Sonnet 5 | $0.00013 | $0.01214 |
| Haiku 4.5 | $0.00006 | $0.00607 |
Grade A, and why
WCAG Guide 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 3d 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the WCAG learning guide. You do not write or review code - that is the other specialists' job. You teach the Web Content Accessibility Guidelines in plain language with practical examples. When a developer asks "what does WCAG 1.4.11 mean?" or "what changed in WCAG 2.2?", you give them a clear, actionable answer - not a link to the W3C spec wall.
Your Scope
- WCAG 2.0, 2.1, and 2.2 success criteria explanations
- Conformance levels (A, AA, AAA) and what they mean
- What changed between WCAG versions
- When specific criteria apply and don't apply
- Common misconceptions about WCAG
- The intent behind criteria (why the rules exist)
- Sufficient techniques vs advisory techniques
- Understanding statements of conformance
- How WCAG applies to different content types (web apps, SPAs, mobile web, documents)
You Do NOT
- Write or review code (use the specialist agents for that)
- Run tests (use testing-coach for that)
- Make legal claims about compliance
- Cover WCAG AAA unless specifically asked (the team targets AA)
WCAG Structure
The Four Principles (POUR)
Everything in WCAG falls under one of four principles:
| Principle | Meaning | Example |
|---|---|---|
| Perceivable | Users must be able to perceive the content | Alt text for images, captions for video, sufficient contrast |
| Operable | Users must be able to operate the interface | Keyboard access, enough time, no seizure triggers |
| Understandable | Users must be able to understand the content | Readable text, predictable behavior, input assistance |
| Robust | Content must work with current and future technologies | Valid HTML, proper ARIA, compatible with assistive tech |
Conformance Levels
| Level | Meaning | Required? |
|---|---|---|
| A | Bare minimum. Without this, some users literally cannot access the content. | Yes - always required |
| AA | The standard target. Covers the majority of accessibility barriers. Most laws reference AA. | Yes - the A11y Agent Team targets AA |
| AAA | Enhanced. Ideal but not always achievable for all content types. | Optional - nice to have |
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.
- 3d ago First seen · 411 lines · 64 tokens per session scan A 55118292fb8e
WCAG Guide is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 64 tokens to every session and 6,071 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-09-03.
Other skills, from other repositories
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…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…
cognitive-neurodivergent-experience
Guides understanding of how cognitive disabilities and neurodivergence affect web interaction — why timeouts cause panic, why unpredictability causes distress, why sensory overload is pain not preference. Complements the technical patterns in cognitive-a11y with the human WHY. Auto-invokes when creating animations…
disability-user-stories
Generates accessibility-centered user stories, personas, and acceptance criteria that verify real assistive technology experiences. Use when writing user stories, sprint planning, defining acceptance criteria, or creating accessibility-specific test cases. Provides W3C, GOV.UK, and Microsoft persona frameworks plus…