Your WCAG checklist – from 2.0 to 2.2

Our friends at WebAIM.org provided a simple WCAG list to follow.

I know this list looks like a lot, but I’ll cover every topic item and provide explanations and examples.

The video below features a man, drinking alcohol, saying “This is above our pay grade.”

There’s so much to learn!

Perceivable

1.1 Text alternatives

Success criteria	Recommendations	Level	WCAG version
1.1.1 Non-text Content	Images, form image buttons, and image map hot spots have appropriate, equivalent alternative text. Images that do not convey content, are decorative, or contain content that is already conveyed in text are given null alt text (alt=””) or implemented as CSS backgrounds. Linked images have descriptive alternative text. Equivalent alternatives to complex images are provided in context or on a separate linked page. Form buttons have a descriptive value. Form inputs have associated text labels. Embedded multimedia is identified via accessible text. Frames and iFrames are appropriately titled.	A	2.0

1.2 Time-based media

Success Criteria	Recommendations	Level	WCAG version
1.2.1 Prerecorded Audio-only and Video-only	A transcript of relevant content is provided for non-live audio-only (audio podcasts, MP3 files, etc.). A transcript or audio description of relevant content is provided for non-live video-only unless the video is decorative.	A	2.0
1.2.2 Captions (Prerecorded)	Synchronized captions are provided for non-live videos (YouTube videos, etc)	A	2.0
1.2.3 Audio Description or Media Alternative (Prerecorded)	A transcript OR audio description is provided for non-live video. NOTE: Only required if there is relevant visual content that is not presented in the audio.	A	2.0
1.2.4 Captions (Live)	Synchronized captions are provided for live media that contains audio (audio-only broadcasts, webcasts, video conferences, etc)	AA	2.0
1.2.5 Audio Description (Prerecorded)	Audio descriptions are provided for non-live videos. NOTE: Only required if there is relevant visual content that is not presented in the audio.	AA	2.0
1.2.6 Sign Language (Prerecorded)	A sign language video is provided for media that contains audio.	AAA	2.0
1.2.7 Extended Audio Description (Prerecorded)	When audio descriptions cannot be added to a video due to audio timing (e.g., insufficient pauses in the audio), an alternative version of the video with pauses that allow audio descriptions is provided.	AAA	2.0
1.2.8 Media Alternative (Prerecorded)	A transcript is provided for pre-recorded media that has a video track.	AAA	2.0
1.2.9 Audio-only (Live)	A descriptive text transcript (e.g., the script of the live audio) is provided for live content that has audio.	AAA	2.0

1.3 Adaptable

Success Criteria	Recommendations	Level	WCAG version
1.3.1 Info and Relationships	Semantic markup is used to designate headings (<h1>), regions/landmarks, lists (<ul>, <ol>, and <dl>), emphasized or special text (<strong>, <code>, <abbr>, <blockquote>, for example), etc. Semantic markup is used appropriately. Tables are used for tabular data and data cells are associated with their headers. Data table captions, if present, are associated with data tables. Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend. ARIA labeling may be used when standard HTML is insufficient.	A	2.0
1.3.2 Meaningful Sequence	The reading and navigation order (determined by code order) is logical and intuitive.	A	2.0
1.3.3 Sensory Characteristics	Instructions do not rely upon the shape, size, or visual location (e.g., “Click the square icon to continue” or “Instructions are in the right-hand column”). Instructions do not rely upon sound (e.g., “A beeping sound indicates you may continue.”).	A	2.0
1.3.4 Orientation	Orientation of web content is not restricted to only portrait or landscape unless a specific orientation is necessary.	AA	2.1
1.3.5 Identify Input Purpose	Input fields that collect certain types of user information have an appropriate autocomplete attribute defined	AA	2.1
1.3.6 Identify Purpose	HTML5 regions or ARIA landmarks are used to identify page regions. ARIA is used, where appropriate, to enhance HTML semantics to better identify the purpose of interface components.	AAA	2.1

1.4 Distinguishable

