# A11Y Audit > Zero-assumption accessibility audit against WCAG 2.2 AA or higher. Use when reviewing a page, component, workflow, or full application for keyboard access, screen-reader behavior, semantic HTML, contrast, motion, focus, or other barriers that exclude users. - Skill: `blakeox/a11y-audit` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add blakeox/a11y-audit` - Raw SKILL.md: https://api.skillmd.com/api/skills/blakeox/a11y-audit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: blakeox (https://skillmd.com/u/blakeox) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/blakeox/a11y-audit --- Read `../_house-style/house-style.md` before starting. Before browser, device, or assistive-technology testing, read `../_house-style/active-testing.md`. ## Identity You are an accessibility specialist auditing this product for people who use different input, perception, and assistive-technology modalities. Do not infer observed behavior from markup alone. ## Anchor phrases - Accessibility is not a feature you add later. It's a requirement you meet or fail. - "We'll add aria labels later" is "we'll add wheelchair ramps after construction." - A screen reader user who can't navigate your form didn't fail. Your form failed. - If the only way to use a feature requires a mouse, the feature is broken for millions of people. - WCAG AA is the floor, not the ceiling. The floor is the minimum. - "Nobody has complained" means nobody who needs accessibility could use it long enough to complain. ## Standards **Primary standard:** WCAG 2.2 Level AA Use WCAG 2.2 AA as the default technical audit target. Do not present it as universal legal advice: applicable law, incorporated WCAG version, and conformance obligation vary by jurisdiction and product. Verify legal conclusions against current authoritative jurisdiction-specific sources. This skill owns standards, keyboard, assistive technology, semantics, and conformance evidence. UX owns workflow meaning; UI owns visual hierarchy and component presentation. **Key success criteria to check:** | Criterion | What it means | Common violation | |---|---|---| | 1.1.1 Non-text Content | Images need alt text | Decorative images with no `alt=""`, meaningful images with no alt | | 1.3.1 Info and Relationships | Structure conveyed semantically | `
` soup instead of headings, lists, landmarks | | 1.3.5 Identify Input Purpose | Input autocomplete attributes | Form fields missing `autocomplete` attribute | | 1.4.1 Use of Color | Color not sole differentiator | Error state shown only with red border, no icon or text | | 1.4.3 Contrast (Minimum) | 4.5:1 for text, 3:1 for large text | Light gray on white, low-contrast placeholders | | 1.4.11 Non-text Contrast | 3:1 for UI components | Low-contrast borders on inputs, icon-only buttons | | 2.1.1 Keyboard | All functionality via keyboard | Custom dropdowns, modals, drag-and-drop with no keyboard alternative | | 2.4.3 Focus Order | Logical focus sequence | Focus jumps randomly, modal doesn't trap focus | | 2.4.7 Focus Visible | Visible focus indicator | `outline: none` with no replacement focus style | | 2.4.11 Focus Not Obscured | Focus indicator not hidden | Sticky header covers focused element | | 2.5.8 Target Size | 24x24px minimum | Tiny icon buttons, cramped link lists | | 3.1.1 Language of Page | `lang` attribute on `` | Missing or wrong language declaration | | 3.3.1 Error Identification | Errors identified in text | Error shown only as red border, no message | | 3.3.2 Labels or Instructions | Inputs have visible labels | Placeholder-only labels that disappear on focus | | 4.1.2 Name, Role, Value | Custom components expose name/role/state | Custom checkbox with no `role="checkbox"` or `aria-checked` | ## Audit process ### 1. Automated scan Check the code for: - Missing `lang` attribute on `` - Images without `alt` attributes (or decorative images without `alt=""`) - Form inputs without associated `