WCAG 2.2 Checklist: 50 Criteria Every Website Should Pass

The Web Content Accessibility Guidelines (WCAG) 2.2 defines how to make web content accessible. This checklist covers all Level A and AA criteria — the standard required by the EU Accessibility Act.

1. Perceivable — Information must be presentable to all users

1.1 Text Alternatives

• ✓ 1.1.1 Non-text Content (A): All images, icons, charts have meaningful alt text

1.2 Time-based Media

• ✓ 1.2.1 Audio/Video only (A): Transcripts for audio, description for video
• ✓ 1.2.2 Captions (A): Captions for all pre-recorded video
• ✓ 1.2.3 Audio Description (A): Audio description or text alternative for video
• ✓ 1.2.4 Live Captions (AA): Captions for live video
• ✓ 1.2.5 Audio Description (AA): Audio description for all pre-recorded video

1.3 Adaptable

• ✓ 1.3.1 Info and Relationships (A): Semantic structure with headings, lists, tables
• ✓ 1.3.2 Meaningful Sequence (A): Content order preserves meaning
• ✓ 1.3.3 Sensory Characteristics (A): No reliance on shape, size, or position alone
• ✓ 1.3.4 Orientation (AA): Content works in portrait and landscape
• ✓ 1.3.5 Identify Input Purpose (AA): Autocomplete attributes on form fields

1.4 Distinguishable

• ✓ 1.4.1 Use of Color (A): Color is never the only way to convey information
• ✓ 1.4.2 Audio Control (A): Ability to pause or stop auto-playing audio
• ✓ 1.4.3 Contrast Minimum (AA): Text contrast ratio ≥ 4.5:1 (large text 3:1)
• ✓ 1.4.4 Resize Text (AA): Text can be resized to 200% without loss of function
• ✓ 1.4.5 Images of Text (AA): Use text instead of images of text where possible
• ✓ 1.4.10 Reflow (AA): Content works at 320px width without horizontal scroll
• ✓ 1.4.11 Non-text Contrast (AA): UI components have contrast ≥ 3:1
• ✓ 1.4.12 Text Spacing (AA): Users can override text spacing without breaking layout
• ✓ 1.4.13 Content on Hover/Focus (AA): Tooltips are dismissible and persistent

2. Operable — All users must be able to operate the interface

2.1 Keyboard Accessible

• ✓ 2.1.1 Keyboard (A): All functionality available via keyboard
• ✓ 2.1.2 No Keyboard Trap (A): Focus can always move away from any element
• ✓ 2.1.4 Character Key Shortcuts (A): Single-key shortcuts can be remapped or disabled

2.2 Enough Time

• ✓ 2.2.1 Timing Adjustable (A): Users can extend time limits
• ✓ 2.2.2 Pause, Stop, Hide (A): Auto-moving content can be paused

2.3 Seizures and Physical Reactions

• ✓ 2.3.1 Three Flashes (A): No content flashes more than 3 times/second

2.4 Navigable

• ✓ 2.4.1 Bypass Blocks (A): Skip-to-content link available
• ✓ 2.4.2 Page Titled (A): Every page has a descriptive title
• ✓ 2.4.3 Focus Order (A): Focus follows a logical order
• ✓ 2.4.4 Link Purpose (A): Clear link text, no generic "click here"
• ✓ 2.4.5 Multiple Ways (AA): Multiple ways to find pages (nav, search, sitemap)
• ✓ 2.4.6 Headings and Labels (AA): Descriptive headings and labels
• ✓ 2.4.7 Focus Visible (AA): Visible keyboard focus indicator
• ✓ 2.4.11 Focus Not Obscured (AA): Focused element is not hidden behind other content

2.5 Input Modalities

• ✓ 2.5.3 Label in Name (A): Accessible name matches visible text
• ✓ 2.5.7 Dragging Movements (AA): Actions can be performed without dragging
• ✓ 2.5.8 Target Size (AA): Touch targets are at least 24×24 CSS pixels

3. Understandable — Content must be understandable

• ✓ 3.1.1 Language of Page (A): Page language declared in HTML
• ✓ 3.1.2 Language of Parts (AA): Language changes are marked
• ✓ 3.2.1 On Focus (A): No unexpected context change on focus
• ✓ 3.2.2 On Input (A): No unexpected context change on input
• ✓ 3.2.3 Consistent Navigation (AA): Navigation order is consistent
• ✓ 3.2.4 Consistent Identification (AA): Same function = same label everywhere
• ✓ 3.3.1 Error Identification (A): Errors are described in text
• ✓ 3.3.2 Labels or Instructions (A): All inputs have labels
• ✓ 3.3.3 Error Suggestion (AA): Error messages suggest corrections
• ✓ 3.3.4 Error Prevention (AA): Legal/financial submissions are reversible
• ✓ 3.3.7 Accessible Authentication (AA): No cognitive function tests for login

4. Robust — Content must work with current and future technology

• ✓ 4.1.2 Name, Role, Value (A): All UI components have proper ARIA
• ✓ 4.1.3 Status Messages (AA): Status updates are announced to screen readers

← Blog · Scan