Vendors · Overlay widgets
A Widget With People Behind It, Up to a Point
AudioEye puts human testers behind the automation, and by its own account those testers are people with disabilities. What you actually receive still depends entirely on which tier you bought.
Last reviewed August 30, 2026
What it is
AudioEye is a company listed on Nasdaq that sells automated remediation together with human work. The automation installs as JavaScript, evaluates your page, and applies fixes as it loads. The human half is testing and remediation carried out by its own people, and it arrives only at the tiers that include it.
There are three tiers and the differences between them are the whole story. The lowest is monitoring plus automated fixes, and the company's own pricing page says it does not include expert testing for the remaining issues. The middle tier is sold on guiding your team to fix at source, with developer tools and integrations into ticketing systems and test suites. The top tier is sold on managing accessibility for you, with fixes written by AudioEye's developers.
No prices are published anywhere. You get a number by talking to them, which means any comparison against a product with a published price is not comparing like with like.
What it does well
- Expert audits are run by certified professionals alongside what the company calls its A11iance Team, described as a group of people with disabilities testing with a range of assistive technology, input devices, and browsers. That is the same argument we make for our own method, and it is a real difference from a product that ships automation alone.
- Those audits reach pages behind a login or a paywall. Our free scan cannot, because it has no credentials and no session, and that is usually where the transactions live. Scanners that take a login do exist, so this is a limit of the free tool rather than a law of nature, and the point stands either way: somebody has to be given an account before the checkout gets tested.
- When their developers write a custom fix, the page is retested by members of the disability community before anyone calls it done. Very few firms describe a validation loop that specific, and ours does not say it that plainly either.
- Monitoring runs continuously rather than on a schedule, so a change that breaks something gets noticed instead of waiting for the next crawl.
What it cannot do
- The automated layer has the ceiling every automated layer has. It cannot decide whether alt text is accurate or whether a purchase flow works by ear, and no volume of scanning turns into that judgment.
- Managed custom fixes are added to your automated fixes layer, which is AudioEye's script, rather than committed to your repository. Your own HTML never changes, so if the subscription ends the fix leaves with it. The middle tier is the opposite proposition and is sold on fixing at source, which is why the tier you bought tells you more than the logo in the footer does.
- Knowing that a site runs AudioEye tells you almost nothing. It does not tell you which plan, whether a person ever looked, or which pages and flows they looked at.
- The company's headline figures, roughly half of detected issues fixed automatically and roughly 97 percent resolved before your developers get involved, are its own measurements of its own product. Read them as claims with a name attached, not as findings.
- AudioEye Assurance appears at the top tier, and what the public page gives you is a short summary rather than the terms. The detail sits in the order you sign, and it will carry eligibility conditions, exclusions and obligations of yours. If legal protection is part of why you are buying, ask for that document and read it before you sign, because vendor assistance and an indemnity are not the same purchase.
The documented record
None of this comes from us. Each item links to its source below.
The National Federation of the Blind's 2021 resolution on overlays names AudioEye in its first clause, among six vendors. What it condemns is how the category is marketed rather than the idea that software can help at all, and its conclusion is calibrated. Overlays may help make certain parts of a website accessible without sight, and they alone cannot guarantee full nonvisual access to every website where they are deployed.
NFB: the 2021 resolutions, including 2021-04 on overlaysUsableNet's tracker counted 4,928 web accessibility lawsuits filed in 2025, across federal courts plus the New York and California state courts. It also counts, every month, how many of the defendants were running a third-party accessibility control at the time, and in July 2026 that was 113 of 401 filings. So a widget on the page is not a bar to being sued. That is a count of filings rather than a measure of anyone's risk, it says nothing about who wins, and none of it is broken out by vendor, so none of it attaches to AudioEye in particular.
UsableNet: the ADA digital accessibility lawsuit tracker and its yearly reportsAudioEye's own account of how a custom fix gets made describes the stage where its developers find issues the automation, in the company's words, "cannot or will not fix". Four words, written by the vendor, conceding the ceiling of its own product. That is worth more than any critic saying the same thing at length.
AudioEye: how managed custom fixes are written and where they liveA December 2021 settlement in a case against somebody else named this company in writing. ADP had been using an AudioEye overlay and was sued by blind employees. The agreement records that for its purposes, overlay solutions such as those currently provided by companies such as AudioEye and accessiBe will not suffice to achieve accessibility. That is negotiated language rather than a judge's finding, and it binds nobody outside that case. It is still two vendors named in a signed settlement, and this is one of them.
Law Office of Lainey Feingold: the overlay legal update, carrying the ADP settlement languageIn April 2022 AudioEye sent a cease and desist letter to Adrian Roselli, an accessibility expert who had contributed to the Overlay Factsheet. He published the letter along with his reply, which argued that threatening genuine criticism with expensive legal action is not in the interests of the people both sides say they want to help. No lawsuit followed. We put it here because a page that ends up recommending a product should say when its maker has used lawyers on somebody for writing about it, and because it is the fact on this page that argues hardest against our own verdict below.
Adrian Roselli: the cease and desist letter he received from AudioEye, and his reply
Our read
AudioEye is the most defensible product in this category, and the reason is straightforward. It admits automation is not enough and puts people behind it, including people who use assistive technology every day rather than for an afternoon.
Fixes that live in a vendor's runtime layer instead of your codebase are rented rather than owned. For a business with no developers, renting is a reasonable trade and we would say so. For a company with an engineering team, it is a lease on something you could have built into your own repository instead. We are not going to tell you which costs less, because AudioEye publishes no prices and our audit fee buys a report rather than the repair work, so the two are not the same purchase and anyone comparing them needs two real quotes.
So the questions before you sign are narrow and answerable. Which pages and which flows get human testing. What AudioEye Assurance actually covers. And whether anything at all ends up in your own repository, where it will still be there next year.
What we would do instead
Sources
- NFB: the 2021 resolutions, including 2021-04 on overlays
- UsableNet: the ADA digital accessibility lawsuit tracker and its yearly reports
- AudioEye: plans and pricing, and what each tier includes
- AudioEye: how managed custom fixes are written and where they live
- AudioEye: expert accessibility audits and the A11iance Team
- Law Office of Lainey Feingold: the overlay legal update, carrying the ADP settlement language
- Adrian Roselli: the cease and desist letter he received from AudioEye, and his reply
We have no commercial relationship with any company named on this page, and no affiliate arrangements. We sell audits, so we compete with some of them, and you should weigh what we say accordingly. Nothing here is legal advice. Product names and trademarks belong to their owners.
Other vendors
Whatever you are running, find out where you stand.
The free scan checks 10 pages in a real browser and reports what your markup actually contains. No widget, no subscription, no signup.