Reference
WCAG 2.2 success criteria, in plain English
The Web Content Accessibility Guidelines are the global standard for digital accessibility — and the baseline the European Accessibility Act expects. Here are the Level A and AA criteria that apply to most websites, each explained simply with how to fix it.
55 criteria · grouped by the four WCAG principles. Each links to a detailed page.
Perceivable
Information and interface components must be presentable to users in ways they can perceive.
- 1.1.1Non-text ContentAAll meaningful images, icons and other non-text content need a text alternative that conveys the same information; decorative images should be hidden from assistive tech.
- 1.2.1Audio-only and Video-only (Prerecorded)APrerecorded audio-only and video-only content needs an equivalent alternative (a transcript, or audio describing the video).
- 1.2.2Captions (Prerecorded)APrerecorded video with sound must have synchronised captions.
- 1.2.3Audio Description or Media Alternative (Prerecorded)APrerecorded video needs either audio description of important visuals or a full text alternative.
- 1.2.4Captions (Live)AALive audio in synchronised media must have real-time captions.
- 1.2.5Audio Description (Prerecorded)AAPrerecorded video must include audio description of meaningful visual detail.
- 1.3.1Info and RelationshipsAStructure conveyed visually (headings, lists, tables, labels) must also be available in the markup so assistive tech can perceive it.
- 1.3.2Meaningful SequenceAWhen the order of content matters, the DOM/reading order must match the visual order.
- 1.3.3Sensory CharacteristicsAInstructions must not rely only on shape, size, colour, or position ("click the round button on the right").
- 1.3.4OrientationAAContent must not be locked to a single display orientation unless essential.
- 1.3.5Identify Input PurposeAAThe purpose of common input fields (name, email, address) must be programmatically identifiable.
- 1.4.1Use of ColorAColour must not be the only way information is conveyed (e.g. error state, required field, links in text).
- 1.4.2Audio ControlAIf audio plays automatically for more than 3 seconds, users must be able to pause or stop it.
- 1.4.3Contrast (Minimum)AAText must have a contrast ratio of at least 4.5:1 (3:1 for large text) against its background.
- 1.4.4Resize TextAAText must be resizable up to 200% without loss of content or functionality, and users must be able to zoom.
- 1.4.5Images of TextAAUse real text instead of images of text wherever possible.
- 1.4.10ReflowAAContent must reflow to a single column at 320px width without horizontal scrolling.
- 1.4.11Non-text ContrastAAUI components and meaningful graphics need at least 3:1 contrast against adjacent colours.
- 1.4.12Text SpacingAANo loss of content when users override line height, paragraph, letter and word spacing.
- 1.4.13Content on Hover or FocusAATooltips/popovers shown on hover or focus must be dismissible, hoverable, and persistent.
Operable
Interface components and navigation must be operable by everyone.
- 2.1.1KeyboardAAll functionality must be operable with a keyboard alone.
- 2.1.2No Keyboard TrapAKeyboard focus must never get trapped in a component with no way out.
- 2.1.4Character Key ShortcutsASingle-character key shortcuts must be remappable or only active on focus.
- 2.2.1Timing AdjustableAUsers must be able to turn off, adjust or extend time limits.
- 2.2.2Pause, Stop, HideAMoving, blinking or auto-updating content must be pausable or stoppable.
- 2.3.1Three Flashes or Below ThresholdAContent must not flash more than three times per second.
- 2.4.1Bypass BlocksAProvide a way to skip repeated blocks of content, such as a skip-to-content link or landmarks.
- 2.4.2Page TitledAEvery page needs a descriptive, unique <title>.
- 2.4.3Focus OrderAFocus order must follow a logical, meaningful sequence.
- 2.4.4Link Purpose (In Context)AThe purpose of each link should be clear from its text (or immediate context).
- 2.4.5Multiple WaysAAProvide more than one way to find pages (e.g. nav plus search or sitemap).
- 2.4.6Headings and LabelsAAHeadings and labels must describe their topic or purpose.
- 2.4.7Focus VisibleAAKeyboard focus must be clearly visible.
- 2.4.11Focus Not Obscured (Minimum)AANew in 2.2When an element gets focus, it must not be entirely hidden by other content (e.g. sticky headers).
- 2.5.1Pointer GesturesAMulti-point or path-based gestures must have a single-pointer alternative.
- 2.5.2Pointer CancellationAActions triggered by a single pointer must be cancellable (fire on up-event, allow abort).
- 2.5.3Label in NameAA control's accessible name must contain its visible label text.
- 2.5.4Motion ActuationAFunctions triggered by device motion must have a UI alternative and be disableable.
- 2.5.7Dragging MovementsAANew in 2.2Any dragging action must have a single-pointer alternative that isn't a drag.
- 2.5.8Target Size (Minimum)AANew in 2.2Pointer targets must be at least 24×24 CSS pixels (with exceptions).
Understandable
Information and the operation of the interface must be understandable.
- 3.1.1Language of PageAThe default human language of the page must be set in the markup.
- 3.1.2Language of PartsAAPassages in a different language must be marked up with their language.
- 3.2.1On FocusAMoving focus to a component must not trigger an unexpected change of context.
- 3.2.2On InputAChanging a setting must not automatically cause an unexpected context change.
- 3.2.3Consistent NavigationAANavigation repeated across pages must stay in a consistent order.
- 3.2.4Consistent IdentificationAAComponents with the same function must be identified consistently.
- 3.2.6Consistent HelpANew in 2.2Help mechanisms (contact, chat, FAQ) must appear in a consistent location across pages.
- 3.3.1Error IdentificationAInput errors must be identified and described in text.
- 3.3.2Labels or InstructionsAForm controls need labels or instructions so users know what to enter.
- 3.3.3Error SuggestionAAWhen an input error is detected and a fix is known, suggest it.
- 3.3.4Error Prevention (Legal, Financial, Data)AAFor legal/financial/data submissions, changes must be reversible, checked, or confirmed.
- 3.3.7Redundant EntryANew in 2.2Don't ask users to re-enter information they already provided in the same process.
- 3.3.8Accessible Authentication (Minimum)AANew in 2.2Don't require a cognitive function test (like remembering a password or solving a puzzle) without an alternative.
Robust
Content must be robust enough to work with current and future assistive technologies.
Check your site against AccessScan
See your issues ranked by impact in seconds — free.
Run a free accessibility scan