InputTestHub

WCAG 2.2 Checklist Generator

Builds a WCAG 2.2 checklist for your level and site type, with what each success criterion actually asks in plain terms.

Security Nothing uploaded No sign-up Free, unlimited
Security tool
Fill in the fields and press Generate.
In short WCAG 2.2 Checklist Generator is a free online tool on inputtesthub.com that builds a WCAG 2.2 checklist for your level and site type, with what each success criterion actually asks in plain terms. It needs no account, no download and no payment, and there is no daily usage limit. Everything is processed inside your own browser, so the data you paste is never uploaded to a server.

How to use the WCAG 2.2 Checklist Generator

  1. Fill in the fields with your own details.
  2. The generated code updates live in the output panel.
  3. Copy the code and paste it into your page, file or CMS.

About the WCAG 2.2 Checklist Generator

The WCAG 2.2 Checklist Generator builds a WCAG 2.2 checklist for your level and site type, with what each success criterion actually asks in plain terms. It runs as plain JavaScript inside the page, which means there is no upload step, no queue and no size limit imposed by a server — the only limit is your own device.

What people use it for

  • Running a manual accessibility review with nothing missed.
  • Briefing a developer on what level AA actually contains.
  • Checking which criteria WCAG 2.2 added over 2.1.

Details

Level AAWhat EU and most national law requires
New in 2.2Nine criteria, four at level AA
Removed in 2.24.1.1 Parsing
Target size24×24 CSS px, criterion 2.5.8
Automated tools findRoughly 30–40% of failures

The maths behind it

This tool uses the WCAG 2.2 success criteria at the chosen level, grouped by the four principles — perceivable, operable, understandable, robust — with the nine criteria new in 2.2 marked. Every intermediate value is shown on screen, so the result can be checked by hand.

A checklist is a memory aid, not an audit. Roughly a third of these criteria cannot be judged from code at all — whether alt text is useful, whether focus order preserves meaning, whether an error message helps — and those are the ones that matter most to a real user.

Where this tool stops

It lists criteria and what they ask; it does not test your site. Automated checking finds perhaps 30 to 40% of real failures, and the rest need a person with a keyboard and a screen reader.

Frequently asked questions

What changed between WCAG 2.1 and 2.2?
Nine new success criteria and one removal. The AA additions are 2.4.11 Focus Not Obscured, 2.5.7 Dragging Movements, 2.5.8 Target Size and 3.3.8 Accessible Authentication; 3.2.6 Consistent Help and 3.3.7 Redundant Entry came in at level A. Criterion 4.1.1 Parsing was withdrawn because browsers now recover from the markup errors it covered.
Is level AAA worth aiming for?
Not as a site-wide target, and the W3C says so explicitly — some AAA criteria cannot be satisfied for all content. Level AA is the legal standard almost everywhere. Picking individual AAA criteria that matter for your audience is sensible; claiming AAA across a whole site generally is not.
Is there a limit on how often I can use the WCAG 2.2 Checklist Generator?
It is free, with no account, no trial and no daily cap. Every security tool on inputtesthub.com works the same way: open the page and use it.
Can you see what I put into this page?
No. The WCAG 2.2 Checklist Generator runs entirely in your browser using JavaScript. Your input never reaches inputtesthub.com or any third party — open your browser's Network tab while you use it and you will see no request go out.
What is the equation behind the WCAG 2.2 Checklist Generator?
It uses the WCAG 2.2 success criteria at the chosen level, grouped by the four principles — perceivable, operable, understandable, robust — with the nine criteria new in 2.2 marked. The full working is printed under the result, so you can follow every step rather than trusting a black box.
Who is the WCAG 2.2 Checklist Generator for?
The most common reasons people reach for it: running a manual accessibility review with nothing missed. Briefing a developer on what level AA actually contains. Checking which criteria WCAG 2.2 added over 2.1. It is built for exactly those cases rather than being a general-purpose tool with this bolted on.
When is the WCAG 2.2 Checklist Generator not the right tool?
It lists criteria and what they ask; it does not test your site. Automated checking finds perhaps 30 to 40% of real failures, and the rest need a person with a keyboard and a screen reader. Knowing where a tool stops being trustworthy matters more than the cases where it works.
Which values should I know?
Level AA is What EU and most national law requires. New in 2.2 is Nine criteria, four at level AA. Removed in 2.2 is 4.1.1 Parsing. These are printed on the page itself, so you do not have to take them on trust.
Does the WCAG 2.2 Checklist Generator work on a phone?
Yes. The page is responsive and the page works in Chrome, Safari, Firefox, Edge and Samsung Internet on both Android and iOS. There is no app to install and nothing to sign into.

Related security tools

All 100
01

htpasswd Generator

Generates .htpasswd lines for Apache basic authentication using APR1-MD5, SHA-1 or crypt.

05

Privacy Policy Generator

Generates a privacy policy covering what you collect, why, how long you keep it and the rights…

07

Disclaimer Generator

Generates disclaimers for affiliate links, advice, earnings claims and external content.