WCAG Quick Reference
Search and filter all WCAG 2.0 through 2.2 success criteria. Each criterion includes a plain-English description with testing and remediation guidance.
Showing 28 of 28 criteria
Non-text Content
All non-text content (images, icons, charts) must have a text alternative that serves the equivalent purpose.
Audio-only and Video-only (Prerecorded)
Prerecorded audio-only content needs a transcript. Prerecorded video-only content needs either a transcript or audio description.
Captions (Prerecorded)
All prerecorded audio content in synchronized media must have captions.
Info and Relationships
Information, structure, and relationships conveyed through visual presentation must be programmatically determined or available in text.
Use of Color
Color must not be the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Contrast (Minimum)
Text and images of text must have a contrast ratio of at least 4.5:1 (3:1 for large text).
Non-text Contrast
UI components and graphical objects must have a contrast ratio of at least 3:1 against adjacent colors.
Keyboard
All functionality must be operable through a keyboard interface without requiring specific timings for individual keystrokes.
No Keyboard Trap
If keyboard focus can be moved to a component, focus can also be moved away from it using only the keyboard.
Bypass Blocks
A mechanism must be available to bypass blocks of content that are repeated on multiple pages (like navigation).
Page Titled
Web pages must have titles that describe their topic or purpose.
Focus Order
If a page can be navigated sequentially and the navigation order affects meaning or operation, focusable components receive focus in a meaningful order.
Headings and Labels
Headings and labels must describe the topic or purpose of the content they introduce.
Focus Visible
Any keyboard-operable user interface must have a visible focus indicator.
Target Size (Minimum)
Interactive targets must be at least 24x24 CSS pixels, with some exceptions for inline links and legacy controls.
Language of Page
The default human language of each web page must be programmatically determined.
On Focus
When a UI component receives focus, it must not initiate a change of context (like navigating to another page or significantly altering the page).
Error Identification
If an input error is automatically detected, the item in error must be identified and the error described to the user in text.
Labels or Instructions
Labels or instructions are provided when content requires user input.
Parsing
In content implemented using markup languages, elements have complete start and end tags, are nested properly, and do not contain duplicate attributes.
Name, Role, Value
For all UI components, the name and role can be programmatically determined. States, properties, and values can be programmatically set.
Orientation
Content must not restrict its view and operation to a single display orientation (portrait or landscape) unless essential.
Identify Input Purpose
The purpose of form fields collecting user information can be programmatically determined using autocomplete attributes.
Label in Name
For UI components with visible text labels, the accessible name must contain the visible text.
Motion Actuation
Functionality triggered by device motion (shaking, tilting) must also be operable through a conventional user interface, and motion can be disabled.
Consistent Help
If help mechanisms (contact info, chat, FAQ links) are repeated on multiple pages, they appear in the same relative order.
Redundant Entry
Information previously entered by or provided to the user that is required again must be auto-populated or available for selection.
Accessible Authentication (Minimum)
Authentication processes must not require cognitive function tests (like puzzles or memorization) unless an alternative method is available.