---
name: accessibility-full-audit
description: Use when asked for a full accessibility review of a website or web app against WCAG 2.2 AA - keyboard access and focus, landmarks and headings, alt text, forms and labels, error handling, motion, reflow and zoom, target size, authentication, and screen reader spot checks - with fixes as a review PR. Combines automated tools with manual checks. For contrast-only work use wcag-contrast-audit; this skill calls it as one step.
---

# Full accessibility audit (WCAG 2.2 AA)

Last reviewed: 2026-11-10

## Quick prompts

For anyone improving a site or app, whether a small-business owner or someone at a larger company practicing better prompts. Accessibility problems lock some people out entirely, and many can be fixed cheaply once someone finds them. Paste a prompt into any AI assistant that can see the site or repo.

1. "Try using the site I work on with only a keyboard: Tab, Enter, and Escape. Tell me where you get stuck or can't see where you are. Plain-language report first, no fixes yet."
   *Why this prompt works:* Scope: one clear test method gives concrete, repeatable findings.

2. "Check the images and forms on the site I work on. Which images lack useful descriptions, and which form fields lack clear labels or error messages? List them by page before changing anything."
   *Why this prompt works:* Narrowing to two areas keeps the report short enough to act on.

3. "Review this page of the site I work on against WCAG 2.2 AA. Group problems as must-fix, should-fix, and nice-to-have, and explain each simply. Don't make changes yet."
   *Why this prompt works:* Give criteria and ask for priority groups so the result is a to-do list, not a dump.

Automated tools catch roughly a third of issues. The rest needs keyboard, zoom, and screen reader checks. Report against WCAG success criteria so findings are traceable.

## Hard limits

- Fix markup, ARIA, CSS, and focus handling only. No content rewrites (alt text and labels are proposed to the owner unless missing entirely and obvious), no navigation or behavior changes beyond what a criterion requires.
- Prefer native HTML over ARIA. Do not add ARIA that changes how existing working controls are announced.
- Never submit real forms or create real records; force states or use a test environment.
- Review PR only; no merge or production deploy without the owner's approval.

## Inputs to gather

1. Routes (one per template), user flows that matter (sign up, search, checkout, contact), test accounts.
2. Component library and whether it claims accessibility support.
3. Any existing accessibility statement or prior audit.

## Step 1: Classify

| Type | Most common failures |
|---|---|
| Article / editorial | Heading skips, missing/meaningless alt, link text "read more", embeds without titles, autoplay media |
| Marketing / landing | Carousels without pause, background video, low-contrast text on images, icon-only social links without names |
| Docs | Code blocks not keyboard scrollable, copy buttons without names, sidebar disclosure state not exposed |
| E-commerce | Filters and swatches not keyboard operable, price changes not announced, cart updates silent, CAPTCHA on checkout |
| Dashboard / data | Charts with no text alternative, data tables without headers/scope, color-only status, drag-and-drop with no alternative (2.5.7) |
| SaaS / app | Modals without focus trap and return, custom selects/menus, toasts not announced (`role="status"`), session timeouts, auth needing puzzles (3.3.8) |
| Forms flow | Missing labels, placeholder-as-label, errors not linked (`aria-describedby`), required not indicated, redundant entry across steps (3.3.7) |
| SPA | Route changes not announced, focus not moved to new content, page `<title>` not updated |

## Step 2: Automated pass

- axe-core (via Playwright or browser extension) on every sampled route in every theme, at desktop and phone sizes.
- Lighthouse accessibility as a second opinion. HTML validation for duplicate IDs and invalid nesting.
- Treat automated results as leads; confirm each one.

## Step 3: Manual checks

- **Keyboard (2.1.1, 2.1.2, 2.4.3, 2.4.7)**: Tab through every page: skip link first, logical order, no traps, every control reachable and operable with Enter/Space/arrows as expected, visible focus.
- **Focus not obscured (2.4.11)**: focused items are not fully hidden by sticky headers, footers, cookie bars, chat widgets.
- **Structure (1.3.1, 2.4.2, 2.4.6)**: one `main`, `header`/`nav`/`footer` landmarks, unique page titles, headings in order, lists as lists, tables with `th`/`scope`/caption.
- **Images and media (1.1.1, 1.2.x)**: informative images have meaningful alt, decorative have `alt=""`, complex images/charts have text equivalents, videos have captions, audio has transcripts.
- **Forms (1.3.5, 3.3.1–3.3.3, 4.1.2)**: visible labels tied to inputs, `autocomplete` on personal fields, errors in text and linked to fields, focus moves to the error summary or first error.
- **Names, roles, states (4.1.2)**: icon buttons have accessible names, toggles expose `aria-expanded`/`aria-pressed`, custom widgets follow ARIA Authoring Practices patterns.
- **Status messages (4.1.3)**: added-to-cart, saved, results counts announced via live regions.
- **Reflow and zoom (1.4.4, 1.4.10, 1.4.12)**: 200% zoom and 320 CSS px width with no loss or two-way scrolling (except data tables, maps); text spacing override does not clip.
- **Contrast (1.4.3, 1.4.11)**: run the wcag-contrast-audit skill or reuse its results.
- **Motion (2.2.2, 2.3.3 advisory)**: anything that moves for more than 5 seconds can be paused; respect `prefers-reduced-motion`.
- **Pointer (2.5.7, 2.5.8)**: dragging has a single-pointer alternative; targets at least 24×24 CSS px or spaced.
- **Consistency and help (3.2.3, 3.2.4, 3.2.6)**: navigation and help links in the same place across pages.
- **Authentication (3.3.8)**: paste allowed in password and code fields, password managers work, no cognitive puzzles without an alternative.
- **Screen reader spot check**: NVDA + Firefox/Chrome or VoiceOver + Safari on 2–3 key flows: landmarks list, headings list, form completion, one dynamic update.

## Step 4: Fix and recheck

Fix shared components first; re-run axe and the manual checks on affected flows.

## Report format

1. Scope: type(s), routes, flows, themes, sizes, assistive tech used.
2. Findings table: WCAG criterion, level, component/selector, page(s), how to reproduce, impact, fix, status (fixed in PR / needs owner / deferred).
3. Content items for the owner (alt text, captions, link text).
4. Not verified. PR link, "not merged". Note that an audit is not a legal conformance certification.

## References

- WCAG 2.2: https://www.w3.org/TR/WCAG22/
- How to Meet WCAG (Quick Reference): https://www.w3.org/WAI/WCAG22/quickref/
- WAI Easy Checks: https://www.w3.org/WAI/test-evaluate/preliminary/
- WCAG-EM evaluation methodology: https://www.w3.org/WAI/test-evaluate/conformance/wcag-em/
- ARIA Authoring Practices Guide: https://www.w3.org/WAI/ARIA/apg/
- MDN Accessibility: https://developer.mozilla.org/en-US/docs/Web/Accessibility
- axe-core: https://github.com/dequelabs/axe-core
- MDN `prefers-reduced-motion`: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion
