The Accessibility Basics Vibe Coders Miss Before Shipping
Quick Answer
Most AI-built sites are unusable for a real slice of their visitors, because AI tools skip the accessibility basics by default. In the WebAIM Million 2026 report, 95.9% of the top one million home pages failed automatic accessibility checks, with an average of 56 errors each — and the same six mistakes have repeated for seven straight years. The most common is low-contrast text, found on 83.9% of pages, followed by missing image descriptions on 16.2% of images. This is no longer just an inclusion issue: about 4,000 website accessibility lawsuits were filed in the United States in 2024, federal cases jumped 27% in 2025, and roughly 40% of those federal filings came from people representing themselves — many using AI to draft the complaints. A short, no-code check before you launch closes most of that risk in about fifteen minutes.
You built it with Lovable, Bolt, or Cursor. It looks finished. The colors are nice, the buttons work when you click them, and you're ready to share the link. But "looks finished" and "works for everyone" are two very different things.
A real share of your visitors don't use a mouse, can't read low-contrast text, or rely on software that reads the page aloud. For them, the polished site your AI built can be confusing, or completely unusable.
Your AI Built a Site Some People Can't Use
When you ask an AI tool to build a page, it optimizes for what looks right on your screen. It rarely adds the quiet labels and descriptions that people with disabilities depend on — unless you ask for each one, by name.
That gap is everywhere. Across the top million home pages, the most common failure is text that's too faint against its background. The second is images with no description for screen readers. The third is form fields with no label, so someone using a screen reader hears a blank box and has no idea what to type.
These aren't exotic edge cases. They are the basics, and they've topped the list for seven years running in the annual WebAIM Million report.
Why This Is Suddenly a Real Risk
For a long time, accessibility felt optional for small builders. That has changed fast, for three reasons.
First, the lawsuits are climbing. Roughly 4,000 web accessibility cases were filed across U.S. courts in 2024, and federal filings rose 27% in 2025. Restaurants, shops, and small e-commerce brands are the most common targets.
Second, the barrier to suing has collapsed. About 40% of 2025 federal accessibility filings came from people with no lawyer, according to law firm Seyfarth Shaw. Many now use AI tools to find violations and draft the complaint — work that once needed a costly legal retainer. In other words, AI is now helping people sue the kind of sites that AI built.
Third, if you serve customers in Europe, the European Accessibility Act has been in force since June 28, 2025. It expects your digital product to meet a recognized accessibility standard.
Definition
Web accessibility means building your site so people with disabilities can use it — including those who can't see the screen, can't use a mouse, or need text they can actually read. The widely used standard is called WCAG, and the practical target for most sites is its "Level AA."
The 7 Accessibility Basics to Check Before You Ship
You don't need to learn all 86 WCAG rules. At launch, a handful of checks close most of the gap, and none of them require code.
| # | Check | What "good" looks like |
|---|---|---|
| 1 | Run a free scan | A browser tool like the axe extension or Chrome's built-in Lighthouse lists your issues in plain language |
| 2 | Fix color contrast | Text is dark enough against its background that the scanner stops flagging it |
| 3 | Add real image descriptions | Each meaningful image describes what it shows — not the word "image" |
| 4 | Label every field and button | A screen reader announces what each one does |
| 5 | Set page language and titles | Each page declares its language and has a clear, unique title |
| 6 | Try it with the keyboard only | Unplug the mouse and tab through everything — you can reach every button |
| 7 | Listen with a screen reader | Turn on the one built into your phone or laptop and hear your home page |
A free scanner catches roughly 30% of problems on its own. The other 70% are caught by the last two checks — the keyboard test and the listen test — which cost nothing and take a few minutes.
What Most Builders Get Wrong
Two traps catch people who think they've handled it.
The first is the "accessibility widget" — an overlay you paste in that promises instant compliance. They don't deliver it. In the first half of 2025, 456 lawsuits — nearly a quarter of all filings — targeted sites that had an overlay installed.
The second is trusting AI-written image descriptions. AI will happily fill them in, but the result is often so generic it says nothing useful. A screen reader user just hears "image, image, image," which is no better than silence.
We turned the whole thing into a plain-English audit you can run before launch — the exact checks, plus the simple instruction to hand your AI tool to fix each one. Grab it before you ship.
Key Takeaways
- **95.9% of top home pages fail accessibility checks**, averaging 56 errors each, and the same six mistakes have repeated for seven years (WebAIM Million 2026).
- **Low contrast text (83.9% of pages) and missing image descriptions (16.2% of images)** are the most common failures.
- **The legal risk is rising fast** — about 4,000 lawsuits in 2024, federal cases up 27% in 2025, with ~40% filed by self-represented people often using AI.
- **Accessibility overlays don't protect you** — 456 suits in early 2025 targeted sites that had one installed.
- **A free scanner catches only ~30%** — the no-code keyboard and screen-reader checks catch the rest in minutes.
Read Next
- The 10-Step Security Check Before Your AI App Goes Live
- Why Google Ignores AI-Built Sites and How to Get Indexed
- Why AI-Built Sites Feel Slow and How to Fix It Before Launch
- The Best AI Coding Tool for People Who Can't Code
- 5 AI Agents That Actually Run Your Business (Not Just Chat)
Frequently Asked Questions
Do I really need to worry about accessibility for a small AI-built site?
Yes, and small sites may be more exposed, not less. About 4,000 website accessibility lawsuits were filed across U.S. courts in 2024, and federal filings rose 27% in 2025. Roughly 40% of 2025 federal cases were filed by people with no lawyer, per Seyfarth Shaw, and many now use AI tools to find violations and write the complaint. That collapse in cost means small, undefended sites — exactly the kind built quickly with AI tools — are easy targets. Beyond the legal risk, a real share of your visitors simply can't use a site that ignores the basics, so you lose customers either way.
What is WCAG and which level do I need?
WCAG stands for the Web Content Accessibility Guidelines, the standard that most accessibility laws point to. The current version, WCAG 2.2, was released in October 2023 and has 86 individual checks split into three levels: A, AA, and AAA. You do not need all 86. The practical target for almost every site is "Level AA," which is what U.S. courts and the European Accessibility Act effectively expect. The good news for a first launch is that a small group of AA basics — color contrast, image descriptions, form labels, and keyboard access — closes most of the real-world risk.
Can't I just install an accessibility widget to be safe?
No. Overlay widgets promise instant compliance but don't deliver it, and they can make you a target rather than protect you. In the first half of 2025, 456 lawsuits — about 22.6% of all filings — were aimed at sites that had an overlay installed. The reliable path is to fix the underlying basics: readable contrast, real image descriptions, labeled fields, and a site you can navigate with only a keyboard. Those fixes are permanent and free, and they actually improve the experience for the people the widget claimed to help.
Will the alt text my AI tool wrote count?
Often not. AI tools will fill in image descriptions automatically, but the results are frequently so generic they say nothing — a screen reader user just hears "image" over and over. A useful description says what the image actually shows and why it matters on that page. The quick test is to read your descriptions out loud with your eyes closed: if you'd still understand the page, they're working. If they're vague or repetitive, rewrite the few that carry real meaning and mark the purely decorative ones so screen readers skip them.
How long does a basic accessibility check take?
For most small AI-built sites, about fifteen minutes. Running a free scanner like the axe browser extension or Chrome's built-in Lighthouse takes a couple of minutes and lists your biggest issues in plain language. Fixing contrast and adding real image descriptions is mostly a matter of telling your AI tool what to change. The two checks that catch what scanners miss — tabbing through the site with no mouse, and listening to your home page with a built-in screen reader — take only a few minutes each. None of it requires writing code; it requires knowing what to look for and in what order.