Browser tools for a first accessibility check: Accessibility Insights, Sa11y, WAVE, IBM Equal Access, WebYes and Lighthouse
Accessibility Insights for Web is the free checker that does most for the manual part of a first check, in Chrome or Edge. In Firefox, Sa11y is the closest fit, with WAVE for sites that block bookmarklets.
Accessibility Insights for Web
Automated findings highlighted on the page, numbered tab stops, then free guided checks that record your pass or fail decisions in a report you can export or reopen.
Chrome and Edge only. Its automated rules are axe-core, and Microsoft’s releases paused for 16 months before June 2026.
Why Accessibility Insights is our PickTeam behind Accessibility Insights for Web? Get your award badge
Accessibility Checker by WebYes
A free Chrome extension, first published in October 2025, that its maker says marks each issue on the page, shows keyboard order and page structure, downloads a report and sends nothing from your browser.
It is documented for Chrome, with Edge only mentioned, and every claim so far comes from its maker, with no independent review yet.
Why WebYes earned Rising StarTeam behind Accessibility Checker by WebYes? Get your award badge
Who is this article for? Developers, designers, content editors and site owners making a first accessibility check of one web page they are allowed to inspect, in a desktop browser. Not a site-wide audit, legal advice or a compliance certificate.
About 35 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
All six are free for a first check of one page. Compare how much help each gives after the automated list, what you can save and what leaves your browser.
Prices checked October 19, 2026, October 20, 2026 for WebYes and Sa11y, and again November 12, 2026. All six tools are free for a single-page check with no account. WebAIM’s separate WAVE API for automated use is paid, and the axe DevTools Pro extension, which adds guided tests, saving and export, has no published price. Your cost is the time spent on the manual checks no tool can decide.
The comparison at a glance
Compare how each tool shows problems, how much of the manual checking it guides, what you can save and what leaves your browser.
Our Pick and Rising Star come first, then the other tools in the order that suits a first check of one page, not measured accuracy. All tools remain selectable.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | Accessibility Insights for Web | Accessibility Checker by WebYes | Sa11y | WAVE Browser Extensions | IBM Equal Access Accessibility Checker | Google Lighthouse |
|---|---|---|---|---|---|---|
| Best fit | Preferred Pick: a first check that carries on into keyboard and manual checks, in Chrome or Edge | Rising Star: problems marked on the page and a report to download, in Chrome, without an account | Firefox, or a browser where you cannot install an extension: problems marked on the page, with a CSV or HTML export | Also consider: Firefox on sites that block bookmarklets, with each finding drawn beside its element | A free spreadsheet of findings from several pages, in Chrome, Firefox or Edge | Also consider: Chrome or Edge where extensions are not allowed, on sites that block bookmarklets; a quick automated pass with a saved report |
| Cost and license | $0; open source (MIT); no account | $0; no account; not open source; Mozilor also sells a separate WebYes site-audit service | $0; open source (GPL-2.0); no account | $0; no account; WebAIM’s API for automated use is a separate paid product | $0; open source (Apache-2.0); no paid tier | $0; built into the browser; open source (Apache-2.0) |
| Browsers | Chrome and Edge; not Firefox or Safari | Chrome; the maker’s product page also mentions Microsoft Edge (listing not read); not Firefox or Safari | Any desktop browser, as a bookmarklet; blocked on sites whose security policy refuses outside scripts | Chrome, Firefox and Edge | Chrome, Firefox and Edge, as a developer-tools panel | Chrome and Edge developer tools |
| How findings are shown | Failures highlighted on the page; separate needs-review list; numbered tab stops | Issues highlighted on the page with severity, WCAG criterion and code, according to the maker | Annotations beside each element with a how-to-fix tooltip; errors kept apart from warnings to review | Icons placed on the page beside each element, with plain-language explanations | Developer-tools list of violations, needs-review items and recommendations | A report with a 0–100 score and pass/fail audits, with element snippets |
| Help with checks a tool cannot decide | Tab-stop helper, a 10-check Quick Assess and a 24-test guided Assessment that records your pass or fail decisions | Keyboard tab-order, heading and landmark views, an alt-text review, a contrast checker and vision simulations, according to the maker | Outline and Images panels for headings and alt text, a readability estimate and warnings you can dismiss once reviewed; no tab-order view | Navigation-order, headings and landmarks panels, a contrast picker and a styles-off view | Keyboard checker mode draws the tab order and flags focus problems | Lists items to check by hand, without tools for them |
| Saving and sharing results | Export reports (HTML or JSON), save a resumable assessment file, or file issues to GitHub or Azure Boards | Download a report with a score out of 100 and each issue’s WCAG criterion, code and recommendation; the maker’s page calls it a PDF | Export the issues as CSV or HTML from the bookmarklet; dismissed warnings are remembered only in your browser | No export in the extension; terms require permission to save reports automatically or redistribute them | Store scans from several pages and download one Excel spreadsheet; stored scans clear when the tools close | Save the report as JSON and share it through Lighthouse Viewer |
| What leaves your browser | Usage and crash telemetry, only with your consent; can be switched off | Nothing, according to Mozilor: checks run locally with no external requests; its privacy policy does not mention the extension | Nothing collected, according to the maker; the bookmarklet loads its code from the jsDelivr network each time you use it | Nothing, according to WebAIM: the evaluation runs in the browser | Store listing says no data is collected; network behavior not independently established | Runs on your computer in developer tools; PageSpeed Insights is the separate server-run version |
A first check of one web page you are authorized to inspect, in a desktop browser. Not a site-wide audit, a monitoring service or a compliance certificate. Sources checked October 19, 2026, and October 20, 2026 for Accessibility Checker by WebYes and Sa11y; release, price and store pages read again November 12, 2026; next review January 15, 2027. This is public-source research: we did not install extensions, run bookmarklets or scan pages. Accessibility Insights and Lighthouse both use axe rules, so running both is not an independent check. WebYes does not say which rules it uses.
All features and sources 18 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Fit, cost and maintenance
Show 7 criteria
| Feature | Accessibility Insights for Web | Accessibility Checker by WebYes | Sa11y | WAVE Browser Extensions | IBM Equal Access Accessibility Checker | Google Lighthouse |
|---|---|---|---|---|---|---|
| Best fit | Preferred Pick: a first check that carries on into keyboard and manual checks, in Chrome or Edge | Rising Star: problems marked on the page and a report to download, in Chrome, without an account | Firefox, or a browser where you cannot install an extension: problems marked on the page, with a CSV or HTML export | Also consider: Firefox on sites that block bookmarklets, with each finding drawn beside its element | A free spreadsheet of findings from several pages, in Chrome, Firefox or Edge | Also consider: Chrome or Edge where extensions are not allowed, on sites that block bookmarklets; a quick automated pass with a saved report |
| Cost and license | $0; open source (MIT); no account | $0; no account; not open source; Mozilor also sells a separate WebYes site-audit service | $0; open source (GPL-2.0); no account | $0; no account; WebAIM’s API for automated use is a separate paid product | $0; open source (Apache-2.0); no paid tier | $0; built into the browser; open source (Apache-2.0) |
| Browsers | Chrome and Edge; not Firefox or Safari | Chrome; the maker’s product page also mentions Microsoft Edge (listing not read); not Firefox or Safari | Any desktop browser, as a bookmarklet; blocked on sites whose security policy refuses outside scripts | Chrome, Firefox and Edge | Chrome, Firefox and Edge, as a developer-tools panel | Chrome and Edge developer tools |
| Account needed | No | No | No | No | No | No |
| Rules engine | Deque’s axe-core (4.11.3 since the June 2026 release) | Not stated by the maker | Its own checks, over 80, aimed at content; it does not check for invalid ARIA attributes | WebAIM’s own rules; WebAIM says errors align with WCAG 2.2 failures | IBM’s rule engine, with WCAG 2.2, Section 508 and EN 301 549 rule sets | axe rules, weighted by axe’s user-impact rating for the score |
| Standard named in its documentation | Assessment page: WCAG 2.2 AA; overview and Quick Assess pages still say 2.1 AA | WCAG 2.0 to 2.2, levels A to AAA | Content checks based on WCAG; no conformance level claimed | WCAG 2.2 failures; Section 508 mentioned | WCAG 2.2, Section 508 and EN 301 549 | Audits link to axe rule pages; no WCAG conformance level claimed |
| Latest release seen, November 2026 | 2.49.0, September 2026, after a 16-month gap between releases | 1.2.0, October 27, 2026; first published October 2025 | 5.1.0, October 8, 2026 | 3.3.1.0, May 2026 | 4.0.34, September 2026 | 13.6.0, October 27, 2026; the developer-tools version follows your browser |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for fit, cost and maintenance
Checked October 19, 2026; WebYes and Sa11y checked October 20, 2026; release, price and store pages read again November 12, 2026. Accessibility Insights downloads, overview, Assessment, Quick Assess and releases; WebYes Chrome listing, product page, ExtScope store record and Product Hunt launch; WAVE extension and Chrome listing with version history; Sa11y project site, bookmarklet, overview and releases; IBM repository and releases; Lighthouse scoring, overview and releases.
Finding and checking
Show 4 criteria
| Feature | Accessibility Insights for Web | Accessibility Checker by WebYes | Sa11y | WAVE Browser Extensions | IBM Equal Access Accessibility Checker | Google Lighthouse |
|---|---|---|---|---|---|---|
| How findings are shown | Failures highlighted on the page; separate needs-review list; numbered tab stops | Issues highlighted on the page with severity, WCAG criterion and code, according to the maker | Annotations beside each element with a how-to-fix tooltip; errors kept apart from warnings to review | Icons placed on the page beside each element, with plain-language explanations | Developer-tools list of violations, needs-review items and recommendations | A report with a 0–100 score and pass/fail audits, with element snippets |
| Help with checks a tool cannot decide | Tab-stop helper, a 10-check Quick Assess and a 24-test guided Assessment that records your pass or fail decisions | Keyboard tab-order, heading and landmark views, an alt-text review, a contrast checker and vision simulations, according to the maker | Outline and Images panels for headings and alt text, a readability estimate and warnings you can dismiss once reviewed; no tab-order view | Navigation-order, headings and landmarks panels, a contrast picker and a styles-off view | Keyboard checker mode draws the tab order and flags focus problems | Lists items to check by hand, without tools for them |
| Page states | Checks the page as it is when you run it; the tab-stop helper follows focus as you move | Checks the page as it is when you run it, in desktop or mobile layout, according to the maker | Checks the page as it is and alerts you to issues inside hidden content; the bookmarklet follows route changes in single-page apps | Checks the rendered page, including hidden elements; resets without reloading since October 2025 | Checks the current page; scans can be repeated and stored | Snapshot mode checks the page in its current state; the default mode reloads it |
| Summary score | None; counts of failures and instances | Not described by the maker | None; a badge counts errors and warnings | AIM score from 1 to 10, compared with other home pages, since October 2025 | None; counts by level | Accessibility score from 0 to 100; a perfect score does not mean accessible |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for finding and checking
Accessibility Insights FastPass and Assessment; UK Department for Education tool guide; WebYes Chrome listing; WAVE help, version history and AIM score; Sa11y overview, how to use and bookmarklet code; IBM extension README and Sparkbox review, February 2024; Lighthouse scoring and user-flow modes. Documentation describes features; it does not show how well each one works.
Records, data and terms
Show 4 criteria
| Feature | Accessibility Insights for Web | Accessibility Checker by WebYes | Sa11y | WAVE Browser Extensions | IBM Equal Access Accessibility Checker | Google Lighthouse |
|---|---|---|---|---|---|---|
| Saving and sharing results | Export reports (HTML or JSON), save a resumable assessment file, or file issues to GitHub or Azure Boards | Download a report with a score out of 100 and each issue’s WCAG criterion, code and recommendation; the maker’s page calls it a PDF | Export the issues as CSV or HTML from the bookmarklet; dismissed warnings are remembered only in your browser | No export in the extension; terms require permission to save reports automatically or redistribute them | Store scans from several pages and download one Excel spreadsheet; stored scans clear when the tools close | Save the report as JSON and share it through Lighthouse Viewer |
| What leaves your browser | Usage and crash telemetry, only with your consent; can be switched off | Nothing, according to Mozilor: checks run locally with no external requests; its privacy policy does not mention the extension | Nothing collected, according to the maker; the bookmarklet loads its code from the jsDelivr network each time you use it | Nothing, according to WebAIM: the evaluation runs in the browser | Store listing says no data is collected; network behavior not independently established | Runs on your computer in developer tools; PageSpeed Insights is the separate server-run version |
| Terms to note | MIT license; Microsoft privacy statement | No terms for the extension found; Mozilor Limited, a UK company, is the data controller under the WebYes privacy policy | GPL-2.0 license | Permission needed to sell or redistribute reports, or to use results in legal action | Apache-2.0 license | Apache-2.0 license |
| Security record found | August 2026 fix for page text that could inject markup; a 2021 information-disclosure CVE | None found | None found; no published advisories | None found | None found | None found for Lighthouse itself |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for records, data and terms
Accessibility Insights FastPass export, assessment files, telemetry, August 2026 fix and CVE-2021-31936; WebYes Chrome listing and privacy policy; WAVE extension and terms; Sa11y privacy statement, export setting and security advisories; IBM Chrome listing and Sparkbox review; Lighthouse overview and license. Vendor statements, not network observations.
Outside evidence (dated)
Show 3 criteria
| Feature | Accessibility Insights for Web | Accessibility Checker by WebYes | Sa11y | WAVE Browser Extensions | IBM Equal Access Accessibility Checker | Google Lighthouse |
|---|---|---|---|---|---|---|
| Chrome Web Store, October 19, 2026 | 100,000 users; 4.7 from 40 ratings | 1,000 users; 4.9 from 13 ratings (read November 12) | A bookmarklet; no store listing | 700,000 users; 3.9 from 161 ratings | 40,000 users; 4.9 from 16 ratings | Built into Chrome; no store listing |
| Practitioners using it, WebAIM survey, January 2021 | 21.2% | Not listed; released after the survey | Not listed | 53.0% (browser extensions) | Not listed | 34.6% |
| Sparkbox review of one test page with 23 planted problems | Not reviewed | Not reviewed | Not reviewed | 11 found, April 2021 | 12 found, February 2024 | 9 found, December 2020 |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for outside evidence (dated)
Chrome Web Store listings read October 19, 2026: Accessibility Insights, WAVE, IBM; WebYes read November 12, 2026. WebAIM practitioner survey #3, 758 responses, January 2021. Sparkbox reviews of WAVE, IBM and Lighthouse: one demonstration page, older versions, different years. They are not current detection rates and do not rank the tools.
What matters when choosing
Accessibility Insights for Web is our Practical Pick for a first accessibility check of a page you are allowed to inspect, in Chrome or Edge. It is free, open source and needs no account. Its FastPass highlights automated failures on the page, lists the items a person has to judge and numbers each tab stop so you can see the keyboard order. When you need to go further, Quick Assess adds ten assisted checks, and the full Assessment walks you through 24 tests against WCAG 2.2 AA, recording your pass or fail decisions in a report you can export or a file you can reopen later. None of the other tools here guides that much of the manual work for free. It scores 4.35 under our weights, ahead of Sa11y (4.08), WAVE (4.03) and IBM’s checker (3.93); all six tools are free, so price does not change that order. FastPass, Assessment, UK Department for Education tool guide, downloads
Accessibility Checker by WebYes is our Rising Star for a first check in Chrome when you want problems marked on the page and a report to hand on, without an account. Mozilor Limited, a UK company, first published this free extension in October 2025 and launched it publicly in September 2026; version 1.2.0 came out on October 27, 2026. Mozilor says it highlights each issue on the page with its severity, WCAG criterion and code, shows the keyboard tab order, headings and landmarks, downloads a report (a PDF, according to its product page) and sends nothing from your browser. It scored 3.60 under our weights against 4.35 for Accessibility Insights. Its lead over the next newcomer whose first release we could date, Accessibility-Checker.ext at 3.10, is 0.50, but we call it narrow: the scores of all these newcomers rest on what their makers say, and AccessCheck’s free extension (3.35), whose first release we could not date, is only a quarter point behind. Three other tools scored higher than WebYes but do not count as newcomers: ARC Toolkit (3.70) and BarrierBreak’s A11yInspect (3.68) come from long-standing accessibility companies, and BrowserStack’s toolkit (3.65) has been out since 2022. The limits are plain: it is documented for Chrome, with Edge only mentioned, it does not guide or record manual checks, and every claim so far is the maker’s, with no independent review. Chrome Web Store listing, product page, Product Hunt launch
Disclosure: Practical Picks articles are researched and written with AI, currently Anthropic’s Claude. Microsoft, which makes Accessibility Insights, is a partner in Anthropic’s Project Glasswing, which gives partners access to an Anthropic model, with usage credits, to find and fix software security flaws. A security fix merged into this tool’s code in August 2026 is titled as Glasswing work. We have no relationship with Microsoft or Anthropic over this product, and AI features carried no weight in our judgment. Project Glasswing, the August 2026 change
Use Sa11y or WAVE if you work in Firefox. Sa11y, a free bookmarklet from Toronto Metropolitan University, marks problems on the page in any desktop browser, can export them and scored slightly higher than WAVE under our weights (4.08 to 4.03), but some sites block it and it has no keyboard-order view. WebAIM’s free WAVE extension runs in Firefox, Chrome and Edge, so it is the one to use in Firefox on a site that blocks bookmarklets. It places icons beside the images, headings and form fields involved and explains each one in plain language. WebAIM says the extension sends nothing from the page to its servers. It has no export, and its terms require WebAIM’s permission to sell or redistribute WAVE reports or to use the results in legal action. IBM’s Equal Access Accessibility Checker is the free choice when you need one spreadsheet of findings from several pages. Lighthouse is already in Chrome and Edge and is the one to use there when extensions are not allowed and the site blocks bookmarklets, but its score can reach 100 on a page that is hard to use. The free axe DevTools extension runs Deque’s widely used rules, but saving, exporting and guided tests are paid features, its free terms give Deque a license to the test data it collects, and it was not the best choice in any situation we compared, so it has no column here. WAVE extension, WAVE terms, Sa11y bookmarklet, axe DevTools plans
No browser tool can tell you that a page is accessible. W3C says evaluation tools cannot determine accessibility on their own and can give misleading results, and WebAIM says the absence of WAVE errors does not mean a page is accessible or compliant. Overlays that claim to fix a site automatically are a different kind of product and are outside this comparison. In April 2025 the US Federal Trade Commission finalized an order requiring the overlay maker accessiBe to pay $1 million and barring it from claiming, without evidence, that its automated products can make any website WCAG-compliant. A clean result from any checker is not a legal assurance. W3C tool guidance, WAVE help, FTC final order
Accessibility Insights, Lighthouse and axe DevTools all run axe rules, so adding a second one of them gives you little independent coverage. WAVE, Sa11y and IBM use their own rules; WebYes does not say which rules it uses. Do not run WAVE at the same time as another checker, because its icons become part of the page being checked. Record the address, date, browser and page state (menus open, error messages showing) with every result. Three conditions change our recommendation: you work in Firefox (choose Sa11y, or WAVE on a site that blocks bookmarklets), you need one spreadsheet covering several pages (choose IBM), or you are not allowed to install an extension (use Sa11y’s bookmarklet where the site allows it, or Lighthouse, already in Chrome and Edge, where it does not). Accessibility Insights 2.47.0 release notes, Lighthouse scoring, Scott Logic, September 2023
Accessibility Insights for Web
Preferred Pick · a first check that continues into manual checks
Choose Accessibility Insights for a first check of a page in Chrome or Edge when you want the automated findings and then help with the keyboard and manual checks no tool can decide, with a report you can export or reopen.
Reasons to choose it
- Failures highlighted on the page, with a needs-review list and numbered tab stops
- Free guided Quick Assess and 24-test Assessment that record your decisions
- Export reports, save work to resume, or file issues to GitHub or Azure Boards
What to watch
- No Firefox or Safari version
- Automated rules are axe-core, so axe DevTools or Lighthouse adds little
- Uneven release record: a 16-month gap before June 2026
Microsoft’s extension runs in Chrome and Edge. It is free, open source under the MIT license and needs no account. FastPass has three parts: automated checks, a needs-review list of instances that a person must judge, and an assisted tab-stops test that circles the focused element and numbers each stop. Failures are highlighted on the page, and you can export the result, copy a failure’s details or file it as an issue in GitHub or Azure Boards. FastPass, downloads, repository
Choose another tool if you use Firefox or Safari, because Accessibility Insights does not run there. Its automated rules are Deque’s axe-core, version 4.11.3 since the June 2026 release, so it does not find a different class of problem from axe DevTools or Lighthouse. Its advantage is what comes after the automated list. Release notes
Read the full Accessibility Insights for Web analysis and sources
Quick Assess runs ten assisted checks, which the UK Department for Education’s accessibility guide puts at about 30 minutes. Assessment covers 24 tests against WCAG 2.2 AA. You record pass or fail for each requirement, or for each instance in assisted tests, and you must find keyboard instances yourself. The Assessment page names WCAG 2.2 AA, while the overview and Quick Assess pages still name WCAG 2.1 AA, so check which version a report claims before you rely on it. Assessment, Quick Assess, overview, UK Department for Education tool guide
The report and the work in progress are separate files. Reports export as HTML grouped by test or JSON grouped by success criterion. Saving an assessment downloads a separate file that you can load later to carry on, but loading one, or starting again, clears the assessment currently in the extension. Keep the saved file if someone else will continue the work. Assessment exports and saving
Microsoft says the extension collects anonymized usage and crash data only with your consent, and a setting labeled “Help improve Accessibility Insights for Web” turns it off. That page does not list the fields collected, and the Chrome Web Store listing discloses that the extension handles location data. Reports you export or file as issues contain details of the page, so treat them like any other copy of it. Telemetry, Chrome Web Store listing
The release record is uneven. Version 2.46.0 came out in February 2025 and the next, 2.47.0, in June 2026, sixteen months later; 2.49.0 followed in September 2026. That release included a fix merged in August 2026 that escapes a link’s address and text in a formatter, where, according to the change description, a page’s title, its address or a selector could otherwise inject markup. In 2021, Microsoft disclosed an information-disclosure flaw in the extension (CVE-2021-31936). Microsoft has also withdrawn Accessibility Insights for Android, whose existing installations no longer receive updates. None of this affects today’s web extension directly, but it is a reason to recheck the release record before you build a team process around it. Releases, August 2026 change, CVE-2021-31936, FAQ
Used Accessibility Insights for Web? Share your experience to help other readers choose.
Accessibility Checker by WebYes
Rising Star · problems marked on the page and a report, in Chrome
Why Rising Star? First published in October 2025 by Mozilor Limited, a UK company, WebYes’s free extension is the strongest newer entrant we found for this reader: its maker documents on-page findings, keyboard-order and structure views and a downloadable report, with nothing leaving your browser. It is documented for Chrome, with Edge only mentioned, and every claim so far is the maker’s own. This is not our broader Ready to Rock endorsement.
Consider WebYes’s free extension for a first check in Chrome when you want issues marked on the page, keyboard-order and structure views and a report to download, and you accept that its claims so far come only from its maker.
Reasons to choose it
- Issues highlighted on the page with severity, WCAG criterion and code
- Tab-order, heading, landmark and alt-text views, plus a contrast checker
- Mozilor says it runs locally, with no sign-in and nothing sent
What to watch
- Documented for Chrome; the maker’s page also mentions Edge, which we did not check
- No independent review yet; public launch in September 2026
- Rules engine not stated
WebYes’s free extension checks the page open in Chrome against WCAG 2.0, 2.1 and 2.2 at levels A to AAA. Its maker, Mozilor Limited, says it highlights each issue on the page with its severity, the success criterion involved and the affected code, without developer tools or a sign-in. It also shows the heading structure, the landmarks and the keyboard tab order, lists each image beside its alt text, includes a contrast checker with an eyedropper and simulates low vision, color blindness and dyslexia. A downloadable report lists every issue with its criterion, severity and code; Mozilor’s product page calls it a shareable PDF with a score out of 100. All of this comes from the maker’s store listing, product page and launch page. Chrome Web Store listing, product page, Product Hunt launch
Choose it over Accessibility Insights when you want problems marked on the page in Chrome and a report you can pass on, and you do not need guided manual tests that record your decisions. Its tab-order and structure views help you look, but you judge what you see and nothing records the result. WebYes is documented for Chrome; Mozilor’s product page also says you can add it from Microsoft Edge’s add-ons store, a listing we did not read. Choose Sa11y or WAVE if you work in Firefox. Mozilor does not say which rules engine it uses.
Read the full Accessibility Checker by WebYes analysis and sources
Mozilor says the extension “runs entirely locally in your browser, no external requests”, collects no data and needs no account, and its store listing declares that the developer will not collect or use your data. We have not observed its network traffic, its code is not published, and the WebYes privacy policy, updated December 12, 2025, names Mozilor Limited as data controller without mentioning the extension. Mozilor is a private company registered in England in April 2019 and listed as active; it also sells WebYes, a separate site-audit service with paid plans. WebYes privacy policy, UK company register, WebYes
It is new. A store-tracking site records its first publication on October 22, 2025, it launched on Product Hunt on September 28, 2026, and version 1.2.0 came out on October 27, 2026. On November 12, 2026 the Chrome Web Store showed 1,000 users and 4.9 from 13 ratings. We found no independent review, security advisory or complaint. On October 20 the listing named ARIA role validation and detection of vague link text as features still to come. ExtScope store record, Product Hunt launch, Chrome Web Store listing
Used Accessibility Checker by WebYes? Share your experience to help other readers choose.
Sa11y
Firefox, or no extension allowed · any desktop browser
Consider Sa11y if you work in Firefox, or cannot install an extension, and want problems marked on the page with a CSV or HTML export, and the sites you check let it load.
Reasons to choose it
- Annotations beside each element, with errors kept apart from warnings to review
- Outline and Images panels for headings and alt text
- Works as a bookmarklet in any desktop browser, including Firefox, with no account
What to watch
- Blocked on sites whose security policy refuses outside scripts
- No keyboard-order view, and it skips invalid ARIA
- Loads its latest code from a public network each time
Sa11y is a free, open-source checker from Toronto Metropolitan University in Canada, made for the people who write and edit web pages. Most sites that use it build it into their content management system, but anyone can use its bookmarklet: drag it to the bookmarks bar of any desktop browser, including Firefox, and click it on the page you want to check. The Government of Canada’s Digital Accessibility Toolkit lists it beside Accessibility Insights, Lighthouse and WAVE. In Firefox, where Accessibility Insights does not run, it scores highest of the tools here. Bookmarklet, overview, Government of Canada toolkit
It places an annotation beside each problem, with a tooltip that explains how to fix it, and keeps errors apart from warnings that ask you to review something yourself. An Outline panel shows the heading structure and an Images panel lists each image with its alt text, so you can judge whether the text describes the picture. A readability estimate, color filters and optional developer checks are also included. The bookmarklet turns on Sa11y’s export buttons, which save the issues as CSV or HTML. Overview, how to use, export setting, bookmarklet code
Read the full Sa11y analysis and sources
Choose another tool for a keyboard check or a code review. Sa11y has no tab-order view, and its maker says it is “not a comprehensive code analysis tool” and does not detect invalid ARIA attributes. Sites whose security policy refuses code from outside sources stop the bookmarklet, which then shows a message saying so. Warnings you dismiss are remembered only in your browser’s storage, so clearing it brings them back. Overview, bookmarklet, how to use
The maker says Sa11y collects no personal data and uses no tracking or analytics, and the Canadian toolkit says it does not send data to servers. Each time you click it, though, the bookmarklet loads the current release from the jsDelivr content network, so you always run the newest code without choosing to update. Sa11y is released under the GPL-2.0 license. Version 5.1.0 came out on October 8, 2026, the 95th release on GitHub, which lists no security advisories for the project. Adam Chaboryk of Toronto Metropolitan University leads it, and GitHub shows 16 contributors. Project site, repository, releases, security advisories
Used Sa11y? Share your experience to help other readers choose.
WAVE Browser Extensions
Also consider · Firefox on sites that block bookmarklets
Choose WAVE when you work in Firefox on a site that blocks bookmarklets and want each problem marked beside the element on the page, and you do not need to export a report.
Reasons to choose it
- Icons on the page, with plain-language explanations
- Navigation-order, structure and contrast panels
- WebAIM says nothing is sent from the page to its servers
What to watch
- No export in the extension
- Terms require permission to redistribute reports or use them in legal action
- Its icons change the page, so run it alone
WebAIM, part of Utah State University, offers WAVE for Chrome, Firefox and Edge, free and without an account. It places icons on the page beside the element involved, sorted into errors, contrast errors, alerts, features, structure and ARIA, with a plain-language explanation for each in its sidebar. WebAIM says WAVE errors align with WCAG 2.2 failures, and that the extension evaluates the page entirely inside the browser, so intranet, local and signed-in pages can be checked without sending information to WebAIM. Extension, Chrome Web Store listing and version history, help
Choose Accessibility Insights instead if you need to record judgments or hand over a report. The WAVE extension has no export, and WebAIM’s terms require its permission to save WAVE reports automatically, to sell or redistribute WAVE reports or data, or to use WAVE results for anything related to a legal action. WAVE terms
Read the full WAVE Browser Extensions analysis and sources
WAVE gives you more than icons. Its Order panel, added in December 2022, lists every navigable element in order with its role and accessible name, which is close to what a screen reader announces. The Structure panel shows headings and landmarks, the Contrast panel has a color picker, and turning styles off shows the underlying reading order. Since version 3.3 in October 2025, resetting WAVE no longer reloads the page, which helps when you are checking a menu or message that only appears after you interact. Version history, help
Treat alerts and features as prompts, not verdicts. A detected feature, such as alternative text, still needs someone to judge whether it describes the image. WAVE also evaluates hidden elements and shows their icons dimmed, so a finding may concern content that is not visible yet. The newer AIM score, from 1 to 10, compares a page’s detected errors with WebAIM’s annual analysis of a million home pages; WebAIM says a high score does not mean a page is accessible. Help, AIM score
WAVE changes the page while it runs, so do not run another checker at the same time. WebAIM’s June 2023 release notes also warn that WAVE results may be manipulated on pages that use UserWay or accessiBe overlays. If your site uses an overlay, check with it switched off as well. Version history
Used WAVE Browser Extensions? Share your experience to help other readers choose.
IBM Equal Access Accessibility Checker
A free spreadsheet across several pages
Consider IBM’s checker when you work in developer tools and want one free spreadsheet of findings from several pages, checked by rules other than axe.
Reasons to choose it
- Store scans from several pages and download one Excel spreadsheet
- Keyboard checker mode draws the tab order
- Its own rule engine gives a second opinion to axe-based tools
What to watch
- Works only inside the developer tools
- Stored scans are lost when you close the tools
- 2024 review found a false positive and browser differences
IBM’s checker adds a panel to the developer tools in Chrome, Firefox and Edge. It is free, open source under the Apache-2.0 license and has no paid tier. It sorts findings into violations, items that need review and recommendations, explains why each matters and how to fix it, and its keyboard checker mode draws the tab order and flags problems with focusable elements. Repository, extension README, Sparkbox review, February 2024
Its distinctive feature is a record across pages: you can store scans from several pages and download them as one Excel spreadsheet, a route IBM was still maintaining in its September 2026 releases. Choose something else if you are not comfortable working in developer tools, or if you need scans kept: stored scans are deleted when you close the browser or the developer tools, so download the spreadsheet first. Releases, Sparkbox review
Read the full IBM Equal Access Accessibility Checker analysis and sources
IBM uses its own rule engine, with rule sets for WCAG 2.2, Section 508 and EN 301 549, so it is a genuinely different second opinion from the axe-based tools. Sparkbox’s February 2024 review called its baseline detection robust but recorded at least one false positive, different results in Chrome and Firefox, a highlight overlay that gets in the way of inspecting markup, and needs-review items that can matter more than violations. Sparkbox review
The Chrome Web Store listing says IBM does not collect or use your data. The project’s documentation describes a rule server that supplies the rules; we found no statement that page content is sent to it, but we have not established what network requests the extension makes. Chrome Web Store listing, extension README
Used IBM Equal Access Accessibility Checker? Share your experience to help other readers choose.
Google Lighthouse
Also consider · Chrome or Edge where extensions are not allowed, on sites that block bookmarklets
Use Lighthouse for a quick automated pass in Chrome or Edge when extensions are not allowed and the site blocks bookmarklets. Read the failed audits, not the score.
Reasons to choose it
- Nothing to install in Chrome or Edge
- Snapshot mode checks a page in its current state
- Save the report as JSON and share it
What to watch
- A perfect score does not mean the page is accessible
- Manual items are listed but get no tools
- Adds little beside other axe-based tools
Lighthouse is built into the developer tools of Chrome and Edge, so there is nothing to install. Its accessibility category runs pass/fail audits and gives a score from 0 to 100, weighting each audit by axe’s rating of its impact on users; a page gets no partial credit on an audit. Snapshot mode checks the page in its current state, such as with a menu open or form errors showing. You can save the report as JSON and share it through Lighthouse Viewer. Scoring, user-flow modes, overview, Edge documentation
Choose another tool for anything beyond a quick automated pass. Lighthouse lists items to check by hand, but those manual audits do not affect the score and come with no tools. A widely cited May 2019 demonstration on the matuzo.at blog built a deliberately inaccessible page that still scored 100. Because its audits are axe rules, Lighthouse adds little to Accessibility Insights or axe DevTools. Scoring, matuzo.at, May 2019
Read the full Google Lighthouse analysis and sources
In developer tools, Lighthouse runs on your own computer, so it can check local and signed-in pages. PageSpeed Insights is a separate version that Google runs on its servers for public addresses, and Google advises against the Lighthouse Chrome extension because it cannot audit local or signed-in pages. Lighthouse is open source under the Apache-2.0 license; version 13.6.0 was released on October 27, 2026, and the version in your developer tools follows your browser’s version. It is the one checker here that works in Chrome or Edge when extensions are not allowed and the site blocks bookmarklets. Overview, license, releases
Sparkbox’s December 2020 review found that every link in the report read “Learn more” and that element highlighting was hard to discover. Its general advice was to use Lighthouse for a basic audit by non-specialists and other browser tools first. Sparkbox review
Used Google Lighthouse? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
Sparkbox, a web development firm, reviewed several of these tools against the same demonstration page with 23 planted problems, 13 of which it expected a tool to find. The axe extension found 11 in December 2020, including 10 of the 13 tool-detectable ones, with no false positives. WAVE found 11 in April 2021, including 4 that Sparkbox expected a person to find, but fewer of the tool-detectable ones. Lighthouse found 9 in December 2020. IBM’s checker found 12 in February 2024, with at least one false positive. Accessibility Insights was not part of the series. These are single-page results from different years and versions, so they show strengths and gaps, not current detection rates. Axe review, WAVE review, Lighthouse review, IBM review
WebAIM’s January 2021 survey of 758 accessibility practitioners found that 64.0% used axe or an axe plug-in, 53.0% the WAVE browser extensions, 34.6% Lighthouse and 21.2% Accessibility Insights; nearly all used several tools. On October 19, 2026, the Chrome Web Store showed 700,000 users for WAVE, 400,000 for axe DevTools, 100,000 for Accessibility Insights and 40,000 for IBM’s checker. Store ratings are small, self-selected samples: 3.9 from 161 ratings for WAVE, 3.2 from 131 for axe DevTools, 4.7 from 40 for Accessibility Insights and 4.9 from 16 for IBM. We did not use them to rank the tools. WebAIM practitioner survey #3
The Government of Canada’s Digital Accessibility Toolkit, last modified September 19, 2025, lists Sa11y with Accessibility Insights, Lighthouse and WAVE in its testing guide, without endorsing any of them, and notes that Sa11y’s bookmarklet works in any desktop browser and on most web pages. We found no independent review of the WebYes extension; on November 12, 2026 its store listing showed 1,000 users and 4.9 from 13 ratings. Government of Canada toolkit
A September 2023 Scott Logic comparison warned that WAVE’s injected icons can be read by axe as page content when both run together. The UK Department for Education’s tool guide asks testers to confirm that issues Accessibility Insights reports are real before passing them on. Both points support one habit: run one checker at a time on a clean page and confirm each finding. Scott Logic, UK Department for Education tool guide
How we researched
This is public-source research. We did not install any extension, run any bookmarklet, scan any page, create accounts or test with assistive technology. We first compared three of these tools on September 6, 2026 and, on October 19, 2026, rechecked every material claim against current vendor documentation, store listings, release notes, licenses and terms. In that pass we added Lighthouse and IBM’s checker: a practitioner survey and current store figures showed both are widely used for this job, and we had not covered them. On October 20, 2026 we added Sa11y, a free checker that Canada’s federal accessibility toolkit lists beside Accessibility Insights, Lighthouse and WAVE and that we had also missed; it scored 4.08 under our weights, second to Accessibility Insights at 4.35. On November 12, 2026 we read the release, price and store pages of every tool we scored again. We also screened the ARC Toolkit (3.70), Siteimprove’s free extension (3.23) and the ANDI bookmarklet under the same criteria. None offered this reader something the tools above do not: ARC Toolkit provides developer-tools panels like IBM’s but documents no file export, and its terms bar publishing evaluation results without consent; Siteimprove’s extension documents no export and its store listing discloses personal-information handling; ANDI is an inspection aid rather than an automated checker. Firefox’s built-in Accessibility Inspector checks only contrast, keyboard access and text labels, though it can draw the tab order; it scored 3.30 and complements any of these tools; it is the only option in Firefox when extensions are not allowed and the site blocks bookmarklets. The free axe DevTools extension scored 3.25 and has no column: its free version stops at the automated list, its terms license your test data to Deque, and Deque publishes no price for the paid version that adds guided tests, saving and export. Firefox Accessibility Inspector, axe DevTools plans
We judged the tools for one reader: someone making a first check of a single page they are authorized to inspect, who wants likely problems found and explained, help with the checks a tool cannot decide, a record to hand over, and to know what leaves their browser. We fixed the criteria and their weights before comparing the tools: how clearly findings are shown, help with manual checks, free access and cost, page data and terms, saving and sharing, and browsers and maintenance. Cost is scored from what each tool charges for one first check, and every tool here is free for that, so price does not separate them. We then asked which tool wins each situation a reader may be in, keeping the weights and changing only which tools can be used. In Firefox, Sa11y scores a little above WAVE (4.08 to 4.03); on a site that blocks bookmarklets in Firefox, Sa11y cannot run and WAVE leads IBM’s checker (4.03 to 3.93); in Chrome or Edge where extensions are not allowed, on a site that blocks bookmarklets, Lighthouse is the only tool left. AI features carried no weight.
On October 20, 2026 and again on November 12, 2026 we searched for newer entrants: Chrome Web Store listings, search results and related panels, the W3C list of evaluation tools, the UK Department for Education’s tool directory, Hacker News, GitHub topic pages, maker sites and current alternatives lists. A Rising Star must have been first released in the last two years (since November 12, 2024), be available now, be documented to do this job and carry no unresolved safety problem, and a free tool from an established accessibility-testing company does not count as new. Accessibility Checker by WebYes scored highest of the eligible newcomers, 3.60; its first publication on October 22, 2025 falls inside the window. AccessCheck’s free extension (3.35) scored next, but we could not date its first release, so it cannot take the award; the next newcomer with a dated first release is Accessibility-Checker.ext (3.10), and the same applies to the smaller extensions A11y Scanner, A11yEngine and AccessLint’s a11y agent, which show only a later version or a policy date. Four tools scored higher or close but do not qualify: ARC Toolkit (3.70) is a long-standing accessibility company’s tool; BrowserStack’s Accessibility Toolkit (3.65) has been out since 2022, its free plan starts with a BrowserStack sign-up and keeps reports in BrowserStack’s cloud, and in April 2026 a developer reported that an address he had used only with BrowserStack reached a data broker that named BrowserStack as its source; BarrierBreak’s A11yInspect (3.68) comes from an established accessibility company; and HalfAccessible’s free Chrome toolkit (3.50) was first published in September 2023 and so is outside the window; it exports CSV and keeps scan history, but it has no keyboard-order view, no privacy policy and does not name the company or person responsible. The Accessibility Analyzer extension (3.28) was first published in September 2023, so it is outside the window too. Smaller extensions scored lower, and one, Website Accessibility Checker (2.90), has had no update since September 2025. The free checkers from Silktide and Rocket Validator come from established accessibility-testing companies, so they do not qualify; the ACE extension from AccessibilityChecker.org (3.45) and the A11y Quick Check extension (3.33) have no first-release date we could find; and EqualWeb’s checker claims a W3C recognition that W3C does not give. Our adverse search covered news, court records, regulator actions, company registers and security advisories for each maker. Beyond the security fixes and the BrowserStack report noted above, it found nothing that changed these conclusions; a search that finds nothing is not proof that nothing exists. Terence Eden, April 5, 2026, W3C tools list disclaimer
| Tool | Public sources | What remains uncertain |
|---|---|---|
| Accessibility Insights for Web | FastPass, Assessment, Quick Assess, telemetry and FAQ pages; GitHub releases and the August 2026 fix; Chrome Web Store listing; UK Department for Education guide. | Which WCAG version each report states; the full telemetry field list; how steady future releases will be. |
| Accessibility Checker by WebYes | Chrome Web Store listing (version 1.2.0, October 27, 2026); product page; Product Hunt launch, September 28, 2026; ExtScope store record; WebYes privacy policy; UK company register entry for Mozilor Limited. | Every feature and data claim is the maker’s; the rules engine; whether the Edge version exists; network behavior, which we did not observe; how steady releases will be. |
| Sa11y | Project site, overview, how-to-use, bookmarklet and developer pages; GitHub repository, releases, security advisories and bookmarklet code; Government of Canada Digital Accessibility Toolkit. | How many sites block the bookmarklet; detection compared with the other tools. |
| WAVE Browser Extensions | Extension, help, AIM score and terms pages; Chrome and Firefox listings with version history; Sparkbox review, April 2021. | Actual network behavior, which we did not observe; current detection compared with the other tools. |
| IBM Equal Access Accessibility Checker | Repository, extension README and September 2026 releases; Chrome and Firefox listings; Sparkbox review, February 2024. | Whether page data reaches IBM’s rule server; current export formats beyond the spreadsheet. |
| Google Lighthouse | Chrome and Edge documentation, scoring and user-flow pages, license and releases through 13.6.0; Sparkbox review, December 2020. | How the version in your browser differs from the latest release; current report wording. |
| Axe DevTools Extension | Extension, plans, documentation, data-collection and free-extension terms pages; Chrome and Firefox listings; Sparkbox review, December 2020. | Pro price; whether the free extension’s analytics can be switched off; how the 2018 terms are applied today. |
None of this establishes how many real problems any tool finds on your pages, or that a page is accessible. Next substantive review is due January 15, 2027, or sooner if a tool’s terms, price or release record changes. No vendor supplied access or payment, and there are no affiliate links. See our methods. Found a changed term or feature? Contact the editors.
Sources and evidence
Sources were checked October 19, 2026 unless another date is given; sources for Accessibility Checker by WebYes, Sa11y and the October 20 newcomer search were checked October 20, 2026; the release, price and store pages of every tool we scored were read again on November 12, 2026. Vendor documentation establishes documented features and terms, not how well they work. Reviews and store figures are attributed observations, not representative samples.
- Scope and context: W3C, selecting web accessibility evaluation tools; FTC final order requiring accessiBe to pay $1 million, April 22, 2025 and case page, matter 2223156.
- Accessibility Insights for Web: overview; downloads; FastPass; Quick Assess; Assessment; telemetry; FAQ; repository and releases; pull request 7802, merged August 19, 2026; CVE-2021-31936; Chrome Web Store; UK Department for Education tool guide.
- Accessibility Checker by WebYes: Chrome Web Store; product page; Product Hunt launch, September 28, 2026; ExtScope store record; WebYes; WebYes privacy policy, updated December 12, 2025; Mozilor Limited, UK company register.
- WAVE: extension; help; item reference; AIM score; terms; Chrome Web Store with version history; Firefox add-on.
- Sa11y: project site; overview; how to use; bookmarklet; props and export setting; repository, releases, security advisories and bookmarklet code; Government of Canada Digital Accessibility Toolkit, modified September 19, 2025.
- IBM Equal Access Accessibility Checker: repository; extension README; releases; Chrome Web Store; Firefox add-on.
- Google Lighthouse: overview, updated June 2, 2025; accessibility scoring, updated October 22, 2025; user-flow modes; license; releases; Microsoft Edge documentation.
- Axe DevTools Extension: extension; plans; extension documentation; export documentation; data collection; free-extension terms, April 4, 2018; Chrome Web Store; Firefox add-on.
- Independent and community evidence: Sparkbox reviews of axe, December 9, 2020, Lighthouse, December 11, 2020, WAVE, April 7, 2021 and IBM, February 14, 2024; WebAIM practitioner survey #3, January 2021; Scott Logic, September 27, 2023; matuzo.at, May 31, 2019.
- Newcomer search and other options, October 20, 2026: W3C evaluation tools list; Firefox Accessibility Inspector; BrowserStack Accessibility Toolkit, BrowserStack plans and Terence Eden, April 5, 2026; HalfAccessible toolkit.
- Newcomer search and prices, November 12, 2026: Chrome Web Store search for accessibility checkers; ExtScope record for HalfAccessible and for Accessibility Analyzer; BarrierBreak A11yInspect plans; AccessibilityChecker.org browser extension; WAVE API pricing; UK Department for Education tools directory.
- AI disclosure: Anthropic, Project Glasswing.
This is a researched comparison, not a product review. Method: evidence standard, editorial picks.