Free tool

Free website accessibility checker.

Check any public page against WCAG 2.1 AA in seconds. Free, no signup, and no scan limit. You get every automated violation explained in plain language.

Privacy: we fetch the single public URL you provide, run the checks, and keep only the host name and aggregate issue counts. Page content, screenshots, and full URLs are never stored.

What this tool actually checks

When you submit a URL, our server loads the page in a real headless browser, waits for it to render, and runs axe-core, the same detection engine used by the Complaudax extension, against the live DOM. The rules cover the automatable portion of WCAG 2.1 at levels A and AA: missing text alternatives, insufficient colour contrast, form fields without labels, broken ARIA usage, document structure problems, and dozens of similar checks. Each finding is reported against the success criterion it fails, with the number of affected elements, so a developer can go straight to the fix.

What WCAG 2.1 AA means

The Web Content Accessibility Guidelines organize accessibility into testable success criteria at three levels. Level AA is the bar referenced by the European Accessibility Act, EN 301 549, US legal practice, and most procurement requirements, which makes it the sensible default target for commercial sites. If the terminology is new, our plain-language explainer on WCAG 2.1 and 2.2 covers the four principles and what changed between versions.

Why one page is not a full audit

Two limits matter here, and hiding them would be dishonest. First, automated rules can verify roughly half of the AA criteria; judgements like whether the focus order makes sense or an error message genuinely helps still need a person. Second, this scanner only reaches pages a stranger can reach. The places accessibility problems actually concentrate, such as checkout steps, account dashboards, and staging builds awaiting release, sit behind logins that a server-side tool cannot cross. Auditing those requires running in your own browser session, which is exactly what the extension does.

What to do next

Fix the critical and serious findings first, re-scan to confirm, then repeat on your other key templates: home, product, forms, checkout. When you need the parts a free page checker cannot give you, per-client tracking, audits behind a login, and conformance documentation, see how the full workflow fits together or install the extension and keep working in the same engine you just used here.

Questions about the free checker

Is this really free?

Yes. Scanning a public page is free and unlimited: no account, no scan counter, no trial clock. The paid product is the Chrome extension workflow for agencies, which audits pages behind a login, tracks fixes over time, and exports conformance documentation.

Do I need to sign up?

No. Enter a URL and scan. The full result is visible without giving an email address. Emailing yourself the report is optional and never required to see anything.

Can it check a page behind a login?

No. This scanner runs on our servers, so it can only reach public pages. The Complaudax extension runs inside your own browser session, which is how it audits logged-in areas, staging environments, and checkout flows.

Does a passing scan mean my site is compliant?

No. A passing result means no automated WCAG 2.1 AA violations were detected on this one page, nothing more. Automated testing can verify roughly half of the AA success criteria; the rest need human review, and a site is more than one page.

How is this different from the Complaudax extension?

The free scanner checks one public page at a time and keeps nothing but aggregate counts. The extension audits any page you can open in your browser, including authenticated ones, keeps a per-client issue history across audits, and generates conformance reports and accessibility statements.