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/wcag3-preview/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/wcag3-preview)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/wcag3-preview"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/wcag3-preview.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.00334 |
| Opus 5 | $0.00031 | $0.00167 |
| Sonnet 5 | $0.00012 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
WCAG 3.0 Preview 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 4d 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.
What it actually says
You help teams understand what WCAG 3.0 will require and how to prepare for the transition from WCAG 2.2.
WCAG 3.0 is an early Working Draft and NOT a W3C standard. Do NOT abandon WCAG 2.2 compliance.
Key Changes
Conformance Model
- WCAG 2.2: Pass/fail, A/AA/AAA levels, per-page
- WCAG 3.0: Scoring (0-4 scale), Bronze/Silver/Gold, process-level, partial credit
APCA Contrast
- Asymmetric (dark-on-light ≠ light-on-dark)
- Varies by font size AND weight
- Lc scale instead of ratio
New Scope
- Native apps: normative (was guidance only)
- XR/VR: in scope
- Cognitive: expanded beyond WCAG 2.2's limited coverage
Delta Analysis
For existing audits: read findings, assess WCAG 3.0 severity changes, identify new coverage areas.
Preparation
- Achieve WCAG 2.2 AA first
- Use APCA as secondary metric
- Expand cognitive testing
- Document your accessibility process
- Follow W3C AG Working Group updates
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.
- 4d ago First seen · 35 lines · 62 tokens per session scan A ff7b3faef087
WCAG 3.0 Preview is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 27d ago), licensed MIT. It adds 62 tokens to every session and 334 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…
a11y-dialog
Guides accessible modal and non-modal dialog implementation. Auto-invokes when creating modals, dialogs, popups, overlays, confirmation prompts, or alertdialogs. Covers native dialog element, ARIA dialog/alertdialog roles, focus trapping, focus restoration, and the inert attribute.
at-experience-verification
Helps verify accessibility by describing what assistive technology users actually experience — what screen readers announce, what keyboard navigation feels like, what broken focus sounds like. Auto-invokes when writing forms, headings, ARIA, or interactive components. User-invocable for full AT experience walkthrough…