Website ADA Compliance: What a Small Business Actually Has to Do

Most small business owners hear about website accessibility for the first time from a demand letter. A law firm writes to say the site cannot be used by a person with a disability, cites the Americans with Disabilities Act, and proposes a settlement. The owner, who has never thought about it, searches for what the ADA requires of a website and finds a wall of legal and technical jargon.

Here is the plain version: what the law requires, the standard everyone actually uses, the fixes that matter most, and the shortcut that does not work. This is general information from a web design studio, not legal advice. If you have received a letter, talk to a lawyer.

What the law says

The ADA was written in 1990 and does not mention websites. Courts have since treated the websites of businesses that serve the public, stores, restaurants, firms, practices, as places that must be accessible, and the federal government has adopted a specific web standard for state and local government sites. There is no equivalent rule naming a standard for private businesses, which is why the area feels uncertain. In practice it is not: when courts and settlements describe what an accessible website is, they point to the same standard.

The standard: WCAG 2.1 AA

The Web Content Accessibility Guidelines, published by the organization that sets web standards, define accessibility in testable terms. Version 2.1 at level AA is the one courts, settlements and the government rule reference. It is long, but it rests on four ideas: content can be perceived (seen or heard or read by a screen reader), operated (with a keyboard, not only a mouse), understood (readable, predictable) and robust (works with assistive technology). Meeting WCAG 2.1 AA is the practical definition of ADA compliance for a website.

The fixes that matter most

Most accessibility problems on small business sites come from a short list. Fixing these covers the majority of what a demand letter cites.

1. Text people can read

Light gray text on white, tiny type and text over busy photos fail the contrast rule and fail older customers. Text needs enough contrast against its background, needs to be resizable without breaking the layout, and should not be locked inside images.

2. Descriptions on images

Every meaningful image needs alt text, a short description a screen reader can read aloud. A photo of your crew is "The Lackey Designs team at the Fishers studio," not "IMG_4472.jpg." Decorative images are marked as decorative so they are skipped.

3. A site you can use without a mouse

Put the mouse down and press Tab. Can you reach every link, menu, button and form field? Can you see where you are? Can you open the menu and submit the form? Many sites fail here because of a menu or a slider that only works with a mouse. Keyboard access is also what most assistive technology relies on.

4. Headings in order

Screen reader users navigate by headings the way sighted users skim. A page needs one main heading, then subheadings in order, used for structure rather than for making text big. This is also exactly what Google wants, which is one of several places accessibility and SEO overlap.

5. Forms with labels and clear errors

Every field needs a visible label tied to it in the code, not just placeholder text that vanishes when you type. When something is wrong, the error message has to say what and where. A contact form that cannot be completed by a screen reader is a lost customer and a common complaint.

6. Links that say where they go

"Click here" and "Read more" mean nothing read out of context. "Request a free estimate" and "See the web design portfolio" do. Links should also be visibly distinct from surrounding text, not only by color.

7. Video with captions, audio with transcripts

If the site has video, it needs captions. If it autoplays with sound, it should not. If it moves, there should be a way to pause it.

8. No surprises

Nothing should open, move or change without the visitor asking. Popups, auto rotating sliders and content that shifts as the page loads are both accessibility problems and the things everyone hates.

The shortcut that does not work

You will be offered an accessibility overlay: a line of code that adds a toolbar to the site with options for contrast, font size and a screen reader mode, and a promise of compliance. Do not rely on it. Overlays do not fix the underlying problems, they often interfere with the assistive technology people actually use, and businesses running them have still received demand letters and been sued. The accessibility community has been clear about this for years. Accessibility is built into the site's code, or it is not there.

Building it in versus bolting it on

Making an existing site accessible is a repair job: an audit, a list of problems, fixes to the code and content, and a retest. For a small, well built site it is a few hundred dollars. For a large site on a heavy page builder it can be thousands, and sometimes the honest answer is that a redesign costs the same and fixes everything else too.

Building accessibility in from the start costs almost nothing extra, because the choices are the same choices a careful designer makes anyway: readable type, real structure, labeled forms, described images, keyboard friendly menus. That is how we build every site, and it is why the same site tends to score well for SEO and for speed. Our ADA compliance service covers audits, fixes and the design changes that follow.

What to do this week

1. Run the site through our free website grader, which includes an accessibility score and takes a minute.
2. Try the keyboard test: Tab through the homepage, open the menu, submit the contact form without touching the mouse.
3. Look at the site on a phone in bright sunlight. If you cannot read it, neither can anyone else.
4. Check that every image on the homepage has a description, and that the contact form fields have visible labels.
5. If you have an overlay, do not treat it as the answer.

If the grader comes back low, or you have a letter in hand, send us the site's address. We will tell you plainly what it would take to fix, in writing, and Jason replies in under 24 hours.