Every designer eventually hits the same wall: the client build looks finished, the handoff date is Friday, and someone asks whether the site is WCAG compliant. Enterprise accessibility platforms cost thousands per year. So the realistic question becomes: which free website accessibility checker actually finds the problems that matter before handoff?
Instead of listing tools with marketing copy, we did something more useful. We built a deliberately flawed business website, seeded it with 20 known WCAG 2.2 failures, and ran seven free accessibility checkers against the exact same pages. Below you will find what each tool caught, what it quietly missed, how readable the reports were, and how to combine two or three of them into a workflow that takes about 20 minutes per project.
How We Tested: One Site, 20 Seeded WCAG Failures
The test subject was a three-page sample business site (home, services, contact) built with a standard theme structure: sticky header, hero with overlay text, icon navigation, card grid, pricing table, embedded video, contact form, and a cookie banner. Nothing exotic, just the anatomy of 90% of SMB sites we see.
We then injected 20 failures that map to real WCAG 2.1 and 2.2 success criteria, split across three difficulty tiers:
Tier 1: Easy automated wins (should be caught by everything)
- Hero image with no
altattribute (1.1.1) - Body text at 3.8:1 contrast ratio (1.4.3)
- Email input with no associated label (3.3.2 / 4.1.2)
- Missing
langattribute on the services page (3.1.1) - Icon-only hamburger button with no accessible name (4.1.2)
- Empty link wrapped around a decorative SVG (2.4.4)
Tier 2: Detectable, but tool dependent
- Heading level skip from h2 straight to h4 (1.3.1)
- Four identical “Read more” links with different destinations (2.4.4)
- Pricing table with no
thscope or header cells (1.3.1) - Placeholder text used as the only field label (3.3.2)
- Form error message not linked with
aria-describedby(3.3.1) aria-hidden="true"applied to a focusable social link (4.1.2)- Duplicate page titles across two pages (2.4.2)
- Text over a hero background image at roughly 2.9:1 (1.4.3)
Tier 3: Mostly manual territory
outline: noneremoving all visible focus indicators (2.4.7 / 2.4.11)- Modal with no focus trap and no return focus (2.4.3)
- Auto-rotating carousel with no pause control (2.2.2)
- Embedded video with no captions (1.2.2)
- Horizontal scrolling at 320px width / 400% zoom (1.4.10)
- Mobile menu target smaller than 24 by 24 CSS pixels (2.5.8, new in WCAG 2.2)
Important baseline: no automated scanner catches everything. Industry consensus puts automated coverage at roughly 30 to 40 percent of WCAG issues. Our results line up with that, which is exactly why tool selection matters less than tool combination. Related reading: Free Accessibility Checker: accessScan.

The Results Table: What Each Free Accessibility Checker Caught
| Seeded issue | WAVE | axe DevTools | Lighthouse | Access. Insights | Silktide | IBM Equal Access | ARC Toolkit |
|---|---|---|---|---|---|---|---|
| 1. Missing alt | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 2. Low contrast text | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 3. Unlabelled input | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 4. Missing lang | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 5. Unnamed icon button | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 6. Empty link | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 7. Heading skip | Yes | Flag only | No | Yes | Yes | Yes | Yes |
| 8. Ambiguous link text | Flag only | No | No | Manual step | Yes | Flag only | Yes |
| 9. Table without headers | Yes | Partial | No | Partial | Yes | Yes | Yes |
| 10. Placeholder as label | Flag only | No | No | Manual step | Yes | Yes | Yes |
| 11. Orphan error message | No | No | No | Manual step | No | No | Flag only |
| 12. aria-hidden on focusable | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| 13. Duplicate page titles | No | No | No | No | Yes | No | No |
| 14. Text on background image | Flag only | Flag only | No | Manual step | Flag only | Flag only | Flag only |
| 15. No focus indicator | No | No | No | Manual step | Yes | No | Flag only |
| 16. Modal focus handling | No | No | No | Manual step | No | No | No |
| 17. Auto-rotating carousel | No | No | No | Manual step | Flag only | No | No |
| 18. Video without captions | Flag only | Flag only | Flag only | Manual step | Flag only | Flag only | Flag only |
| 19. Reflow at 320px | No | No | No | Manual step | No | No | No |
| 20. Target size under 24px | No | Partial | No | Manual step | Yes | Partial | No |
| Confirmed auto-detections | 9 / 20 | 9 / 20 | 7 / 20 | 8 / 20 | 13 / 20 | 10 / 20 | 11 / 20 |
“Flag only” means the tool raised an alert or warning requiring human confirmation rather than reporting a definite failure. “Manual step” means Accessibility Insights routed the issue into its guided assessment rather than its automated FastPass scan, where a human tester would reliably find it.

