WebAIM's WCAG 2 Checklist
The experts at WebAIM can audit your web site and provide a detailed report to help you remediate accessibility and WCAG compliance issues.
The following is NOT the Web Content Accessibility Guidelines (WCAG) 2. It is a checklist that presents our recommendations for implementing the most common accessibility principles and techniques for those seeking WCAG conformance. The language used here significantly simplifies and condenses the official WCAG 2.2 specification and supporting materials to make it easier to implement and verify for web pages. The first column of the table below links to the official success criteria.
A PDF version of this checklist is also available
Web content is made available to the senses - sight, hearing, and/or touch
Provide text alternatives for any non-text content
- Images, 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 empty alternative text (
alt="") or implemented as CSS backgrounds. All 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.
- Inputs have associated text labels.
- Embedded multimedia is identified via accessible text.
- Frames and iframes are appropriately titled.
Provide alternatives for time-based media.
NOTE: If the audio or video is designated as an alternative to web content (e.g., an audio or sign language version of a web page, for example), then the web content itself serves as the alternative.
- Synchronized captions are provided for non-live video (YouTube videos, etc.).
- A descriptive 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.
1.2.4 Captions (Live)
- Synchronized captions are provided for live media that contains audio (audio-only broadcasts, web casts, video conferences, etc.)
- Audio descriptions are provided for non-live video.
NOTE: Only required if there is relevant visual content that is not presented in the audio.
- While not required at Level AA, for optimal accessibility WebAIM recommends descriptive transcripts in addition to audio descriptions.
- A sign language video is provided for media that contains audio.
- When audio description cannot be added to video due to insufficient pauses in the audio, an alternative version of the video with pauses that allow audio descriptions is provided.
- A descriptive transcript is provided for pre-recorded media that has a video track. For optimal accessibility, WebAIM strongly recommends transcripts for all multimedia.
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.
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
- Semantic markup is appropriately used to designate headings, regions/landmarks, lists, emphasized or special text, etc.
- Tables are used for tabular data and data cells are associated with their headers. Data table captions, if present, are associated to data tables.
- Text labels are associated with form inputs. Related form controls are grouped with fieldset/legend. ARIA labelling may be used when standard HTML is insufficient.
- The reading and navigation order (determined by code order) is logical and intuitive.
- Instructions do not rely upon 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.").
- Orientation of web content is not restricted to only portrait or landscape, unless a specific orientation is necessary.
- Input fields that collect certain types of user information have an appropriate
1.3.6 Identify Purpose
- Regions/landmarks are used to identify page regions.
- ARIA is used, where appropriate, to enhance HTML semantics to better identify the purpose of interface components.
Make it easier for users to see and hear content including separating foreground from background.
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 keyboard focus.
1.4.2 Audio Control
- A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.
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.
1.4.4 Resize text
- The page is readable and functional when the page is zoomed to 200%. NOTE: 1.4.10 (below) introduces additional requirements for zoomed content.
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.
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) and bold - has a contrast ratio of at least 4.5:1.
- Audio with speech has no or very low background noise so the speech is easily distinguished.
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 defined or inherited foreground and background colors.
- Do NOT require horizontal scrolling when the text size is doubled.
- Text is used within an image only for decoration (the image does not convey content) OR when the information cannot be presented with text alone.
- 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 web sites. 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.
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 is maintained in the various states (focus, hover, active, etc.) of author-customized interactive components.
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.
- 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.
Interface forms, controls, and navigation are operable.
Make all functionality available from a 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.
- 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.
- All page functionality is available using the keyboard.
- 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.
Provide users enough time to read and use content.
- 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.
- 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.
2.2.3 No Timing
- The content and functionality have no time limits or constraints.
- Interruptions (alerts, page updates, etc.) can be postponed or suppressed by the user.
- If an authentication session expires, the user can re-authenticate and continue the activity without losing any data from the current page.
- 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.
Do not design content in a way that is known to cause seizures.
2.3.2 Three Flashes
- No page content flashes more than 3 times per second.
- Users can disable non-essential animation and movement that is triggered by user interaction.
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks
- 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 to meet this success criterion, because keyboard navigation by headings or regions is not supported in most browsers, WebAIM recommends a "skip" link in addition to headings and regions.
2.4.3 Focus Order
- The navigation order of links, form controls, etc. is logical and intuitive.
- The purpose of each link (or 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 with the same text that go to different locations are readily distinguishable.
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, or list of all available web pages.
- Page headings and labels for form and interactive controls are informative. Avoid duplicating heading and label text unless the structure provides adequate differentiation between them.
2.4.7 Focus Visible
- There is a visible indicator for page elements when they receive keyboard focus.
- 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").
- The purpose of each link (or image button or image map hotspot) can be determined from the link text alone.
- There are no links with the same text that go to different locations.
2.4.10 Section Headings
- Beyond providing an overall document structure, individual sections of content are designated using headings, where appropriate.
- When elements have keyboard focus, they are not entirely covered or hidden by page content.
- When elements have keyboard focus, they are entirely visible.
2.4.13 Focus Appearance
- If a custom focus indicator or background color is in place, the focus indicator pixels must:
- have at least 3:1 contrast between focused/unfocused states
- be at least as large as the area of a 2 pixel thick perimeter surrounding the element. The formula
(width × 4) + (height × 4) = focus indicator areacan be used for rectangular components.
Make it easier for users to operate functionality through various inputs beyond keyboard.
- 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).
- 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.
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.
- 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.
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.
- Content does not require a specific input type, such as touch-only or keyboard-only, but must support alternative inputs (such as using a keyboard on a mobile device).
2.5.7 Dragging Movements
- Functionality that uses pointer dragging can also be achieved using a single pointer without dragging (unless dragging is essential).
- Pointer input target sizes are at least 24 by 24 pixels unless:
- A 24 pixel diameter circle centered on the target element does not intersect with any other target or a 24 pixel circle centered on an adjacent target.
- The functionality can be achieved in some other conformant manner.
- The target is in a sentence or list.
- The target size can't be modified or is essential to the functionality.
Information and the operation of user interface must be understandable.
Make text content readable and understandable.
- The language of the page is identified using the
3.1.2 Language of Parts
- The language of page content that is in a different language is identified using the
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 other suitable method.
- 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.
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.
- 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.
Make Web pages appear and operate in predictable ways.
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.
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.
- Navigation links that are repeated on web pages do not change order when navigating through the site.
- 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.
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.
- Contact and self-help details or functionality are presented consistently when present on multiple web pages.
Help users avoid and correct mistakes.
- Required inputs or inputs 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.
- Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned input labels, or fieldsets/legends.
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.
- If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed.
- Instructions and cues are provided in context to help in form completion and submission.
3.3.6 Error Prevention (All)
- If the user can submit information, the submission is reversible, verified, or confirmed.
- Information that a user must re-enter to complete a single-session process must be auto-populated or available for the user to select, unless re-entering the information is essential to the functionality, the information poses security issues, or the previously-entered information is no longer valid.
- A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless the cognitive function test can be bypassed in some way, can be completed with assistance by some other mechanism, uses object recognition (such as "click on the photo of a flower"), or uses identification of non-text content provided by the user (such as a user-provided image).
- A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless the cognitive function test can be bypassed in some way or can be completed with assistance by some other mechanism.
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Maximize compatibility with current and future user agents, including assistive technologies.
NOTE: This success criterion is no longer useful and as of 2023 has been removed from WCAG. It previously required that significant HTML validation/parsing errors be avoided.
- Markup is used in a way that facilitates accessibility. This includes following the HTML specifications and using forms, input labels, frame titles, etc. appropriately.
- ARIA is used appropriately to enhance accessibility when HTML is not sufficient.
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.
This checklist is provided as a resource to help implement Web Content Accessibility Guidelines (WCAG) 2.2 (W3C Recommendation), which is Copyright © 2017-2023 W3C®.