WCAG Accessibility Skills

Portable WCAG accessibility audits with explicit human-review boundaries.

WCAG Accessibility Skills is an open-source command skill for static accessibility evidence, review planning, and CI regression gates. It is intended for web accessibility audits, digital accessibility development, and accessibility compliance workflows across Claude MCP, OpenAI Codex, Gemini function calling, and any agent host that can execute a command or consume JSON.

For skill-aware agents, SKILL.md is the portable adapter. It routes every /wcag-* command to the CLI and preserves the manual-review boundary.

Contents

• Why
• Features
• Install
• Quick start
• Usage guide
• Complete CLI reference
• WCAG coverage
• Architecture
• API reference
• Comparison
• FAQ
• Contributing, roadmap, and support

Why

Web accessibility is a quality requirement, not an optional visual polish pass. People use websites through keyboards, voice input, screen readers, magnification, switches, browser zoom, different colour perception, and different cognitive strategies. A product that hides a submit button’s name from assistive technology, omits a language declaration, or puts a keyboard user into a broken interaction is not merely failing a checklist: it is blocking a person from completing a task. WCAG provides a stable shared language for detecting and discussing these barriers, and laws or procurement standards often reference WCAG-based requirements. The exact legal duty depends on jurisdiction, product type, contract, and current law; a technical tool cannot decide it for an organisation.

The WebAIM Million study is a useful reminder that obvious, detectable barriers remain widespread. It is not a universal compliance census and should always be cited with its date and method. Its value here is practical: teams need feedback while code is being written, before a defect becomes a release risk or an expensive remediation project. A static audit can reliably recognize several high-value patterns, including an image without an alt attribute, a document without lang, an unnamed control, an empty link, a missing title, or a positive tabindex. Those checks are quick, objective, and appropriate for continuous integration.