← Accessibility Insights & Resources

Free Accessibility Testing Tools (WAVE, axe, Lighthouse) and What They Miss

Which free accessibility checker to use for what, where each one stops, and a simple workflow that gets the most out of them before you pay anyone.

Run a free scan

The best free accessibility testing tools are WAVE, the axe DevTools browser extension, Lighthouse and Accessibility Insights for Web for automated checks, a colour contrast checker for design work, and the screen readers already on your computer or free to download: NVDA, VoiceOver and Narrator. You don't have to pick one. They overlap, each is better at something, and together they cost nothing.

If you only want a quick answer: use WAVE if you're not a developer, axe DevTools or Accessibility Insights if you are, Lighthouse for a fast number you already have in Chrome, and a screen reader plus your keyboard for everything the others can't see.

What none of them can do is tell you that your site is accessible. An automated checker reads code. It can't judge whether a description makes sense or whether a customer can finish a booking. This guide covers each tool, its limit, and what to do about the gap.

The free accessibility checkers, one by one

WAVE (WebAIM)

WAVE is a set of evaluation tools developed by WebAIM at Utah State University, which describes it as a free community service. You can paste a web address into the WAVE site, or install the browser extension for Chrome, Firefox or Edge and test the page you're looking at.

Good at: showing problems where they are. WAVE marks up your actual page, so a missing label or an empty link is flagged next to the element itself. That makes it the easiest tool for content editors, designers and business owners to read. WebAIM also says plainly that WAVE is there to support human evaluation, not replace it.

Limit: it tests one page at a time, in the state the page is in when you run it. A busy page can end up covered in markers, and it takes some practice to tell a real error from an item WAVE is only asking you to look at.

axe DevTools browser extension (Deque)

The axe DevTools extension comes from Deque and runs in Chrome, Edge and Firefox, inside the browser's developer tools. It is built on axe-core, Deque's open-source rules library, which also sits underneath several of the other tools on this page.

Good at: precise, developer-ready results. Each issue points to the exact element and the rule it breaks. Deque treats false positives as bugs to be fixed, so when axe reports a failure it is usually worth acting on.

Limit: Deque's own page says the free extension "only provides automated testing, and you can only test one page at a time." The guided manual tests and other extras belong to the paid Pro plan. The same caution that makes axe trustworthy also means it stays quiet about anything it can't be sure of.

Lighthouse (Chrome DevTools)

Lighthouse is Google's open-source page quality tool. It is already in Chrome: open DevTools and choose the Lighthouse panel. It audits performance, accessibility, SEO and more, and gives each category a score out of 100. Chrome's documentation notes that axe is the underlying engine that powers the Lighthouse panel's accessibility checks.

Good at: speed and convenience. There is nothing to install, the result is one number that's easy to track over time, and developers can run it from the command line as part of a build.

Limit: the number is easy to misread. It summarizes a set of automated pass-or-fail checks on one page, and nothing else. More on that further down.

Accessibility Insights for Web (Microsoft)

Accessibility Insights for Web is an open-source extension from Microsoft for Chrome and Edge. Its automated checks are also powered by axe-core. It has two modes. FastPass runs the automated checks and then walks you through a tab stops test with a visual helper. Assessment is a longer, guided review against WCAG 2.1 Level AA that adds step-by-step manual tests.

Good at: getting you past automation. The tab stops view draws your keyboard path on the page, which is the quickest way we know to see a broken focus order. The guided Assessment tells you what to check, how, and what a pass looks like.

Limit: the manual tests are still manual. The tool gives instructions, but you supply the time and the judgement, and a full Assessment of even one page is a real piece of work. Microsoft's documentation is direct about the automated part: it "can detect some common accessibility problems," but "most accessibility problems can only be discovered through manual testing."

A colour contrast checker

Two free ones cover almost every case. The WebAIM Contrast Checker is a web page: enter a text colour and a background colour and it tells you whether the pair passes for normal text, large text and graphical objects. The Colour Contrast Analyser (CCA) from TPGi, now published on the Vispero site, is a free desktop app for Windows and Mac with an eyedropper, so you can sample colours from anything on your screen, plus a colour blindness simulator.

Good at: the cases page scanners struggle with, such as text over a photo or gradient, colours in a design file before anything is built, and icons or button borders.

Limit: it checks one pair of colours that you choose. It won't find the problem for you, and it knows nothing about the rest of the page. Our colour contrast guide explains the ratios and where they apply.

Free screen readers: NVDA, VoiceOver and Narrator

