AI Ready Hub logoAI Ready Hub
Always Keep Your Head on a Swivel in the Age of AI · Part 1

Your Vibe-Coded Website Still Has to Follow the Law: Why WCAG Compliance Matters

AI site builders make launching easy, but accessibility law still applies. What WCAG 2.2 AA means, the legal risk, why overlays fail, and a checklist for your AI-built site.

By AI Ready Hub

About this series: AI tools are helping small businesses move faster than ever. But speed has a way of hiding risk. Always Keep Your Head on a Swivel in the Age of AI is AI Ready Hub's series on the things that are easy to miss when AI does the heavy lifting, and how to catch them before they cost you. We're starting with the website you may have built last weekend.

You described your business to an AI tool, and twenty minutes later you had a website. It had a hero image, a services section, a contact form, and a slick mobile menu. Maybe you used Lovable, Bolt, v0, Cursor, or Manus. It looks great. You published it.

Here's what most people don't hear until a demand letter shows up: the law doesn't care how your site was built. If people with disabilities can't use it, "the AI wrote it" isn't a defense.

What "vibe coding" actually is

"Vibe coding" is a term AI researcher Andrej Karpathy coined in February 2025. It describes building software by telling an AI what you want in plain language and accepting what it produces, without reading the code closely. For small businesses this is a real gift. You can launch in hours instead of hiring an agency for months.

The catch is in the definition: you aren't looking at the code. And accessibility problems almost always live in the code.

Why AI-built sites so often miss accessibility

AI site builders are trained to produce things that look finished. Accessibility is mostly invisible to a sighted person using a mouse. That's why the same problems show up again and again:

  • Missing alt text. Images with no text description, so screen reader users hear nothing, or just a file name.
  • Poor color contrast. Trendy light-gray text on white backgrounds that people with low vision can't read.
  • No keyboard navigation. Buttons and menus that only respond to a mouse click or tap, so people who navigate by keyboard get stuck.
  • Missing form labels. Contact and booking forms where a screen reader announces "edit text, edit text, edit text" with no clue what goes where.
  • Mobile menus that vanish. Hamburger menus that open visually but can't be reached by keyboard or screen reader. Or menus that disappear completely at certain screen sizes or zoom levels.

These aren't unusual problems. WebAIM's 2026 analysis of the top one million home pages found detectable WCAG failures on 95.9% of them. Low-contrast text showed up on 83.9% of pages, missing alt text on 53.1%, and missing form labels on 51%. WebAIM noted that errors rose this year after six years of slow improvement. It pointed to growing page complexity and AI-assisted "vibe coding" as likely factors.

What WCAG 2.2 AA means, in plain terms

The Web Content Accessibility Guidelines (WCAG) are the international technical standard for web accessibility, published by the W3C. Version 2.2 is the current one. It has three levels: A, AA, and AAA. Level AA is the practical target that most laws and lawsuits point to.

In everyday language, AA means:

  • People can perceive your content. Images have text alternatives, videos have captions, and normal text has a contrast ratio of at least 4.5:1.
  • People can operate it. Everything works with a keyboard, focus is visible, and tap targets are at least 24×24 CSS pixels.
  • People can understand it. Forms have clear labels, errors are explained, and navigation stays consistent.
  • It's robust. Assistive technologies like screen readers can correctly interpret your buttons, menus, and controls.

The W3C says content that meets WCAG 2.2 also meets WCAG 2.0 and 2.1, so building to 2.2 AA covers the older versions many rules still cite.

The legal risk is real, and it's growing

This section is general information, not legal advice. Talk to a qualified attorney about your specific situation.

United States, private businesses (ADA Title III). The Department of Justice has long held that the ADA applies to the websites of businesses open to the public. It has no website-specific technical rule for private businesses, so WCAG is the benchmark that courts and plaintiffs usually use. Lawsuits are frequent. Seyfarth Shaw counted 3,117 federal website accessibility lawsuits in 2025, a 27% jump over 2024. UsableNet, which also tracks key New York and California state courts, counted 4,928 digital accessibility lawsuits for 2025. And this isn't only a big-company problem. In UsableNet's 2025 year-end report, companies with more than $25 million in revenue made up just 36% of those sued. The other 64% were smaller.

United States, public entities (ADA Title II). In April 2024, the DOJ issued a rule requiring state and local government websites and apps to meet WCAG 2.1 AA. A 2026 interim final rule moved the deadlines to April 26, 2027 for entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special districts. If you build sites for, or sell to, a city, county, school district, or public college, expect accessibility requirements in your contracts.

European Union (European Accessibility Act). The EAA has applied since June 28, 2025. It covers services such as e-commerce, consumer banking, and e-books. Microenterprises that provide services are exempt, meaning fewer than 10 employees and no more than €2 million in annual turnover or balance sheet. If you sell online to EU customers and are bigger than that, it likely applies to you.

Why an overlay widget won't save you

You've probably seen the little accessibility icon that promises "instant compliance" with one line of code. Be skeptical. In 2025 the U.S. Federal Trade Commission finalized an order requiring accessiBe to pay $1 million. The FTC said the company's claims that its AI tool could make any website WCAG-compliant were deceptive. Overlays don't stop lawsuits either. UsableNet's 2025 year-end data shows more than 1,400 lawsuits filed against companies that already had widgets installed. It notes that widgets typically don't fix underlying code problems and can interfere with screen readers.

