How do I check a whole website for accessibility, not just one page?

Run the audit from a crawler instead of a browser extension. Enter the domain above, open More options and tick “Include JavaScript rendering checks”. Each page the crawl finds is loaded in a browser and audited with axe-core, and the Accessibility check lists the results for the whole site.

An open-source accessibility testing engine made by Deque. It is the engine inside Lighthouse’s accessibility score and most browser accessibility extensions. Its rules are written to avoid false alarms.

Does a clean result mean my site meets WCAG?

No. Automated rules find the faults a machine can decide: a missing label, insufficient contrast, an invalid ARIA attribute. They cannot judge whether alt text describes the image or whether a form works with a keyboard. A clean result is a floor. Conformance needs testing by people.

Why do I have to tick a box?

Because the audit needs a real browser. An ordinary crawl reads the HTML each page sends, which is fast. Contrast, visibility and ARIA can only be judged on the page as a browser builds it, so each page is also opened in headless Chromium. That is slower, so it is a choice.

Is it really free for the whole site?

Yes. The crawl covers up to 5,000 pages with no account, and the audit runs on the pages it renders.

Accessibility

Free accessibility checker for an entire website

A browser extension audits the page in front of you. The faults that reach the most people are in the templates: the product page, the article layout, the checkout form. Checking the home page says nothing about those.

Enter a domain and tick Include JavaScript rendering checks under More options. Each page is loaded in a real browser and audited with axe-core, and the violations are listed for the whole site, worst impact first.

One email when the scan finishes, with the score and every check. No newsletter.

More options: paths, depth, JavaScript rendering, privacy

What to crawlOnly crawl paths matching (one per line)Leave out paths matching (one per line)Maximum link depth from the start pageDrop these query parameters (comma-separated, * allowed)

Drop tracking parameters utm_*, gclid, fbclid and the like, so tagged links are not crawled twice.Stay inside the start folder Start at /blog/ and only pages under /blog/ are crawled.Crawl subdomains of this host Starting at example.com includes shop.example.com and blog.example.com. Starting at blog.example.com includes only that host and hosts beneath it.Lower-case paths Treat /About and /about as the same page.

Include JavaScript rendering checks Each page is also loaded in a real browser and compared with the HTML the server sent. Slower.Keep this scan private No public report page, no place in the rankings or the sitemap.

Crawls up to 5000 pages plus their images, scripts and stylesheets. No account needed: you get a private link to the results.

What you get

One row for each rule a page breaks:

The page and the rule, by its axe-core id.
The impact: critical, serious, moderate or minor, with the table sorted in that order.
How many elements on the page break the rule, and the first of them as a selector, so a developer can find it.
What it means in a sentence.

The summary names the three commonest rules across the site and how many pages have any violation. Export the table as a CSV and group it by rule: that is the work list.

What the rules cover

Names and labels. Images without alt text, form fields without labels, buttons and links with no accessible name, frames without titles.

Colour contrast. Text that does not stand out enough from its background.

ARIA. Roles and attributes that are invalid, misapplied or missing what they require.

Structure. Landmarks, heading order, lists and tables marked up as what they are, one main region, a page title.

Language. A missing or invalid lang attribute, which decides how a screen reader pronounces everything.

Working through the results

Group by rule first. A rule broken on three hundred pages with the same selector is one fault in one template. Fix it and three hundred rows go.

Take critical and serious before the rest. Those are the ones that stop someone using the page at all: a control with no name, a field with no label.

Then test by hand what a machine cannot. Use the site with only a keyboard. Turn on a screen reader and complete the most important task. Read the alt text and ask whether it says what the image shows.

Re-scan. Run the crawl again after the fixes and compare the counts per rule with the export you kept.

Where it stops

It is an automated audit of pages a crawler can reach. Pages behind a login, states that only appear after a click (an open menu, a dialog, an error message) and anything that needs a human judgement are outside it. Most images and fonts are not downloaded while rendering, to keep the crawl gentle on your server, which can affect contrast results for text laid over a photograph.

It is not a statement of legal compliance, and no automated tool is. It is the fastest way to find the faults that can be found automatically, on every page instead of one.

The same scan compares the HTML your server sends with the page the browser builds, and runs 37 checks in all. For the alt text of one page without a crawl, there is the image alt auditor.

Questions people ask

How do I check a whole website for accessibility, not just one page?: Run the audit from a crawler instead of a browser extension. Enter the domain above, open More options and tick “Include JavaScript rendering checks”. Each page the crawl finds is loaded in a browser and audited with axe-core, and the Accessibility check lists the results for the whole site.
What is axe-core?: An open-source accessibility testing engine made by Deque. It is the engine inside Lighthouse's accessibility score and most browser accessibility extensions. Its rules are written to avoid false alarms: what it reports is nearly always a real fault.
Does a clean result mean my site meets WCAG?: No. Automated rules find the faults a machine can decide: a missing label, insufficient contrast, an invalid ARIA attribute. They cannot tell whether alt text describes the image, whether the reading order makes sense or whether a form can be completed with a keyboard. A clean result is a floor. Conformance needs testing by people, including people who use assistive technology.
Why do I have to tick a box?: Because the audit needs a real browser. An ordinary crawl reads the HTML each page sends, which is fast. Contrast, visibility and ARIA can only be judged on the page as a browser builds it, so each page is also opened in headless Chromium. That is slower, so it is a choice.
Is it really free for the whole site?: Yes. The crawl covers up to 5,000 pages with no account, and the audit runs on the pages it renders. Free accessibility scanners commonly stop at the home page or ten pages.

Audit every page, not only the first

Tick “Include JavaScript rendering checks” under More options. Free, no signup.

Scan a site, free