Legal & Compliance

Is Your Website Accessible? What Small Businesses Need to Know About ADA Compliance

Picture this: a customer tries to buy from your website using a screen reader. Your product photos have no text descriptions, so she can't tell what she's looking at. The checkout fields show faint placeholder text but no real labels, so she can't tell which box is the email and which is the ZIP code. She gives up and leaves — and a few weeks later, a demand letter arrives citing specific technical failures on your site. This isn't a hypothetical. Federal courts saw more than 3,000 website accessibility lawsuits in 2025, and small businesses are a favorite target. Here's what website accessibility actually means, what the law expects, and what fixes actually work.

What "Website Accessibility" Actually Means

Forget the legal language for a second. An accessible website is one that a person can actually use regardless of disability. Someone who can't see the screen and navigates with a screen reader. Someone who can't use a mouse and navigates entirely with a keyboard. Someone with low vision who needs text to stand out sharply against its background. Someone who's deaf and needs captions on your videos. That's it — that's the whole idea. Accessibility is whether these real interactions succeed or fail on your site.

The technical rules behind this are the Web Content Accessibility Guidelines (WCAG), published by the W3C — the organization that sets web standards. They roll up to four ideas, remembered as POUR: content must be Perceivable (you can perceive it — alt text on images, enough contrast, captions), Operable (you can operate it — everything works by keyboard), Understandable (forms are labeled, navigation is predictable), and Robust (it works with assistive technology like screen readers).

Here's the part most business owners miss: accessibility is a property of the site's code, not a badge you add at the end. A button that's just a picture of the word "Submit" with no label isn't accessible, no matter how pretty the page looks. These aren't design opinions; they're testable failures in the code.

What the ADA Says About Your Website (Plain English)

The Americans with Disabilities Act was signed in 1990 — before the commercial web existed. It bans discrimination in "places of public accommodation," which back then meant ramps, doorways, and restrooms. Courts have spent three decades closing the gap to the online world, and the dominant interpretation today is that your website is an extension of your public accommodation. If the public can buy from you, book with you, or get information from you online, that experience has to be usable by people with disabilities.

Two cases did most of the heavy lifting. In 2008, a class action against Target over its inaccessible online store ended in a $6 million settlement. Then came Robles v. Domino's Pizza: a blind customer couldn't order pizza through the company's website or app with his screen reader. In 2019, the Ninth Circuit held that the ADA applies to the website of a business with a physical presence — and, crucially, that a business can be liable even though the government has never issued website accessibility regulations for private businesses. The U.S. Supreme Court declined to hear Domino's appeal later that year, leaving the ruling intact.

So what's the actual standard? For government bodies, the Department of Justice named one explicitly in April 2024: WCAG 2.1 Level AA. Private businesses don't have a regulation naming a standard — but in its absence, courts have overwhelmingly adopted WCAG 2.1 AA as the working definition of an accessible site. Think of it as your legal floor; aiming at WCAG 2.2 AA (the current version) covers the same ground plus newer issues like minimum touch-target sizes. One caveat: I'm a web professional, not a lawyer — this is how courts have been treating the law, not legal advice.

There's no small-business exemption. Title III of the ADA applies to public-facing business websites regardless of company size or revenue. A quote form on a roofer's site faces the same technical requirements as a national retailer's checkout page, because the law cares about public access, not how big you are.

Why Small Businesses Get Targeted (Not Just Big Brands)

The common assumption — "they only sue big companies" — is exactly backwards. Federal website accessibility filings reached 3,117 in 2025, up 27 percent from 2024, and the economics favor targeting small operators. The filing process is industrialized: firms run automated scanners across long lists of sites, flag machine-detectable failures, and send demand letters. A smaller business is more likely to settle quickly to make the problem disappear — and each quiet settlement funds the next batch of letters.

And the scanner doesn't need to know anything about your business. The failures it looks for are provable by a tool, so the cases are cheap to bring and expensive to defend. Being small isn't protection; in this arena it's part of the appeal. The same handful of technical issues appear on the vast majority of websites — which is why this matters even if you've never heard of the ADA before today.

The pattern is concentrated: e-commerce and restaurant sites absorb the majority of filings, and four states — New York, Florida, California, and Illinois — account for roughly two-thirds of federal filings. But a demand letter can reach a business anywhere, since the plaintiff's location sets the venue.

The 6 Mistakes That Trigger Most Complaints

Here's genuinely useful news: the problem is extremely concentrated. The WebAIM Million — the largest annual audit of the web — found 95.9 percent of the top one million home pages have detectable WCAG failures, yet just six failure types account for 96 percent of all detected errors. These are what plaintiff scanners flag first, because they're unambiguous and machine-detectable. Fix these six and you've eliminated the bulk of your measurable exposure.

• Low-contrast text (found on 83.9% of pages). Light gray text on a white background is a classic offender — unreadable for low-vision users. WCAG AA requires at least a 4.5:1 contrast ratio for normal text (3:1 for large text). Darken the text or lighten the background until it passes.
• Missing image alt text (53.1%). Without a text alternative, a screen reader has nothing to announce — the visitor hears "graphic" or nothing at all. Add a short description of what the image communicates. Purely decorative images should use an empty alt so the reader skips them.
• Missing form input labels (51.0%). Search bars and checkout fields that never say what to type in. Tie every input to a label in the code — placeholder text that disappears is not a label.
• Empty links (46.3%). Links wrapping an icon or image with no text — navigation that collapses for screen readers. Give the link real text, or label the icon so its destination gets announced.
• Empty buttons (30.6%). "Submit" and "Add to cart" controls with no accessible name. The screen reader announces only "button." Put text inside the button or add a proper label describing the action.
• Missing document language (13.5%). Without it, a screen reader can pick the wrong pronunciation engine. One line of code fixes it.

