AudioEye alternative: the corrected code, without the overlay
What AudioEye does, what its automatic fixes cannot reach, what happened when it sued a critic in 2023, and what a report with the corrected code delivers instead.
Facts checked on
What AudioEye is
AudioEye is a publicly traded company (Nasdaq: AEYE) that sells an accessibility overlay: a script that applies automatic fixes in the visitor's browser and shows a floating toolbar, plus paid human audits on higher plans.
What AudioEye does not do
- In 2023 AudioEye sued accessibility consultant Adrian Roselli over a blog post criticising its overlay; the suit was withdrawn in January 2024 as part of a settlement. The post is still online.
- It does not change your site's code. The script runs in the visitor's browser; the HTML your developer sees, and a lawsuit cites, stays the same.
- Screen-reader users typically already have their own settings; a second layer of "profiles" can conflict with them.
- It cannot write a description for a product photo it has never seen, or fix a checkout button that the keyboard cannot reach.
- Lawsuit trackers (UsableNet, yearly reports) count hundreds of ADA web lawsuits per year filed against sites that had an overlay installed.
Where it is fair to say it helps
AudioEye's higher plans include human testing and remediation by its own team, which is real work on the code. This page is about the script that most customers install on its own.
What changes with Rampa
- Scans every page that matters (up to 100 per site), on desktop and on a phone, with axe-core in a real Chromium browser.
- Writes the corrected HTML for each failure, tests it in an isolated browser, and gives it to your developer with a copy button. Your code changes; the visitor's browser does not have to.
- Explains every finding twice: for the owner, in plain words, and for the developer, with the WCAG criterion and the fix.
- Gives you the manual half of WCAG as 7 one-minute tests with a pass criterion, and re-scans every week so a new plugin or theme does not undo the work.
Short version
AudioEye changes what the visitor sees. Rampa changes the code. Only one of those survives a demand letter, a re-scan and the next theme update.
Questions people ask
- Does AudioEye protect me from an ADA lawsuit?
- No tool can promise that. What lawyers look for is whether the code fails WCAG and whether you are fixing it. An overlay leaves the code as it was; lawsuit trackers count hundreds of cases per year against sites with an overlay installed.
- Can I keep AudioEye and use Rampa too?
- Yes. Rampa audits the underlying code, not the widget. Many sites remove the widget once the code is fixed because the fixes make it redundant.
- Is Rampa a widget?
- No. Rampa does not add anything to your page. It gives you a report, the corrected code and a public accessibility statement. There is an optional temporary patch that applies only the fixes we verified, element by element, while your developer moves them into the source.
Sources
- Adrian Roselli: "AudioEye Has Dropped Its Suit Against Me" (January 2024) ↗
- Law Office of Lainey Feingold: the case, in context (2023) ↗
- UsableNet: ADA web accessibility lawsuit reports ↗
- Overlay Fact Sheet (accessibility practitioners) ↗
AudioEye is a trademark of its owner. Rampa is not affiliated with it. Statements about third-party products come from the public sources listed above, on the date shown; if something has changed, write to us and we will correct it.