WCAG 2.2 Plain English Reference

Every piece of non-text content shown to users has a text alternative that serves the equivalent purpose. Controls and inputs need a name that describes their purpose. Time-based media, tests that would be invalid in text, and content meant to create a specific sensory experience only need a text alternative that identifies them. A CAPTCHA needs a text alternative describing its purpose and a version that uses a different sense. Content that is pure decoration, used only for visual formatting, or not presented to users must be implemented so assistive technology can ignore it.

Prerecorded audio-only content has a text alternative that presents equivalent information (an "alternative for time-based media"). Prerecorded video-only content has either that text alternative or an audio track with equivalent information. Media that is itself an alternative for text, and clearly labeled as such, is exempt.

Prerecorded audio in synchronized media (video with sound) has captions. By definition, captions cover both speech and the non-speech audio needed to understand the content. Media that is a clearly labeled alternative for text is exempt.

Prerecorded video with sound has either a full text alternative for time-based media or audio description of the video. Media that is a clearly labeled alternative for text is exempt.

Live audio in synchronized media, such as a live-streamed event with video, has captions.

Prerecorded video in synchronized media has audio description: narration added to describe important visual details that can't be understood from the main soundtrack alone.

Information, structure and relationships conveyed through presentation can be programmatically determined, or are available in text. If something looks like a heading, list, table or group, that structure has to be available to software too.

When the order of content affects its meaning, a correct reading order can be programmatically determined.

Instructions for understanding and operating content don't rely solely on sensory characteristics such as shape, color, size, visual location, orientation or sound.

Content doesn't restrict its view and operation to a single display orientation (portrait or landscape) unless a specific orientation is essential.