The insight most "accessibility audit" sales pitches won't volunteer: most of these are content and markup fixes, not redesigns. Alt text, labels, contrast values, link text — a careful pass through your key pages clears a huge portion of the machine-detectable risk without rebuilding anything. But if your theme or builder resists clean repairs, the underlying structure is the problem — see our work to compare what a properly built site looks like.

Why Accessibility Overlay Widgets Don't Protect You

When a business owner first learns about this risk, the instinct is to find the fastest possible fix — and an entire industry sells exactly that: an accessibility overlay, a single line of JavaScript that drops a widget onto your site promising instant compliance. It's the most dangerous purchase in this space, because it treats a code problem as a bolt-on.

An overlay sits on top of your site at runtime. It doesn't rewrite the underlying HTML that a screen reader actually reads — the missing alt attributes, the unlabeled form fields, the empty links are all still there in the source. Assistive technology reads the source, not the marketing. Plaintiffs increasingly target overlay-equipped sites on purpose, and in some complaints the widget itself is cited as a barrier rather than a solution.

The data is blunt: in 2025, 1,416 businesses that had installed an overlay widget were sued anyway — up from 1,023 the year before. And in May 2025, the FTC ordered a leading overlay vendor, accessiBe, to pay $1 million over misleading claims about its automated tool. If a single script actually made sites compliant, the lawsuits would have stopped. They haven't.

Real compliance means correcting the source: the alt text, the labels, the contrast, the keyboard paths. A widget layered over broken code can't do that work for you — no matter what the sales page promises.

What Real Accessibility Remediation Looks Like

Fixing accessibility is a project with a beginning, a repair phase, and a testing phase — not a product you install. Here's the honest process:

• Scan the pages that matter. Start with your homepage, service pages, contact page, quote forms, and anything that takes payment or bookings. A free automated scan (tools like WAVE flag the machine-detectable issues in minutes) tells you what a plaintiff's scanner would see. Save the report with the date.
• Fix the machine-detectable failures in the code. Alt text, form labels, contrast, empty links, button names — repair them in the actual HTML and CSS, not with an overlay. If your theme or builder blocks clean repairs, that's a sign the structure itself needs attention.
• Test with a keyboard and a screen reader. Unplug the mouse and try to complete your site's key tasks — navigate the menu, fill the quote form, close the popups — using only Tab and Enter. Then check representative pages with a screen reader. Automation catches maybe a third of real barriers; only real interaction catches the rest.
• Document everything. Keep the original scan, the list of issues, what you changed, and the retest results with dates. A dated record of good-faith maintenance is worth its weight if questions ever come up — and it keeps you honest as new content and plugins add new barriers over time.

There's also an upside beyond legal risk, though you should treat the big claims with the same skepticism as the scare tactics: pages that are readable, navigable, and clearly labeled tend to be easier for everyone to use — including search engine crawlers. Clear heading structure, descriptive links, and real form labels are accessibility work and good SEO work at the same time.

The practical bottom line: if the idea of running a scanner, reading the report, and fixing your theme's code makes your eyes glaze over, that's what a web professional is for. Our web design services include accessibility remediation built into the code — alt text, labels, contrast, keyboard navigation — rather than bolted on afterward. Or get a free website audit and we'll tell you exactly where your site stands, including the machine-detectable failures a scanner would flag today.

Frequently Asked Questions

Does my small business website need to be ADA compliant?

Yes. Title III of the ADA applies to public-facing business websites regardless of company size or revenue — there is no small-business exemption. Courts treat a business website as an extension of its place of public accommodation. A service-area business with a quote form or booking tool faces the same technical requirements as a national retailer.

What is the actual standard for an accessible website?

U.S. courts overwhelmingly use WCAG 2.1 Level AA as the working definition of an accessible site, and the Department of Justice formally adopted it for government bodies in April 2024. Practically, treat WCAG 2.1 AA as your legal floor and WCAG 2.2 AA as your target — the newer version is backward-compatible and adds criteria for touch targets, keyboard focus visibility, and authentication.

Will an accessibility overlay widget make my site compliant?

No. An overlay sits on top of your site at runtime and does not repair the underlying HTML, CSS, forms, or scripts that screen readers actually read. Roughly a quarter of January 2026 accessibility cases involved sites already using widgets, and the FTC fined a leading overlay vendor $1 million in 2025 over misleading claims. Real compliance requires fixing the source code.

How do I start checking my website's accessibility?

Run an automated scan (for example with the WAVE tool) on your homepage, service pages, contact page, and any quote or booking forms. Fix the machine-detectable failures first — missing alt text, unlabeled form fields, low color contrast, empty links, and broken keyboard navigation. Then test key tasks using only a keyboard, check pages with a screen reader, and document every fix with dates.

Keep Reading