Is Your AI Generated Website Leaving Your Business Open to an ADA Lawsuit?

Can an AI Generated Website Get You Sued Under the ADA?

Yes, in the sense that any website can. Courts and the Department of Justice treat websites of businesses open to the public as covered by the ADA, and an AI builder does not check accessibility for you. The risk is not the AI. The risk is that nobody inspected the site after it was generated.

You asked AI to build a website. It looks good. It loads. The contact form works. You spent $100 instead of $5,000.

Then somebody tells you your website may violate the ADA. That is a hell of a way to find out what WCAG means.

We hear this from business owners around Denham Springs, Livingston Parish, and Baton Rouge, and the reaction is almost always the same. Not defensiveness. Genuine surprise. Nobody told them this was a category of risk, because the person who sold them the site did not know either.

What WCAG Means in Plain English

The acronym does most of the intimidating work here, so let us take it apart.

WCAG stands for Web Content Accessibility Guidelines. It is a published technical standard that describes what a website has to do so people with disabilities can use it. Not a law, a standard. Laws and settlements point at it.

The version that keeps appearing in federal settlement agreements is WCAG 2.1 Level AA. When the Justice Department resolves a website accessibility matter, that is usually the bar it sets. Treat it as the working definition of an accessible site.

The standard covers plain, physical things: text a person with low vision can read, controls a person can reach without a mouse, images that mean something to a screen reader, and video a deaf customer can follow. If you want the full explainer with the four POUR principles and a fifteen minute self-check, we wrote that separately in our guide to website accessibility for small businesses. This article is about the legal exposure and the AI angle specifically.

Why Your Website Can Look Fine and Still Be Unusable

This is the part that catches owners off guard, and it is the reason accessibility problems survive for years without anyone noticing.

You test your website the way you built it. Mouse, good monitor, familiar layout, and you already know what every button does. Under those conditions almost any site passes.

Your customer may not be working under those conditions. A form can submit perfectly with a mouse and be impossible to complete with a keyboard. An image can look great and tell a screen reader nothing at all. Text can read fine to you and fail the measured color contrast threshold that someone with low vision depends on.

None of that shows up in a screenshot. That is precisely where the risk lives, and it is why “it works for me” is not evidence of anything.

What the ADA Actually Says About Business Websites

Here is the short version, drawn from the government’s own guidance rather than from a vendor scaring you toward a subscription.

Title III of the ADA applies to businesses open to the public. The Justice Department’s guidance on web accessibility states that the ways websites are designed can create barriers that keep people with disabilities from the information and services a business offers online, in the same way steps can keep someone out of a building.

That guidance also lists the specific barriers it sees most often. Poor color contrast. Using color alone to carry meaning. Missing alt text on images. Videos with no captions. Online forms without labels, clear instructions, or error indicators. And mouse-only navigation, where a person who cannot use a mouse simply cannot reach the content.

Read that list again with your own site in mind. Every item is something a person could have checked in an afternoon, and almost nobody does.

What the Fashion Nova Case Shows About Where This Is Heading

One recent case is worth understanding, less as a scare story and more as a look at how seriously this is being taken.

In Alcazar v. Fashion Nova Inc., plaintiffs alleged the retailer’s site was not accessible and denied blind users full and equal access to its goods and services. The parties reached a proposed settlement in which Fashion Nova would pay roughly $2.43 million split among California class members who filed valid claims, while plaintiffs’ counsel sought over $2.52 million in fees and costs.

Then the story took a turn worth noting. On February 2, 2026 the Justice Department filed a Statement of Interest opposing that settlement as unfair, on the grounds that it delivered little of value to blind consumers while generously compensating attorneys. The DOJ argued the injunctive relief was a bare recitation of an obligation Fashion Nova already had, with no confirmation or enforcement mechanism behind it.

“A class action under the ADA should, above all else, secure greater accessibility for consumers with disabilities,” said Assistant Attorney General Harmeet K. Dhillon in the department’s February 2026 announcement. The DOJ also pointed out that class counsel’s own website for administering the settlement was itself inaccessible to blind users.

The point is not that Fashion Nova got sued and therefore you will. The point is that this area has active federal attention, courts are being asked to look past paper promises, and being small does not make inaccessible code accessible.

Enforcement is not limited to retail either. The Justice Department reached a series of agreements with Rite Aid, Hy-Vee, Kroger, Meijer, and CVS over COVID-19 vaccine registration portals that screen reader and keyboard users could not complete. Those were scoped to the vaccine scheduling flows rather than entire websites, and the remedy in each was conformance to WCAG 2.1 Level AA.

Where AI Website Builders Miss Accessibility

This is where the honest answer is more useful than the alarming one, because the data does not say what most agency blogs claim it says.

An AI generator will happily produce a layout, a form, images, buttons, menus, and animation. What it does not do is sit with the result and ask what the experience is for someone who cannot see it. It can output a button that looks perfect and carries an accessible name that means nothing out loud.

Now the part the fear-based version leaves out. WebAIM’s 2026 study of a million home pages found that pages built on the major site builders averaged fewer accessibility errors than the web overall, with Squarespace at 33.0 and Wix at 33.3 against an all-page average of 56.1. WordPress landed at 52.8, slightly under the average.

So the tool is not the villain. Across the whole sample, 95.9% of home pages had detectable WCAG failures, up from 94.8% the year before. Nearly everything fails, on every platform, at every price point.

