WCAG 2.2 AA Checklist for Designers
WCAG 2.2 has 78 success criteria across 4 principles. As a designer, you don't need to memorize all of them — your engineering and QA teams handle the technical ones. But there are ~28 criteria that get decided in the design tool, before code exists. If they're wrong in Figma, they'll be wrong in production. This checklist is those 28.
References: WCAG 2.2 (W3C Recommendation, Oct 2023), WAI-ARIA 1.2
016 items
Perceivable — Color & Contrast
- 01Body text contrast ≥4.5:1 against background
WCAG 1.4.3
- 02Large text (≥18pt regular or 14pt bold) contrast ≥3:1
WCAG 1.4.3
- 03UI controls and icons contrast ≥3:1 against adjacent colors
WCAG 1.4.11
- 04Focus indicator contrast ≥3:1 against unfocused state
WCAG 2.4.7, 2.4.11
- 05Information not conveyed by color alone (icons, labels, patterns supplement)
WCAG 1.4.1
- 06Link text distinguishable from surrounding text by more than color (underline, weight)
WCAG 1.4.1
024 items
Perceivable — Imagery & Media
- 07Decorative images marked decorative (alt="") in design hand-off
WCAG 1.1.1
- 08Informative images have meaningful alt text (not "image of", not file name)
WCAG 1.1.1
- 09Functional images (icon buttons) have alt describing the action
WCAG 1.1.1
- 10Videos have captions specified, autoplay disabled
WCAG 1.2.2, 1.4.2
035 items
Operable — Focus & Targets
- 11Touch targets ≥24×24px (WCAG 2.2 new SC)
WCAG 2.5.8
- 12Focus indicators visible on all interactive elements
WCAG 2.4.7
- 13Focus order matches visual order (no jumping)
WCAG 2.4.3
- 14Skip-to-main-content link in design (engineering will wire)
WCAG 2.4.1
- 15Hover states have keyboard equivalents designed
WCAG 2.1.1
043 items
Operable — Motion & Time
- 16Animations respect prefers-reduced-motion (alternative state designed)
WCAG 2.3.3
- 17No content flashes >3× per second (seizure risk)
WCAG 2.3.1
- 18Timeouts have user warning + extension control
WCAG 2.2.1
055 items
Understandable — Forms
- 19Every input has a visible persistent label (not just placeholder)
WCAG 3.3.2
- 20Required fields indicated visually + textually
WCAG 3.3.2
- 21Error messages near the field, descriptive ("Email must contain @")
WCAG 3.3.1, 3.3.3
- 22Field purpose tagged for autocomplete (email, name, address)
WCAG 1.3.5
- 23Login forms support password manager autofill
WCAG 2.2 SC 3.3.7-9
065 items
Robust — Naming
- 24Page title unique, descriptive, designed
WCAG 2.4.2
- 25Headings used hierarchically (H1 → H2 → H3, no skipping)
WCAG 1.3.1, 2.4.6
- 26Region landmarks identifiable (header, nav, main, aside, footer)
WCAG 1.3.1
- 27Status messages designed (toast, snackbar, banner) with icon + text
WCAG 4.1.3
- 28Form errors don't rely on color alone (icon + text + position)
WCAG 1.4.1, 3.3.1
AccessAudit AI for iPhone
Run this on your phone.
Point your iPhone camera at any color pair to see its WCAG contrast ratio and whether it passes, in real time, on the device.
More for AccessAudit AI users
- 14 items
Color Contrast Cheatsheet — WCAG Quick Reference
The single page you keep open while designing.
- 24 items
Mobile App Accessibility Checklist (iOS + Android)
Catch every accessibility gap before App Store / Play Store review.
- 18 items
Form Accessibility Checklist
Accessible forms convert better. This is how.
- 16 items
Keyboard Navigation Audit Checklist
Unplug your mouse. Now do the entire site.
- 20 items
Image Alt Text Guide with Examples
90% of accessibility issues with images are alt text. Here's how to write them right.
- 18 items
Figma Accessibility Audit Checklist
Fix accessibility in Figma. Save 10× the time fixing it in production.
- 12 items
ARIA Cheatsheet for Designers
Most designers shouldn't use ARIA. Here's when you actually should.
- 14 items
Dark Mode Accessibility Checklist
Dark mode is its own audit. Treat it that way.
- 11 items
WCAG 3.0 Preview for Designers
WCAG 3.0 isn't final. But the things it's testing matter now.