Free WCAG checker for WCAG 2.2 AA
- No signup
- WCAG 2.2 A and AA + EN 301 549
- Result in about a minute
Updated October 13, 2026
A WCAG checker opens a web page and tests its code against the Web Content Accessibility Guidelines. Enter the address of one page above: we load it in a real browser, run the automated WCAG 2.2 A and AA checks and show every issue found with the success criterion it relates to and how to fix it. It is free, needs no account and takes about a minute. This is an automated check, not a full audit, and not legal advice.
What you see in the result
The result lists the problems found on the page, most serious first. Each problem comes with:
- a plain-language explanation of what it means for your visitors;
- the element on the page (selector, code and, where possible, a screenshot);
- how to fix it, with tips for Shopify, WooCommerce, PrestaShop and Shoptet;
- a link to the rule card with the WCAG success criterion and the EN 301 549 clause.
The cart button has no name
What this means for your visitors
A shopper using a screen reader only hears “button” and cannot tell that it adds the product to the cart.
How to fix it in Shopify
In the product template, give the icon button the text “Add to cart”, visible or as an aria-label.
Element: .product-form > button.cart-icon
Rule: button-name · WCAG 4.1.2 Name, Role, Value (A) · EN 301 549 9.4.1.2
The result is shown in the language of this page, so you can forward it to a shop owner or a client who does not read English.
What the WCAG checker tests
The checker runs axe-core, the open-source rules engine by Deque Systems that most accessibility tools build on, and maps every finding to a card in our library of rules. Typical findings are images without alternative text (1.1.1), text with too little contrast (1.4.3), links and buttons without an accessible name (2.4.4 and 4.1.2), form fields without a label, a missing page language (3.1.1) and touch targets that are too small (2.5.8).
The table shows all 55 success criteria of WCAG 2.2 at levels A and AA, and which of our automated rules test part of each one. A criterion with rules is only partly automated: the rules catch typical mistakes, but cannot judge everything the criterion asks for.
22 of the 55 WCAG 2.2 success criteria of levels A and AA have at least one automated check in our library. The others are marked "manual review": a person has to check them.
What no automated test can find
Studies disagree on how large a share of accessibility problems automation finds (GOV.UK test, Deque study), but they agree that it is not all of them. A machine can tell that an image has alternative text, not whether the text makes sense. It can see a focus style, not whether the focus order is logical.
After the automated check, test these by hand:
- Keyboard: reach every link, button and field with Tab, operate it with Enter or Space, and never get stuck (2.1.1, 2.1.2, 2.4.3, 2.4.7).
- Zoom and reflow: zoom the page to 200 % and 400 %; nothing should be cut off or need horizontal scrolling (1.4.4, 1.4.10).
- Screen reader: listen to the page with NVDA, VoiceOver or TalkBack; headings, buttons and form errors should make sense (1.3.1, 3.3.1, 4.1.3).
- Forms and checkout: make deliberate mistakes; error messages should say what is wrong and how to fix it (3.3.1, 3.3.3).
- Media: videos need captions, and nothing should play sound automatically (1.2.2, 1.4.2).
Our WCAG 2.2 checklist explains each of these steps for online shops.
What is new in WCAG 2.2
WCAG 2.2 added six success criteria at levels A and AA — among them 2.4.11 Focus Not Obscured, 2.5.7 Dragging Movements, 2.5.8 Target Size and 3.3.8 Accessible Authentication — and removed 4.1.1 Parsing. Of the new criteria, our automated rules test only 2.5.8 Target Size; the others need a person. Details in our article on EN 301 549 V4.1.1 and WCAG 2.2.
How it differs from WAVE, Lighthouse and axe DevTools
These are good tools, and Lighthouse and axe DevTools use the same axe-core engine. The difference is what happens after the test:
- the result explains each issue for a business owner, not only for a developer;
- it is available in seven languages;
- each rule is mapped to EN 301 549, the European standard behind the accessibility laws;
- with a plan, the same checks run on every page of the site every week, and you see what changed.
For checks inside a browser, behind a login or on a staging site, use our browser extension (Chrome, Edge, Firefox). For WordPress and WooCommerce there is a WordPress plugin that shows problems next to each page and product.
WCAG, EN 301 549 and the law
WCAG itself is not a law, but laws refer to it. In the European Union, the European Accessibility Act relies on the harmonised standard EN 301 549, whose web chapter takes over the WCAG success criteria at level AA. National laws implement the Act: the BFSG in Germany, the act on accessibility of products and services in Poland, Act No. 424/2023 Coll. in Czechia and Law 232/2022 in Romania. In the US, WCAG 2.1 or 2.2 level AA is the usual yardstick under the ADA.
The Act applies to B2C services in specific sectors and not to micro-enterprises. Before you worry about the law, check whether it applies to you. A checker result is not a statement of conformity, but it is useful input for the "known limitations" part of your accessibility statement.
Check every page, every week
One page is a sample. Problems usually repeat across templates — product pages, the cart, the checkout — and come back after theme updates. With a plan, Pandus checks every page of your site each week, sends you a readable report and tells you when new problems appear. Agencies get the reports under their own brand.
Frequently asked questions
What is a WCAG checker?
A tool that opens a web page and tests its code against the WCAG success criteria. It finds problems a machine can detect reliably, such as missing alternative text, low contrast or buttons without a name.
Is this WCAG checker free? Do I need an account?
Yes, it is free and needs no account. The e-mail address is optional. To prevent abuse, checks are limited per hour and results for the same address are kept for 24 hours. Only check sites you are entitled to check.
Does it test WCAG 2.2 or WCAG 2.1?
WCAG 2.2 levels A and AA. WCAG 2.2 includes every criterion of 2.1 except the removed 4.1.1 Parsing.
Can an automated checker confirm WCAG conformance?
No. A clean result does not mean the page meets WCAG, and a result with issues does not mean you are breaking any law. Manual testing with a keyboard and a screen reader is still needed.
Which level do I need: A, AA or AAA?
Level AA — the level EN 301 549, the European Accessibility Act and national laws rely on. AAA is stricter and not required by these laws. If you only want to check colours, use the contrast checker.
Is this an official W3C validator?
No. The W3C does not run an official WCAG validator. Our checker is built on axe-core and our own rule cards. If you run a shop and care less about criterion numbers than about your customers, start with the free website accessibility check: the same test, explained for owners.