Blog

WCAG 2.2 Level AA Compliance: Complete Implementation Checklist

TestParty
TestParty
April 13, 2025

WCAG 2.2 Level AA represents the standard for legal accessibility compliance worldwide. ADA requirements, European Accessibility Act, and most procurement requirements reference WCAG Level AA. Achieving conformance requires meeting all 50 Level A and AA success criteria.

This comprehensive checklist covers every WCAG 2.2 Level AA requirement with testing approaches and implementation guidance.


Checklist Overview

WCAG 2.2 Level AA includes:

  • 30 Level A criteria (essential accessibility)
  • 20 Level AA criteria (enhanced accessibility)

Criteria are organized under four principles: Perceivable, Operable, Understandable, and Robust (POUR).


Principle 1: Perceivable

Content must be presentable to users in ways they can perceive.

1.1 Text Alternatives

1.1.1 Non-text Content (Level A)

Requirement: All non-text content has text alternatives serving equivalent purpose.

Checklist:

  • [ ] Informative images have descriptive alt text
  • [ ] Decorative images have empty alt (alt="")
  • [ ] Functional images describe the function
  • [ ] Complex images have extended descriptions
  • [ ] Form image buttons have descriptive alt
  • [ ] Image maps have alt for image and areas
  • [ ] CAPTCHA has text alternative identifying purpose

Testing:

  • Automated: Detect missing alt attributes
  • Manual: Evaluate alt text quality

1.2 Time-based Media

1.2.1 Audio-only and Video-only (Level A)

Requirement: Alternatives provided for prerecorded audio-only and video-only content.

Checklist:

  • [ ] Audio-only has text transcript
  • [ ] Video-only has text description or audio description

1.2.2 Captions (Prerecorded) (Level A)

Requirement: Captions provided for prerecorded audio in synchronized media.

Checklist:

  • [ ] All videos with audio have captions
  • [ ] Captions include dialogue and sounds
  • [ ] Captions are synchronized with audio

1.2.3 Audio Description or Media Alternative (Level A)

Requirement: Audio description or full text alternative for prerecorded video.

Checklist:

  • [ ] Videos have audio description OR
  • [ ] Videos have full text transcript including visual descriptions

1.2.4 Captions (Live) (Level AA)

Requirement: Captions provided for live audio in synchronized media.

Checklist:

  • [ ] Live video/audio has real-time captions
  • [ ] CART or auto-captioning configured

1.2.5 Audio Description (Prerecorded) (Level AA)

Requirement: Audio description provided for prerecorded video.

Checklist:

  • [ ] Videos have audio description track
  • [ ] Visual content is described in audio

1.3 Adaptable

1.3.1 Info and Relationships (Level A)

Requirement: Information, structure, and relationships are programmatically determinable.

Checklist:

  • [ ] Headings use proper heading elements (h1-h6)
  • [ ] Lists use proper list elements (ul, ol, li)
  • [ ] Tables use proper table elements with headers
  • [ ] Form labels are programmatically associated
  • [ ] Regions use landmark elements
  • [ ] Required fields are programmatically indicated

1.3.2 Meaningful Sequence (Level A)

Requirement: Correct reading sequence is programmatically determinable.

Checklist:

  • [ ] DOM order matches visual reading order
  • [ ] CSS positioning doesn't break reading sequence
  • [ ] Content makes sense when linearized

1.3.3 Sensory Characteristics (Level A)

Requirement: Instructions don't rely solely on sensory characteristics.

Checklist:

  • [ ] Instructions don't rely only on shape ("round button")
  • [ ] Instructions don't rely only on color ("click green")
  • [ ] Instructions don't rely only on location ("menu on left")
  • [ ] Instructions don't rely only on sound

1.3.4 Orientation (Level AA)

Requirement: Content doesn't restrict operation to single orientation.

Checklist:

  • [ ] Content works in portrait and landscape
  • [ ] No forced orientation unless essential

1.3.5 Identify Input Purpose (Level AA)

Requirement: Input purpose can be programmatically determined for common fields.

Checklist:

  • [ ] Personal info fields have autocomplete attributes
  • [ ] Name fields: autocomplete="name"
  • [ ] Email: autocomplete="email"
  • [ ] Phone: autocomplete="tel"
  • [ ] Address fields use appropriate tokens

1.4 Distinguishable