A screen reader isn't a checker. It's the software many blind and low-vision people actually use, which makes it the most honest test you can run.

  • NVDA: a free, open-source screen reader for Windows, made by NV Access.
  • VoiceOver: the screen reader built into macOS, and also available on iPhone and iPad. On a Mac, press Command-F5 to turn it on or off.
  • Narrator: the screen reader built into Windows 10 and 11. Press Ctrl + Windows logo key + Enter to start it.

Good at: showing you what your site is like without the visual layout. You hear whether a button has a name, whether a form error is announced, and whether the page makes sense read top to bottom.

Limit: there is a learning curve, and no report at the end. A beginner can also mistake their own unfamiliarity with the commands for a bug on the site. Our screen reader testing guide has the key commands and a script to follow.

Our free scan (CodexMotive Audit)

Our own free accessibility scan belongs in this list, with the same honesty about its limits. You enter a web address and nothing is installed. It finds pages on your site, runs automated WCAG 2.1 Level A and AA checks on a sample of up to five of them, and shows the issues grouped by severity: critical, serious, moderate and minor.

Good at: a first look across several pages at once without opening developer tools, in a report a non-technical person can read.

Limit: it is automated, so it has the same blind spots as every other checker here. It scans a sample of public pages, not the whole site, and it doesn't complete tasks such as signing in or checking out. A clean result is a good sign, not evidence that your site meets WCAG or the AODA.

WAVE vs axe vs Lighthouse and the rest: comparison table

The automated checkers overlap heavily, and three of them share the axe-core engine, so running all of them finds less than you'd expect. Choose by who is testing and what they need to see.

Free accessibility testing tools compared
ToolMade byHow you run itBest forMain limit
WAVEWebAIMWebsite, or Chrome, Firefox and Edge extensionNon-developers who want to see issues on the pageOne page at a time; results take practice to read
axe DevTools extensionDequeChrome, Edge and Firefox extensionDevelopers who need exact elements and rulesFree version is automated only, one page at a time
LighthouseGoogleBuilt into Chrome DevTools; also command lineA quick check and a number to trackThe score is easy to mistake for a pass
Accessibility Insights for WebMicrosoftChrome and Edge extensionKeyboard and tab order checks; guided manual reviewManual tests take time and judgement
WebAIM Contrast Checker, Colour Contrast AnalyserWebAIM; TPGi (Vispero)Web page; Windows and Mac appChecking colour pairs, including in designs and over imagesOnly checks the colours you give it
NVDA, VoiceOver, NarratorNV Access; Apple; MicrosoftDownload (NVDA) or built into the deviceHearing what a screen reader user actually getsLearning curve; no report
CodexMotive Audit free scanCodexMotiveEnter a web addressA first snapshot across a sample of pagesAutomated only; up to five public pages

What no automated accessibility checker can judge

Every scanner on this page works the same way: it reads the page's code and compares it to rules. That finds anything with a clear signature, such as an image with no alt attribute or a form field with no label. It can't answer questions about meaning or use. Five of those questions matter most.

Is the alt text any good?

A tool can confirm an image has alt text. It can't tell whether "image1" or "photo" describes anything, or whether a decorative image should have been left silent. See our image accessibility guide for how to write it.

Do custom widgets work with a keyboard?

Scanners don't press keys. A dropdown, date picker or pop-up built from scratch can pass every automated rule and still be impossible to open, use or leave without a mouse. Our keyboard accessibility guide shows how to test this yourself.

Does focus move in a sensible order?

When you press Tab, does focus follow the page the way a reader would? Does it move into a dialog when one opens, and back when it closes? You find out by tabbing through. The tab stops view in Accessibility Insights helps you see the path, but a person still has to decide whether it makes sense.

Does link text make sense in context?

A tool can flag a link with no text at all. It can't tell whether six links that all say "Read more" can be told apart, or whether "click here" means anything to someone moving through a list of links.

Can someone actually complete the task?

This is the question that matters to your customers, and no checker attempts it. Booking, buying, applying and signing in involve several screens, error messages that only appear after a mistake, and steps such as payment or sign-in that a scanner never reaches. A site can be free of automated errors and still stop a keyboard user at the second step of checkout.

For a criterion-by-criterion look at where automation ends, see our article on automated vs manual accessibility testing. The W3C's own advice on selecting evaluation tools says the same thing in one line: tools "can not determine accessibility, they can only assist in doing so."

Start with a free scan of your own site

Enter your web address and get an automated snapshot of a sample of your pages, grouped by severity. It's a first pass, not a compliance check.

Run a free scan

Why a Lighthouse score of 100 is not conformance

A Lighthouse accessibility score of 100 means every automated check Lighthouse ran on that page passed. It doesn't mean the page conforms to WCAG, and Google doesn't claim it does.

