UtilibyWritten by the Utiliby editorial team · Last updated October 13, 2026 · Rules and formulas reviewed October 2026
What this free WCAG checklist generator does
This free online WCAG 2.2 checklist generator turns the Web Content Accessibility Guidelines into a working audit sheet. All 86 success criteria are listed with their level (A, AA or AAA), their principle (Perceivable, Operable, Understandable or Robust), a one-line description of what to look for and a status menu: Not tested, Pass, Fail or Not applicable. You add notes for each item, filter by level, principle or status, and watch your progress and pass rate update as you go.
The Audit summary tab turns your marks into a report with the overall result against your target level, a donut chart, pass rates for each principle, results at each level and a table of failures with your notes. You can print it to PDF, export a CSV or copy it for a ticket or an email. Progress is kept in your browser, so you can come back and carry on. The nine criteria that are new in WCAG 2.2 are clearly marked.
How to use the WCAG checklist
- Set up. Enter the project name, website address, tester and date, and choose the target level. AA is the usual choice.
- Work through the criteria. Test the site against each item and set Pass, Fail or Not applicable. Use Search and the Principle filter to focus on one area at a time.
- Add notes. Write the page, the problem or the fix beside each result. Notes appear in the summary and CSV.
- Track progress. The bar shows how many criteria you have reviewed.
- Read the summary. It tells you whether you meet the target level, and lists the failures.
- Export. Print to PDF or download the CSV to share, import into a tracker or use as a base for a VPAT.
WCAG levels A, AA and AAA explained
| Level | Criteria | Meaning | Typically required? |
|---|---|---|---|
| A | 31 | The minimum. Without these, some people cannot use the content at all. | Always part of any conformance claim |
| AA | 24 more (55 total) | Removes the biggest remaining barriers, such as low contrast and missing captions for live video. | Yes, in most laws and policies |
| AAA | 31 more (86 total) | The highest level, with demanding requirements such as sign language and 7:1 contrast. | No, but useful as a goal for suitable content |
Conformance is cumulative: to claim Level AA you must meet all Level A and all Level AA criteria. You cannot skip A to reach AA.
The four principles: POUR
- Perceivable. Information must be presentable in ways users can perceive: text alternatives, captions, adaptable layout, colour contrast and distinguishable content (guidelines 1.1 to 1.4).
- Operable. The interface must be operable: keyboard access, enough time, no seizure-causing flashes, navigation, input modalities and pointer targets (guidelines 2.1 to 2.5).
- Understandable. Content and operation must be understandable: readable language, predictable behaviour and help with errors (guidelines 3.1 to 3.3).
- Robust. Content must work with current and future user agents, including assistive technology: names, roles, values and status messages (guideline 4.1).
What is new in WCAG 2.2
WCAG 2.2 became a W3C Recommendation in October 2023 and builds on 2.1. It focuses on users with low vision, cognitive and learning disabilities and users of touch screens and mobile devices.
| Criterion | Level | In plain English |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Sticky headers and banners must not completely cover the focused item. |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focused item is hidden. |
| 2.4.13 Focus Appearance | AAA | The focus indicator must be big enough and contrast enough. |
| 2.5.7 Dragging Movements | AA | Anything you can drag must also work with a simple click or tap. |
| 2.5.8 Target Size (Minimum) | AA | Targets are at least 24 by 24 CSS pixels, or well spaced. |
| 3.2.6 Consistent Help | A | Help links appear in the same place on every page. |
| 3.3.7 Redundant Entry | A | Do not make users type the same information twice. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in must not depend on remembering or solving a puzzle. |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | No cognitive test at all for authentication. |
WCAG 2.2 also removes 4.1.1 Parsing. Six of the nine new criteria are at Level A or AA (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7 and 3.3.8), so a site that already meets WCAG 2.1 AA has six new items to check for AA.
Defining your scope: pages, processes and samples
WCAG conformance is claimed for whole web pages, and for complete processes such as a checkout. Before you start, decide which pages or templates are in scope. For a large site, test a representative sample: the home page, key templates, forms, search, account pages, a few content pages, error states and PDFs or media that are essential. List the browser and assistive technology combinations you used. Write that scope in the project name or the notes so the summary can be understood later.
How to test the criteria
| Technique | Helps you test |
|---|---|
| Keyboard only | 2.1.1, 2.1.2, 2.4.3, 2.4.7, 2.4.11, 2.5.7 |
| Zoom to 200% and 400% | 1.4.4, 1.4.10, 1.4.12 |
| Colour contrast checker | 1.4.3, 1.4.6, 1.4.11 |
| Screen reader (NVDA, VoiceOver, TalkBack) | 1.1.1, 1.3.1, 2.4.4, 3.3.1, 4.1.2, 4.1.3 |
| Automated checker | Language, titles, labels, ARIA errors, alt attributes |
| Review of captions and transcripts | 1.2.1 to 1.2.5 |
| Try forms and login with errors | 3.3.1 to 3.3.4, 3.3.7, 3.3.8 |
Automated tools find only a share of problems, so every criterion needs human judgement. Use the HTML accessibility checker and colour contrast checker on this site for the parts they can do.
Turning results into a report
After testing, open the Audit summary tab. It shows the headline result, a pass rate for each principle and a table of failures. Export the CSV to import into a bug tracker, a spreadsheet or a VPAT template. Group failures by template or component to fix the root causes. Re-test after fixes and update the date, then publish an honest accessibility statement, for example with the accessibility statement generator on this site.
WCAG and the law
WCAG 2.2 AA is the usual technical benchmark behind accessibility laws and policies, including the European Accessibility Act and EN 301 549 (which currently references WCAG 2.1 AA), Section 508 in the United States (which refers to WCAG 2.0 AA), the ADA as applied in court and by the Department of Justice, the UK Public Sector Bodies Accessibility Regulations, the Accessibility for Ontarians with Disabilities Act and others. Which version applies depends on the law and your sector. Meeting a newer WCAG version normally satisfies older ones, because 2.2 is built to be backwards compatible with 2.1 and 2.0 (apart from the removed 4.1.1).
Limits of a self-assessment checklist
The checklist is as accurate as the person who completes it. It does not verify your results, and one-line summaries cannot replace the full text, techniques and failure examples at the W3C. Complex products, single-page applications, PDFs, video and mobile apps often need specialist testing with assistive technology and real users with disabilities. Use this tool to organise your work and learn the standard, and bring in an expert for critical systems.
Privacy and data
Your project details, statuses and notes are saved only in your browser's local storage so you can return later. They are not uploaded or shared. Use Clear all results (click twice) to erase them, or clear your browser data. Export a CSV or PDF before you switch device.
Frequently asked questions
What is a WCAG checklist?
A WCAG checklist lists the success criteria of the Web Content Accessibility Guidelines so you can check a website against each one and record whether it passes, fails or does not apply. This generator includes all 86 criteria of WCAG 2.2.
How many success criteria are in WCAG 2.2?
There are 86: 31 at Level A, 24 at Level AA and 31 at Level AAA. WCAG 2.2 added nine criteria to WCAG 2.1 and removed 4.1.1 Parsing.
What is new in WCAG 2.2?
Nine criteria: 2.4.11 Focus Not Obscured (Minimum), 2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance, 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry, 3.3.8 Accessible Authentication (Minimum) and 3.3.9 Accessible Authentication (Enhanced). They are marked New in 2.2 in the checklist.
Which level should I aim for?
Level AA is the target in most laws, policies and contracts, so it is the default. It means meeting all Level A and Level AA criteria. Level AAA is not required for whole sites, because some AAA criteria cannot be met for all content, but many AAA criteria are good practice.
What do the four principles mean?
WCAG is organised under four principles, often abbreviated POUR: Perceivable (users can perceive the content), Operable (users can operate the interface), Understandable (content and operation are understandable) and Robust (content works with current and future technologies, including assistive technology).
Does this tool test my website automatically?
No. It is a checklist and record. You test the site yourself or with tools, then mark each criterion. For automated checks of code, use the HTML accessibility checker on this site.
Where is my progress saved?
In your browser's local storage on this device. It is not uploaded, and it will not appear on another device or browser. Download the CSV or print to PDF to keep a copy.
What does Not applicable mean?
Mark a criterion Not applicable when it does not apply to your content, for example media criteria on a site with no video or audio. Those criteria are excluded from the pass rate.
What does the summary tab tell me?
It shows your overall result against the target level, pass, fail, not applicable and not tested counts, a donut chart, pass rates by principle, results by level and a list of failures with your notes.
Is passing this checklist the same as being WCAG conformant?
Only if every Level A and AA criterion in scope is honestly tested and passes, for every page or every page in your defined sample, including processes. This tool records your judgement and does not verify it. A formal claim needs the full conformance requirements in WCAG.
Can I use it to create a VPAT?
It can organise your testing, but a VPAT or Accessibility Conformance Report has a specific format with conformance levels and remarks for each criterion. Use the CSV as source material for that report.
Can I check just Level A or Level AAA?
Yes. Use the Target level menu. Level A shows 31 criteria, Level AA shows 55 and Level AAA shows all 86.
What is WCAG 4.1.1 and why is it missing?
4.1.1 Parsing required valid markup. The W3C removed it in WCAG 2.2 because modern browsers and assistive technology handle most markup errors, so it no longer served users. Duplicate ids and broken ARIA references are still worth fixing, under other criteria.
How do I test the criteria that need a human?
Use the keyboard alone, zoom to 200% and 400%, turn on a screen reader (NVDA, JAWS, VoiceOver or TalkBack), check contrast, read captions and try the forms. The one-line descriptions on each criterion tell you what to look for.
Can a team use it together?
Because progress is saved only on one device, share results by exporting the CSV or PDF. For team audits, agree on one tester per section, or merge CSV files in a spreadsheet.
Does it cover mobile apps?
WCAG applies to web content, including web content on mobile. For native mobile apps, WCAG is used by analogy and guidance such as WCAG2ICT, EN 301 549 and platform guidelines also applies.
What can I print or save?
Print / save as PDF, CSV and Copy summary work for the tab you are viewing: the full checklist with statuses and notes, the audit summary with failures, or the list of new criteria in WCAG 2.2.
Sources and further reading
- W3C Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation 5 October 2023 (updated 2024), for the success criteria, levels and principles.
- W3C WAI, What's New in WCAG 2.2, for the nine new criteria and the removal of 4.1.1 Parsing.
- W3C WAI, Understanding WCAG 2.2 and Techniques for WCAG 2.2, for testing guidance and failure examples.
- W3C WAI, WCAG-EM Website Accessibility Conformance Evaluation Methodology, for scope and sampling.
Sources were consulted in October 2026. Standards and rules can change, so always check the official page for your situation.