Find my businessStart

WCAG 2.1 AA checklist: all 50 criteria in plain words

A WCAG 2.1 AA checklist covers 50 success criteria: 30 at Level A and 20 at Level AA. Passing means every one of them is met on the pages you test, or does not apply. Below is the full list in plain words, grouped by what a visitor experiences, with a note on which ones a free scanner can check and which need you to look. Courts and settlements most often point to this standard when they judge a business website, though no US rule names it for private businesses. We are not lawyers; this is not legal advice.

Rather not walk 50 rows yourself? Site Record tests up to 25 pages and lists each error with the fix for your platform, then rechecks monthly for 12 months: $499 once.

How to use this WCAG 2.1 AA checklist

  1. Pick your key pages: home, a service or product, the contact or checkout page, and one long page.
  2. Run a free scanner first (see our Chrome extension guide). Scanners test the rows marked scan below, and only part of those.
  3. Go through the rows marked look yourself with the keyboard, zoom and your own eyes.
  4. Write pass, fail or not applicable beside each criterion, with the page and the element.
  5. Fix in the order at the end, then rescan.

Verify wording against the W3C's own text, the WCAG 2.1 Quick Reference, before you rely on any checklist, including this one; some published lists place criteria at the wrong level (for example 44 by 44 pixel touch targets, which is a Level AAA criterion in 2.1).

1. Perceivable: can people see, hear or read it?

No.LevelPlain wordsHow to test
1.1.1 Non-text contentAEvery meaningful image has alt text; decoration has empty altscan, then look
1.2.1 Audio-only, video-onlyAA transcript or alternative for recorded audio or silent videolook
1.2.2 Captions (recorded)AVideos with sound have captionslook
1.2.3 Audio description or alternativeAVideo has a description or a text versionlook
1.2.4 Captions (live)AALive video has captionslook
1.2.5 Audio description (recorded)AARecorded video has audio descriptionlook
1.3.1 Info and relationshipsAHeadings, lists, tables and form labels are real markupscan, then look
1.3.2 Meaningful sequenceAThe reading order makes sense without the stylinglook
1.3.3 Sensory characteristicsAInstructions do not rely only on shape, colour or positionlook
1.3.4 OrientationAAWorks in portrait and landscapelook
1.3.5 Identify input purposeAAName, email and address fields say what they are, so browsers can fill themscan
1.4.1 Use of colourAColour is not the only way to show something (link, error)look
1.4.2 Audio controlASound that plays over 3 seconds can be pausedlook
1.4.3 Contrast (minimum)AAText is at least 4.5 to 1 against its background (3 to 1 for large text)scan
1.4.4 Resize textAAText zooms to 200 per cent with nothing lostlook
1.4.5 Images of textAAReal text instead of text in a picturelook
1.4.10 ReflowAAAt 400 per cent zoom, no sideways scrolling for main contentlook
1.4.11 Non-text contrastAAButtons, fields and icons are at least 3 to 1 against neighbourslook
1.4.12 Text spacingAANothing breaks if a user increases line, letter and word spacinglook
1.4.13 Content on hover or focusAAPop-ups from hover or focus can be dismissed and do not vanish when you reach themlook

The two rows scanners do best at are 1.1.1 (finding images with no alt attribute at all) and 1.4.3 (colours). Our colour contrast checker guide shows how to fix a failing colour in a minute.

2. Operable: can people use it without a mouse?

No.LevelPlain wordsHow to test
2.1.1 KeyboardAEverything works with the keyboard alonelook
2.1.2 No keyboard trapAYou can always tab out of a widgetlook
2.1.4 Character key shortcutsASingle-key shortcuts can be turned off or changedlook
2.2.1 Timing adjustableATime limits can be extended or removedlook
2.2.2 Pause, stop, hideAMoving or auto-updating content (sliders) can be stoppedlook
2.3.1 Three flashesANothing flashes more than three times a secondlook
2.4.1 Bypass blocksAA skip link or landmarks let people jump past the menuscan, then look
2.4.2 Page titledAEach page has a clear titlescan
2.4.3 Focus orderATab order follows the visual orderlook
2.4.4 Link purposeALink text makes sense in contextscan, then look
2.4.5 Multiple waysAAMore than one way to find a page (menu, search, sitemap)look
2.4.6 Headings and labelsAAHeadings and labels describe their contentlook
2.4.7 Focus visibleAAYou can see where the keyboard focus islook
2.5.1 Pointer gesturesAAnything done with a swipe or pinch also works with a taplook
2.5.2 Pointer cancellationAA tap triggers on release, so a slip can be undonelook
2.5.3 Label in nameAA button's spoken name contains its visible wordsscan, then look
2.5.4 Motion actuationAShaking or tilting is never the only way to actlook

