ADA website compliance: a practical checklist for small businesses

What the ADA says about websites

The Americans with Disabilities Act prohibits discrimination against people with disabilities by businesses open to the public (Title III) and by state and local governments (Title II). The Department of Justice's guidance on web accessibility states that it has no regulation setting out detailed technical standards for private-business websites, and it points to existing standards such as the Web Content Accessibility Guidelines (WCAG) as helpful guidance. See DOJ's web accessibility guidance.

In practice that means there is no checkbox to tick. People who raise accessibility complaints, and the lawyers and consultants who evaluate them, generally measure a site against WCAG 2.1 or 2.2 at Level AA. Government websites are different: the DOJ has set WCAG 2.1 Level AA as the standard for state and local governments, with dates covered in the Title II web rule guide.

A checklist you can work through

1. List your pages that matter most. Start with the home page, your main product or service pages, contact and booking forms, and the checkout or sign-up flow. These are where a barrier costs you a customer.
2. Run an automated scan on each. Use the free Clir scan or another checker from the comparison of free accessibility checkers. Scanners find a subset of problems quickly: missing image descriptions, low contrast, unlabeled form fields, empty links and buttons.
3. Test by hand for 10 minutes. Put the mouse away and use Tab, Shift+Tab, Enter and Space to move through the page and complete a purchase or form. Zoom the browser to 200 percent. Our guide to checking a site by hand walks through it.
4. Fix by impact. Anything that stops someone from completing a task (a form they cannot submit, a menu they cannot reach by keyboard) comes before cosmetic issues. The fix guides show the common ones with code.
5. Recheck after each change. Themes, plugins and content edits reintroduce problems. Run the same scan again and compare.
6. Publish an accessibility statement. Say what you aim for, what you know is not yet fixed, and how to reach a person. The accessibility statement guide has a template.
7. Make a contact route that works. If someone cannot use part of your site, give them an email or phone number and answer promptly.
8. Keep dated records. Save scan results, what you changed and when. If you ever receive a complaint, a record of steady improvement is useful. See what to do with a demand letter.
9. Put it on the calendar. Recheck after any redesign, theme update or new app, and at least a few times a year.

What matters most for a small business site

• Every image that carries meaning has a text alternative (how to write alt text).
• Text has enough contrast against its background (contrast guide).
• Every form field has a visible label and clear error messages (form labels).
• Everything works with a keyboard and shows where focus is (keyboard focus).
• Links and buttons say what they do (link and button names).

The ADA is one part of running a website. For privacy, cookie and email basics alongside accessibility, see the small business website compliance checklist.

Who the ADA covers, in plain terms

Title III of the ADA applies to private businesses that are open to the public. The law calls them “places of public accommodation,” and the list is broad: shops, restaurants, hotels, medical and legal offices, gyms, theaters, schools, and many other businesses that serve customers.

The Department of Justice's position is that the ADA's nondiscrimination rules apply to what these businesses offer online, not only in the building. Courts have not all agreed on how far that reaches, and some have asked whether a website must be tied to a physical location. Because the answer can differ by state and circuit, it is a question for an attorney who knows your area.

There is no general exemption for small businesses. The statute does exempt private clubs and religious organizations from Title III (42 U.S.C. 12187). The law also recognizes limits such as “undue burden” for some obligations, but whether those limits apply to a particular website is a legal judgment, not something to assume.

Common misunderstandings

Who you are making the site usable for

Accessibility is easier to prioritize when you picture the people involved. These are common groups and the changes that help them most.

A worked example: a neighborhood bakery with online ordering

This is an illustration, not a real case. A bakery has five kinds of page: the home page, a menu, an order form, a checkout and a contact page. The owner follows the checklist in order.

1. Scan. A free scan of each page finds product photos without descriptions, light gray text on the menu, and an "Order now" button whose white text on a pale orange background is hard to read.
2. Hand test. Using only the keyboard, the owner finds that the pickup-date picker cannot be opened without a mouse, so a customer who relies on a keyboard cannot place an order. This is the most serious problem, and the scanner did not flag it.
3. Fix by impact. The date picker is replaced with a labeled date field. Next the button color is darkened, then alt text is written for each menu photo, then the gray text is darkened.
4. Recheck. Each fix is confirmed with a rescan and another keyboard pass.
5. Document and publish. The owner saves the before-and-after scan results, adds an accessibility statement with an email address, and puts a quarterly reminder on the calendar.

The whole exercise takes a few focused sessions for a small site. The order matters: the issue that stopped orders came from the hand test, not the scan, which is why the checklist uses both.

Setting priorities with a simple severity scale

Not every finding deserves the same urgency. A rough scale keeps the work moving.

Third-party tools and content you do not control

Most business sites include code written by someone else: a booking widget, a payment page, a chat bubble, an embedded map, a video player. Your visitors will not know or care who wrote it. If a booking widget cannot be used by keyboard, your customer cannot book.

• List every outside tool that visitors use to do something, not just look at something.
• Test each one with a keyboard and zoom, the same way you test your own pages.
• Ask the vendor for an accessibility conformance report (see VPATs explained) and how they handle reported problems.
• Have a fallback such as a phone number or an email address for anything that stays hard to use.
• Replace PDFs with web pages where you can. A menu or price list in HTML is far easier to make accessible than a scanned PDF.

Apps, email and social media

The same principles apply outside the website. If you publish a mobile app, test it with the phone's built-in screen reader and large text setting. In email, use real text and descriptive alt text rather than a single large image. On social media, use the platform's alt text feature and add captions to video.

What to record and keep

Records show steady, good-faith work. They are also practical: they tell you what you already fixed and when to check it again.

A quarterly routine you can keep

1. Week 1: scan the pages that matter most and compare with the last results.
2. Week 2: run the 10-minute keyboard and zoom check on the home page, a key content page, your main form and checkout.
3. Week 3: fix what you found, starting with blockers.
4. Week 4: rescan, update your records and, if anything changed, your accessibility statement.
5. After any redesign, new plugin or theme update: repeat the first two steps right away instead of waiting for the quarter.

What it costs and a note on tax

Cost depends on how many problems exist, how complicated your templates are and who does the work. A small site with a good theme may need a few hours of fixes. A store with many custom apps needs more. Free scans and hand checks cost only time, and a detailed guide to options is in what an accessibility audit costs.

Some federal tax incentives exist for small businesses that spend money on accessibility, and the IRS describes the disabled access credit on its Form 8826 page. Whether website work qualifies is a question for a tax professional, so ask before counting on it.

Turn accessibility findings into improvements

Automated testing is the quickest way to find the technical issues on a page, and it works best alongside a few checks only a person can make: whether alt text is meaningful, whether the reading order makes sense, whether captions are accurate and whether custom widgets work well with a screen reader. Clir lists items like these separately for review, so its confirmed findings stay clean and actionable. That is why the checklist above includes hand testing; the DOJ web guidance takes the same approach.