Tool by Tool: Accuracy, Reporting and Who It Suits
1. WAVE by WebAIM
WAVE remains the most recognised free website accessibility checker, and for good reason: it overlays icons directly on the rendered page, so a designer sees where the problem lives without reading a single line of code. skynettechnologies.com has a solid rundown on this.
- Accuracy: Very low false positive rate on hard errors. Its separation of Errors, Contrast Errors, Alerts and Features is genuinely well calibrated.
- Reporting: Best in class for visual learners. The structure panel and the one-click contrast tester are excellent. Weak point: no exportable PDF or CSV in the free browser extension, so client handoff means screenshots.
- Caught uniquely: flagged the placeholder-only field and the ambiguous links as alerts, which is enough to prompt a fix.
- Missed: everything dynamic. The modal, carousel and focus indicator issues were invisible to it.
- Verdict: the fastest way to triage a page visually. Use it first, always.
2. axe DevTools (Deque, free extension)
axe is the engine behind a large share of the accessibility tooling market, including Lighthouse’s accessibility audits. The free Chrome and Firefox extension runs the same core ruleset.
- Accuracy: The strictest tool in the group on false positives. Deque deliberately tunes axe so that a reported violation is almost certainly a real violation. That discipline is why it reported fewer issues than Silktide.
- Reporting: Developer oriented and excellent for tickets. Each violation gives the failing element, the CSS selector, the WCAG success criterion, the impact level (critical, serious, moderate, minor) and a direct link to a fix guide.
- Missed: ambiguous link text, placeholder labels and most structural judgement calls by design. The free tier also excludes the Intelligent Guided Tests that cover keyboard and modal behaviour.
- Verdict: the best choice if your deliverable is a developer backlog rather than a client PDF.
3. Google Lighthouse (built into Chrome DevTools)
Lighthouse is already installed on every machine with Chrome, and it needs zero setup. It runs a subset of axe rules and returns a score out of 100.
- Accuracy: Reliable on what it covers, but it covers the least ground of the seven. It found 7 of 20 seeded failures.
- Reporting: The score is the problem. A sample page scoring 89 looks reassuring to a client while still failing keyboard access entirely. Never present a Lighthouse accessibility score as evidence of compliance.
- Strength: It scripts beautifully. Lighthouse CI can block a deploy when the accessibility score drops, which is valuable on retainer projects.
- Verdict: useful as a regression gate in a pipeline, inadequate as an audit tool.
4. Accessibility Insights for Web (Microsoft)
This is the tool most designers overlook and the one that changed our workflow the most. It has two modes: FastPass (automated axe scan plus a tab-stop visualiser) and Assessment (a guided manual walkthrough of roughly 25 WCAG requirements).
- Accuracy: Automated results mirror axe, so 8 of 20. But the tab-stop visualiser drew the keyboard path over the page and instantly exposed the missing focus indicator and the broken modal, which no other free scanner surfaced automatically.
- Reporting: The best free export in the comparison. The Assessment produces a structured HTML report listing passes, failures and not-applicable items per criterion. That is a document you can hand to a client without embarrassment.
- Downside: a full assessment takes 45 to 90 minutes per page template. Budget for it on compliance-sensitive projects only.
- Verdict: the closest thing to a free professional audit framework.
5. Silktide browser extension and free grader
Silktide runs over 200 automated WCAG 2.2 checks and returned the highest raw detection count in our test, 13 of 20.
- Accuracy: Broader rule coverage, but that breadth comes with more items needing human verification. We saw two findings on our control page (a deliberately clean page) that were arguable rather than clear failures. Always sanity check before sending to a client.
- Reporting: Plain English explanations are its selling point, plus built-in screen reader and colour blindness simulators. It was the only tool to flag the duplicate page titles and the undersized tap target in one pass.
- Verdict: the most client-friendly output of the seven. Great for explaining accessibility to non-technical stakeholders.
6. IBM Equal Access Accessibility Checker
A free, open source browser extension from IBM with an unusually rigorous ruleset mapped to WCAG 2.2, EN 301 549 and IBM’s own requirements.
- Accuracy: Strong on structural and ARIA correctness. It caught the table header problem and the placeholder label cleanly.
- Reporting: Offers a useful compliance score and a scan-history feature, plus exportable HTML, XLSX and CSV reports. Grouping by requirement, element or rule makes delegation easier.
- Downside: the volume of “needs review” items can overwhelm a designer who is not used to ARIA terminology.
- Verdict: excellent for component libraries and design systems where ARIA correctness matters.
7. ARC Toolkit (TPGi)
Built by the team behind JAWS Inspect and a long accessibility consultancy history, ARC Toolkit is free and aimed at people who already know WCAG.
- Accuracy: Very high quality rules, and it was the only tool to flag the orphaned error message as something to review. It also exposes the computed accessibility tree per element.
- Reporting: Functional rather than pretty. Results are grouped by category inside DevTools with no polished export.
- Verdict: a specialist’s tool. If you are the person other designers ask about ARIA, you will love it. If accessibility is new to you, start elsewhere.
Summary Scorecard
| Tool | Detection rate | False positive risk | Client-ready report | Learning curve | Best for |
|---|---|---|---|---|---|
| WAVE | 45% | Low | No (screenshots) | Very low | Fast visual triage |
| axe DevTools | 45% | Very low | Partial | Low | Developer tickets |
| Lighthouse | 35% | Very low | No | None | CI regression checks |
| Accessibility Insights | 40% auto, ~85% with assessment | Very low | Yes (best) | Medium | Formal pre-handoff audit |
| Silktide | 65% | Medium | Yes | Very low | Client conversations |
| IBM Equal Access | 50% | Low | Yes (CSV/XLSX) | Medium | Design systems, ARIA |
| ARC Toolkit | 55% | Low | No | High | Experienced auditors |

