WCAG 2.2 AA Checklist: All 50 Success Criteria
The complete WCAG 2.2 Level A and AA accessibility compliance checklist. See which issues automated tools catch vs. require manual testing, with practical fix tips for every criterion.
Why WCAG 2.2 AA Compliance Matters in 2026
Web accessibility compliance is no longer optional for most organizations. The regulatory landscape has shifted significantly: the DOJ's April 2024 rule requires state and local governments to meet WCAG 2.1 Level AA, the European Accessibility Act (EAA) mandates EN 301 549 compliance for digital services, and private businesses continue to face legal action citing WCAG as the standard.
According to the WebAIM Million study, 94.8% of home pages have detectable WCAG failures. The most common issues — missing alt text, low color contrast, missing form labels — are among the easiest to fix. That's where this checklist comes in.
WCAG 2.2, published in October 2023 and now the current standard, added 9 new success criteria focused on cognitive accessibility, mobile usability, and authentication. It builds on WCAG 2.1, meaning full 2.2 compliance also covers 2.1. This checklist covers all 50 Level A and AA criteria you need to meet.
Key facts about WCAG 2.2 AA
- 50 success criteria across Level A (18) and Level AA (32)
- Approximately 40% of issues can be caught by automated scanning tools
- The remaining 60% require manual testing with assistive technologies
- WCAG 2.2 AA is referenced by ADA, EAA, and EN 301 549 requirements
Quick Reference: WCAG 2.2 at a Glance
This checklist covers all WCAG 2.2 Level A and AA success criteria. Use it to audit your website for accessibility issues. Criteria marked with a green check can be partially detected by automated tools like inclly. Those marked with a warning icon require manual testing.
How to Use This Checklist
- Automated criteria can be detected by scanning tools (inclly catches these)
- Manual criteria require human judgment and testing
Automated tools catch approximately 40% of accessibility issues. Use this checklist to cover the remaining 60% that requires manual testing.
Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
Non-text Content
Level AAll non-text content has a text alternative that serves the equivalent purpose.
How to Fix
- -Add alt text to all images that convey meaning
- -Use empty alt="" for decorative images
- -Provide text alternatives for charts and diagrams
- -Add captions or transcripts for audio content
Audio-only and Video-only
Level AProvide alternatives for time-based media.
How to Fix
- -Provide transcripts for audio-only content
- -Provide audio description or text alternative for video-only content
Captions (Prerecorded)
Level ACaptions are provided for all prerecorded audio content in synchronized media.
How to Fix
- -Add captions to all videos with audio
- -Ensure captions are synchronized with audio
- -Include speaker identification when multiple speakers
Info and Relationships
Level AInformation, structure, and relationships conveyed through presentation can be programmatically determined.
How to Fix
- -Use semantic HTML (headings, lists, tables)
- -Associate form labels with inputs
- -Use ARIA landmarks appropriately
- -Ensure reading order matches visual order
Meaningful Sequence
Level AWhen the sequence affects meaning, a correct reading sequence can be programmatically determined.
How to Fix
- -Ensure DOM order matches visual order
- -Test with CSS disabled to verify reading order
Sensory Characteristics
Level AInstructions don't rely solely on sensory characteristics like shape, color, size, or location.
How to Fix
- -Don't use "click the red button" or "see sidebar"
- -Provide multiple ways to identify elements
Use of Color
Level AColor is not used as the only visual means of conveying information.
How to Fix
- -Add icons or text labels alongside color indicators
- -Use patterns in addition to colors in charts
- -Ensure links are underlined or have other non-color indicators
Audio Control
Level AIf audio plays automatically for more than 3 seconds, provide a way to pause or control volume.
How to Fix
- -Avoid auto-playing audio
- -If necessary, provide visible pause/stop controls
- -Include volume control independent of system volume
Contrast (Minimum)
Level AAText has a contrast ratio of at least 4.5:1 (3:1 for large text).
How to Fix
- -Use a contrast checker tool
- -Large text (18pt+ or 14pt bold) needs 3:1 ratio
- -Normal text needs 4.5:1 ratio
Resize Text
Level AAText can be resized up to 200% without loss of content or functionality.
How to Fix
- -Use relative units (rem, em) instead of pixels
- -Test at 200% zoom in browser
- -Ensure no horizontal scrolling at 200% zoom
Images of Text
Level AAIf the same visual presentation can be made using text, don't use images of text.
How to Fix
- -Use CSS for text styling instead of images
- -Logos are an exception to this rule
Reflow
Level AAContent can be presented without horizontal scrolling at 320px width.
How to Fix
- -Use responsive design
- -Test at 320px viewport width
- -Avoid two-dimensional scrolling except for complex content
Non-text Contrast
Level AAUI components and graphics have 3:1 contrast ratio.
How to Fix
- -Form inputs need visible borders with sufficient contrast
- -Icons conveying meaning need 3:1 contrast
- -Focus indicators need 3:1 contrast
Text Spacing
Level AANo loss of content when text spacing is adjusted.
How to Fix
- -Don't use fixed height containers for text
- -Test with increased line-height, letter-spacing, word-spacing
Content on Hover or Focus
Level AAAdditional content triggered on hover/focus is dismissible, hoverable, and persistent.
How to Fix
- -Tooltips should be dismissible with Escape
- -User should be able to hover over tooltip content
- -Content should remain visible until dismissed
Operable
User interface components and navigation must be operable.
Keyboard
Level AAll functionality is available using only a keyboard.
How to Fix
- -Test entire site using only Tab, Enter, Space, and arrow keys
- -Ensure all interactive elements are focusable
- -Custom components need keyboard support
No Keyboard Trap
Level AKeyboard focus is never trapped in a component.
How to Fix
- -Test modals and dialogs for keyboard navigation
- -Ensure focus can always move away from any element
Character Key Shortcuts
Level ASingle-character keyboard shortcuts can be turned off or remapped.
How to Fix
- -Avoid single-key shortcuts (like "s" for search)
- -If used, provide settings to remap or disable
Timing Adjustable
Level AUsers can extend, adjust, or disable time limits.
How to Fix
- -Session timeouts should warn users and allow extension
- -Don't auto-advance carousels without user control
Pause, Stop, Hide
Level AMoving or auto-updating content can be paused, stopped, or hidden.
How to Fix
- -Carousels need pause controls
- -Auto-updating content needs stop controls
- -Animations lasting more than 5 seconds need controls
Three Flashes or Below Threshold
Level AContent doesn't flash more than 3 times per second.
How to Fix
- -Avoid flashing content entirely
- -If necessary, keep flash rate below 3 Hz
Bypass Blocks
Level AProvide a way to skip repeated blocks of content.
How to Fix
- -Add a "skip to main content" link
- -Use ARIA landmarks (main, nav, etc.)
- -Ensure proper heading structure
Page Titled
Level APages have titles that describe topic or purpose.
How to Fix
- -Each page should have a unique, descriptive title
- -Title should include both page name and site name
Focus Order
Level AFocus order preserves meaning and operability.
How to Fix
- -Tab order should follow visual reading order
- -Modals should trap focus appropriately
- -Focus should return to trigger element when modal closes
Link Purpose (In Context)
Level ALink purpose can be determined from the link text or its context.
How to Fix
- -Avoid "click here" or "read more" without context
- -Link text should make sense out of context or with surrounding text
- -Use aria-label if link text alone isn't descriptive
Multiple Ways
Level AAMore than one way is available to locate a page within a set of pages.
How to Fix
- -Provide site search
- -Include a sitemap
- -Use clear navigation menus
Headings and Labels
Level AAHeadings and labels describe topic or purpose.
How to Fix
- -Use descriptive, unique headings
- -Form labels should clearly describe expected input
Focus Visible
Level AAKeyboard focus indicator is visible.
How to Fix
- -Don't remove outline styles without replacement
- -Focus indicator should be clearly visible
- -Use :focus-visible for keyboard-only focus styles
Focus Not Obscured (Minimum)
Level AAFocused element is not entirely hidden by other content.
How to Fix
- -Sticky headers shouldn't cover focused elements
- -Cookie banners shouldn't cover focused elements
- -Use scroll-margin to account for sticky elements
Pointer Gestures
Level AMultipoint or path-based gestures have single-pointer alternatives.
How to Fix
- -Pinch-to-zoom should have button alternatives
- -Swipe gestures need button alternatives
- -Map interactions need single-click alternatives
Pointer Cancellation
Level AActions triggered on pointer down can be cancelled.
How to Fix
- -Use click/touch-end instead of mousedown/touchstart
- -Provide undo functionality for destructive actions
Label in Name
Level AVisible text labels are included in accessible names.
How to Fix
- -Accessible name should include or match visible label
- -Don't use aria-label that contradicts visible text
Motion Actuation
Level AFunctions triggered by motion have UI alternatives.
How to Fix
- -Shake-to-undo needs a button alternative
- -Motion controls should be optional
Dragging Movements
Level AADrag operations have single-pointer alternatives.
How to Fix
- -Drag-to-reorder should have button alternatives
- -Provide up/down arrows for list reordering
Target Size (Minimum)
Level AATouch targets are at least 24x24 CSS pixels (with exceptions).
How to Fix
- -Buttons and links should be at least 24x24 pixels
- -Provide adequate spacing between touch targets
- -44x44 pixels is recommended for mobile
Understandable
Information and the operation of the user interface must be understandable.
Language of Page
Level AThe default human language of the page can be programmatically determined.
How to Fix
- -Add lang attribute to the html element
- -Use correct language code (en, es, fr, etc.)
Language of Parts
Level AALanguage changes within content are identified.
How to Fix
- -Use lang attribute on elements with different language text
- -Include proper names and technical terms in main language
On Focus
Level AReceiving focus doesn't automatically change context.
How to Fix
- -Don't automatically submit forms on focus
- -Don't open new windows on focus
- -Don't navigate away on focus
On Input
Level AChanging settings doesn't automatically change context unless user is warned.
How to Fix
- -Forms should have explicit submit buttons
- -Warn users before auto-submitting
- -Radio buttons shouldn't submit forms automatically
Consistent Navigation
Level AANavigation appears in the same order across pages.
How to Fix
- -Keep navigation in the same location on all pages
- -Maintain consistent order of navigation items
Consistent Identification
Level AAComponents with the same functionality are identified consistently.
How to Fix
- -Use consistent labels for similar functions
- -Search icons should always mean search
- -Don't use different labels for the same action
Consistent Help
Level AHelp mechanisms appear in the same relative order on pages.
How to Fix
- -Keep help links in consistent location
- -Contact information should be in same place across pages
Error Identification
Level AInput errors are automatically detected and described to the user.
How to Fix
- -Show clear error messages for invalid input
- -Identify which field has an error
- -Don't rely only on color to indicate errors
Labels or Instructions
Level ALabels or instructions are provided when content requires user input.
How to Fix
- -Every form field needs a visible or sr-only label
- -Provide format hints (e.g., "MM/DD/YYYY")
- -Indicate required fields
Error Suggestion
Level AAIf an input error is detected, suggestions are provided.
How to Fix
- -Suggest corrections when possible
- -Show expected format for invalid input
- -Provide examples of valid input
Error Prevention (Legal, Financial, Data)
Level AAFor legal/financial transactions, submissions are reversible, checked, or confirmed.
How to Fix
- -Allow users to review before final submission
- -Provide confirmation step for important actions
- -Allow users to undo or correct submissions
Redundant Entry
Level AInformation previously entered is auto-populated or available for selection.
How to Fix
- -Don't ask users to re-enter information
- -Auto-fill shipping from billing address
- -Remember preferences within a session
Accessible Authentication (Minimum)
Level AACognitive function tests aren't required for authentication unless alternatives exist.
How to Fix
- -Allow password managers
- -Provide copy-paste for verification codes
- -Don't use CAPTCHAs as only option
Robust
Content must be robust enough to be interpreted reliably by a wide variety of user agents.
Name, Role, Value
Level AUI components have accessible names, roles, and states.
How to Fix
- -Custom components need proper ARIA roles
- -Toggle buttons need aria-pressed
- -Expandable sections need aria-expanded
Status Messages
Level AAStatus messages can be programmatically determined without receiving focus.
How to Fix
- -Use aria-live regions for dynamic updates
- -Success/error messages need role="alert" or aria-live
- -Loading states should be announced
Frequently Asked Questions
What is the difference between WCAG 2.1 and 2.2?
WCAG 2.2 builds on WCAG 2.1 by adding 9 new success criteria focused on users with cognitive disabilities, low vision, and mobile device users. Key additions include Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), and Target Size Minimum (2.5.8). WCAG 2.2 also removed criterion 4.1.1 Parsing as obsolete. If you comply with WCAG 2.2, you automatically comply with 2.1.
What percentage of WCAG issues can automated tools detect?
Automated accessibility testing tools can detect approximately 30-40% of WCAG issues. These include technical issues like missing alt text, color contrast failures, missing form labels, and improper heading structure. The remaining 60-70% require human judgment—such as whether alt text is meaningful, if content is logically organized, or if error messages are helpful.
Is WCAG 2.2 AA legally required?
It depends on your jurisdiction. In the US, the DOJ's April 2024 rule requires state and local governments to meet WCAG 2.1 Level AA. Private businesses face ADA lawsuits citing WCAG as the standard. In the EU, the European Accessibility Act (effective June 2025) requires WCAG 2.1 AA for many digital products and services. WCAG 2.2 is increasingly becoming the expected standard.
How long does it take to achieve WCAG 2.2 AA compliance?
Timeline varies significantly based on your site's current state, size, and complexity. A small marketing site might need a few weeks of focused work, while a large web application could require months. The key is to prioritize: fix critical issues (Level A) first, then address AA criteria. Remember that accessibility is ongoing—new content and features need continuous testing.
What are the most common WCAG failures?
According to the WebAIM Million report, the most common failures are: missing alternative text for images (54.5%), low color contrast (81%), missing form labels (45.9%), empty links (44.6%), missing document language (17.1%), and empty buttons (26.9%). Most of these can be detected by automated tools and are relatively straightforward to fix.
What is a WCAG AA checklist and who needs one?
A WCAG AA checklist systematically covers all Level A and Level AA success criteria from the Web Content Accessibility Guidelines. Any organization with a public-facing website benefits from one — especially those subject to ADA requirements (US), the European Accessibility Act (EU), or sector-specific accessibility regulations. It helps teams track which criteria they meet, which need work, and which require manual testing beyond automated tools.
Continue Learning
Explore related guides to deepen your accessibility compliance strategy.
Automated vs Manual Testing
Understand what each approach catches and build an effective testing strategy.
Manual Accessibility Testing Guide
5 essential tests every developer should know — keyboard, screen reader, zoom, and more.
EAA Compliance Checklist
EN 301 549 requirements mapped to WCAG 2.2 for European Accessibility Act compliance.
Accessibility Testing Tools Compared
Compare axe DevTools, WAVE, Lighthouse, Pa11y, and more — with pros, cons, and recommendations.
Need Help Implementing These Fixes?
inclly automatically scans your website for WCAG 2.2 AA issues and provides framework-specific code examples to fix them. Start with a free scan to see which criteria your site meets — and which need attention.
Start Free Scan