AudioEye Study Finds AI Coding Tools Do Not Write Accessible Code
AudioEye (AEYE) published research testing AI-generated websites for accessibility and a survey examining business confidence in AI-written code.
Sentiment and the balance of points
Rhea-AI Sentiment reads the wording of the document, how positive or negative its language is on a 1 to 5 scale. The balance of points shown with the takes weighs what the document actually discloses, so the two can disagree, for example when a trial that missed its main goal is described in upbeat language.
Rhea-AI Summary
AudioEye (AEYE) published research testing AI-generated websites for accessibility and a survey examining business confidence in AI-written code.
Five AI coding tools each built three websites using a brief requiring WCAG 2.2 AA, a web accessibility standard. Testing found 306 distinct accessibility issues, appearing more than 59,000 times across the 15 sites; 91% were rated medium or high severity. The generated sites averaged 55 issues per page, compared with 62 in AudioEye's 2026 Digital Accessibility Index. In the survey, 81% expressed confidence that AI-generated code met accessibility standards, while 73% reported increased accessibility issues and complaints since adopting AI.
News Explained
The survey adds a legal-claim measure: almost half of respondents had received a demand letter or lawsuit, and
Key Figures
- Websites tested
- 15 websites
- Five AI tools tested across three website types
- Distinct accessibility issues
- 306 issues
- Found across the tested websites
- Medium- or high-severity issues
- 91%
- Share of issues identified
- Issues per page
- 55 vs. 62 issues
- LLM-coded sites vs. the typical website in AudioEye's 2026 Digital Accessibility Index
- Confidence in AI-generated code
- 81%
- Survey respondents confident their site's code meets accessibility standards
- Reported accessibility issues and complaints
- 73%
- Survey respondents reporting an increase since adopting AI
- Demand letter or lawsuit
- 46%
- Survey respondents who had received one
- AI tools used on complained-about pages
- 71%
- Respondents who received a demand letter or lawsuit
Previous AI Reports
-
Index reported 62 accessibility issues per page, the benchmark cited in the current study.
24h Move is the share-price change in the day after each event; other market factors may also have contributed.
Key Terms
wcag 2.2 aa technical
llm technical
AI-generated analysis. How Rhea-AI works. Not financial advice.

AI coding tools build inaccessible sites with high-severity issues
AudioEye gave five AI tools, including OpenAI, Anthropic, Google, xAI, and Lovable, the same brief: build a news and media site, an online store, and a financial services site that meet WCAG 2.2 AA requirements, the global standard for accessibility compliance.
Testing across the 15 sites found 306 distinct accessibility issues, appearing more than 59,000 times across the pages. A single mistake in a navigation menu or form field repeats on every page that uses it. Of the issues found,
The LLM-coded sites averaged 55 issues per page, while the typical website in AudioEye's 2026 Digital Accessibility Index averaged 62. Asking an AI tool to build an accessible site made little difference; their pages were still nearly as inaccessible as the average website today.
AI did not hallucinate these failures. It has been trained on an inaccessible web, and it writes inaccessible code as fast as teams can ship it.
The Trust Gap: Teams are confident in AI-generated code even as complaints climb
AudioEye also surveyed developers and business leaders on how much they trust AI-written code. The results show a gap between what they believe and what they are experiencing. While
Almost half (
What this means for teams building with AI
None of this means AI and accessibility are incompatible. It means a tool trained on inaccessible web content cannot judge or fix its own accessibility. Organizations relying on LLMs alone for accessibility are accumulating legal exposure with every page they ship.
"AI is producing code faster than ever, and it's clear there is a false sense of security that AI tools write accessible, compliant code," said Kelly Georgevich, CEO of AudioEye. "AudioEye Intelligence, our proprietary dataset, is built on more than one million human reviews, billions of interactions, and years of testing with assistive technology. We have paired this intelligence with the latest in generative AI, allowing customers to ship accessible code at scale."
Methodology
AudioEye asked five AI tools (OpenAI, Anthropic, Google, xAI, and Lovable) to each build three websites that followed WCAG 2.2 AA standards. AudioEye then scanned and tested the resulting 15 websites for accessibility issues like keyboard focus, dialog handling, form error announcements, and screen reader output. Each issue was then rated high, medium, or low severity based on impact to the end user and legal risk.
About AudioEye
AudioEye exists to ensure the digital future we build is accessible for people with disabilities and AI agents. AudioEye's comprehensive solution for over 129,000 customers combines industry-leading AI automation technology with expert fixes informed by the disability community. This powerful combination delivers industry-leading protection against lawsuits and readiness for AI agents. With 25 US patents, AudioEye's solution includes 24/7 accessibility monitoring, automated WCAG issue testing and fixes, expert testing, developer tools, and legal protection, empowering organizations to confidently create accessible digital experiences for all.
Media Contact
Aulani Capuchin
aulani.capuchin@audioeye.com
Investor Contact
Tom Colton
Gateway Group, Inc.
AEYE@gateway-grp.com
949-574-3860
View original content to download multimedia:https://www.prnewswire.com/news-releases/audioeye-study-finds-ai-coding-tools-do-not-write-accessible-code-302893917.html
SOURCE AudioEye, Inc.
FAQ
AI-generated questions and answers. How Rhea-AI works. Not financial advice.
How did AudioEye test AI-generated websites for accessibility?
AudioEye asked five AI tools to each build a news and media site, an online store and a financial services site meeting WCAG 2.2 AA standards. It scanned and tested the resulting websites for keyboard focus, dialog handling, form error announcements and screen reader output, then rated issues by severity.