What Is on the WCAG Level AA Checklist for 2026?

WCAG Level AA compliance requires meeting all 56 success criteria across Levels A and AA—the standard referenced by virtually every web accessibility law worldwide. With the WebAIM Million 2024 report finding that 96.3% of homepages have detectable WCAG failures and accessibility lawsuits exceeding 4,000 annually, a systematic checklist approach is essential for comprehensive compliance. This WCAG Level AA checklist for 2026 incorporates all WCAG 2.2 requirements and organizes criteria by testing category for efficient auditing.

Key Takeaways

This checklist provides a complete, actionable guide to WCAG Level AA compliance.

• WCAG Level AA requires 56 total criteria: 32 from Level A plus 24 from Level AA
• WCAG 2.2 (October 2023) added 6 new Level A/AA criteria and removed 1, reflected in this checklist
• Automated tools can detect approximately 30-40% of issues; manual testing is required for complete coverage
• The checklist is organized by functional category for efficient testing workflows
• Each criterion includes testing method indicators: Automated (A), Semi-automated (S), or Manual (M)

How to Use This Checklist

This checklist organizes WCAG Level AA criteria by functional testing category rather than guideline number. This approach enables:

• Efficient testing: Group similar tests together (all contrast checks, all keyboard tests)
• Tool optimization: Run automated tests once, then proceed to manual testing
• Team coordination: Assign categories to team members by expertise
• Progress tracking: Check off entire categories as complete

Testing Method Key

Category 1: Text and Typography

These criteria ensure text content is readable and adaptable.

Checklist Items

Testing Instructions

Contrast (1.4.3):

• Use automated tools to scan for contrast issues
• Manually verify text on images, gradients, and videos
• Check all states: default, hover, focus, active, disabled

Resize Text (1.4.4):

• Zoom browser to 200%
• Verify no text is clipped, overlapping, or hidden
• Confirm all functionality remains available

Reflow (1.4.10):

• Set browser window to 320px width (or zoom to 400%)
• Verify single-column layout without horizontal scrolling
• Exception: Data tables, toolbars, and content requiring two-dimensional layout

Text Spacing (1.4.12): Apply these CSS overrides and verify no content loss: ```css

• {

line-height: 1.5 !important; letter-spacing: 0.12em !important; word-spacing: 0.16em !important; paragraph-spacing: 2em !important; } ```

Category 2: Images and Media

These criteria address non-text content accessibility.

Checklist Items

Testing Instructions

Alt Text (1.1.1):

• Automated tools detect missing alt attributes
• Manual review required for alt text quality:

- Informative images: Describe content and function - Decorative images: Empty alt (alt="") - Functional images: Describe action/destination - Complex images: Brief alt + detailed description

Captions (1.2.2, 1.2.4):

• Verify all video has synchronized captions
• Captions must include speaker identification
• Captions must convey sound effects relevant to content
• Live captions may use CART or auto-captioning with human monitoring

Non-text Contrast (1.4.11):

• Check form field borders, icons, and charts
• Interactive states must also meet contrast requirements
• Use color contrast analyzers with eyedropper tools

Category 3: Keyboard Accessibility

These criteria ensure full keyboard operability.

Checklist Items

Testing Instructions

Keyboard Testing Protocol:

1. Disconnect or disable mouse
2. Start at browser address bar
3. Tab through entire page
4. Verify every interactive element receives focus
5. Verify focus order is logical
6. Test all functionality with Enter/Space/Arrow keys
7. Verify you can Tab away from all elements (no traps)

Focus Visibility (2.4.7, 2.4.13):

• Focus indicator must be clearly visible at all times
• 2.4.13 requires: 2px minimum thickness and 3:1 contrast
• Test with both light and dark color schemes

Focus Not Obscured (2.4.11):

• Tab through page with sticky headers/footers visible
• Verify focused element is never completely hidden
• Check modals, cookie banners, chat widgets

