Accessibility checker: test any page against WCAG 2.2 A and AA
Enter any page. This free accessibility checker loads it in a real browser and runs axe-core's WCAG 2.0, 2.1 and 2.2 Level A and AA rules — the open-source engine many accessibility tools are built on. You get every issue it finds, with the WCAG criterion, how many elements it affects and an example, plus whether the page links an accessibility statement.
Free, no account. One page per scan. Results are kept for 24 hours and shared for the same address; up to 5 scans every 10 minutes and 20 a day.
The barriers a machine can find
Text alternatives
Images and image links with no text alternative, so a screen reader has nothing to announce (WCAG 1.1.1).
Labels and names
Form fields with no label, and buttons or links with no accessible name — an icon button nobody can identify (1.3.1, 2.4.4, 4.1.2).
Colour contrast
Text below the minimum contrast ratio: 4.5:1, or 3:1 for large text (1.4.3).
Language, title, zoom and targets
A missing or invalid page language, a page with no title, zoom disabled on phones, and touch targets that are too small or too close together (3.1.1, 2.4.2, 1.4.4, 2.5.8).
ARIA
ARIA roles and attributes that are invalid or used where they don't belong, which can make a working control unusable with a screen reader (4.1.2).
An accessibility statement
Whether the page links an accessibility statement — what EU rules ask online shops and other consumer services to publish since 28 June 2025. The checker notes it; it doesn't read the statement.
What automated testing can't see
Automated testing finds a share of WCAG issues, not all of them: Deque's study of real audits found it identified about 57% of issues by volume. Whether alt text describes the image, whether the keyboard order makes sense, whether an error message helps — that needs a person. The checker doesn't certify a site, and no tool can.
It also tests one page, as it loads. A barrier in your checkout, in a menu that opens on click or in an error message that appears after a form is sent isn't on the page it sees.
And it's one moment. Themes, page builders and plugins rewrite markup with every update. Relvato's Accessibility monitor tests your home, shop, product, cart, checkout and account pages, keeps the issues you already know as an approved baseline, and alerts you by email, Slack or webhook to each new one after WordPress, theme, plugin and WooCommerce updates.
Questions, answered
Does a clean result mean my page is accessible?
No. It means axe-core found no issue among the rules a machine can test. The W3C says evaluation tools can't decide on their own whether a site is accessible; much of WCAG needs a person to judge. A clean result is a good start, not a certificate.
Which standard does it test against?
WCAG 2.0, 2.1 and 2.2 at Level A and AA, using axe-core's rules. In the EU, websites are generally measured against EN 301 549: version 3.2.1 follows WCAG 2.1 Level AA, and version 4.1.1 moves to WCAG 2.2 AA. Testing against 2.2 covers both.
What does each issue show?
One rule on the page — “Form elements must have labels”, say — with the WCAG criteria it maps to, how many elements are affected and a sample element, so you can find it in your theme or page builder.
Why doesn't it test my whole site?
The free checker tests one page per scan. Relvato's Accessibility monitor tests the pages a customer needs to buy or sign in — home, shop, product, cart, checkout and account — plus any you add, and tests them again after updates.
What happens to the pages I check?
Relvato loads the page once, in a browser that can only reach public addresses, and keeps the result for 24 hours so the same address isn't scanned again. Nothing else about the scan is stored.
Know when an update adds a new barrier.
Relvato's Accessibility monitor repeats this test on your key pages after WordPress, theme, plugin and WooCommerce updates, on any website. On every plan, Free included: on Free you run it yourself or weekly; Pro also re-runs it after updates.