NewAutomated scanners compared: autumn 2026

Independent reviews of web accessibility platforms

We test scanners, monitoring tools, developer tools and overlays the same way, then report how they perform. No sponsorships, no paid rankings.

  • Independent. We don't sell accessibility services or take money from the platforms we review.

  • Evidence-based. Results come from a test site with known issues, not from vendor claims.

  • Written for everyone. Plain-English findings for managers, designers and developers alike.

Every platform is measured against the same standards

  • WCAG 2.2 AA
  • EN 301 549
  • European Accessibility Act
  • Equality Act 2010
  • Public Sector Bodies Regulations
  • WAI-ARIA 1.2

How we test

One method, applied to every platform, so the results can be compared fairly.

  1. Step 1

    Build a site with known problems

    We maintain a realistic test website with 120 documented accessibility issues across WCAG 2.2. Because we know exactly what's broken, we can measure what each platform finds and what it misses.

  2. Step 2

    Run every platform the same way

    Each platform is set up using its default recommended settings and run against the test site. We record every issue it reports, then check each one by hand to separate real finds from false alarms.

  3. Step 3

    Check the results with real assistive technology

    Automated results only tell part of the story. We test the same pages with screen readers, keyboard-only navigation and magnification, so our reviews reflect what disabled people actually experience.

The kinds of platform we review

Accessibility tools do very different jobs. Knowing which type you need is the first step to choosing well.

  • Automated scanners

    Crawl your site and flag issues they can detect from code. Fast and affordable, but they only catch part of the picture.

  • Monitoring platforms

    Scan on a schedule, track issues over time and report on progress. Aimed at teams managing large or busy sites.

  • Developer tools

    Browser extensions, linters and test libraries that catch problems while sites are being built.

  • Design tools

    Plugins for Figma and similar tools that check contrast, structure and annotations before anything is coded.

  • Overlays and widgets

    Scripts that add a toolbar or apply automatic changes to a live site. We test what they change and what they don't.

  • Reporting and statements

    Tools that help produce accessibility statements and compliance reports from your test results.

How we stay impartial

Our reviews are only useful if you can trust them. These are the rules we work to.

  • No paid placements

    Vendors can't pay to be reviewed, ranked or featured. Position in a list is earned in testing.

  • The same test for everyone

    Every platform in a category runs against the same test site, with the same known issues and settings.

  • Independently tested

    Every platform is tested by our own team, not by the vendor, so the results reflect what we found.

  • Corrections in the open

    Vendors and readers can challenge a result. If we get something wrong, we fix it and say so on the page.

Latest reviews and guides

Head-to-head comparisons, in-depth reviews and advice on choosing the right tool.

All articles
  • Deque vs Tenon: Comparing Automated Web Accessibility Testing

    Deque vs Tenon compares a developer-focused, axe-based accessibility platform (Deque) with an API-first automated checker (Tenon). Deque usually suits organisations needing deep integrations and training; Tenon typically fits teams wanting a lightweight, programmatic scanner—both require manual testing to reach WCAG conformance.

  • European Accessibility Act Compliance in France: What You Need to Know

    This article explains how the European Accessibility Act applies in France, what products and services are in scope, which standards to use (for example EN 301 549 and WCAG), and practical steps to comply. It includes a testing checklist, documentation requirements, common mistakes to avoid, and a simple accessibility statement outline.

  • WCAG 2.1.1 Keyboard: How to Test and Improve Keyboard Accessibility

    Step-by-step guidance to test and fix keyboard accessibility for WCAG 2.1.1. Includes a manual test checklist, common failures with direct fixes, patterns for SPAs and modals, and a final sign-off checklist.

Not sure where to start?

Our guide explains what each type of platform can and can't do, and the questions to ask before you buy.