WAVE vs axe: which free accessibility checker should a small business use?
For a small business owner, WAVE is the easier first check, and axe DevTools is the better second check. WAVE draws icons right on your page, so you see the problem where it sits. axe gives a plain list of rule failures with the code behind each one. Both are free to start, both miss most of what a real person with a screen reader would find, and this guide is for owners and the people who maintain their sites.
WAVE vs axe at a glance
| WAVE | axe DevTools (free extension) | |
|---|---|---|
| Made by | WebAIM, a nonprofit at Utah State University | Deque, an accessibility company |
| How you see results | Icons on the page, plus a side panel | A list of issues in the browser's developer tools |
| Best for | Owners, writers, designers | Developers and whoever edits theme code |
| Where it runs | A website you paste a link into, and a browser extension | A browser extension |
| Cost to start | Free | Free tier; paid tiers add more tests and guided checks |
| Engine | WebAIM's own checker | axe-core, an open-source rules library |
| Pages at once | One | One |
We read the vendors' pages and several comparison articles on 2026-11-22. Tool features change, so check the current free limits on each vendor's page before you rely on one.
What is WAVE?
WAVE is the Web Accessibility Evaluation tool from WebAIM. You can paste a web address into the WAVE site, or add the browser extension and click it on any page. It marks your page with small icons: red for errors, yellow for alerts, green for things done well. It also shows contrast errors, headings, landmarks and ARIA labels in one side panel.
The strength is that you look at your own page and see where each flag sits. A red icon next to a photo means that photo has no description for screen readers. A red icon next to a form box means the box has no label. You do not need to read code to know what to fix, and that is why we point beginners here first.
What is axe DevTools?
axe DevTools is a browser extension from Deque. It runs axe-core, an open-source set of accessibility rules that other tools also use. Google's Lighthouse accessibility audit, built into Chrome, is based on the same engine, and Microsoft's Accessibility Insights uses it too. That means the failures you see in axe often match what Lighthouse reports.
You open it inside the browser's developer tools, press scan, and get a list: the rule that failed, how serious it is, the element, and a link to learn more. It is faster for someone who can edit the theme, because it tells you the exact line of HTML. It is harder for an owner, because the list has no picture of the page.
Deque sells paid versions of axe DevTools with extra tests and guided checking. The free version is real, but sources disagree on exactly which rules it holds back, so read the current comparison on Deque's own page before you decide you need to pay.
Which finds more errors, WAVE or axe?
Neither one wins every time. On the same page they usually agree on the big, common errors: missing alt text, missing form labels, low contrast, empty links and empty buttons. They differ at the edges. WAVE shows more "alerts", which are things a person should look at, such as a very long alt text or skipped heading levels. axe is stricter about not reporting false alarms, and it points at the exact element.
So a good habit is to run both on your home page and compare. An error both tools report is almost certainly real. An error only one reports needs a human look. Deque says its rules aim to avoid false positives, so a flag from axe is rarely a false alarm, but WAVE's alerts are meant to be judged by you.
What do both tools miss?
A lot. Deque's own 2021 study of more than 2,000 audits found automated testing covered about 57% of issues by volume. Other sources put the share of WCAG problems a machine can catch much lower, around 30 to 40%. The honest takeaway: a clean scan means the machine found nothing, not that your site works for everyone.
Things no free checker can judge:
- Whether alt text is useful. A tool sees that "image1.jpg" exists, not that it says nothing.
- Whether you can use the whole site with a keyboard only, with no mouse.
- Whether the order a screen reader reads in makes sense.
- Whether a pop-up traps you with no way out.
- Whether videos have captions that are right.
- Whether a form tells you in words, not only in red, what went wrong.
Our free checker guide shows three more tools and how to combine them, and the ADA compliant website checklist lists the by-hand checks.
WAVE vs axe vs Lighthouse: do you need all three?
No. Lighthouse is already in Chrome (open developer tools, find the Lighthouse tab, tick Accessibility). It gives a score out of 100. That number is a rough signal, not a verdict: a page can score 100 and still fail a keyboard test. If you want one path, use WAVE for the picture, axe for the exact code, and skip Lighthouse unless you want a quick number to track over time.
A five-minute check with both
- Open your home page in Chrome. Add the WAVE extension and click it. Write down the count of red errors and contrast errors.
- Click each red icon. Note what it is: photo, form box, link or button.
- Open developer tools, find axe DevTools, and press scan. Write down how many issues it lists and how many are marked serious or critical.
- Compare. Anything both flag goes first on your fix list.
- Press Tab through the page with no mouse. If you lose track of where you are, or cannot reach the menu, write that down. No tool will tell you.
- Repeat on your busiest other page: your contact page, your booking page, or your checkout.
Do this on each type of page, not each page. A theme that puts the same bad button on every page produces the same error on every page, and one fix in the theme clears them all.
What to do with the results
Sort the list into three piles. First, fixes you can make in the editor: alt text, link words, headings, labels. Second, fixes that need theme or plugin code: contrast colors, missing focus outlines, buttons that are not real buttons. Third, errors inside third-party widgets, like a booking form, a chat bubble or an embedded map, where you may need the vendor to change something.
Fix the first pile yourself this week. For the second, our guide to fixing the theme explains why a plugin cannot do it. For colors, use a contrast tool such as the one in our contrast checker guide. And do not buy a script that claims to fix the pile automatically: see why experts say overlays are bad.
When a free checker is not enough
If you got a demand letter, if a big customer asked for a report, or if your site has a store and a booking form, free tools are a starting point only. You need someone to test by keyboard and screen reader and write down each fix for your platform. Our guide to what an accessibility audit costs shows the price ranges, and the ADA website compliance checker guide says what a checker can and cannot say about the law. We are not lawyers and this is not legal advice.
Frequently asked questions
Is WAVE better than axe?
For beginners, yes: the icons on the page are easier to read. For developers, axe often fits better because it points at the code. Using both on the same page catches more than either alone.
Is WAVE free?
The WAVE website and browser extension are free. WebAIM also sells paid access for checking many pages by software, which most small sites do not need.
Is axe DevTools free?
There is a free extension, and Deque sells paid versions with more tests. The axe-core library underneath is open source. Check Deque's page for what the free tier includes today.
Can I pass an ADA lawsuit check with a clean scan?
A clean scan helps but proves little. Courts and agencies point to WCAG, and a machine covers only part of it. For legal risk, talk to a lawyer.
How often should I rerun the check?
After every theme change, new plugin or new page type, and at least once a quarter. New errors arrive with every upload that has a photo with no description.
Which tool should I use on a WordPress site?
Start with WAVE on your home, a post and your contact page. Then run axe on any page that WAVE flagged heavily. The fixes are in the theme, not in the tools.
Sources
- WebAIM, WAVE web accessibility evaluation tools, wave.webaim.org (read 2026-11-22).
- Deque Systems, axe browser extensions and axe-core, deque.com/axe (read 2026-11-22).
- Deque, "Automated testing study identifies 57 percent of digital accessibility issues", March 2021.
- Scott Logic, "Accessibility tooling: WAVE vs axe", 2023-09-27.
- W3C, Web Content Accessibility Guidelines 2.1.