The short answer
If your business is open to the public, the U.S. Department of Justice says the Americans with Disabilities Act applies to your website. There is no detailed federal technical rule for private businesses' websites, so the practical standard most people build and test against is WCAG, the Web Content Accessibility Guidelines.
The good news: most of what makes a site accessible is ordinary careful building. Readable contrast. Text descriptions on images. Forms with real labels. A site you can use without a mouse. Headings that make sense. You can check most of it yourself in about an hour, with free tools, and this guide shows you how.
Not legal advice
We build websites. We're not lawyers, and nothing here is legal advice. If you've received a demand letter or a lawsuit about your website, talk to a lawyer who handles ADA matters before you reply, pay anything or change the site.
What the law and the DOJ actually say
The clearest source is the Department of Justice's own page, the DOJ's web guidance on ADA.gov, dated March 18, 2022. Here is what it says, in plain terms:
- Title III of the ADA covers businesses that are open to the public. If you serve customers, patients, clients or guests, read it as including you.
- The DOJ has taken this position for a long time. In its words, it "has consistently taken the position that the ADA applies to web content", going back to 1996.
- There is no detailed technical regulation for businesses. The guidance says the DOJ "does not have a regulation setting out detailed standards", and that businesses "have flexibility in how they comply".
- WCAG is named as helpful guidance. The guidance points to WCAG and the federal government's Section 508 standards as existing technical standards businesses can use.
- It names the usual barriers: poor color contrast, using color alone to show information, images without text alternatives, videos without captions, forms without labels, and sites that only work with a mouse.
- It names settlements. The DOJ lists Title III website settlements with Rite Aid, Teachers Test Prep, H&R Block and Peapod.
Flexibility doesn't mean optional. It means the DOJ hasn't said exactly which test to pass. WCAG is the obvious choice: it's specific, free to read, and the standard the DOJ itself points to.
The 2024 rule is for governments, not businesses
On April 24, 2024, the DOJ published a separate rule under Title II of the ADA, which covers state and local governments: cities, counties, public schools, public colleges and similar bodies. It sets web accessibility requirements for them. It does not cover private businesses. Sales emails sometimes quote it as if it applies to every website. It doesn't. If you run a site for a city, a county or a school district, though, read the rule itself and talk to whoever handles compliance there.
Lawsuits and demand letters
The DOJ isn't the only route. Private individuals do bring lawsuits over websites they couldn't use, and many small businesses first hear about any of this from a demand letter: a letter from a law firm saying the site has barriers and asking for fixes and a payment. We won't print numbers on how often or what it costs, because we have no source we trust. It happens to small businesses, not only national chains.
If one lands on your desk:
- Don't ignore it, and don't reply on your own. Take it to a lawyer who has handled ADA claims before you answer, pay or promise anything.
- Record the site as it is. Screenshots of the pages named, with the date. Your lawyer may want to know exactly what was there.
- Read the barriers it lists. They're often real and specific: an unlabeled form, images with no alt text, a menu that doesn't work with a keyboard.
- Fix them properly and write it down. What you checked, what you changed, when, and who did it.
- Be wary of anyone selling a one-line fix in response. More on that below.
As builders, we'll say this much: the barriers these letters describe are the ones in the checklist below. They're common and fixable, and fixing them helps real customers either way.
What accessible actually means
WCAG is published by the World Wide Web Consortium, the group that writes web standards. The current version is 2.2. It has three levels: A is the minimum, AA is what most organizations aim for, and AAA is the strictest and isn't expected of whole sites. We aim our own builds at WCAG 2.2 AA, and say so on our accessibility statement.
The guidelines are long, but they boil down to four questions about every page:
- Can people perceive it? Text can be read at enough contrast, images have descriptions, videos have captions.
- Can people operate it? Everything works with a keyboard, nothing flashes in a way that could trigger a seizure, nobody gets timed out of a form without warning.
- Can people understand it? Plain labels, clear errors, menus that behave the same on every page.
- Does it work with their tools? Clean code that screen readers, voice control and zoom can rely on.
Who that helps is wider than most owners expect: blind and low-vision visitors on screen readers, people who zoom everything up, people with color blindness, deaf and hard-of-hearing visitors watching your videos, people with a tremor or an injury who use a keyboard instead of a mouse, and a lot of older customers who'd never call themselves disabled but squint at light gray text. Add anyone on a phone in bright sun.
If you run a clinic or a practice, our medical and dental web design page covers why the bar is higher there.

