The plain-English WCAG 2.2 checklist

Users must be able to perceive your content — see it, hear it, or read it through assistive technology.

• Every meaningful image has descriptive alt text; decorative images are hidden from screen readers (1.1.1)
• Pre-recorded video has captions, and audio content has transcripts (1.2.1–1.2.5)
• Structure uses real markup — headings, lists, tables, and form labels, not styled text (1.3.1)
• Form fields that collect user data identify their purpose so autofill works (1.3.5)
• Text contrast is at least 4.5:1 — 3:1 for large text (1.4.3)
• Text can be resized to 200% without losing content or function (1.4.4)
• Content reflows on small screens without two-directional scrolling (1.4.10)
• Buttons, form borders, icons, and charts have 3:1 contrast (1.4.11)
• Layouts survive user-adjusted text spacing without clipping (1.4.12)
• Tooltips and hover content can be dismissed and hovered without disappearing (1.4.13)

Users must be able to operate every control — with a keyboard alone, a touch screen, or assistive technology.

• Everything works with a keyboard, and focus is never trapped (2.1.1, 2.1.2)
• Time limits can be extended; auto-moving content can be paused (2.2.1, 2.2.2)
• Nothing flashes more than three times per second (2.3.1)
• Pages have a skip link, descriptive titles, logical focus order, and clear link text (2.4.1–2.4.4)
• Headings and labels are descriptive, and keyboard focus is clearly visible (2.4.6, 2.4.7)
• Focused elements aren't hidden behind sticky headers or overlays (2.4.11 — new in 2.2)
• Complex gestures and dragging have single-pointer alternatives (2.5.1, 2.5.7 — new in 2.2)
• Clickable targets are at least 24×24 CSS pixels or well spaced (2.5.8 — new in 2.2)

Users must be able to understand your content and predict how the interface behaves.

• The page language — and any language changes — are set in code (3.1.1, 3.1.2)
• Nothing changes context unexpectedly when an element gets focus or input (3.2.1, 3.2.2)
• Navigation and repeated components stay consistent across pages (3.2.3, 3.2.4)
• Help options appear in the same place on every page (3.2.6 — new in 2.2)
• Form errors are identified in text, explained, and easy to correct (3.3.1, 3.3.3)
• Every input has a visible label and clear instructions (3.3.2)
• Legal and financial submissions can be reviewed and reversed (3.3.4)
• Users never re-enter information they already provided in the same flow (3.3.7 — new in 2.2)
• Logins work without puzzles or memorisation — paste and password managers allowed (3.3.8 — new in 2.2)

Your code must work reliably with browsers and assistive technologies — today and as they evolve.

• Custom controls expose an accessible name, role, and value through correct ARIA (4.1.2)
• Status messages — form saved, items in cart, errors — are announced to screen readers without moving focus (4.1.3)
• Note: 4.1.1 Parsing was removed in WCAG 2.2 — modern browsers handle malformed HTML consistently, so it always passes