WCAG Success
Criteria Explorer
Customizable quick reference to WCAG 2.0-2.2 requirements. Filter by level, principle, and version
Explore Criteria87of 87 success criteria
Principle 1 – Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
Guideline 1.1 – Text Alternatives
Provide text alternatives for non-text content.
1 success criterion
Non-text Content
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for controls, input, time-based media, tests, sensory experiences, CAPTCHAs, and decoration.
Guideline 1.2 – Time-based Media
Provide alternatives for time-based media.
9 success criteria
Audio-only and Video-only (Prerecorded)
For prerecorded audio-only and prerecorded video-only media, an alternative for time-based media is provided that presents equivalent information, except when the media is a media alternative for text and is clearly labeled as such.
Captions (Prerecorded)
Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Audio Description or Media Alternative (Prerecorded)
An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Captions (Live)
Captions are provided for all live audio content in synchronized media.
Audio Description (Prerecorded)
Audio description is provided for all prerecorded video content in synchronized media.
Sign Language (Prerecorded)
Sign language interpretation is provided for all prerecorded audio content in synchronized media.
Extended Audio Description (Prerecorded)
Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.
Media Alternative (Prerecorded)
An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.
Audio-only (Live)
An alternative for time-based media that presents equivalent information for live audio-only content is provided.
Guideline 1.3 – Adaptable
Create content that can be presented in different ways.
6 success criteria
Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Meaningful Sequence
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Sensory Characteristics
Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.
Orientation
Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
Identify Input Purpose
The purpose of each input field collecting information about the user can be programmatically determined when the input field serves a purpose identified in the Input Purposes for User Interface Components section and the content is implemented using technologies with support for identifying the expected meaning for form input data.
Identify Purpose
In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined.
Guideline 1.4 – Distinguishable
Make content easier to see and hear.
13 success criteria
Use of Color
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Audio Control
If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
Contrast (Minimum)
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large text (at least 3:1), incidental text, and logotypes.
Resize Text
Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
Images of Text
If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for customizable or essential purposes.
Contrast (Enhanced)
The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for large text (at least 4.5:1), incidental text, and logotypes.
Low or No Background Audio
For prerecorded audio-only content that contains primarily speech in the foreground, background sounds are at least 20 decibels lower than foreground speech or can be turned off.
Visual Presentation
For the visual presentation of blocks of text, a mechanism is available to achieve specific formatting including foreground and background colors, width, alignment, line spacing, and text spacing.
Images of Text (No Exception)
Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.
Reflow
Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for vertical scrolling content at a width equivalent to 320 CSS pixels and horizontal scrolling content at a height equivalent to 256 CSS pixels.
Non-text Contrast
The visual presentation of user interface components and graphical objects has a contrast ratio of at least 3:1 against adjacent color(s).
Text Spacing
In content implemented using markup languages that support text style properties, no loss of content or functionality occurs by setting line height to at least 1.5 times the font size, spacing following paragraphs to at least 2 times the font size, letter spacing to at least 0.12 times the font size, and word spacing to at least 0.16 times the font size.
Content on Hover or Focus
Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the additional content is dismissible, hoverable, and persistent unless it is an input error or does not obscure other content.
Principle 2 – Operable
User interface components and navigation must be operable.
Guideline 2.1 – Keyboard Accessible
Make functionality available from a keyboard.
4 success criteria
Keyboard
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
No Keyboard Trap
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
Keyboard (No Exception)
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Character Key Shortcuts
If a keyboard shortcut is implemented in content using only letter, punctuation, number, or symbol characters, then at least one of the following is true: the shortcut can be turned off, remapped, or is only active when the relevant user interface component is in focus.
Guideline 2.2 – Enough Time
Provide users enough time to read and use content.
6 success criteria
Timing Adjustable
For each time limit that is set by the content, the user can turn off, adjust, or extend the time limit before encountering it, except for real-time events, essential time limits, or time limits longer than 20 hours.
Pause, Stop, Hide
For moving, blinking, scrolling, or auto-updating information that starts automatically, lasts more than five seconds, and is presented in parallel with other content, there is a mechanism to pause, stop, or hide it, or to control the frequency of the update.
No Timing
Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.
Interruptions
Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
Re-authenticating
When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
Timeouts
Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.
Guideline 2.3 – Seizures and Physical Reactions
Do not design content that causes seizures or physical reactions.
3 success criteria
Three Flashes or Below Threshold
Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
Three Flashes
Web pages do not contain anything that flashes more than three times in any one second period.
Animation from Interactions
Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.
Guideline 2.4 – Navigable
Help users navigate, find content, and determine where they are.
13 success criteria
Bypass Blocks
A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
Page Titled
Web pages have titles that describe topic or purpose.
Focus Order
If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
Link Purpose (In Context)
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, except where the purpose of the link would be ambiguous to users in general.
Multiple Ways
More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.
Headings and Labels
Headings and labels describe topic or purpose.
Focus Visible
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Location
Information about the user's location within a set of Web pages is available.
Link Purpose (Link Only)
A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.
Section Headings
Section headings are used to organize the content.
Focus Not Obscured (Minimum)
When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
Focus Not Obscured (Enhanced)
When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.
Focus Appearance
When the keyboard focus indicator is visible, an area of the focus indicator meets all of the following: is at least as large as the area of 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.
Guideline 2.5 – Input Modalities
Make it easier for users to operate functionality through various inputs.
8 success criteria
Pointer Gestures
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
Pointer Cancellation
For functionality that can be operated using a single pointer, at least one of the following is true: no down-event is used to execute the function, the completion of the function is on the up-event and a mechanism is available to abort or undo the function, the up-event reverses any outcome of the preceding down-event, or completing the function on the down-event is essential.
Label in Name
For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
Motion Actuation
Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when supported motion is essential or not using motions would invalidate the activity.
Target Size (Enhanced)
The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when the target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels, the target is in a sentence or block of text, the size of the target is determined by the user agent and is not modified by the author, or a particular presentation of the target is essential to the information being conveyed.
Concurrent Input Mechanisms
Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.
Dragging Movements
All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
Target Size (Minimum)
The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where the target is available through an equivalent link or control on the same page that is at least 24 by 24 CSS pixels, the target is in a sentence or its size is otherwise constrained by the line-height of non-target text, a particular presentation of the target is essential or is legally required for the information being conveyed, or the size of the target is determined by the user agent and is not modified by the author.
Principle 3 – Understandable
Information and the operation of user interface must be understandable.
Guideline 3.1 – Readable
Make text readable and understandable.
6 success criteria
Language of Page
The default human language of each Web page can be programmatically determined.
Language of Parts
The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.
Unusual Words
A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
Abbreviations
A mechanism for identifying the expanded form or meaning of abbreviations is available.
Reading Level
When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.
Pronunciation
A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.
Guideline 3.2 – Predictable
Make pages appear and operate in predictable ways.
6 success criteria
On Focus
When any user interface component receives focus, it does not initiate a change of context.
On Input
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Consistent Navigation
Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
Consistent Identification
Components that have the same functionality within a set of Web pages are identified consistently.
Change on Request
Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Consistent Help
If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same order relative to other page content, unless a change is initiated by the user: Human contact details, Human contact mechanism, Self-help option, or A fully automated contact mechanism.
Guideline 3.3 – Input Assistance
Help users avoid and correct mistakes.
9 success criteria
Error Identification
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.
Labels or Instructions
Labels or instructions are provided when content requires user input.
Error Suggestion
If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.
Error Prevention (Legal, Financial, Data)
For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: submissions are reversible, data is checked for input errors and the user is provided an opportunity to correct them, or a mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Help
Context-sensitive help is available.
Error Prevention (All)
For Web pages that require the user to submit information, at least one of the following is true: submissions are reversible, data is checked for input errors and the user is provided an opportunity to correct them, or a mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Redundant Entry
Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select, except where re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid.
Accessible Authentication (Minimum)
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: an alternative authentication method that does not rely on a cognitive function test, a mechanism to assist the user in completing the cognitive function test, or an object recognition test where the object is personally chosen by the user.
Accessible Authentication (Enhanced)
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: an alternative authentication method that does not rely on a cognitive function test, or a mechanism is available to assist the user in completing the cognitive function test.
Principle 4 – Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guideline 4.1 – Compatible
Maximize compatibility with assistive technologies.
3 success criteria
Parsing
In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. Note: This criterion is obsolete and always considered to pass in WCAG 2.2.
Name, Role, Value
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
Status Messages
In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.