WCAG 2.1 AA Checklist: Complete Guide to Level A, AA, and AAA Criteria

Despite the benefits of digital accessibility, organizations still struggle to meet minimum accessibility requirements(opens in a new tab). Based on a scan of over 400,000 enterprise web pages across 15,000 websites, we found that:

38% of images are not accessible to individuals with visual impairments.
80% of pages have links that are not clear to people with visual or cognitive impairments.
35% of forms are missing clear labels.

It’s these issues (among dozens of others) that result in just 3% of the internet being accessible to individuals with disabilities.

The World Wide Web Consortium(opens in a new tab) (W3C) created the Web Content Accessibility Guidelines(opens in a new tab) (WCAG) to help organizations improve accessibility for individuals with disabilities. WCAG is a shared, international standard that businesses should follow to meet accessibility standards. The guidelines contain 86 success criteria that, when met, increase accessibility and usability on digital platforms, including websites, mobile devices, digital documents, and other user interfaces.

Below, we’ve put together an in-depth checklist of WCAG success criteria to ensure your digital products meet web accessibility compliance standards.

WCAG Checklist

This WCAG 2.1 AA checklist covers all Level A, Level AA, and Level AAA success criteria, plus the nine new criteria added in WCAG 2.2. Don’t be overwhelmed by the number of success criteria — there are many, but meeting them is doable with the right tools.

We recommend starting with Level A success criteria before moving on to higher levels. You may also want to consider tackling easier fixes while creating a plan for more complex ones.

WCAG Checklist Level A

Level A criteria represent the minimum accessibility requirements. All websites should meet these before moving to higher levels.

Success Criteria	Description	Complete
Non-text Content	All non-text content (i.e. images, image buttons, and image map hot spots) have appropriate alternative text.
Audio-Only and Video-Only	Descriptive and accurate transcripts are provided for video- and audio-only content.
Captions	Captions are provided for pre-recorded videos or on-live videos (e.g., YouTube).
Information and Relationships	Headings include the right semantic markup. Tables are linked to the appropriate headers and include captions if necessary. Text labels are associated with the right form inputs.
Meaningful Sequence	Navigation order follows code order; navigation is clear and intuitive.
Sensory Characteristics	Instructions are not dependent on visual location, shape, or size (i.e., ‘Instructions are listed on the right’ or ‘Click the square button to continue’).
Use of Color	Color alone is not used to portray information, nor is it used to distinguish links from surrounding text unless the color contrast ratio is appropriate.
Audio Control	Users can pause, stop, change volume, or mute audio content that automatically plays on a page for longer than three seconds.
Keyboard	Web elements can easily be shared via a keyboard and include page-specific keyboard shortcuts.
No Keyboard Trap	Keyboard focus and shortcuts are not locked or trapped on any page elements.
Character Key Shortcuts	Users must be able to disable key commands and change to non-printable keys, such as Ctrl, Alt, etc.
Timing Adjustable	Pages with time limits allow users to adjust, turn off, or expand the time limit.
Pause, Stop, Hide	Automatically moving, blinking, scrolling, or updating content lasting longer than five seconds can be paused, stopped, or hidden by users.
Three Flashes or Below	Page content does not flash more than three times per second.
Bypass Blocks	Users can skip navigation or other page elements that are repeated across web pages.
Page Titles	The webpage has a descriptive, informative page title.
Focus Order	The order of links is clear and follows a logical, intuitive order.
Link Purpose	Users can understand the purpose of the link from the text alone. Links with similar text that redirect to different locations are easily distinguishable.
Pointer Gestures	User actions can be performed with a single pointer gesture.
Pointer Cancellation	Inadvertent activation of controls is avoided by non-use of the ‘onmousedown’ activation.
Motion Actuation	Functionalities triggered by user movement or moving the device can be disabled, and similar functionality can be achieved via standard controls like buttons or controls.
Error Identification	Form validation or input errors are clearly identified, and access to the error is quickly provided.

WCAG Checklist Level AA

Level AA is the standard required by most digital accessibility laws, including the ADA (US), EN 301 549 (EU), and AODA (Canada).

