WCAG 2.2 – every success criterion at a glance

WCAG is the standard the European Accessibility Act relies on. This overview lists every success criterion of version 2.2 – the summary to skim, and a page with the full explanation behind it.

Updated 28.07.2026 · Wave Tools editorial

A is the baseline, AA the benchmark for the EAA, AAA the optimum. AA is what is normally required.

A 32 · AA 24 · AAA 31 — 87 criteria

WCAG 2.2 – every success criterion at a glance
Nr.ContentsIn one sentence
1.1 Text Alternatives Principle 1: Perceivable
1.1.1Non-text Content Anything that is not text needs a text alternative – images, icons, charts, controls.
1.2 Time-based Media Principle 1: Perceivable
1.2.1Audio-only and Video-only (Prerecorded) Audio-only needs a transcript; video without sound needs a description.
1.2.2Captions (Prerecorded) Every prerecorded video with sound needs captions.
1.2.3Audio Description or Media Alternative (Prerecorded) What can only be seen must also be available in sound or text.
1.2.4Captions (Live) Live broadcasts need captions too.
1.2.5Audio Description (Prerecorded) Prerecorded video needs audio description – a transcript is no longer enough.
1.2.6Sign Language (Prerecorded) Prerecorded video is additionally interpreted into sign language.
1.2.7Extended Audio Description (Prerecorded) If the dialogue gaps are too short, the video pauses for the description.
1.2.8Media Alternative (Prerecorded) A complete text version exists in addition to everything else.
1.2.9Audio-only (Live) Live audio-only content gets a real-time text alternative.
1.3 Adaptable Principle 1: Perceivable
1.3.1Info and Relationships Structure must exist in the code, not only in the visual design.
1.3.2Meaningful Sequence The order in the code must convey the same meaning as the visual order.
1.3.3Sensory Characteristics Instructions must not rely on shape, colour, size or position alone.
1.3.4Orientation New in WCAG 2.1Content must not be locked to portrait or landscape.
1.3.5Identify Input Purpose New in WCAG 2.1Fields asking for personal data must be machine-identifiable.
1.3.6Identify Purpose New in WCAG 2.1Controls and icons are also marked up machine-readably.
1.4 Distinguishable Principle 1: Perceivable
1.4.1Use of Color Color must never be the only way information is conveyed.
1.4.2Audio Control Sound that starts automatically and runs longer than three seconds must be stoppable.
1.4.3Contrast (Minimum) Text needs a contrast ratio of at least 4.5:1, large text 3:1.
1.4.4Resize Text Text must scale to 200 % without loss of content or function.
1.4.5Images of Text Text should be delivered as text, not as an image.
1.4.6Contrast (Enhanced) Text reaches at least 7:1, large text 4.5:1.
1.4.7Low or No Background Audio Background sound in speech recordings is quiet or can be turned off.
1.4.8Visual Presentation Users can adjust colours, line width, line spacing and alignment.
1.4.9Images of Text (No Exception) Images of text are used only for decoration and logos.
1.4.10Reflow New in WCAG 2.1Content must reflow into narrow viewports without horizontal scrolling.
1.4.11Non-text Contrast New in WCAG 2.1Controls and meaningful graphics need 3:1 contrast too.
1.4.12Text Spacing New in WCAG 2.1Increasing line, word and paragraph spacing must not lose content.
1.4.13Content on Hover or Focus New in WCAG 2.1Content that appears must stay reachable and must not vanish on its own.
2.1 Keyboard Accessible Principle 2: Operable
2.1.1Keyboard Everything must be operable from the keyboard.
2.1.2No Keyboard Trap Keyboard focus must never get stuck.
2.1.3Keyboard (No Exception) Keyboard operability without the exceptions in 2.1.1.
2.1.4Character Key Shortcuts New in WCAG 2.1Single-character shortcuts must be switchable or remappable.
2.2 Enough Time Principle 2: Operable
2.2.1Timing Adjustable Time limits must be adjustable, extendable or removable.
2.2.2Pause, Stop, Hide Moving or auto-updating content must be pausable.
2.2.3No Timing No time limits at all – except for real-time events.
2.2.4Interruptions Interruptions can be postponed or suppressed.
2.2.5Re-authenticating After a session expires, work continues without data loss.
2.2.6Timeouts New in WCAG 2.1Users are warned when inactivity can cause data loss.
2.3 Seizures and Physical Reactions Principle 2: Operable
2.3.1Three Flashes or Below Threshold Nothing may flash more than three times per second.
2.3.2Three Flashes No flashing above three per second at all – without the exceptions in 2.3.1.
2.3.3Animation from Interactions New in WCAG 2.1Motion animation can be disabled.
2.4 Navigable Principle 2: Operable
2.4.1Bypass Blocks Repeated blocks such as navigation must be skippable.
2.4.2Page Titled Every page needs a descriptive title.
2.4.3Focus Order The tab order must be meaningful.
2.4.4Link Purpose (In Context) A link – with its context if need be – must reveal where it goes.
2.4.5Multiple Ways There is more than one way to find a page.
2.4.6Headings and Labels Headings and labels must describe topic or purpose.
2.4.7Focus Visible The focused element must be clearly indicated.
2.4.8Location Users can tell where they are within the site.
2.4.9Link Purpose (Link Only) The link text alone must reveal the destination.
2.4.10Section Headings Longer content is organised with section headings.
2.4.11Focus Not Obscured (Minimum) New in WCAG 2.2The focused element must not be entirely hidden.
2.4.12Focus Not Obscured (Enhanced) New in WCAG 2.2The focused element must not be obscured at all – not even partly.
2.4.13Focus Appearance New in WCAG 2.2The focus indicator needs a minimum size and contrast.
2.5 Input Modalities Principle 2: Operable
2.5.1Pointer Gestures New in WCAG 2.1Anything requiring multiple fingers or a path must also work simply.
2.5.2Pointer Cancellation New in WCAG 2.1An action started by accident must be cancellable.
2.5.3Label in Name New in WCAG 2.1The visible label must be part of the accessible name.
2.5.4Motion Actuation New in WCAG 2.1Functions triggered by shaking or tilting need an alternative.
2.5.5Target Size (Enhanced) New in WCAG 2.1Targets are at least 44 by 44 CSS pixels.
2.5.6Concurrent Input Mechanisms New in WCAG 2.1The available input method must not be restricted.
2.5.7Dragging Movements New in WCAG 2.2Anything draggable must also work without dragging.
2.5.8Target Size (Minimum) New in WCAG 2.2Targets are at least 24 by 24 CSS pixels, or spaced far enough apart.
3.1 Readable Principle 3: Understandable
3.1.1Language of Page The page language must be declared in code.
3.1.2Language of Parts Passages in another language are marked up.
3.1.3Unusual Words Jargon and idioms are explained.
3.1.4Abbreviations Abbreviations are expanded on first use.
3.1.5Reading Level If text requires more than lower secondary education, a simpler version exists.
3.1.6Pronunciation Where pronunciation is needed for meaning, it is provided.
3.2 Predictable Principle 3: Understandable
3.2.1On Focus Focusing an element must not trigger a change of context.
3.2.2On Input Changing a setting must not automatically change context.
3.2.3Consistent Navigation Navigation appears in the same place and order on every page.
3.2.4Consistent Identification The same function is labelled the same way throughout.
3.2.5Change on Request Changes of context happen only on explicit request.
3.2.6Consistent Help New in WCAG 2.2Help mechanisms appear in the same place across pages.
3.3 Input Assistance Principle 3: Understandable
3.3.1Error Identification Input errors must be identified – in text.
3.3.2Labels or Instructions Input fields need labels.
3.3.3Error Suggestion Where possible, suggest how to fix the error.
3.3.4Error Prevention (Legal, Financial, Data) Consequential submissions can be checked, corrected or reversed.
3.3.5Help Context-sensitive help is available for forms.
3.3.6Error Prevention (All) Review, correction and reversal apply to all forms.
3.3.7Redundant Entry New in WCAG 2.2Information already provided is not requested again.
3.3.8Accessible Authentication (Minimum) New in WCAG 2.2Logging in must not require a cognitive function test.
3.3.9Accessible Authentication (Enhanced) New in WCAG 2.2Object or image recognition is not permitted for logging in either.
4.1 Compatible Principle 4: Robust
4.1.1Parsing (removed) Removed in WCAG 2.2Removed in WCAG 2.2 – modern browsers recover from malformed markup.
4.1.2Name, Role, Value Every control must expose its name, role and state programmatically.
4.1.3Status Messages New in WCAG 2.1Messages that appear without focus change must be announced.

Wave Access tests your site against these criteria, corrects some of them in the delivered code, and tells you what to do about the rest.

Discover Wave Access →