Find my businessStart

WCAG 2.1 AA checklist PDF: a printable audit sheet you can fill in

This WCAG 2.1 AA checklist is built to be printed or saved as a PDF: 30 checks a non-developer can run on a page in about 40 minutes, each with how to test it and a box to tick. To get the PDF, press Ctrl+P (Cmd+P on Mac) and choose "Save as PDF" as the printer; the menus and boxes on this page hide themselves in the print version. We do not ask for your email to download it. It covers the errors that most often fail on small business sites; the full guideline has more, listed in our WCAG 2.1 AA checklist of all 50 criteria. We are not lawyers; this is not legal advice.

Rather not do the 30 checks yourself? Site Record runs automated tests and a keyboard walk on up to 25 pages, writes every fix and rechecks monthly for a year: $499 once.

How to use this printable WCAG checklist

  1. Pick three pages: the home page, a page with a form (contact or booking) and a page with the most pictures. Print one copy per page.
  2. Run a free scan first. A browser extension covers the automated rows in a minute; see the Chrome extension guide.
  3. Do the manual rows. Those marked "by hand" cannot be tested by software, so no scanner will tell you.
  4. Tick pass, or write the element and the page in the notes column for a fail.
  5. Score it using the rule at the end and hand the fails to whoever edits your site.

Tools used: a keyboard, a zoom setting, a free scanner and a colour contrast tool. Our contrast checker guide shows how to read a ratio.

WCAG 2.1 AA checklist PDF: images and media

#CheckHow to testPass
1Every meaningful image has alt text that says what it showsScanner, then read by hand: is it a file name or a real description?☐
2Decorative images have empty alt text (alt="")Scanner for missing alt; by hand for the rest☐
3Images of text are avoided (a menu or sale banner is real text)By hand: try to select the words☐
4Videos have captionsBy hand: play with sound off☐
5Nothing flashes more than three times a second; moving content can be pausedBy hand: watch the carousel and any autoplay☐
6PDF menus or forms that matter are also on a web pageBy hand: could you read it without the PDF?☐

Colour and text

#CheckHow to testPass
7Body text has a contrast ratio of at least 4.5 to 1Scanner or contrast tool☐
8Large text (about 24px, or 19px bold) has at least 3 to 1Contrast tool☐
9Buttons, input borders and icons have at least 3 to 1 against what sits behind themContrast tool, by hand☐
10Colour is never the only signal (a red error also has words)By hand: view the page in greyscale☐
11Text can be zoomed to 200% without loss of contentBrowser zoom to 200%; nothing cut off or overlapping☐
12At 320px wide (or 400% zoom) the page scrolls one way onlyNarrow the window or zoom to 400%☐
13Text can be spaced out without breaking the layoutBy hand, with a text-spacing bookmarklet or extension☐

Keyboard and focus

#CheckHow to testPass
14Everything clickable can be reached with the Tab keyBy hand: unplug the mouse, press Tab through the page☐
15The focus outline is always visibleBy hand while tabbing☐
16Tab order follows the visual orderBy hand☐
17Menus, pop-ups and carousels open and close with the keyboardBy hand: Enter, Space, Escape☐
18You are never trapped: you can always Tab awayBy hand, especially in cookie banners and chat widgets☐
19A "skip to main content" link exists, or the page has landmarksPress Tab once on page load☐

Structure and links

#CheckHow to testPass
20The page has one h1 and headings follow in orderScanner shows the outline☐
21Each page has a unique, descriptive titleRead the browser tab☐
22Link text makes sense alone (not "click here" or "read more")Scanner for empty links; by hand for vague ones☐
23Icon-only links and buttons have a name (cart, search, menu)Scanner☐
24The page language is set (lang="en")Scanner☐

Forms and errors

#CheckHow to testPass
25Every field has a visible label, not only placeholder textScanner; by hand: does the label stay after typing?☐
26Required fields are marked in words, not colour aloneBy hand☐
27An error says what went wrong and how to fix itBy hand: submit the form empty and with a bad email☐
28Name, email and address fields use autocompleteScanner or view source☐

