Accessibility resource

WCAG 2.2 Reference

The complete Web Content Accessibility Guidelines, organized by principle, guideline, and success criterion — searchable and filterable by version and conformance level.

4
Principles
13
Guidelines
86
Success criteria
A · AA · AAA
Conformance levels
Version
Level

Showing 86 of 86 success criteria

1.1.1 Non-text Content

A2.0

All non-text content that is presented to the user has a text alternative

Requirements:
  • Images, image buttons, and image map hot spots have appropriate, equivalent alternative text
  • Images that do not convey content are given empty alternative text (alt="") or implemented as CSS backgrounds
  • Equivalent alternatives to complex images are provided in context or on a separate linked page
  • Form buttons have a descriptive value
  • Inputs have associated accessible names
  • Embedded multimedia is identified via accessible text
  • Frames and iframes are appropriately titled

1.2.1 Audio-only and Video-only (Prerecorded)

A2.0

For prerecorded audio-only and prerecorded video-only media

Requirements:
  • A descriptive transcript of relevant content is provided for non-live audio-only
  • A descriptive transcript or audio description is provided for non-live video-only

1.2.2 Captions (Prerecorded)

A2.0

Captions are provided for all prerecorded audio content

Requirements:
  • Synchronized captions are provided for non-live video (YouTube videos, etc.)

1.2.3 Audio Description or Media Alternative (Prerecorded)

A2.0

An alternative for time-based media or audio description of the prerecorded video content is provided

Requirements:
  • Audio descriptions or media alternative is provided for prerecorded video
  • Alternative may be text-based or audio track

1.2.4 Captions (Live)

AA2.0

Captions are provided for all live audio content

Requirements:
  • Synchronized captions are provided for live media that contains audio

1.2.5 Audio Description (Prerecorded)

AA2.0

Audio description is provided for all prerecorded video content

Requirements:
  • Audio descriptions are provided for non-live video
  • Only required if there is relevant visual content not presented in audio

1.2.6 Sign Language (Prerecorded)

AAA2.0

Sign language interpretation is provided for all prerecorded audio content in synchronized media

Requirements:
  • Sign language interpretation is provided for prerecorded audio

1.2.7 Extended Audio Description (Prerecorded)

AAA2.0

Extended audio description is provided for all prerecorded video content where pauses in foreground audio are insufficient

Requirements:
  • Extended audio description with video pausing is provided when normal audio description is insufficient

1.2.8 Media Alternative (Prerecorded)

AAA2.0

An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media

Requirements:
  • Full text alternative is provided for all prerecorded media

1.2.9 Audio-only (Live)

AAA2.0

An alternative for time-based media that presents equivalent information for live audio-only content is provided

Requirements:
  • Alternative presentation of live audio content is provided

1.3.1 Info and Relationships

A2.0

Information, structure, and relationships conveyed through presentation can be programmatically determined

Requirements:
  • Semantic markup is appropriately used to designate headings, regions/landmarks, lists, emphasized text
  • Tables are used for tabular data and data cells are associated with their headers
  • Text labels are associated with form inputs. Related form controls are grouped with fieldset/legend

1.3.2 Meaningful Sequence

A2.0

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined

Requirements:
  • Content is presented in a meaningful order when linearized
  • Navigation order through content is logical and intuitive

1.3.3 Sensory Characteristics

A2.0

Instructions do not rely solely on sensory characteristics such as shape, size, visual location, orientation, or sound

Requirements:
  • Instructions use more than just shape, size, location, or sound
  • References to content include textual identification in addition to sensory characteristics

1.3.4 Orientation

AA2.1

Content does not restrict its view and operation to a single display orientation

Requirements:
  • Orientation of web content is not restricted to only portrait or landscape, unless a specific orientation is necessary

1.3.5 Identify Input Purpose

AA2.1

The purpose of each input field collecting information about the user can be programmatically determined

Requirements:
  • Input fields that collect certain types of user information have an appropriate autocomplete attribute defined

1.3.6 Identify Purpose

AAA2.1

The purpose of user interface components, icons, and regions can be programmatically determined

Requirements:
  • Markup is used to identify the purpose of UI components, icons, and regions

1.4.1 Use of Color

A2.0

Color is not used as the sole method of conveying information

Requirements:
  • Color is not used as the sole method of conveying content or distinguishing visual elements
  • Color alone is not used to distinguish links from surrounding text unless the contrast ratio is at least 3:1

1.4.2 Audio Control

A2.0

If any audio on a Web page plays automatically for more than 3 seconds, a mechanism is available to pause or stop the audio

Requirements:
  • Auto-playing audio can be paused, stopped, or its volume controlled
  • Audio longer than 3 seconds must have user controls

1.4.3 Contrast (Minimum)

AA2.0

The visual presentation of text and images has a contrast ratio of at least 4.5:1