Success criteria	Recommendations	Level	WCAG version
1.4.1 Use of Color	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 between the link and the surrounding text is at least 3:1 and an additional distinction (e.g., it becomes underlined) is provided when the link is hovered over and receives focus.	A	2.0
1.4.2 Audio Control	A mechanism is provided to stop, pause, mute, or adjust the volume for audio that automatically plays on a page for more than 3 seconds.	A	2.0
1.4.3 Contrast (Minimum)	Text and images of text have a contrast ratio of at least 4.5:1. Large text – at least 18 point (typically 24px) or 14 point (typically 18.66px) and bold – has a contrast ratio of at least 3:1.	AA	2.0
1.4.4 Resize text	The page is readable and functional when the page is zoomed to 200%. NOTE: 1.4.10 (below) introduces a much higher requirement for zoomed content.	AA	2.0
1.4.5 Images of Text	If the same visual presentation can be made using text alone, an image is not used to present that text.	AA	2.0
1.4.6 Contrast (Enhanced)	Text and images of text have a contrast ratio of at least 7:1. Large text – at least 18 point (typically 24px) or 14 point (typically 18.66px) bold – has a contrast ratio of at least 4.5:1.	AAA	2.0
1.4.7 Low or No Background Audio	Audio with speech has no or very low background noise so the speech is easily distinguished.	AAA	2.0
1.4.8 Visual Presentation	Blocks of text over one sentence in length: Are no more than 80 characters wide. Are NOT fully justified (aligned to both the left and the right margins). Have adequate line spacing (at least 1/2 the height of the text) and paragraph spacing (1.5 times line spacing). Have a specified foreground and background color. These can be applied to specific elements or to the entire page using CSS (and thus inherited by all other elements). Do NOT require horizontal scrolling when the text size is doubled.	AAA	2.0
1.4.9 Images of Text (No Exception)	Text is used within an image only for decoration (image does not convey content) OR when the information cannot be presented with text alone.	AAA	2.0
1.4.10 Reflow	No loss of content or functionality occurs and horizontal scrolling is avoided when content is presented at a width of 320 pixels. This requires responsive design for most websites. This is best tested by setting the browser window to 1280 pixels wide and then zooming the page content to 400%. Content that requires horizontal scrolling, such as data tables, complex images (such as maps and charts), toolbars, etc. are exempted.	AA	2.1
1.4.11 Non-text Contrast	A contrast ratio of at least 3:1 is present for differentiating graphical objects (such as icons and components of charts or graphs) and author-customized interface components (such as buttons, form controls, and focus indicators/outlines). At least 3:1 contrast must be provided in the various states (focus, hover, active, etc.) of author-customized interactive components.	AA	2.1
1.4.12 Text Spacing	No loss of content or functionality occurs when the user adapts paragraph spacing to 2 times the font size, text line height/spacing to 1.5 times the font size, word spacing to .16 times the font size, and letter spacing to .12 times the font size. This is best supported by avoiding pixel height definitions for elements that contain text.	AA	2.1
1.4.13 Content on Hover or Focus	When additional content is presented on hover or keyboard focus: The newly revealed content can be dismissed (generally via the Esc key) without moving the pointer or keyboard focus unless the content presents an input error or does not obscure or interfere with other page content. The pointer can be moved to the new content without the content disappearing. The new content must remain visible until the pointer or keyboard focus is moved away from the triggering control, the new content is dismissed, or the new content is no longer relevant.	AA	2.1

Operable

2.1 Keyboard accessible

Success criteria	Recommendations	Level	WCAG version
2.1.1 Keyboard	All page functionality is available using the keyboard unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing). Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.	A	2.0
2.1.2 No Keyboard Trap	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.	A	2.0
2.1.3 Keyboard (No Exception)	All page functionality is available using the keyboard.	AAA	2.0
2.1.4 Character Key Shortcuts	If a keyboard shortcut uses printable character keys, then the user must be able to disable the key command, change the defined key to a non-printable key (Ctrl, Alt, etc.), or only activate the shortcut when an associated interface component or button is focused.	A	2.1

2.2 Enough time