Reading and context

#CheckHow to testPass
29Pop-ups and chat bubbles do not hide the content or cannot be closedBy hand, on a phone-sized window too☐
30An accessibility statement page exists and says how to reach youCheck the footer☐

How to score the checklist

Count the ticks per page. Treat the number as a rough guide, not a certificate.

Ticks out of 30What it suggests
27 to 30Good shape; a professional audit may still find criteria not on this sheet
20 to 26Typical: fix the fails, which usually sit in the theme and repeat on every page
Under 20Start with the keyboard, contrast and form rows; they affect the most people

A failed row matters more if it appears on the home page, the form or the checkout. Fix template-level fails first: one footer or menu fix repairs the whole site.

What this checklist does not cover

It is a sample. WCAG 2.1 AA has 50 success criteria, and several need a screen reader or specialist knowledge: reading order for assistive technology, correct ARIA, status messages, orientation, input purpose and consistent navigation among them. A scanner finds part of the rest. If you have received a demand letter, or you take bookings or payments, get a written audit; see accessibility audit services for websites and what an audit costs.

Checklist PDF, spreadsheet or tool: which format

After the checklist: fix, retest, publish

  1. Group the fails by where they live: theme, plugin, page content or a third party.
  2. Fix the theme and plugin ones first, then content.
  3. Rerun the sheet on the same three pages and keep both copies, dated.
  4. Publish an accessibility statement with what you did and a contact; see the statement template.
  5. Repeat every quarter and after any redesign.

Quick fixes for the rows that fail most

RowTypical causeUsual fix
1, 2 Alt textPhotos uploaded with file names; decorative icons with no empty altWrite one plain sentence per meaningful photo; set alt="" on decoration
7, 8, 9 ContrastPale grey text, light brand colours on white, white text on a photoDarken the text colour in the theme settings until the ratio passes; add a solid band behind text on photos
15 Focus outlineA theme rule removes the outline (outline: none)Delete the rule or add a clear focus style
17 MenusHover-only dropdownsOpen on Enter or Space as well; ask the theme maker or switch the menu setting
22, 23 Link namesIcon links and "read more" repeatedAdd a text label or aria-label that says where it goes
25 LabelsPlaceholder used as a label by the form pluginTurn on visible labels in the form plugin settings
27 ErrorsA red border and nothing elseAdd a text message next to the field

Most of these sit in one theme or one plugin, which is why a small site often has 20 to 40 reported errors but only five or six causes. Fix the cause and many rows turn to ticks at once.

Why these 30 checks and not all 50 criteria

The sheet is built around what a person can test without special software and what tends to fail on small business sites: images, contrast, keyboard use, links and forms. It leaves out criteria that mostly matter on complex web apps, such as drag-and-drop alternatives or timing controls, and criteria that need a screen reader to judge. That makes it quick enough to finish, which is the point: a checklist nobody completes finds nothing. When the sheet is clean, move to the full list or a written audit.

Not sure which rules apply to your business? See ADA website compliance requirements.

Frequently asked questions

Is there a free WCAG 2.1 AA checklist PDF?

Yes. This page prints to PDF from your browser, with no email needed. The W3C and WebAIM also publish free lists.

Can a checklist make my site WCAG compliant?

No. It finds problems; fixing them and retesting is what moves a site toward compliance.

How long does the checklist take?

About 40 minutes for one page, less once you know where the repeat errors are.

Which WCAG version is the standard?

WCAG 2.1 AA is the level most often named in ADA settlements and guidance. Newer versions add criteria; a site passing 2.1 AA is a good base.

Do I need a developer?

Not to run the checks. You may need one to change theme code; hand them the filled sheet.

Is a spreadsheet version better?

Use one if you track many pages. Copy the tables here into a spreadsheet and add columns.

Want the full list done for you? Site Record, $499 once. More: all accessibility guides.

Sources