🤖
Technical · January 30, 2026 · 6 min read · Updated June 8, 2026
Why AI-generated accessibility fixes beat automated patches
Overlay widgets promise magic JS fixes. Real fixes need context. Here's why LLM-generated code patches work where overlays fail.
Accessibility overlays, tools like accessiBe and UserWay, inject JavaScript at runtime to "fix" WCAG violations without changing your source code. They don't deliver: in a WebAIM survey, 72% of disabled users rated overlays ineffective. In January 2025 the US FTC settled with accessiBe for $1 million over deceptive claims of automatic WCAG compliance, and sites running overlay widgets recur in US accessibility lawsuits, hundreds of cases a year.
The alternative used to be boring: hire a consultant, wait six weeks, get a PDF of violations with no code. Now LLMs close that gap. A modern LLM can read a violation's ARIA context, the surrounding HTML, and the impact description, and emit a precise code patch, including explaining to a junior dev why the change matters.
Axively runs every violation through the AI with grounded prompts and ships the diff alongside the report. You still own the fix; you just skip the blank-page problem.