ADA website accessibility is one of those topics most small business owners never think about until a letter shows up from a law firm they have never heard of. I'm TJ Slade, I build small business websites here in Kansas City, and I check every site I build for accessibility before it launches. Not because it is trendy, but because it is the right way to build, and because the legal risk is real and mostly avoidable.
This post is not legal advice. It is what a web designer sees from the inside: what the rules actually say, where most sites fall short, and the fixes that cover the bulk of the problem.
The short answer
If your business is open to the public, the Americans with Disabilities Act very likely applies to your website. There is no official checklist written into the law for private businesses, but the standard everyone measures against, courts and plaintiffs included, is WCAG, the Web Content Accessibility Guidelines. Meeting WCAG at the AA level is the practical target.
The good news: most of the problems that show up in lawsuits are basic, and a well-built site avoids them from the start.
What the ADA says about websites
The ADA was written in 1990, before business websites were a thing, so it never mentions them. Title III of the law covers businesses that serve the public, and the Department of Justice has said plainly that this includes the websites those businesses use to serve people. Its guidance on web accessibility walks through what that means in plain language.
What the DOJ has not done is adopt a specific technical standard for private businesses. Government websites got one in 2024 (WCAG 2.1 AA). Businesses did not. In practice that gap does not protect anyone, because WCAG is what lawyers test against when they decide which sites to send letters to.
Why small businesses get sued
Thousands of website accessibility lawsuits are filed in the US every year, and a large share of them target small and mid-sized businesses. Restaurants, retail shops, medical offices, and service businesses show up again and again.
Many of these cases are filed by a small number of firms that scan sites with automated tools, find the common failures, and send demand letters in bulk. Settling one usually costs thousands of dollars, and settling does not fix the site, so the same business can get a second letter from someone else. Fixing the site is the only thing that actually ends the exposure.

The fixes that cover most of it
WCAG is long, but the same handful of failures show up on almost every small business site I audit. Fix these and you have dealt with most of what automated scanners and real users run into:
- Alt text on images. Every meaningful image needs a short description a screen reader can read out. Decorative images should be marked so they are skipped.
- Color contrast. Light gray text on a white background is the most common failure there is. Text needs enough contrast to read for people with low vision, and for everyone on a phone in the sun.
- Keyboard navigation. Every link, button, menu, and form should work with the Tab and Enter keys, with a visible outline showing where you are.
- Labeled forms. Every field needs a real label, not just placeholder text that disappears when you start typing. Error messages should say what went wrong.
- Headings in order. One main heading per page, then sections and subsections in order. Screen reader users skim a page by its headings, the same way sighted users skim by eye.
- Descriptive links. 'Click here' and 'Read more' mean nothing out of context. The link text should say where it goes.
- Captions on video. Any video with speech needs captions, and auto-generated ones need a quick proofread.
None of this makes a site look worse. Most of it makes the site clearer for everybody, and a few items, like headings and descriptive links, quietly help your SEO too.
Skip the overlay widgets
You have probably seen the little accessibility icon in the corner of some websites, sold as a one-line fix for ADA compliance. I don't recommend them. They do not fix the underlying code, screen reader users often find they make sites harder to use, and businesses running them still get sued. The FTC fined one of the best known overlay companies in 2025 over claims that its tool made sites compliant.
An overlay is a monthly bill for the feeling of being covered. The real fix is in how the site is built, and it is usually a one-time job.

How to check your own site
You can get a rough read on your site in about fifteen minutes without buying anything:
- Put your mouse away and try to use your site with only the Tab and Enter keys. Can you open the menu, reach every page, and submit your contact form?
- Run your home page and contact page through a free checker like WAVE or the Lighthouse report built into Chrome. Look at errors first, not warnings.
- Zoom your browser to 200 percent. Does the page still work, or does text overlap and buttons disappear?
- Turn on your phone's screen reader (VoiceOver on iPhone, TalkBack on Android) and listen to your home page for a minute.
Automated tools only catch part of the picture, so a clean score is not proof of compliance. But a page full of errors is a clear sign the site needs work.
What I do on every build
Accessibility is part of how I build, not an add-on. Every site I launch is checked against WCAG 2.2 AA: contrast, keyboard use, labels, headings, alt text, and screen reader testing on the pages that matter most. It is included in my pricing, not a line item.
If your current site was built on a template or a DIY builder and you are not sure where it stands, reach out. I'll take a look and tell you honestly whether it needs a few fixes or a rebuild.
Plain English
Like this one? Get the next one by email.
One short email every Wednesday morning: one idea, one small fix, and whatever I wrote that week. Free, and unsubscribing takes one click.