2.1.1 and 2.4.7 are the ones that fail most on small business sites. Press Tab from the top of the page. If the focus outline disappears, a theme has turned it off, which is usually one line of style code to restore.

3. Understandable: is it clear and predictable?

No.LevelPlain wordsHow to test
3.1.1 Language of pageAThe page declares its languagescan
3.1.2 Language of partsAAA passage in another language is markedscan, then look
3.2.1 On focusALanding on a field does not change the pagelook
3.2.2 On inputAEntering a value does not submit or jump without warninglook
3.2.3 Consistent navigationAAMenus stay in the same place and orderlook
3.2.4 Consistent identificationAASame function, same name everywherelook
3.3.1 Error identificationAForm errors are described in textlook
3.3.2 Labels or instructionsAEvery field has a visible labelscan, then look
3.3.3 Error suggestionAAThe error says how to fix itlook
3.3.4 Error preventionAAPayments and legal forms can be reviewed, corrected or undonelook

4. Robust: does it work with assistive technology?

No.LevelPlain wordsHow to test
4.1.1 ParsingAValid markup, no duplicate IDs (obsolete in 2.2, still listed in 2.1)scan
4.1.2 Name, role, valueACustom controls tell a screen reader what they are and their statescan, then look
4.1.3 Status messagesAA"Added to cart" and similar messages are announcedlook

What the 2.1 AA checklist adds to 2.0

WCAG 2.1 kept every 2.0 criterion and added 17, twelve of them at A or AA: 1.3.4, 1.3.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.4, 2.5.1, 2.5.2, 2.5.3, 2.5.4 and 4.1.3. They mostly concern phones, zoom and low vision. WCAG 2.2 followed in October 2023 with nine more and dropped 4.1.1. In April 2024 the US Department of Justice adopted WCAG 2.1 AA for state and local government websites; private businesses have no such rule, but the standard is the one people will reach for.

What to fix first on a small site

  1. Contrast (1.4.3) and focus outline (2.4.7). Quick style changes with large effect.
  2. Alt text (1.1.1) and link names (2.4.4). Content edits you can make today.
  3. Form labels and errors (3.3.1, 3.3.2, 3.3.3). They block sales and contact messages.
  4. Keyboard access (2.1.1, 2.1.2). Menus, pop-ups and sliders; often a theme issue.
  5. Headings and page titles (1.3.1, 2.4.2, 2.4.6).
  6. Video captions (1.2.2) and zoom (1.4.4, 1.4.10).

The shorter ADA compliant website checklist turns these into 25 checks you can run in a week, and free checkers will do the scanning part. Publish an honest accessibility statement once you have a pass list.

Can a scanner pass a site for WCAG 2.1 AA?

No. Automated tools detect only a part of the criteria, and for those they can say "no errors found", not "accessible". A scan with zero errors can sit on a site where a keyboard user cannot reach the checkout. That is why the table has a "look" column, and why an overlay widget cannot settle it either: the FTC's January 2025 order against accessiBe was about claims that its tool made sites WCAG compliant.

For the legal background, read ADA website compliance requirements.

Frequently asked questions

How many criteria are in WCAG 2.1 AA?

50: 30 at Level A and 20 at Level AA. WCAG 2.1 has 78 in total, with 28 more at Level AAA.

Is WCAG 2.1 AA required by the ADA?

The ADA does not name a standard for private websites. Courts and settlements usually use WCAG 2.1 AA, and government sites have a rule naming it.

What is the difference between WCAG 2.1 and 2.2?

2.2 adds nine criteria, including a minimum target size of 24 pixels, and removes 4.1.1 Parsing.

Is there a WCAG 2.1 AA checklist PDF?

Several vendors publish one. Check any list against the W3C Quick Reference; this page is the same list as a web page you can print.

What do I fix first?

Contrast, focus outline, alt text, form labels and keyboard access.

How long does a WCAG 2.1 AA check take?

A scan takes minutes. A careful manual pass through key pages takes hours; a full audit of a larger site takes longer.

Get the pass and fail list written for you: Site Record, $499 once. More: all accessibility guides.

Want a version you can print? Use the WCAG 2.1 AA checklist PDF, a 30-check sheet with pass boxes.

Sources