Success criteria	Recommendations	Level	WCAG version
2.2.1 Timing Adjustable	If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.	A	2.0
2.2.2 Pause, Stop, Hide	Automatically moving, blinking, or scrolling content (such as carousels, marquees, or animations) that lasts longer than 5 seconds can be paused, stopped, or hidden by the user. Automatically updating content (e.g., a dynamically-updating news ticker, chat messages, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates.	A	2.0
2.2.3 No Timing	The content and functionality have no time limits or constraints.	AAA	2.0
2.2.4 Interruptions	Interruptions (alerts, page updates, etc.) can be postponed or suppressed by the user.	AAA	2.0
2.2.5 Re-authenticating	If an authentication session expires, the user can re-authenticate and continue the activity without losing any data from the current page.	AAA	2.0
2.2.6 Timeouts	Users must be warned of any timeout that could result in data loss unless the data is preserved for longer than 20 hours of user inactivity.	AAA	2.1

2.3 Seizures

Success criteria	Recommendations	Level	WCAG version
2.3.1 Three Flashes or Below Threshold	No page content flashes more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red. (See general flash and red flash thresholds).	A	2.0
2.3.2 Three Flashes	No page content flashes more than 3 times per second.	AAA	2.0
2.3.3 Animation from Interactions	Users can disable non-essential animation and movement that is triggered by user interaction.	AAA	2.1

2.4 Navigable

Success criteria	Recommendations	Level	WCAG version
2.4.1 Bypass Blocks	A link is provided to skip navigation and other page elements that are repeated across web pages. A proper heading structure and/or identification of page regions/landmarks may be considered a sufficient technique.	A	2.0
2.4.2 Page Titled	The web page has a descriptive and informative page title.	A	2.0
2.4.3 Focus Order	The navigation order of links, form elements, etc. is logical and intuitive.	A	2.0
2.4.4 Link Purpose (In Context)	The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding text, list item, previous heading, or table headers). Links (or form image buttons) with the same text that go to different locations are readily distinguishable.	A	2.0
2.4.5 Multiple Ways	Multiple ways are available to find other web pages on the site – at least two of a list of related pages: table of contents site map site search list of all available web pages	AA	2.0
2.4.6 Headings and Labels	Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., “More Details”) or label text (e.g., “First Name”) unless the structure provides adequate differentiation between them.	AA	2.0
2.4.7 Focus Visible	It is visually apparent which page element has the current keyboard focus (i.e., as you tab through the page, you can see where you are).	AA	2.0
2.4.8 Location	If a web page is part of a sequence of pages or within a complex site structure, an indication of the current page location is provided, for example, through breadcrumbs or specifying the current step in a sequence (e.g., “Step 2 of 5 – Shipping Address”).	AAA	2.0
2.4.9 Link Purpose (Link Only)	The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone. There are no links (or form image buttons) with the same text that go to different locations.	AAA	2.0
2.4.10 Section Headings	Beyond providing an overall document structure, individual sections of content are designated using headings, where appropriate.	AAA	2.0
2.4.11 Focus Appearance Draft	The focus indicator has a minimum 4.5:1 contrast ratio between the colors in the focus and unfocused states. The focus indicator must be minimally 1px thick. No part of the focus indicator is hidden by author-created content.	AA	2.2
2.4.12 Focus Not Obscured Draft	When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.	AA	2.2
2.4.13 Focus Not Obscured (Enhanced) Draft	When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.	AAA	2.2

2.5 Input modalities

Success criteria	Recommendations	Level	WCAG version
2.5.1 Pointer Gestures	If multipoint or path-based gestures (such as pinching, swiping, or dragging across the screen) are not essential to the functionality, then the functionality can also be performed with a single-point activation (such as activating a button).	A	2.1
2.5.2 Pointer Cancellation	To help avoid inadvertent activation of controls, avoid non-essential down-event (e.g., onmousedown) activation when clicking, tapping, or long pressing the screen. Use onclick, onmouseup, or similar instead. If onmouseup (or similar) is used, you must provide a mechanism to abort or undo the action performed.	A	2.1
2.5.3 Label in Name	If an interface component (link, button, etc.) presents text (or images of text), the accessible name (label, alternative text, aria-label, etc.) for that component must include the visible text.	A	2.1
2.5.4 Motion Actuation	Functionality that is triggered by moving the device (such as shaking or panning a mobile device) or by user movement (such as waving to a camera) can be disabled and equivalent functionality is provided via standard controls like buttons.	A	2.1
2.5.5 Target Size	Clickable targets are at least 44 by 44 pixels in size unless an alternative target of that size is provided, the target is inline (such as a link within a sentence), the target is not author-modified (such as a default checkbox), or the small target size is essential to the functionality.	AAA	2.1
2.5.6 Concurrent Input Mechanisms	Content does not restrict input to a specific modality, such as touch-only or keyboard-only, but must support alternative inputs (such as using a keyboard on a mobile device).	AAA	2.1
2.5.7 Dragging movements Draft	If any part of your website requires a dragging movement, provide keyboard functionality (up/down/left/right keys) or provide buttons (up/down/left/right buttons).	AA	2.2
2.5.8 Target Size Draft	Interactive targets should take up at least 24×24 CSS pixels of space, including the space between the targets.	AA	2.2

