Skip to content
Website Accessibility

Does a Small Business Website Need to Be ADA Compliant?

Being small is not a reason to ignore website accessibility. Here is what size changes, why small sites get letters, and a plan that fits a few hours a month.

8 sections · 8 min read
In this article · 8 sections

You run a dental office, a bakery with two locations, or a five-person accounting firm. The website has fifteen pages, a contact form and a map. Then a friend in the same trade mentions a demand letter about their website, or a vendor emails you a scan report full of red, and the question arrives: does a small business website need to be ADA compliant, or is that something only national chains have to think about?

This post is about size. What being small changes, what it does not, why small sites receive letters anyway, and a plan that fits someone with a few spare hours a month rather than a project budget. It is general information, not legal advice.

What being small does not change

The part of the Americans with Disabilities Act that matters for most customer-facing businesses is Title III. Its reach is defined by the kind of business, not the headcount: shops, restaurants, clinics, law offices, gyms, hotels and repair services all serve the public in person, and the law treats them as public accommodations. Congress passed it long before anyone had a company website, so judges in different courts have reached different views on how it applies online.

What you will not find is a line in the Department of Justice’s March 2022 web accessibility guidance saying that small business sites are exempt. That guidance speaks to businesses open to the public in general terms and says their web content should be accessible to people with disabilities. It does not set a lighter technical rule for small companies, and there is no DOJ regulation with a technical standard for Title III websites at all. In practice, demand letters, settlements and audits measure a site against Level AA of WCAG (version 2.1 or 2.2), whoever owns it.

Could the size of your business matter to a legal argument? Possibly, but that is exactly the kind of question only your own lawyer can weigh, using facts about your business. For planning the technical work, assume size is not a shield.

For the wider picture, including how the government and federal-agency rules differ, read our overview of how the ADA applies to business websites.

Why small sites get letters too

A website is public in a way a shop floor is not. Anyone, anywhere, can load your contact page and run a free scanner over it in a minute. Nobody has to visit your town or know your name.

Small sites also repeat each other’s faults. Many start from one of a few popular themes, add the same form and slider plugins, and then sit untouched for years. The result is a familiar set of problems:

  • contact or booking forms whose fields have placeholder text but no real label
  • light gray text on white that fails the 4.5:1 contrast ratio
  • a theme that removes the focus outline, so keyboard users cannot see where they are
  • a hero slider that moves on its own with no pause button
  • a logo and photos uploaded without alt text
  • the menu or price list posted as a scanned PDF

None of these are exotic. They are what an automated report flags first, and they are what a real customer using a screen reader or a keyboard runs into first. If a letter has already reached you, stop here and read what to do after a demand letter arrives before changing anything on the site.

Does a small business website need to be ADA compliant? The practical answer

When an owner asks “does a small business website need to be ADA compliant?”, the legal answer belongs to a lawyer. The practical answer is shorter. If the public uses your site to call you, book you, order from you or find your hours, then people who use screen readers, keyboards, voice control and screen magnifiers are among those visitors. The barriers that would appear in a demand letter are the same barriers that make those customers give up and phone a competitor.

So the useful goal is not a badge that says compliant. It is a site that works toward conformance with WCAG 2.2 AA, with the important tasks fixed first and a written record of what was done. That goal makes sense whatever any court eventually decides.

A proportionate plan for a small budget of time