A practical checklist
These eleven items cover the barriers the DOJ guidance names and most of what we find when we look at a small-business site. None of them needs special software to check.
| What to check | What good looks like | Quick test |
|---|---|---|
| Color contrast | Body text at least 4.5 to 1 against its background; large text, icons, input borders and focus outlines at least 3 to 1 | Paste your text and background colors into a contrast checker |
| Alt text on images | Every meaningful image has a short description of what it shows or does; decorative images are marked empty so screen readers skip them | Run the page through an alt text checker, then read the descriptions out loud |
| Keyboard navigation | Every link, menu, button and form field works with Tab, Shift+Tab, Enter, Space and the arrow keys, in a sensible order, with no traps | Put the mouse away and try to book, call or send a form |
| Visible focus | You can always see where you are: a clear outline or highlight moves with the keyboard | Tab through the page and watch for the moment you lose track |
| Form labels and errors | Every field has a visible label (not just placeholder text); errors say in words what's wrong and keep what was typed | Submit the form empty, then with a bad email address |
| Headings | One main heading per page, then sections in order, chosen for structure, not for font size | Use a headings outline (any screen reader lists them) and see if it reads like a table of contents |
| Link text | Links say where they go: "See our furnace repair prices", not "Click here" or six "Read more" links | Read only the links on the page. Do they make sense alone? |
| Captions and transcripts | Videos with speech have accurate captions; audio has a transcript | Watch your own video muted |
| Zoom and reflow | Text can be enlarged to 200% without losing content, and the page reflows to a narrow column with no sideways scrolling | Zoom the browser to 200%, then 400% |
| No color-only cues | Required fields, errors, sale prices and chart lines are marked with words or shapes as well as color | Look at the page in grayscale. Is anything lost? |
| Accessible PDFs | Real text (not a scan), tagged headings, a reading order and labeled form fields, or the content moved onto a web page | Try to select the text in the PDF. If you can't, a screen reader can't read it either |
Based on WCAG, the guideline set the DOJ points to in the DOJ's web guidance on ADA.gov. The ratios are WCAG's level AA contrast targets.
The ones people get wrong most
Contrast. Light gray on white looks clean in a design file and fails on a phone outdoors. Brand colors are the usual trap: a pale yellow or a mid-green button with white text often misses 4.5 to 1. You don't have to change your brand. Use the brand color for backgrounds and shapes, and darken it a step for text.
Alt text. Write what the image is there to say. A photo of a finished deck on a deck builder's page is "Cedar deck with built-in bench and black railings", not "image1.jpg" and not "best deck builder Buffalo MN deck builder". A logo's alt text is the business name. Decorative shapes get empty alt text so screen readers skip them. If an image contains words, like a flyer or a menu photo, those words need to be in the alt text or, better, on the page as real text.
Forms. Placeholder text inside the box disappears when you start typing and isn't a label. Mark required fields with the word "required", not only a red star. When something's wrong, say what in words ("Enter a phone number with area code") next to the field, and don't wipe what the person already typed. Our guide to forms that actually deliver goes further on getting forms right.
PDFs, embeds and third-party widgets
A lot of barriers aren't in your pages at all. They're in the things you attach or embed.
PDFs. Menus, intake forms, price sheets and brochures often go up as scanned images inside a PDF. A screen reader sees a blank page. The fix, in order of preference: put the content on a real web page (better for Google too), or export the PDF from the original Word or design file as a tagged PDF with real text, headings and labeled form fields. Restaurants, see our restaurant web design page: the menu belongs on the page anyway.
Booking, chat, reviews and payment widgets. Your customer doesn't know or care that the scheduling tool is someone else's code. If they can't book with a keyboard, they can't book. Ask the vendor for their accessibility conformance report (often called a VPAT), run the keyboard test below on it, and if two tools do the same job, pick the one that passes.
Maps and video. Put the address in text next to any map. Automatic video captions are a start, but read them: they get names and numbers wrong.
Why an overlay widget isn't the fix
An overlay is a script you paste into your site that adds an accessibility button or toolbar, or claims to find and fix problems automatically. They're sold hard, often with the word "compliance" in the pitch, and often right after a demand letter arrives.
A widely shared view among accessibility practitioners is that overlays don't fix the underlying problems. A form field with no label, a menu that traps the keyboard, a scanned PDF or a video without captions is still there in the code after the overlay loads. Many screen reader users already have their own software set up the way they like it, and an extra layer on top can get in the way rather than help.
We're not going to make claims either way about what an overlay does or doesn't do in a legal dispute; that's a question for your lawyer. As builders, our view is simple: a widget isn't a substitute for fixing the site. The money is better spent on the checklist above.
How to test your own site in about an hour
You don't need to be technical to find most problems. Take your three most important pages (usually home, your main service and contact) through these steps.
- Keyboard only (15 minutes). Click in the address bar, put the mouse aside, and press Tab. Use Tab and Shift+Tab to move, Enter or Space to open things, Escape to close pop-ups. Can you reach everything, see where you are, and send the contact form?
- A screen reader (15 minutes). Most computers and phones have one built in: VoiceOver on a Mac or iPhone, Narrator on Windows, TalkBack on Android. NVDA is a free, widely used screen reader for Windows. Turn one on and listen: do images, links and form fields make sense?
- Zoom (5 minutes). Press Ctrl and plus (Cmd and plus on a Mac) until the browser says 200%, then keep going to 400%. Nothing should overlap or disappear, and you shouldn't have to scroll sideways to read a sentence.
- Contrast (10 minutes). Put your text and background colors into our free Color Contrast Checker. Check body text, buttons, links, and any text laid over a photo.
- Images (10 minutes). Run each page through the Image Alt Text Checker. It lists images with missing alt text. Then read what it finds: would it make sense to someone who can't see the picture?
- Automated scan (5 minutes). Chrome's built-in Lighthouse report (right-click, Inspect, then the Lighthouse tab) includes an accessibility audit. It catches missing labels and contrast failures, but can't tell whether alt text is accurate, so a perfect score is a start, not a finish.
Worked example
A dental office in Maple Grove runs the hour on its home page, services page and new-patient page. The keyboard test finds the online booking widget can be opened but not closed without a mouse. The screen reader reads the team photo as "IMG_4471". The contrast checker fails the light blue hours text on white. The new-patient forms are scanned PDFs. None of it is exotic: they switch the booking tool to an embed that works with a keyboard, write five lines of alt text, darken the blue a step, and move the intake questions onto a web form. That's a few hours of work, done in order of how badly each problem blocks a patient.
This is an example we've set up to show the method, not a client.

