An ADA compliant website is one that people with disabilities can actually use — with a screen reader, a keyboard alone, low vision, or a hearing impairment. In practice, that means meeting the Web Content Accessibility Guidelines (WCAG) at Level AA, because that's the standard courts, settlements, and the Department of Justice keep pointing to. There is no official government seal for private business sites, so "compliant" really means "measurably accessible."
One thing up front: this article is not legal advice. It's a plain-English explanation from someone who builds websites, so you can have an informed conversation with your attorney if you need one.
What the ADA Has to Do With Your Website
The Americans with Disabilities Act was passed in 1990, before most businesses had a website. Title III requires "places of public accommodation" — stores, restaurants, medical offices, service businesses — to be accessible to people with disabilities.
Whether a website counts as a place of public accommodation has been argued in court for years, and different federal circuits have landed in different places. The Department of Justice's position is that the ADA does apply to websites of businesses open to the public. In 2024 the DOJ finalized a rule for state and local government websites naming WCAG 2.1 AA as the standard; at the time of writing, there is no equivalent rule with a specific technical standard for private businesses.
That legal gray area is exactly why demand letters happen.
The Actual Risk: Demand Letters, Not Regulators
No government inspector is going to audit your bakery's website. The realistic risk for a small business is a demand letter from a plaintiff's law firm.
Here's how it typically works. A firm runs an automated scan across thousands of sites, finds one with missing alt text and unlabeled form fields, and sends a letter on behalf of a client with a disability. The letter says the site violates the ADA and offers to settle — often for a few thousand dollars plus a promise to fix the site — instead of filing a federal lawsuit. Web accessibility lawsuits number in the thousands per year in the US, concentrated in states like New York, California, and Florida, and many of them target small and mid-size businesses rather than national brands.
A few honest observations:
- The letters are real, but they're not random. Sites with obvious automated-scan failures — the kind listed below — are the ones that get flagged.
- Some industries get more attention. Restaurants, retail, healthcare, and anything with online ordering or booking are common targets.
- An overlay widget is not a shield. Sites running accessibility overlays have still received letters and been sued, because the widget doesn't fix the underlying code.
The good news: the fixes that stop scans from flagging you are the same fixes that make the site genuinely usable for more people, and most of them are also the basics of an SEO-friendly website.
WCAG 2.2 AA in Plain Terms
WCAG is published by the W3C, the body that maintains web standards. Version 2.2 came out in late 2023. It's organized around four principles, shortened to POUR:
| Principle | What it means for your site |
|---|---|
| Perceivable | People can take in the content. Images have text alternatives, videos have captions, text has enough contrast against its background. |
| Operable | People can navigate and use it. Everything works with a keyboard alone, nothing traps focus, users have enough time and aren't hit with flashing content. |
| Understandable | People can make sense of it. Language is declared, navigation is consistent, forms explain errors clearly. |
| Robust | It works with assistive technology. Clean, valid HTML that screen readers and browsers can interpret. |
Each guideline has success criteria at three levels: A (bare minimum), AA (the standard target), and AAA (specialized, rarely required in full). "WCAG compliant" almost always means Level AA, which includes everything at Level A. WCAG 2.2 added a handful of new criteria on top of 2.1, notably minimum sizes for tap targets, keeping the focused element visible rather than hidden behind sticky headers, and not forcing users to re-enter information they already gave.
The 10 Most Common Failures
The same handful of problems show up on nearly every small-business site. Fix these ten and you've addressed most of what an automated scan — or a plaintiff's firm — will find.
- Low text contrast. Light gray text on white, or white text on a pale brand color. WCAG AA requires a 4.5:1 contrast ratio for normal text and 3:1 for large text. Large-scale scans consistently find this to be the most common failure on the web.
- Missing or useless alt text. Every meaningful image needs a text description a screen reader can read aloud. "IMG_4032.jpg" or "image" doesn't count. Purely decorative images should be marked as decorative so they're skipped.
- Form fields without labels. A placeholder that disappears when you start typing is not a label. Every input needs a real, programmatically linked label — "Email address," not just an empty box.
- Empty links and buttons. An icon-only button (a magnifying glass, a hamburger menu, a social logo) with no accessible name reads as "button" to a screen reader. It needs text or an aria-label.
- Not usable by keyboard. Menus that only open on hover, sliders and modals you can't reach with Tab, custom dropdowns that swallow keystrokes — common on template themes with animated menus.
- No visible focus indicator. Many themes remove the outline that shows a keyboard user which element they're on. If you can't tell where you are when pressing Tab, neither can anyone else.
- Broken heading structure. Headings used for styling instead of structure — three H1s, or jumping from H2 to H5 because it "looked right." Screen reader users navigate by headings, and Google reads them too.
- Missing page language. A one-line
langattribute tells assistive tech how to pronounce the page. Easy to fix, frequently flagged. - Video without captions, audio without transcripts. Autoplaying video with sound makes it worse.
- Vague link text and tiny tap targets. "Click here" tells a screen reader nothing about the destination. And WCAG 2.2 expects interactive targets to be at least 24 by 24 CSS pixels, so cramped mobile menus and tiny icon links count against you.
Several of these overlap with the design mistakes that cost you customers generally — accessibility and usability are mostly the same discipline.
How to Check Your Own Site
You don't need to hire anyone to get a first read.
Step 1: Run an automated scan. Run a Lighthouse accessibility report in Chrome DevTools, or install the free WAVE or axe DevTools extensions. These catch only a fraction of possible issues — roughly a third by most estimates — but they catch the exact ones demand-letter scans look for: contrast, alt text, labels, empty buttons, missing language.
Step 2: Do the keyboard test. Put the mouse away and press Tab through your homepage, contact form, and menu. Can you reach every link and button? Can you always see where you are? Can you open and close the mobile menu and popups with Enter and Escape? If you get stuck, that's a keyboard trap.
Step 3: Try a screen reader. VoiceOver is built into every Mac and iPhone; NVDA is free on Windows. Ten minutes of listening to your own homepage is eye-opening — you'll hear every unlabeled button and every "image, image, image."
Step 4: Check what scans miss. Do videos have captions? Does the site work zoomed to 200%? Do form error messages actually explain what went wrong?
If you're on a template platform and the theme itself is failing — hard-coded low contrast, hover-only menus, no focus styles — you may be limited in what you can fix without a rebuild. Our website redesign page covers when that's the smarter path.
Where Built For Rank Fits
We build custom, SEO-first sites with clean HTML, real labels, logical headings, sufficient contrast, and keyboard-friendly navigation from the start, because those are the fundamentals of a well-built site — the same ones Google rewards. We don't sell "ADA certification," and no one honestly can. If your site is failing the checks above and you want a straight answer on whether to patch it or replace it, request a free consultation or see how a $1,500 build works. And if a few alt-text and contrast fixes are all you need, do those yourself this week.