Requirements:
  • Text and images of text have a contrast ratio of at least 4.5:1
  • Large text has a contrast ratio of at least 3:1

1.4.4 Resize Text

AA2.0

Text can be resized without assistive technology up to 200 percent without loss of content or functionality

Requirements:
  • Text can be zoomed to 200% without loss of content or functionality

1.4.5 Images of Text

AA2.0

Text is used to convey information rather than images of text except for customizable or essential presentations

Requirements:
  • Use actual text rather than images of text when technology allows
  • Images of text are only used when essential or customizable

1.4.6 Contrast (Enhanced)

AAA2.0

The visual presentation of text and images has a contrast ratio of at least 7:1

Requirements:
  • Text and images of text have a contrast ratio of at least 7:1
  • Large text has a contrast ratio of at least 4.5:1

1.4.7 Low or No Background Audio

AAA2.0

For prerecorded audio-only content, background sounds are minimal or can be turned off

Requirements:
  • Background sounds are 20 decibels lower than foreground speech
  • Background sounds can be turned off

1.4.8 Visual Presentation

AAA2.0

For blocks of text, a mechanism is available to achieve various presentation options

Requirements:
  • Foreground and background colors can be selected
  • Width is no more than 80 characters
  • Text is not justified
  • Line spacing is at least 1.5 within paragraphs
  • Text can be resized to 200% without horizontal scrolling

1.4.9 Images of Text (No Exception)

AAA2.0

Images of text are only used for pure decoration or where essential

Requirements:
  • Images of text are only used when absolutely necessary

1.4.10 Reflow

AA2.1

Content can be presented without loss of information or functionality at 320px width

Requirements:
  • No loss of content or functionality occurs when content is presented at 320px width
  • This requires responsive design for most web sites

1.4.11 Non-text Contrast

AA2.1

The visual presentation of user interface components and graphical objects has sufficient contrast

Requirements:
  • A contrast ratio of at least 3:1 is present for differentiating graphical objects and interface components
  • At least 3:1 contrast is maintained in various states (focus, hover, active, etc.)

1.4.12 Text Spacing

AA2.1

No loss of content or functionality occurs when text spacing is adjusted

Requirements:
  • Content adapts when line height is set to 1.5 times the font size
  • Content adapts when paragraph spacing is set to 2 times the font size
  • Content adapts when letter spacing is set to 0.12 times the font size
  • Content adapts when word spacing is set to 0.16 times the font size

1.4.13 Content on Hover or Focus

AA2.1

Additional content that appears on hover or focus can be dismissed, is hoverable, and remains visible

Requirements:
  • Additional content can be dismissed without moving pointer or focus
  • Pointer can move over additional content without it disappearing
  • Additional content remains visible until dismissed or no longer valid

2.1.1 Keyboard

A2.0

All functionality of the content is operable through a keyboard interface

Requirements:
  • All page functionality is available using the keyboard
  • Page-specified shortcut keys do not conflict with existing browser and screen reader shortcuts

2.1.2 No Keyboard Trap

A2.0

If keyboard focus can be moved to a component, it can be moved away from that component

Requirements:
  • Keyboard focus is never locked or trapped at one particular page element
  • The user can navigate to and from all navigable page elements using only a keyboard

2.1.3 Keyboard (No Exception)

AAA2.0

All functionality of the content is operable through a keyboard interface without requiring specific timings

Requirements:
  • All functionality is keyboard accessible without path-dependent input

2.1.4 Character Key Shortcuts

A2.1

If a keyboard shortcut is implemented using only letter, punctuation, number, or symbol characters, then at least one of the following is true

Requirements:
  • If a keyboard shortcut uses printable character keys, then the user must be able to disable the key command, change the defined key, or only activate when focused

2.2.1 Timing Adjustable

A2.0

For each time limit that is set by the content, the user can turn off, adjust, or extend the time limit

Requirements:
  • Users can turn off time limits before encountering them
  • Users can adjust time limits over a wide range (at least 10x default)
  • Users are warned before time expires and can extend it

2.2.2 Pause, Stop, Hide

A2.0

For moving, blinking, scrolling, or auto-updating information, users can pause, stop, or hide it

Requirements:
  • Moving, blinking, or scrolling content lasting more than 5 seconds can be paused, stopped, or hidden
  • Auto-updating information can be paused, stopped, hidden, or its frequency controlled

2.2.3 No Timing

AAA2.0

Timing is not an essential part of the event or activity

Requirements:
  • Content does not require timed responses except for real-time events

2.2.4 Interruptions

AAA2.0

Interruptions can be postponed or suppressed by the user

Requirements:
  • Non-emergency interruptions can be postponed or suppressed

2.2.5 Re-authenticating

AAA2.0

When an authenticated session expires, the user can continue without loss of data after re-authenticating