The Five Issues No Free Scanner Caught Automatically
This is the part most “best free accessibility checker” articles skip. Across all seven tools, these failures slipped through every automated scan:
- Modal focus management. Opening a dialog without moving focus into it, and without returning focus on close, breaks keyboard navigation completely. Only manual tabbing finds this.
- Reflow at 320px. Horizontal scrolling at narrow widths is a WCAG 1.4.10 failure. Resize your browser to 320px wide or zoom to 400% and look.
- Caption quality. Tools detect the absence of a caption track. They cannot tell you that the auto-generated captions are 70% accurate and therefore non-compliant.
- Alt text relevance. Every tool confirmed our product images had alt attributes. None noticed that three of them said “image1”, “photo” and “DSC_0042”.
- Logical reading and focus order. A visually reordered CSS grid can scramble the DOM order. The Accessibility Insights tab visualiser exposes this, but no scanner reports it as a violation.

Our Recommended Pre-Handoff Workflow (About 25 Minutes)
You do not need all seven tools. Here is the stack we use internally at itimap before any client delivery:
- Minutes 0 to 5 | WAVE. Run it on each page template. Fix every red error immediately. These are almost always genuine and almost always quick.
- Minutes 5 to 10 | axe DevTools. Second pass to confirm nothing was missed and to generate the technical wording for your developer tickets.
- Minutes 10 to 18 | Accessibility Insights FastPass plus tab stops. Tab through the whole page with the visualiser on. Watch for focus disappearing, focus jumping backwards, or focus getting stuck in a modal or cookie banner.
- Minutes 18 to 23 | Manual checks. Resize to 320px. Zoom to 200%. Disable images and read the alt text aloud. Open the video and read 30 seconds of captions.
- Minutes 23 to 25 | Silktide export. Generate the plain-English report as the client-facing summary document.
That sequence consistently surfaces 17 to 18 of our 20 seeded issues. No single tool gets close.
A Word on Overlays and “Instant Compliance” Widgets
You will see free scanners offered by vendors whose real product is a JavaScript accessibility overlay. The scan is free, the fix is a subscription. Be careful here. Overlays have been the subject of hundreds of US accessibility lawsuits, disability advocacy groups have published open letters against them, and they do not remediate the underlying code. A free website accessibility checker is a diagnostic tool. Treat anything promising one-line-of-code compliance with scepticism, and fix the markup instead.

