Alt text and structure
Missing image descriptions, headings out of order, form fields without a label.
Free tool
Free website accessibility checker and compliance test
This free website accessibility checker scans one page against WCAG 2.1 AA with axe-core and maps each finding to the European Accessibility Act. It is free: no signup, no card. The paid report adds the national act you select.
Website accessibility testing
We test the one page you enter. The result appears right here.
The scan can take up to a minute. Please stay on the page.
Test result
Score
0/100
Grade
F
Issue types found
- 0Critical
- 0Serious
- 0Moderate
- 0Minor
The full result lists every issue found and stays available at its own address, which you can share with colleagues.
IP address of our scanner:
Need an accessibility statement too?
Our other free tool drafts an accessibility statement from the details you enter.
What the test checks
The test runs axe-core against the page you enter and evaluates nearly 100 accessibility rules: WCAG 2.1 AA plus the WCAG 2.2 target size rule and best-practice rules. We map what it finds onto EN 301 549 and, in the paid report, the national act you select.
Colour contrast
Text and controls whose contrast against the background is too low.
Keyboard operation and ARIA
Elements you cannot reach with a keyboard, plus wrong or redundant ARIA attributes.
Mapping to the law
For the most serious finding we show the specific provision and WCAG criterion, not just a technical description.
Website compliance checker and website standards checker: what this one measures
A website compliance checker and a website standards checker are two names for one kind of tool, one that measures a page against a published standard. Here is exactly which standards this one measures against, and which part of the work an automated check can and cannot do.
WCAG 2.1 Level AA
The success criteria the test measures against, and the ones our findings cite. Level AA is the tier EN 301 549 incorporates for web content, so it is the practical bar for a website.
EN 301 549
The European standard for ICT accessibility. Its web chapters incorporate WCAG 2.1 A and AA, which is why a WCAG 2.1 AA checker is also a standards checker for the web part of EN 301 549. Meeting the standard does not by itself establish that a law is met.
The EAA and its national laws
The European Accessibility Act applies through each country's own act: the BFSG in Germany, Act No. 424/2023 Sb. in Czechia, the Act of 26 April 2024 in Poland. The paid report cites the act you select, not a generic reference.
What a compliance checker cannot do
It reports rule failures; it does not decide whether you comply. Automated testing catches roughly 30 to 40 percent of WCAG success criteria. The rest needs a human, which is what a manual audit is for.
What the test does not check
This is an automated test, and automated tests have hard limits. We name them up front, because a report that hides them will not help you when someone asks.
- Automated testing catches roughly 30 to 40 percent of WCAG success criteria. The rest needs a human.
- We do not check whether alt text actually describes the image. We check that it is there.
- The free test evaluates the one page you enter, not the whole site.
- Zero findings is not conformance with the law. It means the automated test found nothing.
Why this matters now
The European Accessibility Act has applied since 28 June 2025, through each country's own national law. According to WebAIM Million 2026, 95.9% of home pages tested had detected WCAG 2 failures, so findings are the normal starting point. The practical question is therefore not whether you have findings, but what you can show when someone asks.
Common questions
Is the checker free, and do I need an account?
Yes, it is free. You need no account and no card. The free check covers the one page you enter. You pay only for the full report, which covers up to 100 pages with fix guidance, or for ongoing monitoring.
What does the checker test?
It runs axe-core in a real Chromium browser against nearly 100 rules: WCAG 2.1 Level A and AA, the WCAG 2.2 target size rule, and best-practice checks marked as good practice. Findings are mapped to the WCAG success criterion, the matching EN 301 549 clause and the European Accessibility Act, Directive (EU) 2019/882. The paid report cites the national act you select: the BFSG in Germany, zákon č. 424/2023 Sb. in Czechia, the ustawa z 26 kwietnia 2024 in Poland, the BaFG in Austria or zákon č. 351/2022 Z. z. in Slovakia.
Does a clean result mean my site is compliant?
No. A clean result means the automated rules found nothing on the page you entered. Automated testing catches roughly 30 to 40 percent of WCAG success criteria. The rest needs a human review: keyboard use, whether alt text describes the image, reading order, meaning. A grade of 100 means nothing automated was found, not that the page is accessible. The scan is evidence, not a verdict.
What is the difference between WCAG 2.1 and 2.2 for this check?
WCAG 2.2, a W3C Recommendation since 5 October 2023, adds nine success criteria to WCAG 2.1 and removes 4.1.1 Parsing. This check measures against WCAG 2.1 A and AA, the level EN 301 549 v3.2.1 incorporates for web content, and adds one WCAG 2.2 rule, target size. The other new 2.2 criteria are not part of the automated check. Our guide to WCAG compliance levels lists all nine.
How is this different from WAVE or Lighthouse?
On raw detection, not by much. Lighthouse builds its accessibility audits on axe-core, the engine we use, and WAVE from WebAIM is a free automated checker with its own rules. Like ours, both test only the part of WCAG that a machine can check. The difference is what comes after the scan: each finding mapped to the WCAG criterion, the EN 301 549 clause and the law; a timestamped report carrying the engine version and a SHA-256 hash; a draft accessibility statement; and monitoring that re-scans and alerts you on a regression. Those are in the paid report and monitoring.
How do I test a website for accessibility?
Start with an automated pass: enter the address above and the scan checks that page against WCAG 2.1 AA. Then do the part no tool can do. Walk the page with the keyboard alone and confirm you can reach and leave every control, read the alt text and ask whether it describes what the image is for, and check the heading order against how the page actually reads. Website accessibility testing is those two layers together: the automated pass finds the rule breaches cheaply, the manual pass finds the ones that depend on meaning.
Is this a website compliance checker?
It is an automated compliance check: it tests the page against WCAG 2.1 AA and names the provision each finding maps to. It does not decide whether you comply. That conclusion needs a manual audit on top of the automated result.
Can anyone else see the result?
We store the result at an unguessable address known only to you and to whoever you send it to. We do not publish it anywhere.
Want every finding and the fix guidance?
The full report covers more pages, shows each finding with the specific provision, and adds fix guidance written for developers.