Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 38 ยท Principles and WCAG

A Tour of the Success Criteria

A friendly walk through the most important WCAG Level A and AA success criteria, grouped by principle, with plain-language meaning and the fix for each.

WCAG 2.2 has 86 success criteria, which is a lot to memorise. The good news is that a modest handful covers most real-world failures, and most of them map to a small number of habits. This lesson walks through the criteria you will meet most often, grouped by POUR, in plain words with the typical fix. Later lessons go deep on each one.

Treat this as a map, not a replacement for the spec. Each criterion's exact wording and exceptions live in the official document, and the "Understanding" pages for each are worth reading when you audit.

Perceivable

Criterion Level In plain words Typical fix
1.1.1 Non-text Content A Every non-text item has a text equivalent alt, captions, labels for icons
1.2.1-1.2.5 Time-based Media A/AA Captions, transcripts, audio description Add caption tracks and transcripts
1.3.1 Info and Relationships A Structure is in the markup Headings, lists, tables, labels
1.3.2 Meaningful Sequence A Reading order makes sense Keep DOM order logical
1.3.5 Identify Input Purpose AA Personal fields say what they are autocomplete values
1.4.1 Use of Colour A Colour is never the only signal Add text, icons or patterns
1.4.3 Contrast (Minimum) AA Text has 4.5:1 contrast (3:1 large) Darken text or lighten background
1.4.4 Resize Text AA Text scales to 200% without loss Relative units
1.4.10 Reflow AA No two-way scrolling at 320 CSS px Responsive layout
1.4.11 Non-text Contrast AA UI parts and graphics have 3:1 Stronger borders and icons
1.4.12 Text Spacing AA Users can widen spacing without clipping No fixed heights
1.4.13 Content on Hover or Focus AA Tooltips are dismissable, hoverable, persistent Tooltip rules

Operable

Criterion Level In plain words Typical fix
2.1.1 Keyboard A Everything works from a keyboard Native controls
2.1.2 No Keyboard Trap A Focus can always leave Test modals and widgets
2.2.1 Timing Adjustable A Time limits can be extended Warnings, extend option
2.2.2 Pause, Stop, Hide A Moving content can be paused Pause control for carousels
2.3.1 Three Flashes A Nothing flashes more than 3 times/second Remove flashing
2.4.1 Bypass Blocks A A way to skip repeated blocks Skip link, landmarks
2.4.2 Page Titled A Pages have descriptive titles A unique <title>
2.4.3 Focus Order A Focus order is logical Source order
2.4.4 Link Purpose (In Context) A A link's purpose is clear Descriptive link text
2.4.6 Headings and Labels AA They describe topic or purpose Clear wording
2.4.7 Focus Visible AA Focus is always visible :focus-visible styles
2.5.3 Label in Name A Visible label is in the accessible name Match names
2.5.8 Target Size (Minimum) AA Targets at least 24 by 24 CSS px Larger hit areas

Understandable

Criterion Level In plain words Typical fix
3.1.1 Language of Page A The page language is set lang on html
3.1.2 Language of Parts AA Passages in other languages are marked lang on elements
3.2.1 On Focus A Focus does not trigger a context change No auto-submit on focus
3.2.2 On Input A Changing a field does not surprise Explicit submit buttons
3.2.3 Consistent Navigation AA Menus stay in the same order Shared template
3.3.1 Error Identification A Errors are described in text Clear messages
3.3.2 Labels or Instructions A Fields have labels or instructions <label>
3.3.3 Error Suggestion AA Say how to fix the error Helpful text
3.3.4 Error Prevention AA Legal and financial submissions are reversible Confirm step
3.3.7 Redundant Entry A Do not ask again for the same info Autofill from earlier
3.3.8 Accessible Authentication AA Login does not need a cognitive test Allow paste, password managers

Robust

Criterion Level In plain words Typical fix
4.1.2 Name, Role, Value A Custom controls expose name, role and state Native elements or ARIA
4.1.3 Status Messages AA Status updates are announced role="status", live regions

WCAG 2.2 removed 4.1.1 Parsing, because modern browsers handle most markup errors the same way. You should still write valid HTML, but it is no longer a separate success criterion.

Try it: a filter for the map

Filtering by principle or level is a handy way to study. This small tool does it with a handful of the criteria above.

Filter the criteria

Patterns across criteria

Notice how many criteria collapse into a few practical habits:

  • Use native HTML and most of 1.3.1, 2.1.1, 2.4.3 and 4.1.2 take care of themselves.
  • Never rely on a single sensory channel (1.1.1, 1.2.x, 1.4.1).
  • Make interfaces flexible under zoom, spacing and orientation (1.4.4, 1.4.10, 1.4.12).
  • Keep behavior predictable and errors helpful (3.2.x, 3.3.x).

The next lesson looks at the nine criteria WCAG 2.2 added, which reflect the newest thinking about mobile, focus and login.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which criterion requires that colour not be the only way to convey information?

    1.4.1 says colour must not be the only visual means of conveying information, so add text, icons or patterns.
  2. 2. What contrast ratio does Level AA require for normal body text?

    1.4.3 requires 4.5:1 for normal text, 3:1 for large text, and 1.4.6 (AAA) raises it to 7:1.
  3. 3. Which criterion covers skip links and landmarks?

    2.4.1 Bypass Blocks lets users skip repeated content such as a navigation menu.
  4. 4. Which criterion ensures custom widgets expose their name, role and state?

    4.1.2 is the criterion behind most ARIA work on custom controls.

Summary

  • A handful of criteria cause most real failures: alt text, contrast, keyboard, focus, labels, errors and names.
  • Criteria group neatly under POUR and under three levels.
  • Most are met by using native HTML and flexible layouts.
  • 4.1.1 Parsing was removed in WCAG 2.2.

Next: What WCAG 2.2 Added