An overlay sits on top of broken code. The fix is fixing the code.

The upside: this is good business

Accessibility isn't only defense. According to the CDC, more than 1 in 4 U.S. adults (28.7%), roughly 70 million people, report a disability. That's a big share of your potential customers.

The same fixes help everyone else too:

  • SEO. Descriptive alt text and clear headings help search engines understand your pages. Google's own image guidance recommends useful alt text.
  • Mobile UX. Larger tap targets, readable contrast, and layouts that hold up when zoomed make your site easier to use on a phone in bright sunlight.
  • Conversions. Labeled, keyboard-friendly forms get filled out more often by everyone.

A quick checklist for your AI-built site

  1. Tab through every page using only your keyboard. Can you reach and use every link, button, form, and menu? Can you always see where focus is?
  2. Test the mobile menu at phone width, at 200% zoom, and by keyboard. Does it open, stay open, and close properly?
  3. Check every image for meaningful alt text. Decorative images should use empty alt (alt="").
  4. Run a contrast check. Normal text needs at least 4.5:1.
  5. Confirm every form field has a visible, programmatic label and clear error messages.
  6. Run a free automated scan such as WAVE, then test manually. Automated tools catch only part of the problem.
  7. Prompt your AI tool explicitly: "Make this WCAG 2.2 AA compliant." Then verify. Don't trust.
  8. Re-test after every major AI regeneration. One new prompt can undo previous fixes.

A real example: Fullcourt Signal

When AI Ready Hub built fullcourtsignal.com, an independent NBA news and stats site, we set WCAG 2.2 AA as the target from day one. Even so, our mobile accessibility audit caught a navigation menu that disappeared on phones, and we fixed it before it cost visitors. Everything looked fine on a desktop. It only surfaced because we tested deliberately. That's the lesson: even a site built with accessibility in mind needs a human-led check before you call it done.

Get an AI Ready Hub accessibility check

You built your site fast. Let's make sure it's built right. AI Ready Hub helps small businesses use AI tools with confidence, and that includes finding and fixing the accessibility gaps AI tends to leave behind. We'll review your site against WCAG 2.2 AA, flag what matters most, and give you a clear, prioritized fix list. You can apply the fixes yourself or have us handle them.

Email Contact@aireadyhub.tech or visit aireadyhub.tech to request your accessibility check.

Next in the series: Always Keep Your Head on a Swivel in the Age of AI

  • Part 2: Who owns what your AI made? AI-generated content, copyright, and the risk of publishing work you may not be able to protect, or that borrows too closely from someone else's.
  • Part 3: Deepfakes and AI scams aimed at small businesses. Cloned voices, fake invoices, and impersonation attacks, and how to verify before you pay.
  • Part 4: What happens to the data you paste into AI tools? Privacy, confidentiality, and customer data in chatbots and AI assistants.
  • Part 5: When your chatbot makes a promise. Liability for what AI customer-service bots tell your customers.

This article is for general informational purposes only and is not legal advice. Laws and deadlines change. Consult a qualified attorney about your obligations.

Sources

  1. WebAIM, The WebAIM Million: 2026 report — https://webaim.org/projects/million/
  2. W3C, Web Content Accessibility Guidelines (WCAG) 2.2 — https://www.w3.org/TR/WCAG22/
  3. U.S. DOJ, Guidance on Web Accessibility and the ADA (2022) — https://www.ada.gov/resources/web-guidance/
  4. Seyfarth Shaw, Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025 — https://www.adatitleiii.com/2026/03/federal-court-website-accessibility-lawsuit-filings-bounce-back-in-2025/
  5. UsableNet, Web Accessibility Lawsuits Tracker — https://info.usablenet.com/ada-website-compliance-lawsuit-tracker
  6. UsableNet, 2025 Year-End Digital Accessibility Lawsuit Report (PDF) — https://info.usablenet.com/hubfs/Remediated%20-%202025_Year-End_Digital_Accessibility_Lawsuit_Report_FINAL.pdf
  7. U.S. DOJ, Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments — https://www.ada.gov/resources/2024-03-08-web-rule/
  8. Federal Register, Extension of Compliance Dates… (Interim Final Rule, April 20, 2026) — https://www.federalregister.gov/documents/2026/04/20/2026-07663/extension-of-compliance-dates-for-nondiscrimination-on-the-basis-of-disability-accessibility-of-web
  9. EUR-Lex, Summary of Directive (EU) 2019/882 (European Accessibility Act) — https://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX%3A32019L0882
  10. EUR-Lex, Directive (EU) 2019/882, full text — https://eur-lex.europa.eu/eli/dir/2019/882/oj
  11. U.S. FTC, FTC Approves Final Order Requiring accessiBe to Pay $1 Million (April 22, 2025) — https://www.ftc.gov/news-events/news/press-releases/2025/04/ftc-approves-final-order-requiring-accessibe-pay-1-million
  12. CDC, Disability and Health Data Now — https://www.cdc.gov/disability-and-health/articles-documents/disability-and-health-data-now.html
  13. Google Search Central, Image SEO best practices — https://developers.google.com/search/docs/appearance/google-images
  14. Andrej Karpathy on X, original "vibe coding" post (Feb. 2, 2025) — https://x.com/karpathy/status/1886192184808149383
  15. WebAIM, WAVE Web Accessibility Evaluation Tool — https://wave.webaim.org/

Want help applying this? See how we work or request an accessibility check.