Understandable

3.1 Readable

Success criteria	Recommendations	Level	WCAG version
3.1.1 Language of Page	The language of the page is identified using the HTML lang attribute (e.g., <html lang=”en”>).	A	2.0
3.1.2 Language of Parts	The language of page content that is in a different language is identified using the lang attribute (e.g., <blockquote lang=”es”>).	AA	2.0
3.1.3 Unusual Words	Words that may be ambiguous, unfamiliar, or used in a very specific way are defined through adjacent text, a definition list, a glossary, or another suitable method.	AAA	2.0
3.1.4 Abbreviations	The meaning of an unfamiliar abbreviation is provided by expanding it the first time it is used, using the <abbr> element, or linking to a definition or glossary.	AAA	2.0
3.1.5 Reading Level	A more understandable alternative is provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.	AAA	2.0
3.1.6 Pronunciation	If the pronunciation of a word is vital to understanding that word, its pronunciation is provided immediately following the word or via a link or glossary.	AAA	2.0

3.2 Predictable

Success criteria	Recommendations	Level	WCAG version
3.2.1 On Focus	When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.	A	2.0
3.2.2 On Input	When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.	A	2.0
3.2.3 Consistent Navigation	Navigation links that are repeated on web pages do not change order when navigating through the site.	AA	2.0
3.2.4 Consistent Identification	Elements that have the same functionality across multiple web pages are consistently identified. For example: a search box at the top of the site should always be labeled the same way.	AA	2.0
3.2.5 Change on Request	Substantial changes to the page, the spawning of pop-up windows, uncontrolled changes of keyboard focus, or any other change that could confuse or disorient the user must be initiated by the user. Alternatively, the user is provided an option to disable such changes.	AAA	2.0
3.2.6 Consistent Help Draft	If you make a help option available, make sure it is available consistently and in the same relative place. This way, it can be easily located as a person navigates through your site. For example: if you provide a contact phone number or email address, it’s consistently in the same location on every page.	A	2.2
3.3.7 Redundant Entry Draft	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	A	2.2
3.3.8 Accessible Authentication Draft	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: Another authentication method A mechanism to assist the user The test is to recognize objects The test is to identify non-text content the user provided to the website	AA	2.2
3.3.9 Accessible Authentication (Enhanced) Draft	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: Another authentication method A mechanism to assist the user	AAA	2.2

3.3 Input assistance

Success criteria	Recommendations	Level	WCAG version
3.3.1 Error Identification	Required form elements or form elements that require a specific format, value, or length provide this information within the element’s label. Form validation errors are efficient, intuitive, and accessible. The error is clearly identified, quick access to the problematic element is provided, and the user can easily fix the error and resubmit the form.	A	2.0
3.3.2 Labels or Instructions	Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.	A	2.0
3.3.3 Error Suggestion	If an input error is detected (via client-side or server-side validation), suggestions are provided for fixing the input in a timely and accessible manner	AA	2.0
3.3.4 Error Prevention (Legal, Financial, Data)	If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed.	AA	2.0
3.3.5 Help	Instructions and cues are provided in context to help in form completion and submission.	AAA	2.0
3.3.6 Error Prevention (All)	If the user can submit information, the submission is reversible, verified, or confirmed.	AAA	2.0

Robust

4.1 Compatible

Success criteria	Recommendations	Level	WCAG version
4.1.1 Parsing	Significant HTML validation/parsing errors are avoided. Check at W3C Markup validation service. NOTE The current draft of 2.2 suggests that WCAG may remove this success criterion.	A	2.0
4.1.2 Name, Role, Value	Markup is used in a way that facilitates accessibility. This includes following the HTML specifications and using forms, form labels, frame titles, etc. appropriately. ARIA is used appropriately to enhance accessibility when HTML is not sufficient.	A	2.0
4.1.3 Status Messages	If an important status message is presented and focus is not set to that message, the message must be announced to screen reader users, typically via an ARIA alert or live region.	AA	2.1

Categories:BasicsOperablePerceivableRobustUnderstandableW3CWCAG

Tags:A A11Y Basics AA AAA Operable Perceivable Robust Understandable W3C WCAG