Does the ADA legally require small-business websites to be accessible?

There is no single federal regulation that spells out website rules for private businesses the way there is for physical buildings. But the Department of Justice has stated for years that the ADA's requirement to serve the public applies to a business's website too, and courts have increasingly agreed, measuring accessibility against the WCAG guidelines even without a specific rule. In practice, that legal gray area has not stopped demand letters and lawsuits from being filed against small businesses with inaccessible sites, so treating it as a real risk rather than a technicality is the safer read.

What is WCAG and do I need to know it in detail?

WCAG (Web Content Accessibility Guidelines) is the technical standard courts and regulators point to when they say a website should be accessible. You do not need to read the spec. A handful of its most common failure points - missing alt text on images, low color contrast, unlabeled form fields, and menus that only work with a mouse - cover most of the risk on a simple five-to-ten page local-service site.

What actually triggers an ADA demand letter for a website?

Almost always an automated accessibility scan run against your site, followed by a form letter listing the specific failures it found - usually missing image descriptions, poor contrast, a contact form with unlabeled fields, or a mobile menu that traps keyboard and screen-reader users. It is a volume business built on scanning thousands of small-business sites, not a sign that your business was individually targeted.

Does RunCabin build ADA-compliant websites?

RunCabin sites are built on standard, semantic components - real headings, labeled form fields, alt text on photos, contrast-checked colors, and menus that work with a keyboard - which covers the common failure points that trigger most demand letters. No website builder can promise full legal compliance for every page you might add, but because RunCabin sites are AI-editable, if you spot an issue you can just ask - 'add alt text to my gallery photos' or 'increase the contrast on my buttons' - and it is fixed the same way any other edit is.

RunCabin Blog · Fix-it guide

Is my small-business website ADA compliant?

August 20, 2026 · 8 min read

Short answer: there is no single checkbox that makes a website "ADA compliant," but there is a short, concrete list of fixes that covers most of the actual risk on a small local-service site - and most sites are missing at least a couple of them. If you have never thought about this, you are not alone. Almost nobody builds their first website thinking about screen readers. But accessibility demand letters against small businesses have become common enough that it is worth five minutes to understand what they target and fix the obvious gaps before anyone notices them for you.

Where the ADA actually applies to websites

The Americans with Disabilities Act was written in 1990, long before most businesses had websites, so it never explicitly mentions them. For years the Department of Justice has taken the position that a business open to the public has to serve that public online too, not just at its physical door. Courts have mostly agreed, but there is no single federal rule that spells out exactly what a compliant small-business website looks like - which is a real gap, and part of why this area feels murky even to lawyers.

What has filled that gap in practice is a technical standard called WCAG (Web Content Accessibility Guidelines), now on its second point-release beyond 2.0. It was written for web developers, not judges, but it is what courts and demand letters point to when they say a site fails to serve people with disabilities. You do not need to become an expert in it. You need to know the handful of things it flags most often, because those are the same things that show up in nearly every letter a small business actually receives.

What a demand letter usually is

It is worth being plain about the mechanics here, because the letter itself can feel alarming. In most cases, nobody manually reviewed your business and decided to come after you. A law firm or advocacy group runs an automated scanner against a large batch of small-business websites, gets a list of technical failures back in seconds, and sends a form letter to every site with enough hits. Your plumbing company did not get singled out - your site got caught in a net cast over thousands of others. That does not make the letter less real or the underlying legal exposure less worth addressing, but it does mean the fix is usually mechanical, not existential: close the specific gaps the scan found.

The letters typically point to a small, repeating set of issues: images with no text description for a screen reader, text and background colors that do not contrast enough to read, a contact form where the fields have no labels a screen reader can announce, and a mobile menu or button that only responds to a mouse click and traps anyone navigating with a keyboard.

The handful of fixes that cover most of a local-service site

A simple five-to-ten page site for a trade business is not a hospital portal or an e-commerce checkout flow. It is a homepage, a services page or two, some photos, a phone number, and a contact form. That scope actually works in your favor - there are only a few real gaps to close.

Alt text on every photo. A short, honest description of what is in the image - "finished kitchen repaint, sage green walls, white trim" - not the filename, and not stuffed with keywords. This is the single most common failure flagged in demand letters, because it is the easiest to miss and the easiest to scan for.
Enough color contrast. Light gray text on a white background, or a pastel button with white text, looks clean to a designer and is unreadable to a lot of real users. The standard target is a 4.5:1 contrast ratio for normal-size text - free browser tools will tell you the exact number for any two colors you are using.
Labeled form fields. Your contact form's "Name," "Phone," and "Message" fields need actual <label> elements tied to them in the code, not just placeholder text that disappears the moment someone starts typing. A sighted user does not notice the difference. A screen reader user gets a form with no idea what any box is for.
A keyboard-navigable menu. Tab through your own site using only the Tab and Enter keys, no mouse. If you cannot reach every link and open your mobile menu that way, neither can someone using a keyboard or a screen reader by necessity.
Real headings, not just big bold text. Screen readers let a user jump straight to the next heading to skim a page the way a sighted visitor's eye jumps to bold section titles. If your "headings" are just large font-weight text with no actual heading tag underneath, that shortcut does not exist for them.
Captions if you have a video. Plenty of trade sites now have a short intro video or a job walkthrough. If there is spoken audio, it needs captions - free auto-caption tools on YouTube or your phone's editor get you most of the way there, then a quick proofread catches the misheard words.

That list is not exhaustive of everything WCAG covers, but it is the set that shows up over and over in real demand letters against small local-service sites, and closing all six is well within a weekend, not a redesign.

A five-minute self-check you can run right now

Two free checks, no signup, no developer required:

Tab through your site. Click once on your homepage, then use only the Tab key to move and Enter to activate. If a menu item, button, or form field never gets focus, or you cannot tell where you are on the page, that is a real gap - not a nitpick.
Run a free contrast and alt-text scanner. Browser extensions like WAVE (from WebAIM) or Google's own Lighthouse accessibility audit, built into Chrome's developer tools, will scan a live page in seconds and list exactly which images are missing alt text and which text fails the contrast ratio. Both are free, and neither requires an account.

Run both on your homepage and your contact page - those are the two pages most letters cite - and you will know within five minutes whether you have real gaps or a clean bill.

What to do if you already got a letter

Do not ignore it, and do not panic into signing whatever remediation contract is attached to it. Read exactly what it claims your site fails on - most letters list the specific pages and issues - and check whether the claims are accurate using the free tools above. If they are accurate, fix them; that is usually a few hours of real work, not a few thousand dollars of consulting. If you are unsure whether a response carries legal risk for your specific situation, that is a conversation for a lawyer, not a web design vendor cold-calling you with a "compliance package." The fix and the legal response are two separate questions - do not let anyone bundle them into one expensive sale.

Where RunCabin sits

RunCabin sites are built on standard, semantic components by default: real heading tags, labeled form fields, alt text generated for your photos, and a color palette checked for contrast before it ever ships - the same handful of items from the list above, handled without you having to think about them. That covers the common failure points that show up in most demand letters against sites like the ones we build.

No builder, ours included, can promise a site is permanently and fully compliant against every page you might add later - accessibility is an ongoing practice, not a one-time badge. But because a RunCabin site is AI-editable, closing a gap you do notice is as simple as asking: "add alt text to my gallery photos," or "make the text on my green button darker so it's easier to read." No ticket, no waiting on a designer, no separate compliance vendor - it is handled the same way any other change to your site is handled.

See a real preview of your site

Built for you with your name, your work, and your city - standard accessible components included, no setup fee. Sixty seconds, no card.

See your free site preview →