EqualWeb fixes in the browser DOM. TrustScans helps you fix the files.

EqualWeb says “You add one line of JavaScript to your site’s <head> section,” and that the widget “applies fixes in real time through the browser DOM, so your original source files are never modified” [Source: EqualWeb, widget]. It describes “an AI accessibility menu that remediates 80+ WCAG 2.2 issues in real time” [Source: EqualWeb, widget].

EqualWeb also states that “An accessibility widget alone does not on its own make a website ADA compliant” [Source: EqualWeb, widget]. Widget plans start at $39 a month for sites of up to 100 pages [Source: EqualWeb, pricing].

Its testing products include a Monitor with “Continuous WCAG 2.2 scanning with a 0-100 compliance score, lawsuit-risk rating, and developer-ready reports,” and a Crawler, a Chrome extension that can include password-protected pages [Source: EqualWeb, testing]. For litigation, EqualWeb says it “provides documentation - not legal advice or representation” [Source: EqualWeb, litigation].

EqualWeb’s Monitor is a scanner with a score and developer reports [Source: EqualWeb, testing], which is close to what TrustScans does. We agree with EqualWeb that a widget alone does not make a site compliant [Source: EqualWeb, widget].

EqualWeb’s Crawler can scan password-protected pages [Source: EqualWeb, testing]. TrustScans scans public pages only today, so if you need logged-in areas tested, that is a real difference in EqualWeb’s favour.

1. 01

   Nothing is installed on your site

   TrustScans loads your public pages in a real browser from the outside, the way a visitor would. There is no snippet, no toolbar and no change to what your visitors receive. Your site changes only when your team changes it.

2. 02

   Fixes happen in your code, where they reach everyone

   Every finding comes with plain-language guidance on why it matters and how to fix it, written for each rule we test. A fix in the source reaches every visitor, whatever browser or assistive technology they use.

3. 03

   Context, not just a verdict

   Each finding names the WCAG success criterion, the pages it appears on, the element’s selector and HTML, and a highlighted screenshot for the first occurrences on each page. When the same markup fails on three or more pages we flag it as a likely shared component, so one fix can clear them all.

4. 04

   A score you can explain to anyone

   The score counts confirmed WCAG failures only, and the method is explained in the app and in the PDF report. Items that need a person to judge, and best-practice recommendations, are kept in their own lists and never move the number.

5. 05

   Honest about what automation can find

   We never tell you a scan makes a site compliant. The W3C’s guidance is that evaluation tools “can not determine accessibility, they can only assist in doing so” [Source: W3C WAI]. Our reports say what failed, what needs a human, and what we could not test.

6. 06

   Built for the people doing the fixing

   Recurring scans, regression alerts on every plan, remediation progress, report views for executives, managers and developers, PDF and CSV exports, and an API and MCP server that lets a coding agent work through the queue. Marking an issue resolved never changes the score; only a new scan does.

EqualWeb’s widget leaves your source files unmodified by design [Source: EqualWeb, widget]. That is the distinction independent groups draw: the European Disability Forum and the International Association of Accessibility Professionals say overlays “do not make the website accessible or compliant with European accessibility legislation” and are not “a substitute for fixing the website itself” [Source: EDF and IAAP, 2023].

The Overlay Fact Sheet lists EqualWeb among its examples of overlays [Source: Overlay Fact Sheet]. UsableNet, which sells accessibility services and tracks lawsuits, reports that widgets “typically do not resolve underlying code-level accessibility issues” [Source: UsableNet, 2025 report].

Why TrustScans doesn’t build an overlay→