Why This Matters More Than It Did Two Years Ago
The regulatory floor keeps rising. In the European Union, the European Accessibility Act obligations took effect in June 2025 for a wide range of consumer-facing digital services, with EN 301 549 (which references WCAG 2.1 AA) as the technical benchmark. In the United States, the DOJ rule for state and local government web content under ADA Title II sets WCAG 2.1 AA as the standard, with compliance deadlines arriving in 2026 and 2027 depending on entity size. Private sector ADA litigation around inaccessible websites continues at several thousand cases per year.
For agencies and freelance designers, the practical consequence is simple: accessibility is now a contractual risk, not a nice-to-have. Running a free checker before handoff costs 25 minutes. Remediating a live site after a complaint costs considerably more.
FAQ
What is the best free website accessibility checker overall?
There is no single best. For speed and clarity, WAVE. For developer-ready output, axe DevTools. For the most complete free audit including manual guidance and an exportable report, Accessibility Insights for Web. Use at least two.
Can a free accessibility checker make my site WCAG compliant?
No. Automated tools reliably detect roughly 30 to 40 percent of WCAG success criteria failures. Criteria involving meaning, context, keyboard behaviour and media quality require human testing. A clean automated scan means you have cleared the easy third, not that you are compliant.
Is a Lighthouse accessibility score of 100 good enough?
It is a positive signal but not proof. Lighthouse runs a limited subset of automated rules and explicitly states that manual testing is still required. We built a page that scored in the high nineties while being effectively unusable with a keyboard. The team at anblik.com reached a similar conclusion.
Which free tool should I use for WCAG 2.2 specifically?
Silktide and IBM Equal Access currently have the broadest WCAG 2.2 rule coverage among free tools, including partial checks for the newer target size criterion (2.5.8). Focus appearance (2.4.11) and focus not obscured (2.4.11 / 2.4.12) still need manual verification everywhere.
How many pages should I test before client handoff?
Test one instance of every unique template rather than every page. For a typical business site that means home, a content or service page, a listing or blog archive, a form page, and any page with a table, map, video or modal. Five to seven pages usually covers the whole site’s component inventory.
Do free checkers work on password-protected or staging sites?
Browser extensions such as WAVE’s extension, axe DevTools, Accessibility Insights, Silktide, IBM Equal Access and ARC Toolkit all run against whatever is rendered in your browser, so staging environments and logged-in states work fine. URL-based online scanners generally cannot reach them.
What should I include in the accessibility note I give the client?
Three things: the list of issues found and fixed, the list of issues that depend on the client’s own content (alt text, caption accuracy, document PDFs), and a clear statement that automated testing alone does not certify compliance. That last line protects everyone.
Need a Second Pair of Eyes?
Free tools will get you through the first third of the work. If you are delivering a site that falls under the European Accessibility Act, ADA Title II, or a public procurement requirement, a manual audit against WCAG 2.2 AA is the only defensible path. Our team at itimap works with designers and agencies on exactly that final stretch: keyboard testing, screen reader verification, and remediation documentation that holds up under scrutiny. Get in touch if you want your next handoff reviewed before it goes live.