Large organizations audit every page. You do not need to start there. The sensible way to approach ADA for small business websites is to work from the jobs your site actually does.

  1. Write down the tasks. A small business site usually has only a handful: call or email, book an appointment, read the menu or price list, find the address and opening hours, perhaps pay an invoice.
  2. Find the templates behind those tasks. Usually the home page, one service page, the contact page, the booking page and a blog post. On WordPress, fixing a template or a reusable block fixes every page built from it, which is why this step saves so much time.
  3. Look at those pages yourself. Spend half an hour with the owner’s self check for ADA basics, which covers keyboard, zoom, contrast, forms and video. If you would rather someone else take a first look, request a free website accessibility check.
  4. Fix blockers first. A blocker stops a task completely: a form that cannot be submitted with the keyboard, a CAPTCHA puzzle with no alternative, a services menu whose submenu appears only under a hovering mouse, a booking calendar a screen reader cannot read.
  5. Then fix what makes tasks hard. Contrast, missing alt text, link text like “click here”, headings chosen for their size, error messages shown only in red.
  6. Write down what you changed and when. A simple dated list is enough. It helps whoever works on the site next, and your lawyer will want it if anything legal ever comes up.
  7. Book a recurring slot. An hour a month on the calendar does more than one heroic weekend every few years.

Who fixes what on a typical small site

Some fixes are content you can change in the editor. Others live in the theme or a plugin and need a developer. Knowing which is which keeps you from spending an afternoon on something you cannot reach.

Area What tends to go wrong Usually fixed by
Contact and booking forms No visible labels, errors shown only by color, CAPTCHA puzzles Developer, plus form plugin settings
Main menu Submenus open only on hover, mobile toggle not reachable by keyboard Developer (theme)
Images and logo Missing or filename alt text You, in the media library
Colors Pale text, buttons that blend into the background Developer, with your sign-off on brand colors
Headings and links Headings picked for size, vague link text You, in the editor
Video No captions, autoplay with sound You, through the video host’s caption tools
Menus and price lists Scanned PDFs with no text layer You, by moving the content onto a page

What can wait, and what cannot

Being proportionate means choosing. A blog post from six years ago that nobody reads can wait. The contact form cannot. A PDF archive of old newsletters can wait. This month’s menu cannot.

One thing that should not happen is buying a toolbar widget as a shortcut. It sits on top of the page and leaves the form, the menu and the PDF exactly as they were. If you want a broader list of things to look at once the urgent items are done, our general accessibility checklist is written for small businesses too.

Keeping a small site from sliding back

Small sites rarely break all at once. They drift. A new staff member uploads photos without descriptions, a plugin update changes the form markup, someone adds a pop-up for a holiday offer that traps keyboard focus.

A light monthly habit catches most of it: tab through the contact form after updates, glance at the alt text on anything new, look at any page added since last month. If the site is already on monthly WordPress maintenance, ask for those checks to be part of it. For background on every part of this subject, from audits to forms to media, browse our website accessibility hub.

Frequently asked questions

Is there an exemption for very small businesses?

Do not assume one. DOJ’s web guidance speaks to businesses open to the public in general terms and does not set a separate rule for small companies. Whether anything about your size matters legally is a question for your own lawyer. For the technical side, plan as if the same WCAG 2.2 AA benchmark applies to you.

My site is only a brochure with no online sales. Does that matter?

It changes which tasks matter, not whether barriers matter. A brochure site still lets people find your phone number, hours, address and services, and often a contact form. Those are the parts to make work with a keyboard, a screen reader and zoom first. A lawyer can tell you how the law views sites like yours.

Should I start with the home page or the contact form?

Start with whatever page completes the most important task, which for most small businesses is the contact or booking form. A beautiful, accessible home page does not help if the form at the end of the journey cannot be filled in. Fix the form, then the menu that leads to it, then the home page.

Can someone on my staff do the fixes instead of a developer?

Some of them. Alt text, heading levels, link wording, captions and moving a PDF menu onto a page are editor tasks that an office manager can learn in an afternoon. Menus, focus styles, form markup and color changes in the theme usually need a developer, because they live in code that every page shares.

If you would rather hand the technical side to someone, this is how our ADA website compliance support works for small businesses: your key pages are reviewed against WCAG 2.2 AA, the barriers are fixed in the theme and content, and each change is written down. We are not lawyers, so legal questions still go to yours.

Next in this series: Accessibility Overlays: What They Do and Cannot Fix