Input fields collecting information about the user have a programmatically determinable purpose, when the field's purpose is one listed in WCAG's Input Purposes section and the technology supports it. (In HTML, W3C's sufficient technique is the autocomplete attribute; techniques are informative.)

Color is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

If audio plays automatically for more than 3 seconds, there is either a way to pause or stop it, or a way to control its volume separately from the system volume. Under WCAG's non-interference requirement this applies to everything on the page, even content not relied on to meet other criteria.

Text and images of text have a contrast ratio of at least 4.5:1. Large-scale text (at least 18pt, or 14pt bold) needs 3:1. Text in inactive components, pure decoration, invisible text, text inside pictures with significant other visual content, and logos have no contrast requirement.

Apart from captions and images of text, text can be resized up to 200 percent without assistive technology and without loss of content or functionality.

If the technology can produce the visual presentation, real text is used instead of images of text. Exceptions: the image of text can be visually customized (font, size, color and background can be set), or a particular presentation is essential.

Content can be presented without losing information or functionality, and without scrolling in two directions, at a width of 320 CSS pixels (for vertically scrolling content) or a height of 256 CSS pixels (for horizontally scrolling content). Parts of the content that need a two-dimensional layout for their use or meaning are exempt.

These have a contrast ratio of at least 3:1 against adjacent colors: the visual information needed to identify user interface components and their states (except inactive components, and components whose appearance is set by the browser and not modified by the author), and the parts of graphics needed to understand the content (unless a particular presentation is essential).

In content built with markup languages, nothing is lost and nothing stops working when a user sets line height to 1.5 times the font size, spacing after paragraphs to 2 times, letter spacing to 0.12 times and word spacing to 0.16 times, changing no other style. Languages and scripts that don't use one of these properties are exempt for that property.

When hover or keyboard focus makes extra content appear (such as a custom tooltip or submenu): it can be dismissed without moving the pointer or focus, unless it shows an input error or doesn't cover other content; if triggered by hover, the pointer can move onto it without it disappearing; and it stays visible until the trigger is removed, the user dismisses it, or its information is no longer valid. Content whose presentation the browser controls, such as a title-attribute tooltip, is exempt.

All functionality can be operated through a keyboard interface, without needing specific timing for individual keystrokes. The exception is functionality whose underlying function depends on the path of the user's movement, not just its endpoints (such as freehand drawing).

If keyboard focus can move into a component, it can move out again using only the keyboard. If leaving needs more than unmodified arrow or Tab keys or another standard exit method, the user is told how. Under WCAG's non-interference requirement this applies to everything on the page.

If a keyboard shortcut uses only a letter, punctuation, number or symbol key, at least one of these is true: it can be turned off; it can be remapped to include a non-printable key such as Ctrl or Alt; or it only works while the relevant component has focus.

For each time limit the content sets, at least one is true: the user can turn it off before reaching it; adjust it to at least ten times the default; or is warned before it expires and given at least 20 seconds to extend it with a simple action, at least ten times. The limit is exempt if it's a required part of a real-time event with no possible alternative, if it's essential and extending it would invalidate the activity, or if it's longer than 20 hours.

Moving, blinking or scrolling information that starts automatically, lasts more than five seconds and is shown alongside other content can be paused, stopped or hidden, unless the movement is essential. Auto-updating information that starts automatically and is shown alongside other content can be paused, stopped or hidden, or its update frequency controlled, unless essential. Under WCAG's non-interference requirement this applies to everything on the page.

Nothing on the page flashes more than three times in any one second, or the flashing is below the general flash and red flash thresholds defined in WCAG. Under WCAG's non-interference requirement this applies to everything on the page.

A mechanism is available to bypass blocks of content that are repeated on multiple pages.

Pages have titles that describe their topic or purpose.

If a page can be navigated sequentially and the order affects meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

The purpose of each link can be determined from its text alone, or from its text together with its programmatically determined context, except where the purpose would be ambiguous to everyone.

The headings and labels you provide describe their topic or purpose.

Any keyboard-operable interface has a mode of operation in which the keyboard focus indicator is visible.

When a component receives keyboard focus, it is not entirely hidden by content the author created.

For components whose label includes text or images of text, the accessible name contains the text that is shown visually.

Functionality that uses dragging can also be done with a single pointer without dragging, unless dragging is essential or the browser provides the functionality and the author hasn't modified it.

Pointer targets are at least 24 by 24 CSS pixels, except when: a 24 CSS pixel circle centered on each smaller target doesn't overlap another target or another such circle; the same function is available through another control on the page that meets this criterion; the target is in a sentence or limited by the line height of surrounding text; the browser sets the size and the author hasn't changed it; or the presentation is essential or legally required.

The default human language of each page can be programmatically determined. (In HTML, W3C's sufficient technique is the lang attribute on the html element; techniques are informative.)

The human language of each passage or phrase can be programmatically determined. Exempt: proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the surrounding language.

When any component receives focus, that doesn't start a change of context. WCAG defines a change of context as a change of user agent, viewport, focus, or content that changes the meaning of the page.

Changing the setting of a component doesn't automatically cause a change of context, unless the user was told about this behavior before using the component.

If pages in a set repeat any of these help mechanisms, they appear in the same order relative to other page content, unless the user changes it: human contact details, a human contact mechanism, a self-help option, or a fully automated contact mechanism.

If an input error is automatically detected, the item in error is identified and the error is described to the user in text.

Labels or instructions are provided when content requires user input. WCAG defines a label as text, or a component with a text alternative, presented to the user to identify a component.

Information the user has already entered, or that was provided to them, and that must be entered again in the same process, is either auto-populated or available to select. Exceptions: re-entry is essential, is needed for security, or the earlier information is no longer valid.

No step of an authentication process requires a cognitive function test, unless that step offers one of: another method that doesn't rely on one; a mechanism to help complete it; a test that is recognizing objects; or a test that is identifying non-text content the user provided. WCAG defines a cognitive function test as remembering, manipulating or transcribing information, such as remembering a password, transcribing characters, correct spelling, calculations or puzzles. Name, email and phone number don't count.

For all interface components (including form elements, links and scripted components), the name and role can be programmatically determined; states, properties and values the user can set can be programmatically set; and changes to them are notified to user agents, including assistive technologies.

In content built with markup languages, status messages can be programmatically determined through role or properties, so assistive technologies can present them without them receiving focus. WCAG defines a status message as a change in content that isn't a change of context and that tells the user about success or results, waiting, progress, or errors.

Prerecorded audio in synchronized media has sign language interpretation.

Where pauses in the foreground audio are too short for audio description to convey the sense of the video, extended audio description is provided: the video pauses so there is time for more description. Applies to prerecorded video in synchronized media.

All prerecorded synchronized media and all prerecorded video-only media have an alternative for time-based media: a document with correctly sequenced text descriptions of the visual and auditory information, and a way to achieve the outcome of any interaction.

Text and images of text have a contrast ratio of at least 7:1, and large-scale text at least 4.5:1, with the same exceptions as 1.4.3.

For prerecorded audio-only content that is mainly foreground speech (not an audio CAPTCHA, audio logo, or singing or rapping), one of these is true: there are no background sounds, they can be turned off, or they are at least 20 decibels quieter than the speech, apart from occasional sounds of one or two seconds.

For blocks of text, a mechanism is available to: choose foreground and background colors; limit width to 80 characters (40 for CJK); avoid justified text; get line spacing of at least 1.5 and paragraph spacing at least 1.5 times the line spacing; and resize text to 200 percent without horizontal scrolling in a full-screen window.

Images of text are used only for pure decoration, or where a particular presentation of text is essential.

All functionality can be operated through a keyboard interface without needing specific timing for individual keystrokes. Unlike 2.1.1, there is no exception for path-dependent input.

Timing is not an essential part of the event or activity, except for non-interactive synchronized media and real-time events.

The user can postpone or suppress interruptions, except interruptions involving an emergency.

Nothing on the page flashes more than three times in any one second. Unlike 2.3.1, there is no threshold exception for small or dim flashes.

Information about the user's location within a set of pages is available.

A mechanism is available so that the purpose of each link can be identified from the link text alone, except where the purpose would be ambiguous to everyone.

Section headings are used to organize the content.

Pointer targets are at least 44 by 44 CSS pixels. Exceptions: an equivalent target of that size is on the same page; the target is in a sentence or block of text; the browser sets the size and the author hasn't changed it; or the presentation is essential.

A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.

A mechanism is available for identifying the expanded form or meaning of abbreviations.

When text needs reading ability above lower secondary education level (after removing proper names and titles), supplemental content or a simpler version is available.

Changes of context happen only at the user's request, or there's a mechanism to turn such changes off.

Context-sensitive help is available: help text related to the function currently being performed. A general help page doesn't meet the definition.

For pages that require the user to submit information, at least one is true: submissions are reversible; input is checked and the user can correct it; or the user can review, confirm and correct before final submission.

Live audio-only content, such as a live audio stream, has an alternative that presents equivalent information.

In content built with markup languages, the purpose of user interface components, icons and regions can be programmatically determined.

When an authenticated session expires, the user can continue the activity without losing data after signing in again.

Users are warned how long they can be inactive before data is lost, unless the data is kept for more than 20 hours of inactivity.

Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information conveyed.

There is more than one way to find a page within a set of pages, except pages that are the result of, or a step in, a process.

When a component receives keyboard focus, no part of it is hidden by content the author created.

When the focus indicator is visible, an area of it is at least as large as a 2 CSS pixel thick perimeter of the unfocused component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states. It doesn't apply if the browser sets the indicator and the author can't adjust it, or if the author hasn't modified the indicator or its background.

Functionality that uses multipoint gestures (such as pinch) or path-based gestures (such as a swipe pattern) can also be operated with a single pointer without a path-based gesture, unless the gesture is essential.

For single-pointer functionality, at least one is true: nothing happens on the down-event; the function completes on the up-event and can be aborted before or undone after; the up-event reverses whatever the down-event did; or completing on the down-event is essential.

Functionality operated by device motion (such as shaking or tilting) or user motion can also be operated through interface components, and responding to motion can be turned off. Exceptions: the motion works through an accessibility-supported interface, or it's essential and doing it another way would invalidate the activity.

Content doesn't restrict the input methods available on a platform, except where that is essential, needed for security, or needed to respect user settings.

A mechanism is available for identifying the pronunciation of words whose meaning, in context, is ambiguous without knowing how they're pronounced.

Navigation that is repeated on multiple pages within a set of pages appears in the same relative order each time, unless the user changes it.

Components with the same functionality within a set of pages are identified consistently.

If an input error is automatically detected and suggestions for correcting it are known, the suggestions are provided, unless that would compromise the security or purpose of the content.

For pages that create legal commitments or financial transactions, modify or delete user-controllable data, or submit test responses, at least one is true: submissions are reversible; input is checked for errors and the user can correct them; or the user can review, confirm and correct before final submission.

No step of an authentication process requires a cognitive function test, unless that step offers another method that doesn't rely on one, or a mechanism to help complete it. Unlike 3.3.8, there are no object-recognition or personal-content exceptions.

Nothing. WCAG 2.2 marks this criterion obsolete and removed, so it can't be failed under 2.2. WCAG 2.2's introduction notes that organizations required by policy to conform to WCAG 2.0 or 2.1 may still need to test and report it.