The Pragmatic WCAG 2.2 Checklist for Product Teams
We distilled WCAG 2.2 AA into a 36-item checklist your designers, engineers, and PMs can actually run against a sprint.
# The Pragmatic WCAG 2.2 AA Checklist By enabl — accessibility consulting A 36-item checklist your designers, engineers, and PMs can run against a sprint. ## 1. Perceivable - [ ] All non-text content has a meaningful text alternative (1.1.1) - [ ] Captions provided for pre-recorded video (1.2.2) - [ ] Audio description for pre-recorded video (1.2.5) - [ ] Information conveyed with structure, not visuals alone (1.3.1) - [ ] Meaningful sequence preserved when CSS is disabled (1.3.2) - [ ] Instructions don't rely on shape, color, or location alone (1.3.3) - [ ] Orientation is not locked unless essential (1.3.4) - [ ] Inputs use autocomplete tokens for known purposes (1.3.5) - [ ] Color is not the only means of conveying info (1.4.1) - [ ] Text contrast ≥ 4.5:1 (3:1 for large text) (1.4.3) - [ ] Text resizes up to 200% without loss (1.4.4) - [ ] Reflow at 320 CSS px without horizontal scroll (1.4.10) …
Downloadable guide
Preview the asset.
Skim the structure, then grab a copy you can edit, share, or paste into your team's docs.
WCAG is comprehensive — and that's exactly the problem when you're trying to ship. Most teams don't need to read 80+ success criteria; they need a short, ordered list of things to verify before a release.
This is the checklist we use internally at enabl when we run pre-release smoke tests. It covers WCAG 2.2 Level A and AA, including the nine new criteria added in 2.2.
How to use it
- 01Pick one flow per sprint — checkout, onboarding, dashboard. Don't audit "the whole app".
- 02Run the checklist top-to-bottom on that flow with keyboard, then with a screen reader.
- 03File each failure as a ticket with the SC number — e.g. "WCAG 2.4.7" — so engineers can search the spec.
- 04Fix, regression-test, ship. Move to the next flow.
What's new in WCAG 2.2
- 2.4.11 Focus Not Obscured — sticky headers can't hide the focused element
- 2.5.7 Dragging Movements — every drag needs a single-pointer alternative
- 2.5.8 Target Size — interactive targets are at least 24×24 CSS px
- 3.2.6 Consistent Help — help links appear in the same place across pages
- 3.3.7 Redundant Entry — don't make users retype info they've already given
- 3.3.8 Accessible Authentication — no cognitive function tests as the only path
Download the full checklist below as a Markdown file you can drop into Notion, Linear, or your team wiki.
Take it with you
checklist
Free to use and share with attribution.