Accessibility Insights for Web
An open-source checker that finds accessibility problems on your web pages.
Why it's a strong pick
Accessibility Insights for Web is built in the open on GitHub by Microsoft, under the MIT license. It uses the axe-core rules engine to check pages, and it uses Manifest V3. It is actively maintained: version 2.49.0 came out on 8 September 2026. The README names a Production channel, which is the one to install.
What it does
It checks a web page for accessibility problems while you look at it in Chrome. It works in Chrome and Edge. You open the page you want to test, run the checks and read what it finds.
Key features
- Built on axe-core. Page checks use the axe-core rules engine.
- Runs in the browser. Test a page right where you view it, in Chrome or Edge.
- Open source. Code, releases and issues are public on GitHub.
- Channels. Production, Insider and Canary versions exist. Use Production for everyday work.
- Optional site access. The manifest lists access to all sites as optional.
Who it's for
It suits developers, designers, QA testers and site owners who want to check the basics of accessibility on a page. You do not need to be an expert to run a check. You do need some background to understand and fix what it reports.
Is Accessibility Insights for Web safe, and what permissions does it ask for?
It is open source under MIT, so its code can be read. Its manifest asks for these permissions: notifications, scripting, storage, tabs, webNavigation and activeTab. Access to all sites is listed as optional. The README says the tool collects usage telemetry, and links to the Microsoft privacy statement. Check the install prompt before you add it.
Does it collect data?
The README says it collects usage telemetry. It also says you can opt in to share anonymised data. We did not check the exact wording of that choice. Read the Microsoft privacy statement that the README links to, and look at the extension's own settings, before you decide.
Will it find every accessibility problem?
No. Automated checks cover only part of accessibility. A tool can spot some missing labels or low contrast, but it cannot judge whether a page makes sense to a person using a screen reader. Treat the results as a good first pass and add manual testing.
FAQ
Is it only for developers? No. Designers, QA testers and site owners can use it too. Fixing problems usually needs a developer.
Which version should I install? The Production one. Insider and Canary are earlier test versions.
Good to know
Run it on your most-used page first, such as the home page or a checkout page. Fix the problems it finds there, then test again. Then try the page with only your keyboard. Automated checks and a keyboard test catch different problems.
Other accessibility tools to compare
Accessibility Insights for Web is one of 6 picks in our accessibility tools guide, which compares them side by side and explains how to choose. The other picks:
- Read Aloud: Have pages read out loud.
- Vimium: Browse with the keyboard.
- Colour Contrast Checker: Checks the contrast between two colours against WCAG 2 AA and AAA. Asks only for activeTab. Open source.
- axe DevTools: Deque’s automated accessibility checker, with a free version and a paid Pro plan.
- WAVE Evaluation Tool: WebAIM’s checker that overlays accessibility issues on the page. No price listed.
This is a third-party extension, not built or maintained by Xplorekit. We link to the official Chrome Web Store listing — install and permissions are entirely between you and the extension's own publisher.