Success Criteria	Description	Complete
Captions	Live media with audio contain synchronized captions.
Audio Description	Users have access to audio descriptions for non-live video.
Orientation	Web page orientation is not limited to portrait or landscape; users can adjust as needed.
Identify Input Purpose	Fields that collect certain user information have an ‘autocomplete’ attribute defined.
Contrast	Both text and images have a contrast ratio of at least 4.5:1. Large text has a ratio of at least 3:1.
Resize Text	Page elements are still readable and functional when zoomed to 200%.
Images of Text	If a visual representation can be portrayed through text alone, an image alone is not used to present text.
Reflow	Functionality is not lost when content is presented at a width of 320 pixels. Horizontal scrolling is avoided as much as possible.
Non-Text Contrast (Minimum)	A minimum contrast ratio of 3:1 is available for different objects, such as icons, charts, or graphs.
Text Spacing	Content or functionality is not lost when users adjust paragraph spacing.
Content on Hover or Focus	Content presented in hover or focus can be dismissed without moving the keyboard or pointer.
Multiple Ways	Users have more than one way to find other web pages on a site.
Headings and Labels	Page headings and labels are informative and are not duplicated unless absolutely necessary.
Focus Visible	A visible indicator is present for page elements when they receive keyboard focus.
Focus Not Obscured	Elements with keyboard focus are entirely visible.
Dragging Movement	Actions that require pointer dragging can also be done with a single pointer.
Target Size	Pointer sizes are at minimum 24 by 24 pixels unless specified otherwise.
Language of Parts/Page	Language of pages is easily identifiable via the ‘lang’ attribute.
Consistent Navigation	Elements that repeat across a web page (e.g., a search bar) are consistently labeled as such across individual web pages.
Error Suggestion	When an error is detected, suggestions are provided for how to remedy the issue in a timely, accessible way.
Error Prevention	If a user changes or deletes financial, legal, or test data, the action can be reversed, confirmed, or verified as needed.
Excessive Authentication	Cognitive functions are not required during authentication processes unless it can be completed in another way, bypassed, or identification of non-text content is provided by the user (e.g., user-provided image).
Status Messages	Status messages are announced to screen readers via live region or ARIA alerts.

WCAG Checklist Level AAA

Level AAA represents the highest level of accessibility. Most organizations do not target full Level AAA conformance, but individual Level AAA criteria can be implemented where feasible.

Success Criteria	Description	Complete
Sign Language	Sign language interpretation is provided for media with audio.
Extended Audio Description	When the original video contains insufficient pauses and is not optimized for audio description, a separate video with sufficient pauses and audio descriptions is provided.
Media Alternative	Pre-recorded media includes a descriptive transcript.
Audio-Only	Descriptive text is provided for live content that contains audio.
Identify Purpose	ARIA is used to enhance HTML semantics, enabling users to more easily understand the purpose of interface elements.
Contrast	Images and text have a color contrast ratio of 7:1.
Low or No Background Audio	Audio content has little to no background noise, ensuring it is easily distinguished.
Visual Presentation	Blocks of text over one sentence in length are: Less than 80 characters wide, not fully justified, have adequate line spacing, include appropriate foreground and background colors, and does not require horizontal scrolling if size is doubled.
Images of Text	Text within an image is used only for decoration, or if the information cannot be presented through text alone.
Keyboard	All functionalities are available via the keyboard.
No Timing	There are no time limits or constraints to page content or functionality.
Interruptions	Interruptions such as alerts or updates can be postponed by the user.
Re-Authenticating	Users can re-authenticate a page and continue activities without losing data.
Timeouts	Users are adequately warned of timeouts that can result in data loss (unless data can be preserved for more than hours of user inactivity).
Three Flashes	No page content flashes three times per second.
Animations from Interactions	Non-essential animations and movements can be disabled by users.
Location	A web page that’s part of a sequence of web pages is indicated as such through breadcrumbs or specifying sequence steps.
Link Purpose	Users can distinguish the purpose of each link through link text alone.
Section Headings	Sections of content are designated using headers.
Focus not Obscured (Enhanced)	Elements with keyboard focus are entirely visible.
Focus Appearance	Instances where custom indicators or backgrounds are in place have at least a 3:1 contrast between focused/unfocused states, and are at least as large as the area of a 2-pixel-thick perimeter surrounding the element.
Target Size	Clickable targets are 44 by 44 pixels in size unless an alternative target size is provided.
Concurrent Input Mechanisms	Content is not limited to one specific input type (i.e., keyboard-only or touch-only) and supports alternative inputs.
Unusual Words	Unfamiliar or ambiguous words are defined through an index, definition list, or other appropriate method.
Abbreviations	Unfamiliar abbreviations are expanded and defined the first time it is used.
Reading Level	More understandable alternatives are provided for advanced content (typically provided for content above a ninth-grade reading level).
Pronunciation	Pronunciation guides are provided for words that are vital to the comprehension of the page.
Change on Request	Substantial changes (i.e., spawning of pop-up windows or changes in keyboard focus) are initiated by the user and can disable options if desired.
Help	Instructions or cues are provided to users who need assistance to complete tasks.
Error Prevention	Users can reverse, verify, or confirm submissions after information is submitted.
Accessible Authentication (Enhanced)	Cognitive function tests are not required for any step in the authentication process unless the test can be bypassed or completed with assistance from another mechanism.

