Checked
2026-11-15
/ Overlay or audit

Accessibility overlay vs audit: what each does, costs and leaves undone

An overlay is a script that adjusts your pages in each visitor's browser for a yearly fee, with published plans from $490 a year. An audit is a one-off list of what is broken in the pages themselves, by WCAG criterion, and it fixes nothing until someone works through it. If the page has to hold up when a person tests it, you need the audit and the fixes; ours costs $139 for up to 25 pages. If you need something on every page this afternoon and accept its limits, that is what an overlay is for.

/ Compared

Overlay and audit, side by side

An accessibility overlay compared with an accessibility audit
Compared onOverlayAudit
What it isA script from a vendor, loaded on every page. It edits the page in the visitor's browser and adds a panel for text size, contrast and spacing.A review of a set of pages against WCAG that ends in a list of failures, each with its criterion, a severity and a fix.
What it changesWhat the browser shows after the script has run. The HTML your server sends stays as it was.Nothing by itself. It tells whoever fixes the site what to change in templates, components and content.
Time to startMinutes: paste a snippet or install a plugin.A one-off order. The report is the start of the work, not the end.
Published priceaccessiBe from $490 a year (up to 5,000 visits a month). UserWay from $490 a year (up to 100K page views a month). AudioEye publishes none.Ours is $139 once, for up to 25 pages. accessiBe and UserWay price their audits on request.
BillingRecurring, for as long as the script runs.Once. A re-audit after a redesign is a new order.
Third-party pagesNot covered unless the other domain runs the same script: a payment page, a booking engine.Covered if you put them in scope, but the fix belongs to the third party.
PDFs and videoOut of a page script's reach. accessiBe lists documents and media among its excluded issues.Listed as findings if in scope. Fixing a PDF is separate work.
After you stop payingThe script is gone and the page is what your server always sent.The fixes made from the report stay in your code.
  • What it is

    Overlay
    A script from a vendor, loaded on every page. It edits the page in the visitor's browser and adds a panel for text size, contrast and spacing.
    Audit
    A review of a set of pages against WCAG that ends in a list of failures, each with its criterion, a severity and a fix.
  • What it changes

    Overlay
    What the browser shows after the script has run. The HTML your server sends stays as it was.
    Audit
    Nothing by itself. It tells whoever fixes the site what to change in templates, components and content.
  • Time to start

    Overlay
    Minutes: paste a snippet or install a plugin.
    Audit
    A one-off order. The report is the start of the work, not the end.
  • Published price

    Overlay
    accessiBe from $490 a year (up to 5,000 visits a month). UserWay from $490 a year (up to 100K page views a month). AudioEye publishes none.
    Audit
    Ours is $139 once, for up to 25 pages. accessiBe and UserWay price their audits on request.
  • Billing

    Overlay
    Recurring, for as long as the script runs.
    Audit
    Once. A re-audit after a redesign is a new order.
  • Third-party pages

    Overlay
    Not covered unless the other domain runs the same script: a payment page, a booking engine.
    Audit
    Covered if you put them in scope, but the fix belongs to the third party.
  • PDFs and video

    Overlay
    Out of a page script's reach. accessiBe lists documents and media among its excluded issues.
    Audit
    Listed as findings if in scope. Fixing a PDF is separate work.
  • After you stop paying

    Overlay
    The script is gone and the page is what your server always sent.
    Audit
    The fixes made from the report stay in your code.

Their side was read on their own pages on . Our price comes from our live price list.

/ Which one

Who should pick which

An overlay fits if

  • You need something on every page today and nobody can touch the code this quarter.
  • You want the visitor panel: bigger text, contrast, spacing, paused animation.
  • The site has thousands of pages and little traffic, so a traffic-based plan costs less than auditing a sample.
  • You want the litigation support or the financial guarantee some vendors bundle with their plans. We sell neither.

An audit fits if

  • Somebody will test the page as your server sends it: a procurement team, an auditor, a claimant's expert.
  • You have a developer or an agency who can work through a list.
  • Checkout, booking or sign-up runs through forms and custom components, where a wrong guess by a script costs a sale.
  • You would rather pay once for a fix that stays than every year for one that ends with the subscription.

What an overlay does, in the vendors' own words

The three best-known products describe themselves in similar terms. accessiBe's pricing page lists "Ongoing scans & fixes every 24 hrs" and an "Accessibility widget for design & UI adjustments". UserWay's widget page promises "a full suite of 100+ AI-powered accessibility tools". AudioEye's plans page puts a number on the automated part: "Automated tools addressing ~50% accessibility issues", with a note that its basic plan "does not include expert testing for remaining issues".

All three install the same way, as a script. The browser downloads your page, then the vendor's file, and the script edits the page in that browser. A screen reader reads what the browser has built, so a visitor whose browser ran the script may get the edited version. A tester reading the source, a visitor who blocks third-party scripts and any page on another domain get the original.

That is a real service with real limits. It is fast, it needs no developer, and the display panel helps some visitors. It cannot reach a PDF or a video, it has to guess where judgement is needed (is this alt text accurate, does this menu make sense with a keyboard), and it leaves the code as it was.

