Check any page against WCAG — free, with no account
The extension checks the tab you have open and outlines every faulty element right on the page. Nothing to install on the site, no email and no card.
Chrome, Edge, Brave, Opera, Vivaldi, Arc
Three steps, one minute
From install to first result — no account, no configuration
- 1
Install the extension
One click in the Chrome Web Store. Works in any Chromium browser — Chrome, Edge, Brave, Opera, Vivaldi, Arc.
- 2
Open the page you care about
Any page: yours or someone else’s, a landing page or one deep in a catalogue. The scan runs in your own browser, in the tab you are looking at.
- 3
Press “Check”
A few seconds later you get a score, the issues grouped by impact — and those issues outlined on the page itself.
The one thing a report cannot do
You see the issues on the page, not just in a list
A report says “contrast 3.1:1 on 14 elements”. Then you go hunting for those elements by hand. The extension outlines each of them on the live page, numbers them and shows a tooltip with what exactly is wrong.
- Toggle the outlines on and off, show one rule at a time, or step through the elements one by one.
- Template-level issues with nothing to outline — missing landmarks, a missing document language, a missing viewport — are listed separately with an explanation.
- Every rule comes with a link to instructions on how to fix it.
What it actually checks
The same rule set as our server-side Audit, so the scores match
WCAG 2.1 and 2.2, levels A and AA
These are the levels that EN 301 549 and the European Accessibility Act build on. Structural rules are enabled on top: heading order, landmarks, target size.
Desktop and mobile in one pass
First your normal window width, then an emulated 375×812 screen with touch. Some issues — clipped text, targets that are too small — only appear on mobile.
A 0–100 score and a letter
90 and above is A, from 80 B, from 70 C, from 50 D, below that F. It is the same score our server-side scanner gives for the same page.
Four impact levels
Critical, serious, moderate and minor — so you can start with what actually blocks a person instead of with the length of the list.
Free and with an account
The free check asks for nothing. An account removes the limit and adds whole-site scanning.
| Capability | Free | With an account |
|---|---|---|
| Check the open page, desktop and mobile | Free | With an account |
| On-page highlighting and fix instructions | Free | With an account |
| Checks per day | limited | unlimited |
| Scan the entire site | limited | With an account |
| History, team reports, comparison over time | limited | With an account |
| Monitoring and automatic fixes | limited | Audit / Autofix |
How many free checks exactly
The limit is per day and per site. The extension shows on screen how many checks are left and when the limit resets, so there is nothing to guess. Once it runs out, the checks you already made can be moved into a cabinet in one click.
Where a server-side scanner cannot reach
The scan runs from your browser, which removes a whole class of blockers
Pages behind a login
Account areas, carts, admin panels, internal portals. You are already signed in in your browser — the extension sees exactly what you see.
Local development
localhost and staging environments closed to the outside world. You can check the markup before it reaches production.
No firewall changes
The request comes from your own IP rather than our servers, so nothing has to be whitelisted and no WAF rule has to be relaxed.
No queue
The scan starts immediately, because it runs in your browser instead of waiting for a free worker on a server.
What the extension sees and what it sends
Chrome permission prompts look alarming, so here is each one
Nothing happens in the background
The page is read only after you press “Check”. Until then the extension does not touch the contents of your tabs.
Only the result is sent
The address of the checked page, the issues found with the code fragments around them, plus your browser’s User-Agent and IP — the latter only to count the limit. Without an account we do not know who ran the check.
The analysis engine is bundled in
It ships inside the extension itself. Nothing is downloaded from the internet while a check runs.
Access to all sites
Needed precisely so it can check whichever page you opened. Which page that will be is not known in advance, which is why Chrome asks broadly.
The yellow “DevTools is debugging this browser” bar is expected
To check the mobile view, the extension turns on Chrome’s built-in screen-size emulation for a second or two. Chrome always warns about this with a bar at the top, and it disappears when the check is done. Through that mechanism we change the screen size only — we do not read network traffic, the console, or page data.
What the extension does not do
So there are no surprises after you install it
- It does not fix anything — it finds and explains. Fixing without touching the source code is a separate product, Autofix.
- It is not a full audit. An automated check finds a significant share of common issues but not every WCAG criterion: keyboard navigation, focus order, clarity of wording and screen-reader behaviour all need a person.
- It does not guarantee legal compliance. A green score describes the state of the automatically testable rules, not a conformance verdict.
- It does not scan PDFs, and it does not run on Chrome’s own internal pages or in the extension store.
- It does not scan a whole site without an account — the free check covers the page you opened.
Frequently asked questions
Is it really free?
Yes. Checking the page you have open requires no account, no card and no email. Only the number of free checks per day per site is limited, and the extension shows how many are left. An account is needed only if you want to remove that limit or scan a whole site.
Which browsers does it support?
Any Chromium browser that installs extensions from the Chrome Web Store: Chrome, Edge, Brave, Opera, Vivaldi, Arc. It does not work in Firefox or Safari, which are built on different engines. There is no mobile version either, but the mobile rendering of a page is checked from the desktop through screen emulation.
Why does Chrome show a yellow DevTools bar?
To check the mobile view, the extension turns on Chrome’s built-in screen-size emulation for a second or two, and Chrome always warns about that with a bar at the top. It disappears once the check finishes. Only the screen size is changed through that mechanism — network traffic, the console and page data are not read.
Can it check a page behind a login?
Yes, and that is one of the main advantages of scanning from a browser. Account areas, carts, admin panels, internal portals, localhost — anything you can see in a tab, the extension can see too. A server-side scanner cannot reach those pages without separate access configuration.
How is this different from your Audit?
The rule set is identical, so the scores agree. The difference is coverage and cadence: the extension checks one open page on demand, while Audit walks the whole site on a schedule, keeps history, shows trends and produces reports for the team. Free checks can be moved into a cabinet in one click and become part of an audit.
Try it on your own page right now
Installing takes a minute, the first check a few seconds. No email required.
Free · no account · no card