Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

BAAT review

Free#159 of 163 in Accessibility Testing Software

A focused browser-based axe-core checker for automated website scans.

3.0/10Editor score
BAAT3.0 Visit BAAT

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

BAAT is an open-source accessibility testing tool for organizations developing accessible websites, with a practical focus on developers who want automated checks in the browser. It runs as a bookmarklet or userscript and uses axe-core to analyze websites, so its workflow stays close to the page being reviewed. Results include short issue descriptions and severity labels, while impact filters help narrow attention to selected findings. The result is a compact way to surface reported issues during development.

Its strongest differentiator is control within a lightweight scan workflow. Teams can use custom axe-core rulesets, switch on developer mode for detailed test output, and filter issues by impact. That combination gives developers more control than a fixed list of browser findings, while keeping the product focused on automated website checks. The open-source model also suits teams that want a browser-based checker without an additional software installation or browser plug-in.

BAAT is narrower than an accessibility program that combines automated scanning with manual review, remediation guidance, CI/CD workflows, or a broad integration layer. Its listed ecosystem connection is axe-core, and its platform is the web; there is no browser extension. Choose BAAT when browser-based, scan-focused checks and customizable axe-core analysis match the workflow. Choose another product when the team needs manual assessment, integrated remediation, pipeline automation, or wider platform coverage.

BAAT pros and cons

  • Where it wins
    • Custom axe-core rulesets and issue-impact filters
    • Developer mode provides detailed test output
    • Bookmarklet or userscript runs automated website checks in-browser
  • Where it doesn't
    • Browser-only workflow does not cover broader platform testing
    • No manual review or remediation workflow is included
    • No CI/CD workflow or broader integrations beyond axe-core

BAAT fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update