An AudioEye alternative, or a way to check it

AudioEye installs a JavaScript snippet. It shows an accessibility toolbar to visitors and applies automated fixes to the page as it loads, and higher tiers add people who remediate issues for you. The toolbar is the same kind of widget as accessiBe and UserWay.

Fixes applied by a script live in that script. They are not in your templates, so a redesign, a theme change or cancelling the subscription takes them away. The Overlay Fact Sheet, signed by hundreds of accessibility practitioners, recommends against relying on this approach, and sites using overlays still show up in accessibility lawsuits.

This scan changes nothing on your site. It renders the page in a real browser, runs axe-core against WCAG 2.2 A and AA, and lists every failing element with its success criterion. The result is a link you can keep.

Because it renders JavaScript, a scan of a page with the AudioEye script running measures what visitors get with the fixes applied. Scan once before the vendor starts and again after, then compare the two runs. If a "fixed" issue is still in the list, you have the element to point at.

Alt text, form labels, contrast and heading structure belong in your markup and your design tokens. Find them with a scan, fix them in the code, and re-scan to confirm. If you want this to stay fixed without a subscription, the GitHub Action fails a pull request that brings an issue back.