Is this enough to be WCAG 2.2 AA compliant?

It covers the most-failed criteria, but a full WCAG 2.2 AA audit has ~50 success criteria. Use this for ongoing development; commission a formal audit if you need legal or VPAT-level compliance.

How do I test contrast quickly?

Use the contrast checker in this tools collection, or browser devtools (Chrome and Firefox both highlight insufficient contrast inline). Aim for 4.5:1 on body text.

Do I really need to test with a screen reader?

Yes. Automated tools catch maybe 30% of accessibility issues. The rest (wrong reading order, broken focus management, confusing button labels) are only obvious when you actually use a screen reader.

What WCAG version is this for?

WCAG 2.2 Level AA, the standard most regulations (ADA, EAA, AODA) reference. The 2.2 additions over 2.1 include focus appearance and dragging movement requirements.

WCAG accessibility checklist — free tool

Color & contrast

0 / 5

Body text contrast ratio ≥ 4.5:1 against background
Large text (18pt+/14pt bold+) contrast ratio ≥ 3:1
UI components and icons have ≥ 3:1 contrast
Information is not conveyed by color alone
Focus states have ≥ 3:1 contrast against adjacent colors

Keyboard

0 / 6

Every interactive element reachable with Tab
Tab order matches visual order
Focus state visible on every focusable element
No keyboard traps (can Tab in and out of every component)
Skip-to-content link exists at the top of the page
Modal dialogs trap focus inside and return focus on close

Screen reader

0 / 7

Tested with VoiceOver (Mac), NVDA (Windows), or TalkBack (Android)
All non-decorative images have alt text
Decorative images use alt="" (not omitted)
Buttons and links have descriptive accessible names
aria-label used only when no visible label exists
Page has a single, descriptive <h1>
Headings in logical order (no skipped levels)

Forms

0 / 5

Every input has a visible <label>
Required fields marked with both visual and programmatic indicators
Error messages tied to inputs via aria-describedby
Errors announced to screen readers (aria-live region)
Inputs have appropriate type and autocomplete attributes

Media

0 / 4

Videos have captions
Audio content has a transcript
No auto-playing audio (or has visible mute control)
Animations respect prefers-reduced-motion

Structure & semantics

0 / 5

Page uses landmarks (header, nav, main, footer)
Lists use <ul> / <ol>, not styled divs
Tables use <th> with scope attribute for data tables
Language attribute set on <html>
Page title unique and describes the page

Website accessibility (WCAG) checklist

Color & contrast

Keyboard

Screen reader

Forms

Media

Structure & semantics

How to use this tool

About this tool

Related tools

Bug report template generator

Website pre-launch checklist

Website QA checklist

Website handoff checklist

Frequently asked questions

Is this enough to be WCAG 2.2 AA compliant?

How do I test contrast quickly?

Do I really need to test with a screen reader?

What WCAG version is this for?

Reviewing work with your team?