Free WCAG 2.2 accessibility checker
Scan any public page against WCAG 2.2 AA in a real browser. Get a score, the issues ranked by impact, and what to change to fix each one.
Accessibility report
harbour-bakery.example
78
out of 100
Images must have alternative text
6 elements · WCAG 1.1.1
Form elements must have labels
2 elements · WCAG 1.3.1, 4.1.2
Elements must meet minimum color contrast ratio thresholds
14 elements · WCAG 1.4.3
Links must have discernible text
3 elements · WCAG 2.4.4, 4.1.2
How to fix: colour contrast
Designer
Darken the text until contrast is at least 4.5:1 (3:1 for large text), and change the colour in the theme so it fixes every page.
The scan runs the axe-core rules for WCAG 2.0, 2.1 and 2.2 at levels A and AA. These are the areas where they find the most problems.
Order online
Order online
We measure the contrast of every piece of text against its background, and check that links in body text stand out by more than colour alone.
WCAG 1.4.3 WCAG 1.4.1
Read as "image"
<img src="loaf.jpg">
Described
<img src="loaf.jpg" alt="Sourdough loaf">
Images, image buttons and SVGs need a text alternative. Videos need captions.
WCAG 1.1.1 WCAG 1.2.2
Every field needs a label a screen reader can announce, and personal fields need the right autocomplete value so browsers can fill them in.
WCAG 1.3.1 WCAG 1.3.5 WCAG 4.1.2
<!-- Announced as "button" -->
<button><svg>…</svg></button>
<!-- Announced as "Search, button" -->
<button aria-label="Search"><svg>…</svg></button>Icon buttons and image links need a name, and WCAG 2.2 adds a minimum size for tap targets so they are not pressed by mistake.
WCAG 2.4.4 WCAG 2.5.8 WCAG 4.1.2
A way to skip repeated navigation, scrollable areas keyboard users can reach, and nothing focusable hidden from screen readers.
WCAG 2.1.1 WCAG 2.4.1 WCAG 4.1.2
A page language screen readers can pronounce, a descriptive page title, and a viewport that lets people zoom in.
WCAG 2.4.2 WCAG 3.1.1 WCAG 1.4.4
Valid ARIA roles and attributes, lists and tables built so assistive technology reads them in the right structure.
WCAG 1.3.1 WCAG 4.1.2
Accessibility rules in the EU and the US measure websites against the WCAG success criteria. Testing against WCAG 2.2 AA also covers the 2.0 and 2.1 AA rules most of them reference.
A scan report is not legal advice or a certificate of compliance.
Applies from 28 June 2025 to many products and services sold in the EU, including online shops. Its harmonised standard, EN 301 549, is built on the WCAG success criteria.
Title III covers businesses open to the public. The Department of Justice points to WCAG as helpful guidance for making websites accessible.
Requires federal agencies to buy and build accessible technology. The Revised 508 Standards incorporate WCAG 2.0 AA, which is why vendors are asked for a VPAT.
Any public page works. Start with your home page or the page that matters most, such as checkout or contact.
Our servers open the page in headless Chrome, let its scripts finish, then run the axe-core WCAG rules. Most scans finish in under a minute.
You get a score and the top issues ranked by impact, each with the WCAG criteria it fails and what to change.
Something else on your mind? Email our team.
Yes. The scan is free and needs no account. Your report stays available at its own link for 7 days. You only need an account to scan every page on a schedule and track fixes over time.
The scan runs the axe-core rules for WCAG 2.0, 2.1 and 2.2 at levels A and AA. Level AA is the level referenced by EN 301 549, the Revised Section 508 Standards and most accessibility policies.
The score is the share of WCAG rules the page passed, out of every rule that applied to it. It is a quick way to compare pages and track progress, not a compliance grade.
No tool can on its own. Automated rules reliably find issues such as missing alt text, low contrast and unlabelled form fields, but some criteria need a person to judge, like whether alt text is accurate or the focus order makes sense. Fix the clear failures first, then review the rest by hand.
The scan only loads public pages. Pages behind a login, on a private network or staging server, or protected by a CAPTCHA or firewall cannot be scanned anonymously.
No. We load the page the way a visitor's browser does. Nothing is installed, submitted or changed on your site.
A free scan checks one page right now. Reguweb scans your whole site on a schedule, tracks fixes over time and produces the documents buyers and regulators ask for.