Requirements:
  • Users can continue activity without data loss after re-authentication

2.2.6 Timeouts

AAA2.1

Users are warned of the duration of any user inactivity that could cause data loss

Requirements:
  • Users are warned about inactivity timeouts that could cause data loss

2.3.1 Three Flashes or Below Threshold

A2.0

Web pages do not contain anything that flashes more than three times in any one second period

Requirements:
  • Content does not flash more than 3 times per second
  • Flash is below general flash and red flash thresholds

2.3.2 Three Flashes

AAA2.0

Web pages do not contain anything that flashes more than three times in any one second period

Requirements:
  • No content flashes more than 3 times per second

2.3.3 Animation from Interactions

AAA2.1

Motion animation triggered by interaction can be disabled

Requirements:
  • Animation from interactions can be disabled unless essential

2.4.1 Bypass Blocks

A2.0

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

Requirements:
  • A link is provided to skip navigation and other page elements that are repeated across web pages
  • While proper use of headings or regions/landmarks is sufficient, WebAIM recommends a "skip" link

2.4.2 Page Titled

A2.0

Web pages have titles that describe topic or purpose

Requirements:
  • The web page has a descriptive and informative page title

2.4.3 Focus Order

A2.0

If a Web page can be navigated sequentially, focusable components receive focus in an order that preserves meaning

Requirements:
  • The navigation order of links, form controls, etc. is logical and intuitive

2.4.4 Link Purpose (In Context)

A2.0

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context

Requirements:
  • Link purpose is clear from link text or surrounding context

2.4.5 Multiple Ways

AA2.0

More than one way is available to locate a Web page within a set of Web pages

Requirements:
  • Multiple ways to find pages are provided (e.g., search, sitemap, navigation)

2.4.6 Headings and Labels

AA2.0

Headings and labels describe topic or purpose

Requirements:
  • Page headings and labels for form and interactive controls are informative
  • Avoid duplicating heading and label text unless the structure provides adequate differentiation

2.4.7 Focus Visible

AA2.0

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible

Requirements:
  • There is a visible indicator for page elements when they receive keyboard focus

2.4.8 Location

AAA2.0

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

Requirements:
  • Users can determine their location within a website (e.g., breadcrumbs)

2.4.9 Link Purpose (Link Only)

AAA2.0

A mechanism is available to allow the purpose of each link to be identified from link text alone

Requirements:
  • Link purpose can be determined from link text alone

2.4.10 Section Headings

AAA2.0

Section headings are used to organize the content

Requirements:
  • Headings are used to organize content into sections

2.4.11 Focus Not Obscured (Minimum)

AA2.2

When a user interface component receives keyboard focus, the component is not entirely hidden

Requirements:
  • When elements have keyboard focus, they are not entirely covered or hidden by page content

2.4.12 Focus Not Obscured (Enhanced)

AAA2.2

When a user interface component receives keyboard focus, no part of the component is hidden by author-created content

Requirements:
  • Focused elements are not partially obscured by other content

2.4.13 Focus Appearance

AAA2.2

When the keyboard focus indicator is visible, the focus indicator meets minimum size and contrast requirements

Requirements:
  • Focus indicator is at least 2 CSS pixels thick
  • Focus indicator has sufficient contrast (3:1) against adjacent colors

2.5.1 Pointer Gestures

A2.1

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer

Requirements:
  • If multipoint or path-based gestures are not essential to functionality, then functionality can be performed with single point activation

2.5.2 Pointer Cancellation

A2.1

For functionality that can be operated using a single pointer, at least one of the following is true

Requirements:
  • To help avoid inadvertent activation of controls, avoid non-essential down-event activation when clicking, tapping, or long pressing

2.5.3 Label in Name

A2.1

For user interface components with labels that include text or images of text, the name contains the text that is presented visually

Requirements:
  • If an interface component presents text, the accessible name for that component must include the visible text

2.5.4 Motion Actuation

A2.1

Functionality that can be operated by device motion or user motion can also be operated by user interface components

Requirements:
  • Functionality triggered by moving the device or by user movement can be disabled and equivalent functionality is provided via standard controls

2.5.5 Target Size (Enhanced)

AAA2.1

The size of the target for pointer inputs is at least 44 by 44 CSS pixels

Requirements:
  • Target size is at least 44×44 pixels unless specific exceptions apply

2.5.6 Concurrent Input Mechanisms

AAA2.1

Web content does not restrict use of input modalities available on a platform

Requirements:
  • Content can be operated using various input methods (touch, keyboard, mouse, voice)

2.5.7 Dragging Movements

AA2.2

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging

Requirements:
  • Functionality that uses pointer dragging can also be achieved using a single pointer without dragging (unless dragging is essential)

2.5.8 Target Size (Minimum)

AA2.2

