Companies Using AudioEye

We detect AudioEye on 64,975 domains, including Samsung, Weatherford, RWJBH Medical Group. A detection means the technology is present on that domain, which for large organisations is often a single storefront or subdomain rather than a company-wide deployment. Among domains we matched to a company with a resolved industry, the most common is Construction (8.82%).

We detect 64,975 domains running AudioEye across our monthly crawl of live business domains. Company data could be matched for 45,912 of them (70.7%), and every company-size, industry and country breakdown on this page describes that matched subset rather than the full detected base. A further 7,461 domains carried a AudioEye detection previously and no longer do.

AudioEye holds 14.58% of the Accessibility Tools category, ranking #3. This is a share of the domains we detect running a platform in this category — not a share of all websites, and not a share of spending — so it is not directly comparable to figures published on other denominators.

The top alternatives to AudioEye include UserWay (35.57% market share), AccessiBe (21.9% market share), Pojo.me (12.15% market share), Nagich (2.72% market share) — measured as a share of the domains we detect running a platform in this category.

United States leads with 43,719 matched AudioEye domains, followed by Canada (962), Italy (332), United Kingdom (194), Spain (117). These are counts within the 45,912 domains we could match to a company record, not the full detected base.

The most common company size is 1-10 employees, representing 57.84% of the AudioEye domains we could match to a company record and size — a subset of 45,912 matched companies, not of all 64,975 detected domains. This is followed by 11-50 employees (28.82%) and 51-200 employees (7.8%).

Among the AudioEye domains we could match to a company with a known founding date, the largest group was founded in the 2010s (23.13%), followed by the 2000s (19.85%). That matched subset is drawn from 45,912 companies and is not representative of all 64,975 detected domains. This suggests AudioEye is most popular among relatively young companies.

The ideal AudioEye customer is: Company Size: 1-10 employees, Location: United States (95.84%), City: US metros, Houston and Atlanta lead our sample, Founded: 2000-2019, Company Age: ~10-25 years old — based on our analysis of 45,912 enriched companies at TechnologyChecker.io.

AudioEye sells tiered subscriptions priced per website, with entry plans aimed at small sites and higher tiers that add human remediation, audits and legal support. Pricing scales with page volume and how much manual work you want on top of the automated widget. Check audioeye.com for current rates, since published tiers change and partner-resold plans are often priced differently again.

No accessibility product prevents a lawsuit. Courts have declined to accept an overlay widget as an ADA defence, and 3,117 federal website accessibility lawsuits were filed in 2025 regardless of what plaintiffs' targets had installed. AudioEye offers legal support as part of its higher tiers, which helps you respond to a demand letter, but it isn't the same thing as immunity from one.

On its own, no. An overlay patches what it can detect in the rendered page, which covers some contrast, labelling and keyboard issues but not structural problems in your templates, PDFs or custom components. WCAG conformance is a property of the site, not of a script tag. Treat any overlay as a stopgap while the underlying code and content get fixed properly.

In practice AudioEye is a US product: our data shows 95.84% of its enriched customers in the United States, against 0.43% in the United Kingdom, 0.75% in Italy and 0.08% in Germany. The EAA raises obligations for products and services sold in the EU, and a vendor with almost no European base is unlikely to have deep local guidance. Ask about EN 301 549 specifically before signing.

Yes. AudioEye ships a WordPress plugin and the widget itself is a single script tag, so it drops into any theme. In our crawl, WordPress appears on 13.08% of AudioEye domains, which is lower than you might expect for a small-business product. The bigger CMS signal in our data is Duda at 44.99%, a sign that much of this base came in through a builder partnership.

Our co-occurrence data points strongly at Duda, which appears on 44.99% of AudioEye domains. That is far above what a random small-business base would produce, and it suggests the widget reaches many sites through the builder or an agency reselling it rather than through a direct purchase. Shopify shows up on only 1.14% of AudioEye sites, so ecommerce is a small slice here.

accessiBe is bigger, at 97,609 domains and 21.9% category share against AudioEye's 64,975 and 14.58%, and it grew faster in our June to August 2026 window. AudioEye leans harder on human remediation and legal support. Note that accessiBe paid $1M to settle FTC allegations that it misrepresented its AI overlay, with the final order in April 2025.

UserWay leads the category at 158,526 domains and 35.57% share, more than double AudioEye's footprint, and it was acquired by Level Access for $98.7M in a deal announced in December 2023. AudioEye is the more US-concentrated of the two. Direct switching between them is minor: our crawl recorded 97 domains moving to UserWay and 53 coming back since March 2026.

Whatever the widget was patching at runtime stops being patched, and your underlying markup is exposed as it always was. Plenty of sites accept that trade. Since March 2026 our crawl watched 7,461 domains drop AudioEye, and 96.6% of them installed no replacement at all, which tells you most removals are a decision about the whole product class.

It adds a third-party script that has to load, parse and then walk the DOM before it can apply fixes, so there is a real cost, mostly to interaction responsiveness rather than to first paint. The effect is larger on pages that already carry heavy tag loads. Measure it yourself with field data before and after, rather than trusting any vendor benchmark.

The counts it publishes are widely quoted and broadly consistent with other tallies, including the 3,117 federal website accessibility lawsuits filed in 2025. Read it as advocacy as well as research, though. AudioEye sells against that risk and has sued a rival for patent infringement, so it is an interested party in both the numbers and the conclusions drawn from them.

AudioEye brought a patent infringement action against accessiBe, the second-largest vendor in this category. The two sell competing automated overlays, so the dispute matters commercially as well as legally. For buyers the practical takeaway is narrow: litigation between vendors says nothing about whether either widget makes your site usable for someone relying on a screen reader.

No. Automated tooling reliably catches a minority of WCAG failure types, and the rest need a human testing with assistive technology against real user tasks. AudioEye's upper tiers include human remediation work precisely because the automation alone doesn't get there. If a vendor tells you scanning plus a widget equals conformance, treat that claim as the marketing it is.

It depends on why you're buying, though our data shows 57.38% of AudioEye customers have ten employees or fewer, so the fit is real, and for a five-person firm facing a demand letter the legal support alone can justify it. If you want actual conformance, budget for template fixes too, because the widget won't reach your underlying code.

We fetch and render pages during our monthly crawl of 29.9M active domains and match the script and network signatures AudioEye's widget leaves behind. That gives us 64,975 current detections plus a history of which domains dropped it and when. Because the widget is client-side, it is easier to detect than a server-side dependency, which makes this category unusually well covered.