Fixing what you find, in the right order
Start with whatever stops someone becoming a customer, then work outward.
- The ways to reach you. Phone number as real, tappable text. Contact and quote forms that work with a keyboard and a screen reader. Booking that works without a mouse.
- Navigation. A menu that opens with the keyboard, a skip-to-content link, visible focus.
- Contrast and text size across the whole site, usually fixed once in the stylesheet.
- Images and alt text, starting with the pages that get the most visits.
- Video captions, PDFs and embeds.
- Everything else, page by page.
How easy this is depends on what the site is built on. On Wix or Squarespace you control alt text, headings and colors, but not how the platform's own menus and widgets are coded, so pick a template that already works with a keyboard. On WordPress, the theme and every plugin decide most of it. On a custom-coded site it's all in your builder's hands, which is why we build to the guidelines from the first line.
If the list is long and the site is old, it can cost less to rebuild than to patch. A redesign is the moment to get it right underneath, not just repaint it.
Publish an accessibility statement
An accessibility statement is a short page saying what you aim for and how to report a problem. It gives a customer who hits a barrier somewhere to go other than away. Ours is at stonekept.studio/accessibility if you want an example of the shape.
Keep it honest and short:
- The standard you aim for (for most small businesses, WCAG 2.2 AA).
- What you've done: the testing and the main things you built in.
- Anything you know isn't there yet, and when you expect to fix it.
- A real email address and phone number to report a problem, and a promise to reply.
- The date you last reviewed it.
Don't claim full compliance unless every page has actually been tested against every guideline.
Keeping it accessible after launch
Sites drift. A pale promo banner, twenty project photos with no descriptions, a new booking tool, this year's price sheet as a scanned PDF. Each change is small; a year of them adds up.
Before you call a page done
- Every page works start to finish with only a keyboard
- You can always see where the keyboard focus is
- Text and buttons pass the contrast check
- Every meaningful image has alt text; decorative ones are skipped
- Every form field has a visible label, and errors are explained in words
- Headings run in order and read like an outline
- No link says only "click here" or "read more"
- Videos have corrected captions
- The site works at 200% and 400% zoom without sideways scrolling
- Nothing relies on color alone
- PDFs are real, tagged text, or the content is on a web page instead
- There's an accessibility statement with a way to report a problem
Run the hour-long test whenever you add a new kind of page or a new tool, and at least once a year on your top pages. Our website maintenance checklist folds it into the rest of the yearly upkeep. On one of our care plans, edits and new pages are made for you, so the alt text, headings and contrast go in with the change instead of being forgotten. If you'd like us to look at a site you already have, send it over.
Want a straight answer for your business?
Every Stonekept build is custom-coded, hosted on Cloudflare and kept on a monthly plan. Prices are public: builds from $2,200 with care from $199/mo. See pricing or tell us about your project and we'll give you an honest read, even if that's not us.