What separates a compliant site from a risky one is not which builder produced it. It is what happened after the builder finished. AI can build the interface. Someone still has to inspect the experience.

Why Free and $100 Websites Deserve Extra Scrutiny

None of this is an argument that inexpensive websites are bad. Plenty of cheap sites are fine, and plenty of expensive ones are not.

The danger with a $100 website is not the $100. The danger is assuming that because somebody handed you a website, they also checked accessibility, SEO, security, performance, forms, schema, mobile behavior, and compliance.

Those are different jobs, done by different skills, and priced accordingly. A $100 price usually buys the first one and none of the rest. That is not fraud. It is scope, and the trouble starts when the buyer never learns what the scope was.

Ask the person who built your site one question: what did you check, and can you show me the results? A confident answer is worth a lot. A blank look tells you what you bought. When the site itself is the deeper problem, we covered that pattern in our guide to AI slop websites and what they quietly cost.

Why an Accessibility Widget Is Not a Fix

If you have been sold a one-line script that promises compliance, this section is the one to read twice.

Overlay widgets are third-party scripts that load on your site and attempt to repair accessibility problems in the browser. The pitch is appealing because it is one line of code and a monthly fee instead of actual remediation.

In January 2025 the FTC ordered accessibility vendor accessiBe to pay $1 million over claims that its AI powered widget could make any website WCAG compliant. The order bars the company from repeating that representation without evidence, and also addressed third-party reviews formatted to look like independent opinions.

The accessibility practitioners behind the Overlay Fact Sheet put it plainly: while an overlay may improve a handful of provisions, “full compliance cannot be achieved with an overlay.” They also flag a privacy problem, since a widget that auto-enables screen reader settings has to detect assistive technology, which exposes that the person using the device has a disability.

A widget is not worthless. It is just not the thing you were told it was, and it does not substitute for fixing the underlying code.

Why One Automated Scan Is Not Enough

Automated scanners are genuinely useful. They are also the most over-trusted tool in this entire subject.

A scanner reads code and reports the failures it can detect mechanically. It cannot judge alt text accuracy, honest heading structure, a keyboard user’s ability to escape a menu, or how your error messages sound when read aloud.

WebAIM makes this limit explicit. Because its 2026 analysis counted only automatically detectable failures, the report notes that the true rate of full WCAG 2 A/AA conformance was “certainly lower” than the 4.1% of pages that came back clean.

So a green score is a floor, not a finish line. A passing Lighthouse number, a responsive layout, a plugin, and an AI written accessibility statement are four things that can all be true on a site a blind customer cannot use.

What a Website Accessibility Audit Should Check

An audit is worth having when it combines what a machine can measure with what only a person can judge. Here is what we look at.

• Keyboard access. Every link, button, menu, and form field reachable and operable without a mouse, with a visible focus indicator.
• Color contrast. Text measured against its background at the ratios the standard sets, including text sitting on images.
• Alt text quality. Not just present, but describing what the image conveys, with decorative images correctly marked as decorative.
• Form accessibility. Real labels, clear instructions, and error messages a screen reader announces.
• Heading hierarchy. One H1, no skipped levels, headings that describe the section rather than decorate it.
• Link and button naming. Accessible names that make sense out of context, which rules out a page of “click here” and empty icon buttons.
• Mobile behavior. Touch targets, zoom, orientation, and reflow at small widths.
• Screen reader review. Actually listening to the key paths, because this is where generated markup usually falls apart.
• Video and media. Captions on anything with speech, and no content that plays and traps a user.

To be straight with you about what this buys: an audit is a risk assessment, not immunity. Anyone promising to make you lawsuit proof is selling something. Human beings invented lawyers, so naturally nothing gets to be that simple. What an audit does is find the problems before a customer, an attorney, or a demand letter finds them for you.

Common Questions About AI Websites and ADA Compliance

These are the questions small business owners ask us once they realize this is a real category of risk and not a scare tactic.

Is my small business website really covered by the ADA?

Title III of the ADA applies to businesses open to the public, and the Justice Department’s web guidance addresses the barriers that keep people with disabilities from services offered online. There is no small business carve-out that makes inaccessible code acceptable. Talk to an attorney about your specific exposure.

Does using AI to build my site make it more likely to fail?

Not by itself. WebAIM’s 2026 data shows major site builders averaging fewer detected errors than the web overall, and 95.9% of all home pages failing something. The reliable predictor is not the tool that generated the site. It is the presence or absence of a human review.

Can an accessibility plugin or overlay make me compliant?

No. The Overlay Fact Sheet states that full compliance cannot be achieved with an overlay, and in 2025 the FTC fined a vendor $1 million over exactly that kind of claim. A widget can help with a few items. It does not repair the underlying code.

My Lighthouse accessibility score is 100. Am I fine?

A perfect automated score means no machine-detectable failures were found. It says nothing about alt text accuracy, keyboard traps, or how your forms sound to a screen reader. WebAIM notes real conformance is certainly lower than its automated numbers suggest.

What standard should I actually aim for?

WCAG 2.1 Level AA is the practical target. It is the conformance level the Justice Department has required in its website accessibility agreements, including the vaccine portal settlements with CVS, Kroger, Rite Aid, Meijer, and Hy-Vee.

Do I have to rebuild my website to fix this?

Usually not. The six most common failures have been the same for seven years and most are correctable in place: contrast values, alt text, form labels, empty links, empty buttons, and a missing language attribute. A rebuild is warranted when the underlying template fights you.