Is My Website ADA Compliant? What Small Businesses Actually Need to Know in 2026

The short answer

If nobody has ever checked, your website probably is not fully compliant. That is not a scare tactic. It is just the base rate: most sites built without accessibility in mind fail multiple checks, and a quick automated scan will usually surface a handful of issues in the first minute. The good news is that “not compliant today” is a fixable, well-understood problem, and you do not need to panic-buy anything to start.

This guide is the plain-English version: what the law actually asks of a small business, how to check your own site, and what is worth fixing first.

What “ADA compliant” actually means for a website

Here is the thing most articles skip: there is no official government checklist called “ADA website compliance,” and no certificate that makes you compliant. The Americans with Disabilities Act is a civil-rights law from 1990. It requires “places of public accommodation” to be accessible to people with disabilities. Courts have repeatedly read that to include websites, but the ADA itself does not spell out technical rules for web pages.

So in practice, “ADA compliant” is shorthand for “measured against WCAG.” WCAG (the Web Content Accessibility Guidelines) is the technical standard that courts, government agencies, and funders point to when they need to define what accessible means. When someone asks whether your site is ADA compliant, the answerable version of that question is: does your site meet WCAG at the level that matters, which is usually AA.

Does the ADA really apply to small business websites?

Usually, yes, and there is no small-business carve-out. ADA Title III applies to businesses that serve the public: retail, restaurants, professional services, healthcare, hospitality, and most sites that sell or book anything. Size does not exempt you. Public trackers that count these cases consistently find that most businesses sued are not large corporations. Small and mid-size companies get demand letters too, often precisely because they are less likely to have addressed it.

A few specifics worth knowing:

• If you take federal funding (this catches a lot of nonprofits and healthcare organizations), you may also be on the hook for Section 504 and Section 508, which are stricter than a general ADA reading. That is a separate and higher bar.
• State laws can add their own exposure. California’s Unruh Act is the one that generates the most website claims.
• “We’re B2B” or “we’re local” does not reliably get you out of it. The question is whether the public can use your site, not who your ideal customer is.

None of this means every small business is about to be sued. It means the risk is real, it has trended up nearly every year since 2017 according to the firms that track it, and it is cheaper to address on your own schedule than on a plaintiff’s.

WCAG, in plain English

WCAG is organized around four ideas. Your site should be:

• Perceivable. People can perceive the content. Images have meaningful alt text, videos have captions, and text has enough contrast against its background to be readable.
• Operable. People can operate it. Everything works with a keyboard alone (no mouse required), nothing flashes in a way that can trigger seizures, and users have time to complete tasks.
• Understandable. People can understand it. Navigation is predictable, form fields are labeled, and error messages explain what went wrong in words.
• Robust. It works with assistive technology. The underlying code is structured so screen readers and other tools can interpret it correctly.

There are two version numbers you will see: WCAG 2.1 and WCAG 2.2. Version 2.2 is current and adds a handful of newer criteria on top of 2.1 (things like accessible alternatives to dragging, and consistent help). And there are three conformance levels: A, AA, and AAA. The one almost everyone means, and the one courts and contracts reference, is AA. Aim for WCAG 2.2 AA and you have covered 2.1 AA as well.

How to check whether your website is compliant (a 10-minute first pass)

You can get a rough read yourself before you pay anyone. This will not certify anything, but it will tell you whether you have a small problem or a big one.

• Run an automated scanner. Free tools like WAVE (wave.webaim.org) or the Lighthouse accessibility audit built into Chrome’s developer tools will flag obvious failures: missing alt text, low contrast, unlabeled form fields. Run it on your homepage and one or two key pages (a contact form, a product or service page).
• Try to use your site with only the keyboard. Put the mouse down. Press Tab to move through the page. Can you reach every link, button, and form field? Can you see where you are (a visible focus outline)? Can you open and close menus? Can you complete your main action, like submitting a contact form, without ever touching the mouse? If you get stuck, so does a keyboard user.
• Check your contrast. Faint gray text on white, or light text on a busy image, is the single most common failure. WebAIM’s contrast checker will tell you if your body text and buttons pass AA.
• Turn on a screen reader for two minutes. VoiceOver is built into every Mac (Cmd+F5). Close your eyes and listen to your homepage. If it reads as a sensible sequence, good. If it reads as a wall of “link, link, image, button” with no structure, that is a real problem for the people who rely on it.

Important caveat: automated scanners catch only a fraction of real issues, commonly cited as roughly a quarter. A clean Lighthouse score does not mean you are compliant. It means the easy stuff looks okay. The issues that actually get sites into trouble (keyboard traps, unusable forms, meaningless link text, broken screen-reader flows) mostly need a human to catch.

What usually fails (and what it costs you)

Across small business sites, the same handful of issues show up again and again:

• Images without meaningful alt text.
• Low color contrast on text and buttons.
• Forms with no real labels, so a screen reader announces “edit text” with no idea what to type.
• Menus and modals that cannot be operated or closed with a keyboard.
• Link text like “click here” or “read more” that means nothing out of context.
• Poor heading structure, so the page has no navigable outline.

The cost of ignoring these is not only legal. It is customers who leave because they could not check out, book, or contact you. Roughly one in four US adults reports some form of disability, and a site that fights them is a site that loses their business quietly, long before any lawyer is involved.

Why “accessibility overlay” widgets don’t fix this

You have probably seen the little accessibility button that pops up in a corner and promises instant ADA compliance. Skip it. Overlay widgets do not deliver WCAG conformance, because real accessibility lives in your page’s markup, structure, and content, not in a script bolted on at load time. Worse, overlays have become a target in their own right: a meaningful and growing share of accessibility lawsuits now name sites that had an overlay installed. Paying for the illusion of compliance can make you more visible to the people filing claims, not less. The fix is the underlying code, not a widget over the top of it.

What to actually do next

If your 10-minute pass came back clean-ish, keep it that way: bake accessibility into how you add content, and re-check when you redesign.

If it came back messy, the honest path is a proper audit against WCAG 2.2 AA, followed by actually fixing what it finds. A report on its own does not make anyone’s site accessible. The fixes do. That is the part most vendors leave to you, and it is the part that matters. We handle both: we run the accessibility audit and remediation ourselves, fix the code, and re-test to prove conformance, with no overlays. If you are a nonprofit, where funding and Section 508 raise the stakes, we have a dedicated path for accessibility compliance for nonprofits.

Wherever you are on that spectrum, getting ahead of it or already holding a demand letter, the work is the same and it is doable.