1.4.1 Use of Color (Level A)

Requirement: Color is not the only means of conveying information.

Checklist:

  • [ ] Links distinguishable by more than color
  • [ ] Errors indicated by more than color
  • [ ] Charts use patterns/labels, not just colors
  • [ ] Form validation uses icons/text, not just color

1.4.2 Audio Control (Level A)

Requirement: Mechanism to pause/stop audio playing automatically for >3 seconds.

Checklist:

  • [ ] Auto-playing audio has pause control
  • [ ] Or volume control independent of system
  • [ ] Or audio stops within 3 seconds

1.4.3 Contrast (Minimum) (Level AA)

Requirement: Text has minimum 4.5:1 contrast ratio (3:1 for large text).

Checklist:

  • [ ] Normal text: 4.5:1 or higher
  • [ ] Large text (18pt+/14pt bold+): 3:1 or higher
  • [ ] Placeholder text meets requirements
  • [ ] Link text meets requirements

1.4.4 Resize Text (Level AA)

Requirement: Text resizable up to 200% without loss of functionality.

Checklist:

  • [ ] Text resizes with browser zoom
  • [ ] No horizontal scrolling at 200% zoom
  • [ ] Content not truncated or overlapped
  • [ ] All functionality remains available

1.4.5 Images of Text (Level AA)

Requirement: Text used rather than images of text (with exceptions).

Checklist:

  • [ ] Text content is actual text, not images
  • [ ] Logos with text are acceptable exceptions
  • [ ] User-customizable images of text acceptable

1.4.10 Reflow (Level AA)

Requirement: Content reflows without two-dimensional scrolling at 320px width.

Checklist:

  • [ ] No horizontal scrolling at 320px width for vertical content
  • [ ] No vertical scrolling at 256px height for horizontal content
  • [ ] Content remains readable and functional

1.4.11 Non-text Contrast (Level AA)

Requirement: UI components and graphics have 3:1 contrast.

Checklist:

  • [ ] UI component boundaries: 3:1 contrast
  • [ ] Focus indicators: 3:1 contrast
  • [ ] Graphical objects: 3:1 contrast
  • [ ] Custom form controls meet requirement

1.4.12 Text Spacing (Level AA)

Requirement: Content works with increased text spacing.

Checklist:

  • [ ] Line height 1.5x font size works
  • [ ] Paragraph spacing 2x font size works
  • [ ] Letter spacing 0.12x font size works
  • [ ] Word spacing 0.16x font size works

1.4.13 Content on Hover or Focus (Level AA)

Requirement: Additional content on hover/focus is dismissible, hoverable, persistent.

Checklist:

  • [ ] Tooltips/popups can be dismissed (Escape)
  • [ ] User can hover over revealed content
  • [ ] Content persists until dismissed/trigger removed

Principle 2: Operable

User interface components must be operable.

2.1 Keyboard Accessible

2.1.1 Keyboard (Level A)

Requirement: All functionality available via keyboard.

Checklist:

  • [ ] All interactive elements focusable
  • [ ] All actions triggerable via keyboard
  • [ ] No keyboard-specific timing required

2.1.2 No Keyboard Trap (Level A)

Requirement: Keyboard focus can be moved away from any component.

Checklist:

  • [ ] No components trap keyboard focus
  • [ ] Modal focus traps allow Escape to exit
  • [ ] All expandable content can be exited

2.1.4 Character Key Shortcuts (Level A)

Requirement: Single character shortcuts can be turned off/remapped.

Checklist:

  • [ ] Single key shortcuts are remappable OR
  • [ ] Single key shortcuts can be turned off OR
  • [ ] Shortcuts only active on focus

2.2 Enough Time

2.2.1 Timing Adjustable (Level A)

Requirement: Time limits can be adjusted.

Checklist:

  • [ ] User can turn off time limit OR
  • [ ] User can extend time limit OR
  • [ ] User warned with 20 seconds to extend

2.2.2 Pause, Stop, Hide (Level A)

Requirement: Moving/blinking content can be paused.

Checklist:

  • [ ] Carousels have pause controls
  • [ ] Animations can be stopped
  • [ ] Auto-updating content can be paused

2.3 Seizures and Physical Reactions

2.3.1 Three Flashes or Below (Level A)

Requirement: No content flashes more than 3 times per second.

Checklist:

  • [ ] No flashing content above threshold
  • [ ] Videos checked for flash sequences

