Website Accessibility for Small Business: What the ADA Actually Asks of You

What the Law Says, and What It Does Not

The Americans with Disabilities Act was signed in 1990, before most businesses had a website, and its text never mentions one. Title III requires places of public accommodation — restaurants, shops, medical offices, gyms, hotels and most other businesses open to the public — to serve people with disabilities on equal terms. The Justice Department’s published guidance says that obligation extends to the goods and services a business offers online, and the department has pursued it that way for years. You can read its plain-language guidance on ADA.gov.

What the department has never done is publish a technical rule for private businesses saying exactly what an accessible website is. It did that in 2024 for state and local governments, adopting WCAG 2.1 Level AA — the Web Content Accessibility Guidelines published by the W3C — and the compliance dates for that rule have since been pushed back. Private businesses have no equivalent. So the standard is set the slow way: by complaints, settlements and court decisions, nearly all of which measure sites against WCAG 2.1 AA.

Two more layers sit on top. Federal courts disagree about whether a business with no physical location is covered at all. And several states have their own civil rights laws that plaintiffs use alongside the ADA, which is why so many of these cases are filed in New York and California. If you sell into the European Union, the European Accessibility Act has applied to many consumer-facing digital services since June 2025. None of that changes the engineering. It changes how much a failure can cost.

The Demand Letter Usually Starts as a Scan

The owners we talk to tend to picture a frustrated customer who tried their site, could not use it, and went to a lawyer. That happens. Much of the volume, though, comes from a small number of law firms filing large numbers of very similar complaints, and the first step is usually software: an automated checker run across many sites to find the ones with obvious, machine-detectable failures. A small business site with missing image descriptions and an unlabeled contact form shows up in that sweep exactly like a large retailer does, and it is far less likely to have a lawyer on retainer.

That leads to the most useful idea on this page. Your website has two accessibility audiences, and they find different problems.

What a scanner finds

Images with no text alternative. Form fields with no label. Text with too little contrast against its background. Links and buttons with no readable name — the icon-only menu button, the “click here” repeated nine times. Pages with no language declared. Headings that skip levels or do not exist. These are cheap to detect, cheap to fix, and highly visible. They are what makes a site an easy target, and they are the first thing to clear.

What only a person finds

Automated tools catch a minority of real problems. The rest need someone with a keyboard and a screen reader. Can you reach and operate every control without a mouse, and can you see where you are? Does a pop-up trap the keyboard so you cannot close it? When a form rejects an entry, does the error say what is wrong, and is it announced? Does the booking widget time out before a screen reader user can finish? Is the menu a scanned image in a PDF? Do the videos have captions? These are the failures that actually stop disabled customers from buying, and they are where a scanner-only “fix” leaves you exposed.

The Overlay Is a Promise, Not a Repair

The fastest-selling answer to all this is the accessibility overlay: one line of script, a small floating icon, and a claim that the site is now compliant. It is attractive because it skips the work. That is also why it does not hold up. An overlay runs on top of the page after it loads. It can enlarge text or change colors, and it can guess at some missing labels. It cannot rebuild a checkout that was never written to work with a keyboard, and its guesses are sometimes wrong in ways that make the page harder to use with the screen reader the customer already relies on.

The market has noticed. Sites with overlays installed continue to be named in lawsuits, and in 2025 the Federal Trade Commission finalized an order against accessiBe, one of the best-known vendors, barring it from claiming its product could make any website WCAG-compliant without evidence to support that. If a vendor tells you a widget makes you compliant, treat that as a sales claim and ask what the underlying code looks like.

Fix the Path That Makes You Money First

Accessibility audits tend to sprawl into a list of hundreds of issues across every page, which is where small businesses give up. Do not start there. Start with the handful of actions that actually produce revenue: the phone number, the contact or quote form, the booking or reservation flow, the checkout, and whatever page people use to decide — the menu, the service list, the price sheet. Walk each one end to end with only a keyboard, then with a screen reader such as VoiceOver on a Mac or iPhone or NVDA on Windows.

This order is right for two reasons. These paths are where a disabled customer gets turned away, which is both lost business and the specific failure a complaint describes. And they overlap heavily with the problems behind poor mobile conversion — tiny tap targets, forms that fight the user, pop-ups that cover the button. Fixing the path for a screen reader user usually fixes it for the person on a phone in bright sunlight too. If your site gets visitors but not inquiries, the same walk-through is worth doing for the reasons in traffic but no leads.

You Inherit Every Widget You Embed

Most small business websites are partly made of other companies’ software: the booking calendar, the chat bubble, the payment form, the embedded reviews, the map, the online ordering system. To your customer, and in a complaint, all of it is your website. A perfectly built site with an inaccessible scheduling widget in the middle of it still turns the customer away at the step that matters.

Before you choose or renew one of these tools, ask the vendor for an Accessibility Conformance Report, usually prepared using a template called a VPAT. A vendor that has never heard of it is telling you something. A vendor that has one, recently dated, with honest notes about where it falls short, is the one to pick. Then test the embedded piece yourself with a keyboard, because the report describes the product and you are using a configuration of it.

Accessible and Readable by AI Are Mostly the Same Work

Here is the part almost nobody says to small business owners. The structure a screen reader depends on — real headings in a logical order, text as text rather than baked into images, labeled forms, buttons that say what they do, content in the page rather than in a PDF — is the same structure search engines and AI assistants rely on to understand what you do. A restaurant menu uploaded as an image is invisible to a blind customer and very hard for an assistant to quote. The same menu as a properly marked-up page serves both.

We would not claim accessibility work improves rankings by itself. But if you are paying for answer engine optimization on a site full of text in images and unlabeled structure, you are paying to fix the same foundation twice. Done in one pass, through our AEO services or a rebuild, the work counts toward both.

If a Demand Letter Arrives

Do not ignore it, and do not pay or sign anything before a lawyer has read it. Several things are worth knowing before that conversation. Installing an overlay after the letter arrives is not a defense. A record of remediation already underway — an audit, a dated plan, fixes shipped — tends to be useful to whoever represents you. And keep the problem and the response separate: the legal question is your lawyer’s, but the site still has to be fixed either way, and the fix is engineering.

What to Ask Whoever Builds or Fixes Your Site

Five questions sort the serious from the rest, and they belong next to the ones in how to choose a web design agency.

The five questions

Which standard and level will you build to — and will you write it in the contract? How do you test: automated scans only, or manual keyboard and screen reader testing as well? Which third-party tools on my site have you checked, and what did you find? When my staff add a page or upload an image later, what stops them from breaking it again? And do you sell or recommend an overlay? An honest answer to the last one is usually a short no.

The fourth question matters more than it sounds. A site that passes an audit in March can fail by June because someone uploaded a flyer as an image or pasted in a new embed. Ongoing accessibility belongs in website maintenance, not in a one-time project.

Build It In, Rather Than Bolting It On

The cheapest accessible website is the one that was accessible the day it launched. Choosing the right HTML element costs the same as choosing the wrong one; retrofitting the wrong one across forty pages does not. That is why accessibility belongs in the brief for any website build and in the line items covered by the small business website cost guide, not added after a letter arrives.

Our sites are built with Claude Code, which writes semantic, labeled markup by default and makes it fast to fix a pattern everywhere it appears rather than page by page — and we still test the money paths by hand with a keyboard and a screen reader before launch, because no tool replaces that. The goal is not a badge. It is a site where every customer can call you, book you or buy from you, which was the point of having a website in the first place.