WCAG Pass and Fail Examples

Below are pass and fail examples for ten commonly referenced criteria. For each, here is what conformance looks like, and what typically causes a fail.

Non-text Content (1.1.1, Level A)

Pass: A product photo uses alt text that describes an image as: 'Red, high-top sneaker photographed from the side against a white background.'
Fail: The same image uses 'alt=image' or has no alt attribute at all. Decorative images that should be hidden from screen readers use a filename instead of an empty 'alt=""'.

Contrast Minimum (1.4.3, Level AA)

Text needs a contrast ratio of at least 4.5:1 against its background or 3:1 for large text.

Pass: Body text in dark gray (#595959) on a white background, a ratio of 7:1.
Fail: Light gray placeholder text (#AAAAAA) on white, a ratio of 2.3:1, well below the threshold.

Keyboard (2.1.1, Level A)

All keyboard functionality must be operable with a keyboard alone.

Pass: A user can open a dropdown menu, move through its options, and select one using only 'Tab', arrow keys, and 'Enter.'
Fail: A custom menu opens only on mouse hover and cannot be reached or triggered by keyboard.

Focus Visible (2.4.7, Level AA)

Keyboard focus must be visibly indicated on interactive elements.

Pass: Tabbing to a link or button shows a clear outline or highlight around the focused element.
Fail: A stylesheet sets 'outline:none' on buttons with no replacement, so keyboard users cannot tell where they are on the page.

Page Titles (2.4.2, Level A)

Each page needs a descriptive, unique title.

Pass: A checkout page titled 'Checkout, Step 2 of 3, Shipping, Example Store.'
Fail: Every page across the site is titled 'Home' or 'Untitled.'

Link Purpose (2.4.4, Level A)

The purpose of a link should be clear from its text, or from its text plus immediate context.

Pass: A link reads 'Download the 2026 accessibility report.'
Fail: Several links across the page all read 'click here' or 'read more,' with no way to tell where each link goes.

Headings and Labels (2.4.6, Level AA)

Headings and form labels should be descriptive and not misleading.

Pass: A form field is labeled "Email Address," and the section above it is headed "Billing Information."
Fail: A form field has placeholder text but no programmatic label, so a screen reader announces only 'edit text.'

Resize Text (1.4.4, Level AA)

Text must remain readable and functional when zoomed to 200 percent.

Pass: At 200 percent zoom, text reflows and stays fully readable without loss of content or function.
Fail: At 200 percent zoom, text is cut off, overlaps other elements, or forces horizontal scrolling to read a line.

Target Size Minimum (2.5.8, Level AA)

Pointer targets must be at least 24 by 24 CSS pixels, unless an exception such as adequate spacing applies.

Pass: Buttons in a mobile navigation bar are 44 by 44 pixels, comfortably above the minimum.
Fail: Two icon links sit 18 pixels apart at 16 by 16 pixels each, with no spacing exception, making them easy to mis-tap.

Error Identification (3.3.1, Level A)

Input errors must be identified clearly and described to the user in text.

Pass: A form flags "Enter a valid email address, for example name@examle.com" next to the field, and the error is announced to screen readers.
Fail: An invalid field is marked only by turning red, with no text explaining what went wrong.

What Changed in WCAG 2.2: 9 New Success Criteria

WCAG 2.2 was published by the W3C in October 2023, adding 9 new success criteria across the A, AA, and AAA conformance levels. The update focuses heavily on keyboard navigation, touch interaction, and authentication, areas where the previous standard had meaningful gaps.

One criterion was also removed: 4.1.1 Parsing, which had become largely redundant with modern browser behavior and HTML validation practices. Organizations working toward WCAG 2.1 AA conformance will need to evaluate their sites against these additions as adoption requirements continue to evolve.

New Criterion	Level/What It Adds
2.4.11 Focus Not Obscured	AA; Sticky headers, overlays, or other page elements must not entirely hide focused components.
2.4.12 Focus Not Obscured Enhanced	AAA; Stricter version: no part of the focused component may be obscured.
2.4.13 Focus Appearance	AAA; Require focus indicators to meet minimum size and contrast thresholds
2.5.7 Dragging Movements	AA; All functionality that uses dragging must also be achievable with a single pointer (e.g., click or tap).
2.5.8 Target Size Minimum	AA; Interactive targets must be at least 24x24 CSS pixels, with limited exceptions.
3.2.6 Consistent Help	A; Help mechanisms (contact info, chat, etc.) must appear in the same location across pages.
3.3.7 Redundant Entry	A; Users should not have to re-enter information already provided in the same session.
3.3.8 Accessible Authentication	AA; Authentication steps must not require cognitive tests (like puzzles) without an accessible alternative.
3.3.9 Accessible Authentication Enhanced	AAA; Stricter version; removes exceptions allowed at the AA level.

Competitive data on this page was collected as of August 13, 2026 and is subject to change or update. AudioEye does not make any representations as to the completeness or accuracy of the information on this page.

WCAG remains the current compliance benchmark for most international accessibility laws, but organizations should begin planning for alignment with WCAG 2.2.

WCAG Conformance and Digital Accessibility Laws

Everyone has the right to access and use online content — following the success criteria included above enables you to create an accessible, functional environment that everyone can use. However, digital accessibility is also a legal requirement worldwide. Most international accessibility laws use WCAG as the standard for accessibility, including:

The Americans with Disabilities Act (ADA): The ADA(opens in a new tab) prohibits discrimination against individuals with disabilities in public spaces, which includes the internet. Failure to meet ADA requirements (including creating an ADA-compliant website) can result in litigation. To comply with the ADA, you’ll need to meet the requirements included in WCAG 2.1 Level AA.
The European Accessibility Act (EAA): Similar to the ADA, the EAA requires all public-sector organizations within the EU to provide accessible products and services. One thing to note: The EAA enforces POUR principles over WCAG; however, following WCAG principles puts you in a strong position to meet POUR principles.
The Accessibility for Ontarians with Disabilities Act (AODA): Under the AODA, businesses cannot discriminate against individuals with disabilities “with respect to goods, services, facilities, accommodation, employment, buildings, structures, and premises.” The AODA also uses WCAG 2.1 Level AA as a basis for AODA compliance.

AudioEye: Helping You Achieve WCAG Conformance with Ease

Making your website accessible doesn’t have to be overwhelming. The checklist above gives you a solid foundation, but with so many WCAG success criteria — and some highly technical details — it can be difficult to identify and fix every issue on your own.

That’s where AudioEye comes in. We’re the only solution that combines AI-powered automation, expert audits, and expert-written custom fixes in a single platform, covering more WCAG success criteria than any other platform. And with AudioEye Assurance, you get the industry’s only real legal guarantee. The result: 400% more protection than automation-only solutions, and the lowest valid legal claim rate in the industry.

Ready to get started? AudioEye's WCAG compliance solution maps directly to the criteria in this checklist — see how AudioEye helps organizations achieve and maintain WCAG 2.1 AA conformance in our comprehensive WCAG guide.

Want to see how accessible your existing content is? Use our free Website Accessibility Checker. Or schedule a demo to see the full AudioEye platform in action.

Frequently Asked Questions

What are the different WCAG versions?

What are the different WCAG levels?

Which is the latest version of WCAG?

When will WCAG 3.0 be released?

What are the four principles of WCAG?

What are the consequences of non-conformance with WCAG?

What are the new success criteria in WCAG 2.2?

Share Article

The Complete WCAG 2.1 AA Checklist for Website Accessibility