Website ADA compliance: what small businesses actually need to do in 2026.

ADA website compliance means building your site so people using screen readers, keyboard-only navigation, or other assistive technology can actually use it, measured against the WCAG 2.2 Level AA standard that courts consistently reference in web accessibility lawsuits. The ADA itself never mentions websites, it was written in 1990, but federal courts have repeatedly ruled that business websites count as "places of public accommodation" under Title III, and thousands of demand letters go out to small and mid-size business websites every year. The good news: most of the fixes are concrete, well-documented, and don't require rebuilding your site.

Does the ADA actually apply to your website?

There's no small-business size exemption written into how courts have applied Title III to websites. Any business open to the public, selling online, or offering services through its site has been found liable in various circuit courts, regardless of company size. The Department of Justice's 2024 rule formally adopting WCAG 2.2 AA applies directly to state and local government sites (Title II), but it also confirmed the standard courts already treat as the practical benchmark for private business websites under Title III. Risk correlates loosely with traffic and visibility, a well-trafficked local business site is a more attractive target than an obscure one, but visibility isn't a legal shield either way.

What a demand letter actually looks like

Most ADA web cases never reach a courtroom. A firm representing a plaintiff sends a demand letter citing specific WCAG failures found on your site, often via an automated scan, and offers to settle for somewhere between $5,000 and $20,000 to avoid litigation. Industry tracking from firms like Seyfarth Shaw and UsableNet has documented several thousand of these federal lawsuits filed per year for over a decade, with small and mid-size businesses making up a large share of targets precisely because they're less likely to have addressed accessibility already. Ignoring the letter is almost always more expensive than fixing the underlying issues.

The core WCAG 2.2 AA fixes that cover most real risk

• ▸Meaningful alt text on every image that conveys information, empty alt on purely decorative ones
• ▸Text contrast of at least 4.5:1 against its background, a common automated-scan failure
• ▸Full keyboard navigation, every interactive element reachable and usable without a mouse
• ▸Visible focus indicators, so a keyboard user can see where they are on the page
• ▸Descriptive link text ("View pricing plans", not "click here")
• ▸Form fields with properly associated labels, not just placeholder text
• ▸Captions or transcripts for video content
• ▸No content that flashes more than three times per second
• ▸Text that resizes up to 200% without breaking the layout
• ▸A skip-to-content link for keyboard and screen reader users

What overlay widgets don't fix, and can make worse

A large category of vendors sell a one-line JavaScript widget promising instant ADA compliance. This is worth saying plainly even though it costs us an easy upsell: accessibility advocates, in an open letter signed by over 800 professionals and organizations, have specifically called out these overlay tools for failing to achieve real compliance and, in some cases, actively interfering with the assistive technology people already use. Several companies that relied solely on an overlay have still been sued, and courts have not treated the presence of a widget as a defense. An overlay can be one small part of a broader effort, but it is not a substitute for actually fixing the underlying HTML.

A practical fix-it checklist

1. 1Run an automated scanner (axe DevTools or WAVE) as a starting point, not a finish line, automated tools catch roughly 30-40% of real issues
2. 2Manually test your key pages using only a keyboard, no mouse, tab through every interactive element
3. 3Manually test with a screen reader (VoiceOver on Mac, NVDA on Windows) on your homepage, contact form, and highest-traffic pages
4. 4Work through the WCAG 2.2 AA fixes above on the pages that failed
5. 5Publish a plain-language accessibility statement describing your commitment and how to report an issue
6. 6Retest accessibility every time you redesign, it's exactly the kind of thing that silently breaks when a template changes

Accessibility and SEO overlap more than people expect

Most of the work that makes a site accessible also makes it more crawlable and better ranking. Descriptive alt text feeds image search the same way it feeds a screen reader. A clean semantic heading structure supports both a keyboard user and the structured data that helps AI search cite you accurately. A fast, keyboard-navigable page is close to identical to the performant page Core Web Vitals already reward. Accessibility work is rarely wasted effort done for its own sake, it's overlapping investment in the same technical foundation that SEO already needs.

Website accessibility isn't a one-time checkbox, it's an ongoing part of maintaining a site, the same way security patches and performance monitoring are. Most of the core fixes above are achievable in days, not months, and they reduce real legal exposure while genuinely improving the experience for a meaningful share of your visitors. If you want your site properly audited rather than patched with a widget, that's work we build into every redesign and rebuild, not sold separately as an afterthought.