Explain WCAG 2.2 criteria, conformance levels and what changed.

MITAuto-check passedFrontend & Design

Install Wcag Guide

skills CLI
$ npx skills add Community-Access/accessibility-agents --skill wcag-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Community-Access/accessibility-agents wcag-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/wcag-guide .claude/skills/wcag-guide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
wcag-guide
GitHub stars
422
Token cost
~1.5k tokens
SKILL.md length
741 words
Files
4 (incl. references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Explain WCAG 2.2 criteria, conformance levels and what changed.

  • Works in 6 steps: State the criterion number and name → Give the conformance level (A, AA, or AAA) → Explain in plain language what it… → …
  • Tasks that involve Accessibility
  • SKILL.md covers WCAG Guide, Your Scope, You Do NOT and WCAG Structure, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Wcag Guide is an agent skill from Community-Access/accessibility-agents. Explain WCAG 2.2 criteria, conformance levels and what changed.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/common-wcag-misconceptions.md` and `references/complete-wcag-2-2-aa-success-criteria-reference.md`).

It sits in Frontend & Design, covering Accessibility. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.

When your agent uses it

  • Tasks that involve Accessibility

Example prompts

  • “/wcag-guide”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. State the criterion number and name
  2. Give the conformance level (A, AA, or AAA)
  3. Explain in plain language what it requires and why
  4. Give a concrete example of a pass and a fail
  5. Note what it does NOT require (to prevent over-engineering)
  6. Reference the relevant specialist agent if they need code help

What it can do on your machine

Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Wcag Guide loads about 1.5k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 19 tokens; SKILL.md has 741 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 741 words, ~1,546 tokens.

Download SKILL.mdSave it as .claude/skills/wcag-guide/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
wcag-guide
description
Explain WCAG 2.2 criteria, conformance levels and what changed.
license
MIT
disable-model-invocation
true
metadata.tier
specialist
metadata.domain
cross-cutting
metadata.output
guidance
metadata.effort
medium
metadata.title
WCAG Guide

WCAG Guide

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:

PrincipleMeaningExample
PerceivableUsers must be able to perceive the contentAlt text for images, captions for video, sufficient contrast
OperableUsers must be able to operate the interfaceKeyboard access, enough time, no seizure triggers
UnderstandableUsers must be able to understand the contentReadable text, predictable behavior, input assistance
RobustContent must work with current and future technologiesValid HTML, proper ARIA, compatible with assistive tech
Conformance Levels

Each level, with its meaning and required.

LevelMeaningRequired?
ABare minimum. Without this, some users literally cannot access the content.Yes - always required
AAThe standard target. Covers the majority of accessibility barriers. Most laws reference AA.Yes - the A11y Agent Team targets AA
AAAEnhanced. Ideal but not always achievable for all content types.Optional - nice to have

Important: Conformance is inclusive. "Conforms to AA" means ALL Level A criteria AND all Level AA criteria are met. You cannot claim AA while failing any Level A criteria.

Success Criteria Numbering

Example: WCAG 2.1.1

  • 2 = Principle 2 (Operable)
  • 1 = Guideline 2.1 (Keyboard Accessible)
  • 1 = Success Criterion 2.1.1 (Keyboard)

What Changed in WCAG 2.2 (vs 2.1)

WCAG 2.2 added 9 new success criteria. The ones that affect AA conformance:

CriterionLevelWhat It Added
2.4.11 Focus Not ObscuredAAFocused element must not be hidden behind sticky headers/banners
2.5.7 Dragging MovementsAADragging functions must have non-drag alternatives
2.5.8 Target Size (Minimum)AATouch targets >= 24 x 24px (or sufficient spacing)
3.2.6 Consistent HelpAAHelp mechanisms in same location across pages
3.3.7 Redundant EntryADon't make users re-enter info already provided
3.3.8 Accessible AuthenticationAADon't require cognitive tests for login

WCAG 2.2 also removed one criterion:

  • 4.1.1 Parsing - removed because modern browsers handle parsing errors well. HTML validation is still good practice but is no longer a WCAG requirement.

Show full SKILL.md (259 more words)Show less

Understanding "Sufficient Techniques" vs "Advisory Techniques"

WCAG provides techniques to meet criteria. There are two types:

Sufficient techniques - If you use one of these, you pass the criterion. Example: For 1.1.1, providing alt text on <img> is a sufficient technique.

Advisory techniques - Recommendations that go beyond the requirement. Not required for conformance. Example: Providing long descriptions for complex images is advisory beyond basic alt text.

Failures - Common mistakes that violate a criterion. Example: Using alt="image" for all images is a documented failure of 1.1.1.

You don't have to use a specific technique. If you achieve the same outcome through a different method, you can still conform. The success criteria describe the outcome, not the method.


How to Answer WCAG Questions

When a developer asks a WCAG question:

  1. State the criterion number and name
  2. Give the conformance level (A, AA, or AAA)
  3. Explain in plain language what it requires and why
  4. Give a concrete example of a pass and a fail
  5. Note what it does NOT require (to prevent over-engineering)
  6. Reference the relevant specialist agent if they need code help

Example response:

text
WCAG 1.4.11 Non-text Contrast (Level AA, new in WCAG 2.1)

Requires: UI components and meaningful graphics must have at least 
3:1 contrast against adjacent colors.

Example pass: A text input with a #767676 border on a white background 
(contrast ratio 4.48:1).

Example fail: A text input with a #CCCCCC border on white (contrast 
ratio 1.6:1 - the border is nearly invisible).

Does NOT apply to: Disabled/inactive controls, purely decorative elements, 
photographs, logos.

For code-level contrast checking, use @contrast-master.

Reference files

Read one only when the task reaches it. Do not read them all up front.

  • references/complete-wcag-2-2-aa-success-criteria-reference.md - Complete WCAG 2.2 AA Success Criteria Reference
  • references/common-wcag-misconceptions.md - Common WCAG Misconceptions

Output contract

Answer the question. Keep the answer to what was asked, cite the criterion or API by name, and stop. Do not append a checklist that was not requested.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/wcag-guide of Community-Access/accessibility-agents.

  • SKILL.md
  • agents/openai.yaml
  • references/common-wcag-misconceptions.md
  • references/complete-wcag-2-2-aa-success-criteria-reference.md

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Wcag Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Wcag Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wcag Guide this skillCommunity-Access/accessibility-agents422—~1.5kAutomated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k98 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.5k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 98 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed
  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.5k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed
  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.5k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from Community-Access/accessibility-agents

All 108 skills in this repo
  • A11y Core

    Community-Access/accessibility-agents

    Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.

    422 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check passed
  • Kb Web Scanning

    Community-Access/accessibility-agents

    Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.

    422 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check passed
  • Accessibility Lead

    Community-Access/accessibility-agents

    Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.

    422 GitHub stars~932 tokensUpdated 15 days ago
    Auto-check passed
  • Alt Text Headings

    Community-Access/accessibility-agents

    Alt text, SVGs, figures, charts, heading order, page titles and landmarks.

    422 GitHub stars~1.5k tokensUpdated 15 days ago
    Auto-check passed
  • Aria Specialist

    Community-Access/accessibility-agents

    ARIA roles, states and properties for custom widgets and dynamic content.

    422 GitHub stars~1.6k tokensUpdated 15 days ago
    Auto-check passed
  • Cognitive Accessibility

    Community-Access/accessibility-agents

    Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.

    422 GitHub stars~1.4k tokensUpdated 15 days ago
    Auto-check passed

Questions about Wcag Guide

What does Wcag Guide do?

Explain WCAG 2.2 criteria, conformance levels and what changed. Wcag Guide is an agent skill from Community-Access/accessibility-agents.2 criteria, conformance levels and what changed.

When should I use Wcag Guide?

Wcag Guide fits situations like: tasks that involve Accessibility.

How do I install Wcag Guide in Claude Code?

Run `npx skills add Community-Access/accessibility-agents --skill wcag-guide -a claude-code`. Or copy the skill folder (skills/wcag-guide in Community-Access/accessibility-agents) into .claude/skills/wcag-guide in your project. Claude Code loads it when a task matches its description.

How do I install Wcag Guide in Codex?

Run `npx skills add Community-Access/accessibility-agents --skill wcag-guide -a codex`. Or copy the skill folder (skills/wcag-guide in Community-Access/accessibility-agents) into .agents/skills/wcag-guide in your project. Codex loads it when a task matches its description.

Can I use Wcag Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill wcag-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wcag-guide, .gemini/skills/wcag-guide, .github/skills/wcag-guide and .opencode/skills/wcag-guide in your project.

What does Wcag Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: Wcag Guide is instructions for the agent only.

Does Wcag Guide access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Wcag Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Wcag Guide use?

Wcag Guide is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wcag Guide use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.1k tokens, read only when the agent opens those files.

What are the alternatives to Wcag Guide?

Skills that share tags, products or a category with Wcag Guide: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wcag Guide?

Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 422 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.

Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.