What an audit does

An audit looks at a defined set of pages and records each failure against the WCAG success criterion it breaks. A good one tells you where the failure is, how serious it is and what change fixes it, so the report can be handed straight to whoever maintains the site.

An audit fixes nothing. That is its weakness and it should be said plainly: a report that nobody works through leaves the site exactly where it was, and it is out of date after the next redesign. It also covers a sample. Ours is up to 25 pages, which is enough for a small site's templates and key journeys and not enough for a large one.

What you buy is knowledge that survives: where the templates fail, in a form a developer can act on. A fix made in a template repairs every page built from it, for every visitor, with or without any script.

What each costs

Overlay prices are public for two of the three vendors, read on 15 November 2026. accessiBe's accessWidget runs from $490 a year (Micro, up to 5,000 visits a month) to $3,990 a year (Scale, up to 100,000), with a custom price above that. UserWay's widget plans run from $490 a year (Pro) to $2,490 a year (Ultimate) for sites with up to 100K page views a month. AudioEye shows three plans and no prices.

Audit prices are mostly not public. accessiBe sells audits under "Get A Quote" and UserWay under "Talk to us". Ours is $139, paid once, for up to 25 pages against WCAG 2.1 AA.

The two are not the same kind of cost. The overlay is rent: it recurs for as long as the script runs. The audit is a one-off, but it is followed by the cost of the fixes, which depends on how much is broken. Budget for both halves before you compare the totals.

What the FTC and W3C have said

In April 2025 the US Federal Trade Commission approved a final consent order against accessiBe. In the FTC's words, the order "bars accessiBe from representing that its automated products can make any website WCAG-compliant" or keep it compliant over time "unless it has the evidence to support such claims", and requires the company to pay $1 million. The order binds accessiBe alone, and accessiBe agreed to it without admitting or denying the allegations. It does not ban the product.

W3C's guidance on evaluation tools states the general limit: "Tools cannot check all accessibility aspects automatically. Human judgement is required." That sentence cuts both ways. It limits what an overlay can fix by itself, and it limits what any automated scan, ours included, can find. It is the reason an audit involves a person.

Do you need both?

They are not exclusive. Nothing about an audit requires removing a widget first, and a widget that only offers display preferences may do little harm on a site whose code has been fixed.

If you already run an overlay, do not remove it in a hurry. If it patches a real defect today, such as a missing form label, taking it out before the source is fixed brings the defect back. Fix first, test with the script blocked, then decide whether the widget still earns its subscription.

A sensible order of work

For a small site with no budget surprises:

  1. Run a free scan on your most important page. It shows the failures an automated check can find, before any widget has acted.
  2. If the scan is bad, or someone outside will test the site, order an audit of the templates and journeys that matter.
  3. Have the findings fixed in the code, most severe first.
  4. Put the fixed pages under monitoring, so the next release does not undo the work unnoticed.
  5. Then decide about a widget on its merits, as a display aid for visitors.
/ Our side

What we sell, and what it costs

Free

Scan one page

Give it an address. You get the failures an automated check can find, the WCAG criterion behind each and what fixing them costs.

No account, no card.

One-off

WCAG audit

Up to 25 pages against WCAG 2.1 AA. Every finding is checked by a person and comes with its criterion, a severity and the change that fixes it.

Fixed price $139, paid up front.

Monthly

Accessibility monitoring

Up to 5 pages re-scanned daily or weekly, with an alert when a score drops five points or a new critical barrier appears.

$12 a month, or $29 for 25 pages.

Prices are in USD and come from our live price list. What each service covers is on the audit page and the monitoring page.

/ Questions

Questions people ask

Is an overlay enough to make a site WCAG compliant?
No vendor on this page says its automation does that alone. AudioEye puts its automated tools at about 50% of issues, and the FTC's 2025 order bars accessiBe from claiming its automated products make any website WCAG compliant unless it has the evidence. Whether your pages conform depends on the pages, and only testing shows it.
Is an audit enough?
No. An audit is a list of what is broken. The site changes only when the findings are fixed, and it stays fixed only if somebody keeps checking after each release.
How much does an accessibility audit cost?
Ours costs $139, paid once, for up to 25 pages against WCAG 2.1 AA. On 15 November 2026 accessiBe and UserWay both priced their audits on request.
Which is cheaper, an overlay or an audit?
In the first year they can cost about the same: published overlay plans start at $490 a year, and our audit is $139 before the cost of the fixes. The overlay recurs every year. The audit and its fixes are paid once, until the site is rebuilt.
Can I keep my overlay after an audit?
Yes. The audit works with the widget in place, and a good one tests with the script on and off. Once the source is fixed, the widget is a display aid and you can judge it as one.
/ Sources

Where each statement comes from

Checked against the sources on .

This page explains the rules in general terms. It is not legal advice, and it does not tell you whether a rule applies to your organisation. For that, ask a lawyer who practises in the jurisdiction.