The size of the target for pointer inputs is at least 24 by 24 CSS pixels

Requirements:
  • Pointer input target sizes are at least 24 by 24 pixels unless specific exceptions apply

3.1.1 Language of Page

A2.0

The default human language of each Web page can be programmatically determined

Requirements:
  • The language of the page is identified using the lang attribute (e.g., <html lang="en">)

3.1.2 Language of Parts

AA2.0

The human language of each passage or phrase can be programmatically determined

Requirements:
  • The language of page content that is in a different language is identified using the lang attribute

3.1.3 Unusual Words

AAA2.0

A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way

Requirements:
  • Definitions are provided for unusual words, idioms, and jargon

3.1.4 Abbreviations

AAA2.0

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

Requirements:
  • Expanded forms or definitions of abbreviations are provided

3.1.5 Reading Level

AAA2.0

When text requires reading ability more advanced than lower secondary education level, supplemental content or an alternative version is available

Requirements:
  • Supplemental content or simpler version provided for advanced reading level text

3.1.6 Pronunciation

AAA2.0

A mechanism is available for identifying specific pronunciation of words where meaning is ambiguous without knowing pronunciation

Requirements:
  • Pronunciation information provided for ambiguous words

3.2.1 On Focus

A2.0

When any user interface component receives focus, it does not initiate a change of context

Requirements:
  • When a page element receives focus, it does not result in a substantial change to the page, spawning pop-ups, or other changes that could confuse users

3.2.2 On Input

A2.0

Changing the setting of any user interface component does not automatically cause a change of context

Requirements:
  • When a user inputs information or interacts with a control, it does not result in substantial changes unless the user is informed ahead of time

3.2.3 Consistent Navigation

AA2.0

Navigational mechanisms that are repeated on multiple Web pages occur in the same relative order each time they are repeated

Requirements:
  • Navigation links that are repeated on web pages do not change order when navigating through the site

3.2.4 Consistent Identification

AA2.0

Components that have the same functionality within a set of Web pages are identified consistently

Requirements:
  • Components with same functionality have consistent identification across pages

3.2.5 Change on Request

AAA2.0

Changes of context are initiated only by user request or a mechanism is available to turn off such changes

Requirements:
  • Context changes only happen on user request or can be turned off

3.2.6 Consistent Help

A2.2

If a Web page contains help mechanisms, those mechanisms are presented in the same relative order

Requirements:
  • Contact and self-help details or functionality are presented consistently when present on multiple web pages

3.3.1 Error Identification

A2.0

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

Requirements:
  • Required inputs or inputs that require a specific format provide this information within the element's label
  • Form validation errors are efficient, intuitive, and accessible

3.3.2 Labels or Instructions

A2.0

Labels or instructions are provided when content requires user input

Requirements:
  • Inputs are identified by labels or instructions that help users know what information to enter

3.3.3 Error Suggestion

AA2.0

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user

Requirements:
  • If an input error is detected, suggestions are provided for fixing the input in a timely and accessible manner

3.3.4 Error Prevention (Legal, Financial, Data)

AA2.0

For pages causing legal commitments or financial transactions, submissions are reversible, checked, or confirmed

Requirements:
  • Legal/financial transactions can be reversed, checked, or confirmed before completion

3.3.5 Help

AAA2.0

Context-sensitive help is available

Requirements:
  • Context-sensitive help is available for form inputs

3.3.6 Error Prevention (All)

AAA2.0

For pages requiring user to submit information, submissions are reversible, checked, or confirmed

Requirements:
  • All form submissions can be reversed, checked, or confirmed

3.3.7 Redundant Entry

A2.2

Information previously entered by or provided to the user that is required to be entered again is either auto-populated or available for the user to select

Requirements:
  • Information that a user must re-enter to complete a process must be auto-populated or available for selection

3.3.8 Accessible Authentication (Minimum)

AA2.2

A cognitive function test is not required for any step in an authentication process

Requirements:
  • A cognitive function test is not required for authentication unless it can be bypassed or completed with assistance

3.3.9 Accessible Authentication (Enhanced)

AAA2.2

A cognitive function test is not required for any step in an authentication process

Requirements:
  • No cognitive function tests are required for authentication

4.1.2 Name, Role, Value

A2.0

For all user interface components, the name and role can be programmatically determined

Requirements:
  • Markup is used in a way that facilitates accessibility
  • ARIA is used appropriately to enhance accessibility when HTML is not sufficient

4.1.3 Status Messages

AA2.1

In content implemented using markup languages, status messages can be programmatically determined

Requirements:
  • If an important status message is presented and focus is not set to that message, the message must be announced to screen reader users

See how your PDFs score against WCAG 2.2

Upload a document and get a criterion-by-criterion accessibility report in seconds.

This reference is based on Web Content Accessibility Guidelines (WCAG) 2.2 from the W3C.