Bypass Blocks (2.4.1):

• Verify "Skip to content" link is first focusable element
• Link must be visible on focus (can be visually hidden until focused)
• Link must function correctly

Category 4: Forms and Input

These criteria govern form accessibility and user input.

Checklist Items

Testing Instructions

Labels (3.3.2, 2.5.3):

• Every input must have a visible label
• Labels must be programmatically associated (for/id or aria-labelledby)
• Visible label text must be contained in accessible name

Autocomplete (1.3.5): Verify appropriate autocomplete values on common fields: ```html <input autocomplete="name"> <input autocomplete="email"> <input autocomplete="tel"> <input autocomplete="street-address"> <input autocomplete="postal-code"> ```

Error Handling (3.3.1, 3.3.3):

• Submit forms with invalid data
• Verify errors are announced to screen readers (aria-live or focus management)
• Error messages must identify the field and describe the error
• Suggestions for fixing must be provided when possible

Authentication (3.3.8):

• Password fields must support autocomplete
• Verification code fields must allow paste
• If CAPTCHA used, accessible alternative must exist
• Consider: "Sign in with Google/Apple" as alternative

Redundant Entry (3.3.7):

• Complete multi-step processes
• Verify previously entered information is pre-filled
• Confirm "same as billing" type options exist

Category 5: Navigation and Structure

These criteria address page structure and navigation patterns.

Checklist Items

Testing Instructions

Page Structure:

• View page with CSS disabled—reading order should be logical
• Heading hierarchy should be sequential (no skipped levels)
• Use heading outline tools to verify structure

Page Titles (2.4.2):

• Each page must have a unique, descriptive title
• Title format: [Page Name] | [Site Name]
• Automated tools detect missing or duplicate titles

Link Purpose (2.4.4):

• Avoid "click here" and "read more" without context
• Links must make sense out of context OR with surrounding sentence
• Icon-only links must have accessible names

Consistency Testing (3.2.3, 3.2.4, 3.2.6):

• Navigate across multiple pages
• Verify navigation order is consistent
• Verify similar functions use consistent naming (Search vs. Find)
• Verify help links appear in same location

Category 6: Interactive Components

These criteria address complex interactive elements.

Checklist Items

Testing Instructions

Hover Content (1.4.13): Test tooltips, dropdowns, and hover previews:

• Dismissable: Escape key closes without moving mouse
• Hoverable: Can move mouse into the content without it disappearing
• Persistent: Stays visible until dismissed or focus moves

Time Limits (2.2.1):

• Identify all session timeouts
• Verify users can extend time (at least 10x)
• Provide warning at least 20 seconds before timeout

Motion and Gestures (2.5.1, 2.5.4, 2.5.7):

• Pinch-to-zoom: Provide +/- buttons
• Swipe actions: Provide arrow buttons
• Shake to undo: Provide undo button
• Drag-to-reorder: Provide up/down buttons

Target Size (2.5.8):

• Use DevTools to measure interactive elements
• Minimum 24x24 CSS pixels
• Exception: Inline links in text, user-agent controlled, essential sizing

ARIA (4.1.2):

• Custom components must have correct roles
• State changes must update aria attributes
• Screen reader must announce component identity and state

Status Messages (4.1.3):

• Success/error messages after form submission
• Loading indicators and completion notices
• Search result counts
• Cart item additions

Use aria-live regions: ```html <div aria-live="polite" aria-atomic="true"> 3 items added to cart </div> ```

Category 7: Sensory and Cognitive

These criteria address sensory and cognitive accessibility.

Checklist Items

Testing Instructions

Sensory Characteristics (1.3.3):

• Search for instructions like "click the green button" or "see sidebar"
• Ensure shape/color/position references include text alternatives
• "Submit button" not "round button on the right"

Orientation (1.3.4):