The wording is in the Lighthouse report itself, under the Accessibility heading. You can read it in Lighthouse's source code:

"Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged."

Three things follow from how the score is built:

  • It's a weighted average of automated audits. Google's scoring documentation says each audit is pass or fail and the score is a weighted average of them.
  • The manual checks don't count. The report lists extra items to check by hand, described as "areas which an automated testing tool cannot cover." The same scoring page says manual audits don't affect your score. You can ignore every one of them and still get 100.
  • It's one page in one state. The score describes the page as it loaded, not the menu once it's open, the form once it has errors, or the other pages on your site.

Chrome's DevTools documentation makes the same point in its own way: the only way to find out whether a page can be used with a keyboard or screen reader is "to try using a page with a keyboard or screen reader yourself."

So treat 100 as "no known automated failures on this page." That's worth having. It isn't a statement about WCAG 2.0 Level AA, which is what Ontario's AODA requires of public sector organizations and of businesses and non-profits with 50 or more employees. Our AODA requirements guide covers who that applies to. This is general information, not legal advice.

A sensible free accessibility testing workflow

You can get a long way in an afternoon with nothing but free tools. Work in this order, so the quick wins are cleared before you spend time on the slower checks.

  1. Pick your pages. Choose one page for each distinct layout (home, a content page, a product or service page, the contact form) plus the one task customers most need to finish.
  2. Run one automated checker on each. WAVE if you want to see issues on the page, axe DevTools or Accessibility Insights FastPass if you'll be fixing code. Or run our free scan to cover a sample of pages in one go. One checker is enough; a second mostly repeats the first.
  3. Fix what it finds. Missing labels, empty links and buttons, missing alt attributes and low-contrast text are usually quick, and often fixed once in a shared template.
  4. Check contrast where scanners can't. Use a contrast checker on text over images, buttons, icons and anything in your brand colours.
  5. Put the mouse away. Tab through each page and complete your key task with the keyboard only. Can you always see where you are? Can you reach and use everything? Can you get out of every menu and pop-up?
  6. Listen to it. Turn on VoiceOver, NVDA or Narrator and go through the same task. Note anything that is unnamed, confusing or never announced.
  7. Zoom in. Set your browser to 200% and check that nothing is cut off or overlapping.
  8. Write it down and repeat. Keep a short list of what you found and fixed. Re-run the automated check after each round of changes, and the manual steps when a page or task changes. Our WCAG 2.2 AA checklist is a useful list to work from.

When free tools stop being enough

Free tools are the right place to start, and for a small, simple site they'll take you most of the way. They stop being enough when someone needs evidence rather than effort: a buyer asks for a conformance report, you need to stand behind an AODA compliance report, you've had a complaint, or your site has a booking or checkout flow you can't confidently test yourself.

That is the point for a manual audit: a specialist testing your templates and key tasks with a keyboard and screen readers against each WCAG criterion, and writing up what to fix. Our guide to what a website accessibility audit is explains what to expect, and our pricing page lists what each of our packages covers.

Frequently asked questions

What is the best free accessibility checker?

It depends on who is using it. WAVE is the easiest to read if you're not a developer. The axe DevTools extension and Accessibility Insights for Web give developers more precise detail. Lighthouse is the quickest because it's already in Chrome. None of them replaces testing with a keyboard and a screen reader.

WAVE vs axe vs Lighthouse: which should I use?

Use WAVE to see issues marked on the page, axe DevTools for exact elements and rules while fixing code, and Lighthouse for a quick score you can track. Lighthouse's accessibility checks are powered by axe, so those two will largely agree. Running one well is better than running all three.

Are these tools really free?

WAVE's website and extensions, Lighthouse, NVDA, the WebAIM Contrast Checker and the Colour Contrast Analyser are free. VoiceOver and Narrator come with Apple and Windows devices. The axe DevTools extension has a free version limited to automated testing of one page at a time, with a paid Pro plan above it.

Does a Lighthouse accessibility score of 100 mean my site is compliant?

No. It means the automated checks Lighthouse ran on that page all passed. Lighthouse's own report says automatic detection finds only a subset of issues and doesn't guarantee accessibility, and its manual checks don't count toward the score.

If a free tool finds no errors, is my website AODA compliant?

Not necessarily. The AODA's website requirement is WCAG 2.0 Level AA, and many of its criteria can't be tested by software. No errors means the tool found nothing it knows how to detect. Keyboard, screen reader and content checks are still needed to know where you stand.

Do I need to be a developer to use these tools?

No. WAVE, a contrast checker, your keyboard and a web-based scan need no technical background. Reading axe or Lighthouse results, and fixing most of what any tool finds, usually does need someone who can edit the site's code or templates.