2.4 Navigable

2.4.1 Bypass Blocks (Level A)

Requirement: Mechanism to bypass repeated content blocks.

Checklist:

  • [ ] Skip navigation link present
  • [ ] Skip link moves focus to main content
  • [ ] Landmark regions defined

2.4.2 Page Titled (Level A)

Requirement: Pages have descriptive titles.

Checklist:

  • [ ] Every page has unique, descriptive title
  • [ ] Title reflects page content/purpose

2.4.3 Focus Order (Level A)

Requirement: Focus order preserves meaning and operability.

Checklist:

  • [ ] Focus order is logical
  • [ ] Focus order matches visual layout
  • [ ] Modal dialogs trap focus appropriately

2.4.4 Link Purpose (In Context) (Level A)

Requirement: Link purpose determinable from link text or context.

Checklist:

  • [ ] Links have descriptive text
  • [ ] "Read more" links have context
  • [ ] Identical links go to same destination

2.4.5 Multiple Ways (Level AA)

Requirement: Multiple ways to locate pages (except process steps).

Checklist:

  • [ ] Site includes search OR sitemap
  • [ ] Navigation plus additional discovery method

2.4.6 Headings and Labels (Level AA)

Requirement: Headings and labels describe topic or purpose.

Checklist:

  • [ ] Headings are descriptive
  • [ ] Form labels describe input purpose
  • [ ] Section headings reflect content

2.4.7 Focus Visible (Level AA)

Requirement: Keyboard focus indicator is visible.

Checklist:

  • [ ] Focus indicators visible on all elements
  • [ ] Focus indicators have adequate contrast
  • [ ] Custom focus styles are visible

2.4.11 Focus Not Obscured (Minimum) (Level AA) — NEW in 2.2

Requirement: Focused element not entirely hidden.

Checklist:

  • [ ] Sticky headers don't fully cover focused elements
  • [ ] Fixed footers don't fully cover focused elements
  • [ ] At least part of focused element visible

2.4.12 Focus Not Obscured (Enhanced) (Level AAA) — NEW in 2.2

Note: AAA criterion, not required for Level AA compliance.


2.4.13 Focus Appearance (Level AAA) — NEW in 2.2

Note: AAA criterion, not required for Level AA compliance.


2.5 Input Modalities

2.5.1 Pointer Gestures (Level A)

Requirement: Multipoint/path gestures have single-pointer alternatives.

Checklist:

  • [ ] Pinch zoom has button alternative
  • [ ] Swipe gestures have button alternatives
  • [ ] Complex gestures not required

2.5.2 Pointer Cancellation (Level A)

Requirement: Functions using down-event allow abort/undo.

Checklist:

  • [ ] Actions complete on up-event OR
  • [ ] Actions can be aborted OR
  • [ ] Actions can be undone

2.5.3 Label in Name (Level A)

Requirement: Visible label is included in accessible name.

Checklist:

  • [ ] Accessible names include visible text
  • [ ] aria-label includes visible text

2.5.4 Motion Actuation (Level A)

Requirement: Motion-triggered functions have UI alternatives.

Checklist:

  • [ ] Shake/tilt actions have button alternatives
  • [ ] Motion can be disabled

2.5.7 Dragging Movements (Level AA) — NEW in 2.2

Requirement: Dragging functions have single-pointer alternatives.

Checklist:

  • [ ] Drag-and-drop has click alternative
  • [ ] Sliders have increment buttons
  • [ ] Sortable lists have move buttons

2.5.8 Target Size (Minimum) (Level AA) — NEW in 2.2

Requirement: Touch targets at least 24x24 CSS pixels.

Checklist:

  • [ ] Touch targets minimum 24x24 pixels
  • [ ] Spacing between small targets adequate
  • [ ] Inline links exempt

Principle 3: Understandable

Information and interface operation must be understandable.

3.1 Readable

3.1.1 Language of Page (Level A)

Requirement: Page language programmatically identified.

Checklist:

  • [ ] HTML has lang attribute
  • [ ] Language code is valid

3.1.2 Language of Parts (Level AA)

Requirement: Language changes within content identified.

Checklist:

  • [ ] Foreign phrases have lang attribute
  • [ ] Language changes marked in HTML

3.2 Predictable

3.2.1 On Focus (Level A)

