ADA Website Compliance for Small Business: 2026 Guide

A small business owner launches an e-commerce site, runs it for two years without a single complaint, and opens the mail one morning to find a federal lawsuit. The allegation: their website discriminates against people with disabilities. This is not hypothetical — ADA website compliance for small business is one of the fastest-growing areas of civil litigation in the United States, with 77% of these lawsuits targeting companies with annual revenue under $20 million.

The fix is usually simpler than the lawsuit makes it sound. This guide covers what the law actually requires, the six issues that cause the vast majority of failures, and how to audit your site before someone else does it for you.

Yes, Your Small Business Website Needs to Be ADA Compliant

The Americans with Disabilities Act requires businesses that serve the public — known legally as "places of public accommodation" — to be accessible to people with disabilities. Since 2022, the U.S. Department of Justice has made clear that this requirement extends to websites.

There is no revenue threshold. There is no employee minimum for Title III, which covers customer-facing access. If your business operates a website that the public can visit, the ADA applies to it.

The only Title III exemptions are religious organisations and private clubs. Small businesses are not exempt. The confusion stems from Title I (employment), which does exempt businesses with fewer than 15 employees — but Title I covers hiring practices, not your website.

The ADA itself does not mention websites by name. It was written in 1990, before most businesses had a web presence. But federal courts have consistently ruled that websites connected to a physical business qualify as public accommodations — and the landmark Domino's Pizza ruling in 2019, which the Supreme Court declined to review, confirmed this interpretation.

In April 2024, the DOJ published its final web accessibility guidance, formally adopting WCAG 2.1 Level AA as the technical standard for state and local government websites under Title II. While Title II covers government entities, the standard signals where private-sector enforcement under Title III is heading.

The short answer to "does my website need to be ADA compliant" is yes. The question is not whether the law applies to you — it is whether your site meets the standard before someone tests it for you.

What WCAG 2.2 Requires from Your Website

The ADA does not spell out technical standards for websites. Instead, courts and the DOJ point to the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C). The current version is WCAG 2.2, released in October 2023.

WCAG organises requirements into four principles. Your website must be:

• Perceivable — content must be presented in ways all users can access, including people who are blind, deaf, or have low vision
• Operable — every function must work with a keyboard, not just a mouse
• Understandable — text must be readable and the interface must behave predictably
• Robust — content must work reliably across assistive technologies like screen readers

Within these principles, WCAG defines three conformance levels: A (minimum), AA (standard), and AAA (strictest). Level AA is the accepted benchmark for legal compliance. Courts reference it, the DOJ cites it, and it is the standard that accessibility auditors test against.

What Level AA looks like in practice:

• Text has a minimum contrast ratio of 4.5:1 against its background
• Every image has descriptive alt text
• Every form field has a visible, associated label
• All interactive elements are reachable and usable by keyboard
• Video content has captions
• The page declares its language in the HTML
• Error messages identify the problem and suggest a fix

WCAG 2.2 added nine new success criteria beyond version 2.1. The most relevant for small business sites include minimum target size for clickable elements (at least 24×24 CSS pixels), consistent help placement across pages, and accessible authentication that does not rely on cognitive function tests like CAPTCHAs without alternatives.

If your site meets WCAG 2.1 Level AA, you are in strong shape. If it also meets the 2.2 additions, you are ahead of most competitors and well-positioned against any legal claim.

What Happens When You Get a Demand Letter

Most ADA website cases do not start in a courtroom. They start with a demand letter — a formal notice from an attorney representing a person with a disability who claims they could not use your website.

The letter typically lists specific accessibility barriers, cites the ADA, and demands that you fix the issues and pay damages. Under the federal ADA, Title III cases do not allow monetary damages directly — but the plaintiff can seek injunctive relief (forcing you to fix the site) and recover attorney's fees. The first civil penalty for a Title III violation can reach $75,000, and repeat violations can reach $150,000.

State laws add another layer. California's Unruh Civil Rights Act sets minimum damages at $4,000 per violation, plus attorney's fees. A single inaccessible form or missing alt tag can count as a separate violation. Most small businesses settle for $5,000 to $25,000 before counting their own legal defence costs.

The numbers keep climbing. Plaintiffs filed over 3,200 federal web accessibility lawsuits in 2022 alone — a 12% increase from the prior year — and the pace has not slowed. New York, Florida, and California see the highest volume. A disproportionate share targets small businesses because they are less likely to fight back and more likely to settle quickly.

Many of these plaintiffs are serial filers who submit dozens or hundreds of lawsuits per year. This does not make the claims invalid. If your site genuinely fails to meet accessibility standards, the claim has legal standing regardless of the plaintiff's motivation.

The cost of prevention is a fraction of the cost of defence. A basic accessibility audit runs $500 to $2,000. A lawsuit settlement costs ten to fifty times that — plus legal fees, reputation damage, and forced remediation under court supervision.

The 6 Issues That Cause 96% of ADA Website Failures

The WebAIM Million study analyses the top one million websites every year for accessibility compliance. In the most recent analysis, 95.9% of homepages had detectable WCAG failures — and six categories of issues accounted for the vast majority of errors.

Every one of them is fixable.

1. Low contrast text

Text that does not meet the 4.5:1 contrast ratio against its background. This is the single most common failure, appearing on over 81% of pages tested. Test your colour combinations with a free contrast checker and adjust your CSS values.