• Test on mobile devices in both orientations
• Content should adapt, not be locked to one orientation
• Exception: Content requiring specific orientation (piano app)

Use of Color (1.4.1):

• View page in grayscale
• Verify all information is still distinguishable
• Common failures: Required field indicators, error states, link distinction

Audio Control (1.4.2):

• Any audio longer than 3 seconds must have pause/stop
• Volume control must be available
• Ideally: No auto-playing audio

Audit Workflow Recommendation

For efficient WCAG Level AA auditing, follow this sequence:

Step 1: Automated Scan (1-2 hours)

Run automated tools on representative pages:

• Homepage
• Primary navigation/category pages
• Form pages (login, checkout, contact)
• Content pages (articles, product details)
• Search results page

Tools: axe DevTools, WAVE, Lighthouse, IBM Equal Access

Step 2: Semi-Automated Testing (2-4 hours)

Review automated results and verify:

• Contrast flagged by tools (verify in context)
• Missing alt text (assess appropriate alternative)
• Heading structure (review outline logic)
• Link text (evaluate in context)
• Form labels (verify association)

Step 3: Manual Testing (4-8 hours)

Complete hands-on testing:

• Full keyboard navigation test
• Screen reader testing (NVDA + Chrome, VoiceOver + Safari)
• Zoom/reflow testing
• Color/sensory testing
• Interactive component testing

Step 4: Assistive Technology Testing (2-4 hours)

• Screen reader complete workflow tests
• Voice control testing (if applicable)
• Screen magnification testing
• Switch device testing (if applicable)

Frequently Asked Questions

How many criteria are required for WCAG Level AA?

WCAG Level AA requires 56 success criteria—all 32 Level A criteria plus all 24 Level AA criteria. Conformance levels are cumulative, so you cannot skip Level A and only implement Level AA requirements.

What's the difference between this checklist and WCAG 2.1?

This checklist incorporates WCAG 2.2 changes (October 2023). Compared to WCAG 2.1 Level AA: adds 6 new criteria (2.4.11, 2.4.13, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8) and removes 1 (4.1.1 Parsing). The net result is 56 criteria vs. the previous 50.

Can automated tools fully test WCAG Level AA compliance?

No. Automated tools can detect approximately 30-40% of WCAG issues. Criteria requiring human judgment (meaningful sequence, error suggestion quality, consistent identification) and interaction testing (keyboard traps, context changes) require manual evaluation.

How often should we run this checklist?

Full audits should occur annually at minimum. Additionally: run automated scans weekly or with each deployment, test new features before launch, and conduct targeted audits when making significant changes to templates or components.

Which criteria fail most often?

According to WebAIM's annual reports, the most common failures are: 1.4.3 Contrast (86% of homepages), 1.1.1 Non-text Content/Alt Text (54%), 2.4.4 Link Purpose (50%), 1.3.1 Info and Relationships/Labels (46%), 2.4.7 Focus Visible (common but underreported). These should be priority focus areas.

Do accessibility overlays help with Level AA compliance?

Accessibility overlays cannot achieve WCAG Level AA compliance. They cannot fix issues like keyboard traps, missing form labels, incorrect heading structure, or inadequate alt text. The W3C, WebAIM, and disability advocacy organizations advise against overlay reliance. Source code remediation is required for genuine compliance.

Related Resources

• WCAG 2.2 Success Criteria List: Complete 87 Criteria Guide
• WCAG 2.2 vs 2.1: What Changed and Migration Guide
• WCAG 2.4.11 Focus Appearance Minimum: CSS Guide
• Automated vs Manual Accessibility Testing
• How to Write Effective Alt Text

This article was crafted using a cyborg approach—human expertise enhanced by AI to provide accurate, comprehensive accessibility guidance based on the official W3C WCAG 2.2 specification at https://www.w3.org/TR/WCAG22/, WebAIM resources at https://webaim.org/, and the W3C's What's New in WCAG 2.2 at https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/.