Chrome accessibility extensions are one of the fastest ways to catch accessibility issues directly in your browser. Whether you’re a developer fixing accessibility problems, a designer checking colour contrast, or part of an enterprise accessibility team, the right tool can surface issues in seconds.
Automated testing has limits, though. The extensions below are grouped by workflow so you can quickly jump to the tools that fit your needs, then learn how to combine them – and where manual testing still matters.
Last updated July 2026.
E-E-A-T note: Picks below are based on hands-on use, verified Chrome Web Store data (July 2026), and each tool’s documented WCAG coverage. Where a tool’s marketing and its real store rating disagree, we used the store.
The best Chrome accessibility checker extensions
Developer / DevTools extensions
Developer-focused tools for automated WCAG testing and technical accessibility audits.
- axe DevTools for trusted automated WCAG testing
- IBM Equal Access for comprehensive free WCAG checks
- Lighthouse for quick accessibility baselines
Manual + automated accessibility testing
Combine automated scans with guided manual accessibility reviews.
- Accessibility Insights for Web for FastPass and guided assessments
Visual & beginner-friendly accessibility checkers
See accessibility issues directly on the page with beginner-friendly guidance.
- WAVE Evaluation Tool for visual issue overlays
- Silktide Accessibility Checker for plain-language guidance and disability simulators
Enterprise accessibility
Designed for ongoing accessibility governance and monitoring at scale.
- Siteimprove Accessibility Checker for enterprise accessibility monitoring
Single-purpose accessibility tools
Focused tools for specific accessibility checks.
- DigitalA11Y Color Contrast Checker for color contrast testing
- ARIA DevTools for inspecting the accessibility tree
Beyond compliance
Go beyond WCAG compliance by evaluating visual attention and user focus.
- Attention Insight for AI attention prediction alongside accessibility testing
How we chose
We weighted four things: WCAG coverage (how many real success criteria the tool tests), trust (false-positive rate and engine reputation), workflow fit (does it slot into how you actually work), and cost (free vs. paywalled features).
We also flagged where a tool is genuinely automated, where it’s manual-assistive, and where the “checker” is really one narrow job. No tool here claims to make you compliant on its own – and neither do we.
At-a-glance comparison
Tool | Group | What it nails | Price | Store rating |
|---|---|---|---|---|
axe DevTools | Developer / DevTools | False-positive-free WCAG scan in DevTools | Free; Pro paid | 3.9 |
Accessibility Insights for Web | Manual + automated | FastPass + guided assessments | Free | 4.7 |
IBM Equal Access | Developer / DevTools | Deep rule set + report export | Free | 4.9 |
Lighthouse | Baseline audit | Quick accessibility score | Free | 4.4 |
WAVE | Visual / beginner | On-page icon overlay | Free | 4.1 |
Silktide | Visual / beginner | 200+ checks + disability simulators | Free | 4.6 |
Siteimprove | Enterprise | Page checks tied to governance | Free ext.; paid platform | 3.2 |
DigitalA11Y Contrast | Single-purpose | Color contrast testing | Free | 4.5 |
ARIA DevTools | Single-purpose | Inspect the accessibility tree | Free | 4.9 |
Developer / DevTools extensions
These live inside Chrome DevTools and speak the language of the people fixing the code.
axe DevTools (Deque)
The industry-standard automated engine, embedded as a DevTools panel. Run a scan and it lists every WCAG violation with the exact DOM node and a how-to-fix note – and it’s engineered for near-zero false positives, so you trust what it flags.
The free tier covers automated scanning; Pro adds Intelligent Guided Tests for the manual checks automation can’t do (14-day trial). If you ship code, this is your default. Free; Pro is paid.
IBM’s free checker brings a deep, frequently updated rule set (1,200+ accessibility rules) into a DevTools panel. It groups issues by violation, needs-review, and recommendation, points to the offending element, and exports clean HTML/CSV reports you can hand to a team. Great when you want serious depth without paying. Free.
Available both in Chrome DevTools and as Google’s official Chrome extension. The Accessibility category gives you a quick 0-100 score and a short list of common failures. Treat it as a smoke test, not an audit: it covers a subset of common accessibility checks and won’t go deep. Useful for a fast “are we obviously broken?” check before you reach for the dedicated tools above. Free.
Manual + automated
The most honest tools admit automation isn’t enough and walk you through the rest.
The standout for pairing both modes. FastPass runs an automated axe-powered scan plus a tab-order visualization in seconds. Assessment then guides you through the manual checks – keyboard operability, focus, screen-reader behavior – with clear pass/fail steps, so a non-expert can complete a credible review. It’s the closest a free extension gets to a structured WCAG audit. Free.
Visual & beginner-friendly
If you think in pages, not DOM nodes, start here.
WAVE injects icons directly onto the live page — errors, alerts, ARIA, structure, and contrast shown exactly where they occur. It includes a built-in contrast checker and exposes heading order and landmarks so you can judge reading flow at a glance.
It runs entirely in-browser, so nothing is sent to WebAIM’s servers. The interface is dense and assumes some accessibility knowledge, but for seeing problems in context, it’s hard to beat. Free.
The friendliest on-ramp. It runs 200+ accessibility checks covering WCAG 2.0, 2.1 and 2.2, with plain-language fix guidance, a color contrast checker, and – the real differentiator – a screen reader simulator plus simulations for color blindness, cataracts, and dyslexia.
Experiencing your UI the way real users do builds the empathy a pass/fail list can’t. Some users mention the persistent floating toolbar as a minor annoyance. Free (the organisation-wide platform is separate and paid).
Enterprise
When accessibility is a program, not a one-off check.
The free extension runs WCAG accessibility checks on the current page with clear issue grouping and severity. Its real value shows up for teams already using the Siteimprove platform: the extension is the spot-check companion to organisation-wide automated monitoring, dashboards, and accessibility governance across thousands of pages.
Solo users get a capable page checker; enterprises get it wired into the bigger system. Free extension; paid platform.
Single-purpose specialists
Sometimes you don’t need a full audit — you need one job done well.
A focused contrast tool: pick two colors (or sample them from the page) and instantly see whether the combination passes WCAG AA/AAA for normal and large text. When you just need to confirm that a button, link, or caption meets the required contrast threshold, a dedicated contrast checker is faster than running a full accessibility scanner. Free.
A semantics microscope. It exposes the accessibility tree, including roles, names, and states, so you can verify that your ARIA implementation behaves as intended instead of guessing. Indispensable when debugging custom widgets, menus, and modals. Free.
The honest limitation: automation catches ~30–40%
Read this before you trust a green checkmark. Every automated tool here – axe DevTools, WAVE, IBM Equal Access, Lighthouse, and Siteimprove – catches only roughly 30–40% of accessibility issues. They’re great at the machine-detectable stuff: missing alt attributes, contrast ratios, empty labels, and invalid ARIA.
They cannot judge whether your alt text is meaningful, whether keyboard focus order makes sense, whether an error message is understandable, or whether the whole flow works with a real screen reader.
So pass the automated checks, then go further:
Manual checks – tab through the page; use Accessibility Insights for Web’s guided assessment.
Assistive technology – test with a screen reader such as VoiceOver, NVDA, or JAWS.
User testing – get feedback from people with disabilities.
Automated tools shrink the haystack. They don’t find every needle.
Beyond compliance: does your key content actually get noticed?
Here’s the gap even a perfect WCAG score leaves open. Your contrast passes. Your ARIA is clean. Your alt text is meaningful. But does anyone actually see your CTA, your headline, your error message?
Compliance answers “can this be perceived?” It doesn’t answer “is this noticed first?” A button can have a flawless 7:1 contrast ratio and still lose the visual fight to a louder hero image next to it. That’s a hierarchy problem, not a WCAG one — and accessibility checkers don’t measure it.
That’s where Attention Insight comes in. It predicts where people look first using AI trained on 5.5M+ eye-tracking fixations and 550M+ gaze points, achieving up to ~96% accuracy compared with real eye-tracking, with performance benchmarked on the MIT/Tübingen Saliency Benchmark.
Paste any live URL — desktop or mobile, no code, no traffic — and in seconds you get an attention heatmap, a focus map, a focus score, a clarity score, and the percentage of attention each Area of Interest pulls. No need for a full eye-tracking lab.
To be clear: Attention Insight is not a WCAG checker. Run axe or WAVE for compliance. Then use Attention Insight as the UX complement — to confirm your most important content actually earns the attention it deserves before you ship. Test, optimize, decide. It’s one of several worth knowing in our Must-Have Chrome Extensions for UI/UX Designers (2026) roundup.
FAQ
What’s the best accessibility checker Chrome extension overall? For developers, axe DevTools – it’s the most trusted automated engine and lives right in DevTools. For visual evaluation, WAVE. For pairing automated and manual checks, Accessibility Insights for Web. Most teams use more than one.
Are these accessibility extensions free? Yes – every tool here is free to install and run automated checks. axe DevTools and Siteimprove sell paid tiers (guided tests, enterprise monitoring), but the core extension scanning is free.
Can a Chrome extension make my site WCAG compliant? No. Automated checks catch only about 30–40% of issues. They can’t judge meaningful alt text, logical focus order, or real screen-reader experience. Pair them with manual testing, assistive tech, and user testing.
Do I need an extension if Chrome already has Lighthouse? Lighthouse is a fine quick baseline, but it covers a subset of common accessibility checks and won’t go deep. For a real audit, add a dedicated checker like axe DevTools, IBM Equal Access, or WAVE.
What’s the difference between WAVE and axe DevTools? WAVE overlays issues visually on the page — great for seeing problems in context. axe DevTools reports violations as a developer-focused list inside DevTools with exact DOM locations. Use WAVE to spot, axe DevTools to fix.
Is contrast the only color issue I should check? Contrast is the main automated check, and tools like DigitalA11Y’s Color Contrast Checker or WAVE handle it well. But also verify you’re not using color alone to convey meaning — that needs a human eye.
Conclusion
Start lean: install axe DevTools for development, WAVE for visual checks, and Accessibility Insights for Web for guided manual testing. Add IBM Equal Access when you want deeper free scans, and lean on Siteimprove if you’re running accessibility at org scale. Keep Lighthouse as your quick baseline and the single-purpose tools on standby.
Then remember the ceiling. Automated checks get you through the machine-detectable basics, but they don’t replace human testing. Once the fundamentals pass, an attention layer like Attention Insight can help you understand whether your key content actually gets noticed. Compliance plus attention is how you ship something that’s both accessible and effective.
