ADA Website Compliance: A Complete Guide for Small Businesses

ADA Website Compliance: A Complete Guide for Small Businesses

A customer may need a screen reader or keyboard to use your booking form, read a product page or contact your team. This guide describes practical checks for those journeys and explains where to find primary US accessibility guidance. It does not predict litigation or provide advice for a particular legal matter.

What Is ADA Website Compliance?

Title III covers public accommodations, including many businesses and nonprofits open to the public. The DOJ overview explains scope and exclusions. Its web guidance says that covered goods and services offered online must be accessible.

Do not assume every website has the same legal status, or that passing a scan establishes compliance. WCAG is useful for technical evaluation, while the applicable legal duties require a separate assessment.

Distinguish Private Businesses From Public Entities

The Title II web rule applies to state and local governments, not to every private business. It generally uses WCAG 2.1 AA, subject to exceptions. The DOJ's current fact sheet explains the scope and the population calculation.

Following the extension effective April 20, 2026, the technical compliance dates are April 26, 2027 for entities with a total population of at least 50,000, and April 26, 2028 for smaller entities and any special district government. Existing ADA duties continue before these dates. Reviewed October 14, 2026.

Practical Website Checks

Use the WCAG checklist to organize testing, then evaluate essential tasks with people and assistive technology. These checks support remediation; they are not a universal legal checklist.

People Must Be Able to Navigate With a Keyboard

Many people with motor disabilities cannot use a mouse. Your entire website must be operable using only a keyboard. This means every menu, button, form field, and link must be reachable and activatable with the Tab, Enter, and Arrow keys.

Screen Readers Must Be Able to Read Your Content

Blind and low-vision users rely on screen reader software that reads web pages aloud. For this to work, your website needs proper HTML structure: images must have descriptive alt text, form fields must have labels, headings must follow a logical hierarchy, and interactive elements must have accessible names.

Text Must Be Readable

All text on your website must meet minimum color contrast ratios against its background. Light gray text on a white background fails this requirement. WCAG specifies a 4.5:1 contrast ratio for normal-sized text and 3:1 for large text.

Videos Need Captions

If your website includes video content, those videos must have accurate captions for deaf and hard-of-hearing users. Auto-generated captions from platforms like YouTube are a starting point but often contain errors that must be corrected.

Forms Must Be Usable

Contact forms, booking forms, newsletter signups, and any other form on your site must have clearly labeled fields, provide meaningful error messages when something is filled in incorrectly, and be fully operable with a keyboard and screen reader.

Plan Work Without Assuming a Legal Outcome

This guide does not quote a typical lawsuit cost or settlement amount. Costs and obligations depend on the circumstances. Scope technical work around the barriers found, the pages affected and the human testing needed.

How to Improve Your Small Business Website

Start with an important page and a clearly defined customer task, then repair and retest the barriers you find.

Step 1: Run an Automated Accessibility Scan

The first step is to understand where you stand. An automated scan will identify the most common and most detectable accessibility violations on your website. This gives you a clear list of issues to address.

A11yScope's free scanner checks your website against WCAG 2.1 Level AA criteria and delivers a report in seconds. No signup is required. You will get a prioritized list of violations with explanations of what each issue means and how to fix it.

Step 2: Fix the Critical Issues First

Focus on the violations that completely block access for users with disabilities. In order of typical priority:

1. Add alt text to all images. Every image needs a short description. If the image is decorative, mark it with an empty alt attribute.
2. Ensure all form fields have labels. Every input on your contact form, search bar, and newsletter signup must have a label element associated with it. Our form accessibility guide covers the most common label issues and how to fix each one.
3. Fix color contrast. Adjust text and background colors to meet the 4.5:1 ratio requirement.
4. Make navigation keyboard accessible. Test your menus and links using only the Tab key.
5. Set the page language. Add lang="en" (or your appropriate language code) to the HTML tag.

Step 3: Address Your Content Management Practices

Many accessibility issues are introduced through content, not code. If you or your team regularly publish blog posts, add product listings, or upload images, establish these habits:

• Always write alt text when uploading an image.
• Use heading levels (H1, H2, H3) to structure content rather than making text bold and large.
• Add captions to any video you embed.
• Use descriptive link text instead of "click here."

Step 4: Talk to Your Web Developer or Platform Provider

If you use a website builder like Squarespace, Wix, or WordPress, check whether your theme is accessible. Many popular themes have significant accessibility problems built in. Ask your developer or theme provider about WCAG 2.1 compliance and request they fix any structural issues.

If you work with a web development agency, include WCAG 2.1 AA compliance as an explicit requirement in your contract. Do not assume developers build accessible sites by default.

A toolbar or automated report cannot demonstrate that every task is accessible. Test the experience with assistive technology and fix underlying barriers. Our overlay guide discusses technical limitations; no tool certifies legal compliance.

Step 5: Monitor Continuously

New pages, design changes and content updates can introduce accessibility barriers. Repeat automated and human checks after changes; scheduled scans do not cover every state or interaction.

A11yScope's plans offer weekly checks of linked public pages within each plan's crawl limit. Review saved findings, unchecked pages and comparison limits, then perform the human tests needed for important journeys. This is not a guarantee of complete coverage or compliance.

What If You Receive an ADA Demand Letter?

A scan cannot establish the validity of a claim or the response required. Seek qualified legal advice for the specific matter. Keep dated records of the page state, findings, scope and subsequent changes so technical work can be reviewed accurately. An accessibility statement can also give users a channel to report barriers; it is not a defense or certification.

Take the First Step Now

Run a free A11yScope scan of an important public page. Duration varies by the page and service conditions. Review the automated findings and human-check items, then repair and retest.

For recurring checks, compare the current plans. Use monitoring alongside manual testing rather than treating it as ongoing legal protection.