Requirement: Receiving focus doesn't cause unexpected context change.

Checklist:

  • [ ] Focus doesn't trigger navigation
  • [ ] Focus doesn't open new windows
  • [ ] Focus doesn't submit forms

3.2.2 On Input (Level A)

Requirement: Changing settings doesn't cause unexpected context change.

Checklist:

  • [ ] Form changes don't auto-submit
  • [ ] User advised before auto-changes
  • [ ] Select changes don't navigate without warning

3.2.3 Consistent Navigation (Level AA)

Requirement: Navigation is consistent across pages.

Checklist:

  • [ ] Navigation order consistent
  • [ ] Navigation location consistent
  • [ ] Same navigation items across pages

3.2.4 Consistent Identification (Level AA)

Requirement: Same functionality identified consistently.

Checklist:

  • [ ] Same icons labeled consistently
  • [ ] Same functions named consistently
  • [ ] Search always labeled "Search"

3.2.6 Consistent Help (Level A) — NEW in 2.2

Requirement: Help mechanisms in consistent location.

Checklist:

  • [ ] Help contact info in consistent location
  • [ ] Help links/buttons consistently placed
  • [ ] Support mechanisms consistently available

3.3 Input Assistance

3.3.1 Error Identification (Level A)

Requirement: Input errors automatically detected are described.

Checklist:

  • [ ] Errors identified in text
  • [ ] Error fields identified
  • [ ] Errors not indicated by color alone

3.3.2 Labels or Instructions (Level A)

Requirement: Labels or instructions provided for user input.

Checklist:

  • [ ] All form fields have labels
  • [ ] Required fields indicated
  • [ ] Format requirements stated

3.3.3 Error Suggestion (Level AA)

Requirement: Known error corrections suggested.

Checklist:

  • [ ] Error messages suggest fixes
  • [ ] Format examples provided
  • [ ] Valid options suggested

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Requirement: Legal/financial/data submissions are reversible/checked/confirmable.

Checklist:

  • [ ] Submissions can be reviewed before final
  • [ ] Submissions can be corrected
  • [ ] Confirmation step for significant actions

3.3.7 Redundant Entry (Level A) — NEW in 2.2

Requirement: Previously entered info auto-populated or selectable.

Checklist:

  • [ ] Multi-step forms remember earlier entries
  • [ ] Redundant fields auto-filled
  • [ ] Users can select previous entries

3.3.8 Accessible Authentication (Minimum) (Level AA) — NEW in 2.2

Requirement: Cognitive tests not required for authentication.

Checklist:

  • [ ] No transcription CAPTCHAs required OR
  • [ ] Alternative authentication available
  • [ ] Copy/paste allowed for passwords
  • [ ] Password managers supported

Principle 4: Robust

Content must be robust enough for interpretation by assistive technologies.

4.1 Compatible

4.1.2 Name, Role, Value (Level A)

Requirement: UI components have programmatically determinable name, role, and state.

Checklist:

  • [ ] All components have accessible names
  • [ ] Roles are appropriate
  • [ ] States are communicated (expanded, selected, etc.)
  • [ ] Custom components use ARIA correctly

4.1.3 Status Messages (Level AA)

Requirement: Status messages programmatically determinable without focus.

Checklist:

  • [ ] Success messages announced
  • [ ] Error messages announced
  • [ ] Progress updates announced
  • [ ] Use aria-live appropriately

Implementation Approach

Phase 1: Foundation (Weeks 1-2)

Focus on fundamental accessibility:

  • Heading structure
  • Alt text
  • Form labels
  • Keyboard access
  • Color contrast

Phase 2: Enhancement (Weeks 3-4)

Address interaction and experience:

  • Focus management
  • Error handling
  • Captions and transcripts
  • ARIA implementation

Phase 3: Refinement (Ongoing)

Continuous improvement:

  • User testing
  • Edge cases
  • Third-party content
  • New features

Taking Action

WCAG 2.2 Level AA compliance requires systematic attention to all 50 success criteria. Use this checklist as a starting point, implement continuous monitoring to maintain compliance, and integrate accessibility testing into development workflows.

Schedule a TestParty demo and get a 14-day compliance implementation plan.


Related Resources

Contact Us

Automate the software work for accessibility compliance, end-to-end.

Empowering businesses with seamless digital accessibility solutions—simple, inclusive, effective.

Book a Demo