Skip to main content
Accessibility.build
All Posts
AI & AccessibilityOpinion

AI Promised to Fix Accessibility. It Didn’t.

AI accelerates accessibility work, but it does not automate compliance. A measured look at what broke, what regulators said, and what actually works.

AT

The Accessibility.build Team

June 10, 2026·6 min read
AI & Accessibility

Through 2025 and 2026, a gap widened between what AI-powered accessibility remediation tools claimed and what they actually delivered. The promise was automatic compliance; the reality was broken screen-reader experiences and unreliable machine-written alt text. This is not an argument against AI — AI genuinely accelerates expert work. It is an argument against the specific claim that AI can make a website compliant on its own.

Regulators pushed back on the marketing

The clearest signal came from regulators. In April 2025, the Federal Trade Commission finalized a $1 million order against accessiBe, barring it from claiming that its automated product can make any site WCAG compliant. When a federal regulator draws a line under "AI makes your site compliant" marketing, it is worth taking seriously.

The order is narrow in one sense — it names a single company — but broad in what it establishes: the specific promise that an automated product can, by itself, deliver WCAG compliance is one a regulator was willing to challenge and penalize. Any vendor making the same claim now does so knowing that line exists.

Where the automation broke

Two concrete failure modes stood out.

  • AI-driven overlays broke screen-reader compatibility: users of JAWS and NVDA reported overlay scripts intercepting keyboard commands, re-reading page elements out of order, or hiding content their assistive technology had already handled correctly.
  • AI-generated alt text proved unreliable at scale: automation can detect whether an image has alt text, but not whether that alt text is meaningful to a human. Presence is measurable; usefulness is not — at least not without a person in the loop.

Both failures share a root cause. Accessibility is ultimately about whether a real person can use a page, and that is a judgment automated checks cannot fully make. The overlay case is especially telling: a script inserted to improve accessibility actively degraded it for the exact users — JAWS and NVDA users — it claimed to serve, by fighting the assistive technology instead of cooperating with it. The alt-text case is quieter but just as consequential, because a page can pass an automated "does every image have alt text?" check while remaining opaque to a blind user reading descriptions that are technically present and practically useless.

What actually works: augmentation, not automation

The credible, evidence-supported role for AI is augmentation, not automation. In that model, AI does what it is genuinely good at, and people do the rest:

  • AI flags likely violations at scale, far faster than a human could review a large site by hand.
  • AI drafts alt text as a starting point.
  • Human experts then confirm, prioritize, and fix — deciding what a violation means in context and whether a description is actually useful.

Claims of full automation, of replacing manual audits, or of automatic compliance are not supported by evidence. Claims that AI accelerates expert work are. The distinction is not rhetorical: it changes what you buy, how you staff, and where accountability sits. In an augmentation model, the AI is a force multiplier for a person who remains responsible for the outcome. In an automation model, responsibility is quietly handed to a system that, as JAWS and NVDA users learned, can make things worse while reporting success.

How to tell a real tool from hype

You can usually separate a credible tool from a marketing claim before you buy, using a few simple checks. Honest accessibility tooling tends to share these traits:

  • It describes augmentation, not automation: the pitch is "we help your team work faster," not "we make your site compliant."
  • It keeps a human in the loop: AI output is treated as a draft an expert reviews, not a fix that ships unseen.
  • It does not fight assistive technology: a script that intercepts keyboard input or overrides what JAWS and NVDA already do is a red flag, not a feature.
  • It is honest about limits: automated testing can only catch a portion of WCAG issues — the rest require human judgment — and a trustworthy vendor says so plainly.
  • It never promises legal immunity: no widget or subscription makes an ADA lawsuit disappear, and the FTC’s $1 million order against accessiBe shows regulators will challenge "automatic compliance" claims.

If a product cannot survive those five questions, its "AI-powered compliance" is marketing, not engineering.

Why it matters for you

If you are choosing a tool, judge it by the claim it makes. A tool that says "we help our experts work faster" is describing something real. A tool that says "we make your site compliant automatically" is describing something that broke for JAWS and NVDA users and drew a $1 million FTC order. Use AI to move faster; keep a human accountable for the result.

None of this is a case against AI. Used well, it genuinely accelerates expert work: it can triage a large site in a fraction of the time a manual pass would take, surface the issues most likely to matter, and hand a person a running start on descriptions and fixes. The failure was never the technology itself — it was the promise wrapped around it. Treat AI as the fast first pass and a person as the final word, and you get the speed without inheriting the failures that made 2025 and 2026 such a cautionary tale.

  • See where each approach fits in our guide to automated vs manual accessibility testing.
  • Understand the widgets behind many of these failures in our guide to accessibility overlays.
  • Use AI the right way — as a drafting aid — with our alt text generator, then review every result.
  • And put a human in the loop with our guide on how to audit website accessibility.

Sources

  • Tranistics
  • AudioEye
  • Think Design

Enjoyed this article?

Share it with others who care about accessibility.

Written by

AT

The Accessibility.build Team

The Accessibility.build team publishes practical guides, tools, and research on web accessibility, WCAG compliance, and inclusive design.

Essential Accessibility Resources

Comprehensive tools, checklists, and guides to help you create inclusive digital experiences

Top Pick

WCAG 1.4.13 Content on Hover or Focus Guide

Complete guide to accessible tooltips and hover menus — the Dismissible, Hoverable, and Persistent conditions, why the title attribute fails, aria-describedby, copy-ready code, and testing
accessible tooltip
tooltip accessibility
aria-describedby tooltip
+10 more
View guide
Top Pick

WCAG 2.5.7 Dragging Movements Guide

Complete guide to providing a single-pointer alternative to every drag action — accessible patterns for sliders, sortable lists, kanban boards and maps, the two exceptions, code examples, and testing
motor disability
touch accessibility
drag and drop accessibility
+10 more
View guide
Top Pick

WCAG 3.2.6 Consistent Help Guide

Complete guide to keeping help mechanisms in the same relative order across pages — the four covered help types, contact and chat placement, code examples, common mistakes, and testing
help mechanism accessibility
contact information accessibility
chat widget accessibility
+9 more
View guide
accessibility.build© 2026