2. Missing alt text on images

Images without descriptive alternative text are invisible to screen readers. Over 54% of pages had this issue. Every meaningful image needs an alt attribute that describes what the image shows — not "image1.jpg" but "woman completing checkout on mobile phone."

3. Missing form input labels

Form fields without programmatically associated labels. Screen readers cannot tell a user what information a field expects. Over 45% of pages had this issue. Add a <label> element linked to each input with a matching for attribute.

4. Empty links

Links that contain no text — often icon-only links or image links without alt text. Screen readers announce "link" but cannot tell the user where it goes. Found on over 44% of pages. Give every link descriptive text or an aria-label.

5. Empty buttons

Buttons with no accessible name — the same problem as empty links applied to interactive controls. Found on over 28% of pages. Add visible text content or an aria-label to every button element.

6. Missing document language

The HTML element does not declare a language attribute. Screen readers need this to select the correct pronunciation rules. Found on over 17% of pages. Add lang="en" to your opening HTML tag — a one-line fix.

These six issues are not edge cases. They are the baseline failures that accessibility auditors and plaintiff attorneys check first. Fixing all six does not guarantee full WCAG 2.2 compliance, but it eliminates the most common and most legally actionable problems on your site.

How to Audit Your Website for ADA Compliance

You do not need a developer to run a meaningful accessibility audit. A combination of free tools and a keyboard gets you most of the way there.

Step 1: Run an automated scan. Start with a free automated checker. Google Lighthouse, built into Chrome DevTools, includes an accessibility audit. WAVE, from WebAIM, is a browser extension that highlights issues directly on the page. Run each tool on your homepage, your contact page, and your most-visited landing page — these three pages are the ones most likely to be tested in a demand letter. Automated tools catch roughly 30–40% of WCAG failures: the machine-detectable ones like missing alt text, low contrast, and unlabelled form fields.

Step 2: Test with your keyboard. Unplug your mouse. Navigate your entire site using only the Tab key, Enter, and arrow keys. Can you reach every link, button, and form field? Can you see where the keyboard focus is at all times? If anything traps your keyboard or becomes unreachable, that is a WCAG failure.

Step 3: Test your key user flows. Walk through the actions that matter most — finding a product, filling out a contact form, completing a purchase. Do these flows work without a mouse? Do error messages explain what went wrong? Can you complete the process without relying on colour alone to understand the interface?

Step 4: Check your content against the six common issues. Review every page for the failures listed above. Verify alt text on images, labels on form fields, contrast ratios on text, and a language declaration on your HTML element. Check that video content has captions and that downloadable PDFs are tagged for screen readers.

Step 5: Prioritise and fix. Sort issues by severity. Missing form labels on a checkout page are more urgent than low contrast in a footer link. Fix the high-traffic, user-facing problems first — the ones most likely to affect a real user with a disability and most likely to appear in a demand letter.

Automated tools will not test whether alt text is actually meaningful, whether reading order makes logical sense, or whether custom components like modals and accordions work correctly with assistive technology. For those issues, you need a manual review — either by a qualified accessibility auditor or by testing with a screen reader yourself.

Why Accessibility Overlays Do Not Protect You

Accessibility overlays are JavaScript widgets that add a toolbar to your website, offering visitors the ability to adjust font size, contrast, or cursor style. Companies like accessiBe, UserWay, and AudioEye market them as one-click ADA compliance solutions.

They are not. The overlay industry has been widely criticised by accessibility professionals, disability advocates, and the courts.

Overlays do not fix the underlying code. They add a cosmetic layer on top of a site that may still be inaccessible to screen readers, keyboard users, and people with cognitive disabilities. The National Federation of the Blind has publicly opposed overlay products, and multiple lawsuits have been filed against businesses that relied on overlays as their sole compliance measure.

The problem is structural. If a form field has no label in the HTML, an overlay cannot reliably assign one. If a button has no accessible name, the overlay may guess incorrectly. If your navigation traps keyboard users, no overlay can restructure your page layout.

Overlays can serve as a temporary layer while you work on proper remediation. They should never be your only strategy. A plaintiff attorney will not accept "we installed an overlay" as a defence — and neither will a court.

The only reliable path to ADA website compliance is fixing your site's code, content, and design at the source. That means correct HTML semantics, proper ARIA attributes, sufficient colour contrast, and meaningful text alternatives for every non-text element.

What to Do If Your Site Is Not Compliant

If you ran the audit steps above and found issues, you are in good company. The vast majority of websites have accessibility problems. What matters is fixing them before they become a legal problem.

Start with the six common issues. Most can be resolved in a single development sprint. Missing alt text, form labels, and language declarations are HTML-level changes that take minutes per page. Contrast adjustments require updating your CSS colour values. Empty links and buttons need descriptive text or ARIA labels.

For more complex problems — custom interactive components, embedded third-party tools, or legacy CMS platforms — you may need a developer or accessibility specialist. Professional remediation for a typical small business site costs between $1,500 and $10,000, depending on complexity and page count.

If you want your next site built accessible from the ground up — with correct semantic HTML, WCAG 2.2 compliance, and a design system that treats accessibility as a feature rather than an afterthought — Vediwood builds sites that way by default. No retrofit. No overlay. Just a site that works for everyone.