ADA website compliance for small businesses

The Department of Justice says Title III of the Americans with Disabilities Act (ADA) requires businesses open to the public to make the goods and services they offer online accessible to people with disabilities. No regulation sets a technical standard for private business websites, but the Web Content Accessibility Guidelines (WCAG) at Level AA are the benchmark settlements and accessibility experts use. Small businesses that ignore accessibility face demand letters from plaintiff law firms, costly financial settlements, and lost sales from customers unable to use their digital services.

Disclaimer: This article provides general educational information about website accessibility standards and should not be construed as legal advice. Consult an attorney familiar with ADA Title III litigation for guidance on your specific legal situation.

For years, many small and mid-sized business owners assumed that accessibility lawsuits only targeted Fortune 500 retailers, banks, or airline websites. In recent years, litigation has shifted heavily toward independent service businesses, restaurants, medical practices, and local retail stores.

Here is what you need to know about your legal responsibilities, how courts evaluate websites, and how to fix accessibility barriers before receiving a legal notice.

The legal reality of ADA Title III and websites

Passed in 1990, the Americans with Disabilities Act originally governed physical places of public accommodation like storefronts, medical offices, and restaurants. As commerce moved online, many federal courts applied it to business websites too, though courts in different parts of the country disagree about exactly when a website is covered.

The Department of Justice's guidance says businesses must make the goods and services they offer online accessible, and that they have flexibility in how they do it. It points to the Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium (W3C), as a helpful standard. For state and local governments, a 2024 DOJ rule adopted WCAG 2.1 Level AA outright.

Most legal settlements and consent decrees require companies to meet WCAG 2.1 or WCAG 2.2 Level AA. Review our companion website accessibility checklist (WCAG 2.2) to see the full list of technical checkpoints.

Why small businesses are targeted by demand letters

Thousands of website accessibility lawsuits and demand letters are filed each year in states like New York and California. Specialized plaintiff law firms use automated scanning tools to scan thousands of small business websites for routine coding oversights.

When an automated scan detects broken form fields or missing alternative text on an image, the firm sends a demand letter. These letters typically allege that a visually impaired person could not access the company's services, and they offer to settle the dispute for $5,000 to $20,000 to avoid federal court litigation.

For an independent business owner, fighting an ADA claim in court often costs more in legal fees than the settlement amount. The most effective defense is eliminating common technical barriers before your website gets flagged.

The four principles of accessible web design

WCAG standards are built around four core principles, often called POUR:

1. Perceivable. Information and user interface components must be presentable to users in ways they can perceive. Visitors who cannot see images must have text alternatives that screen readers can vocalize.
2. Operable. User interface components must function without a mouse. Users must be able to browse pages, open menus, and submit forms using only a keyboard.
3. Understandable. Information and operation must be clear. Text must be readable, pages must behave predictably, and forms must help users avoid and correct mistakes.
4. Reliable interpretation. Content must be structured cleanly so that assistive technologies, including desktop screen readers and braille displays, can process code without errors.

Common accessibility barriers and how to fix them

Most accessibility lawsuits cite the same basic coding oversights. Addressing these five areas resolves the majority of common legal vulnerabilities:

1. Insufficient color contrast

Text must stand out clearly against its background. WCAG Level AA requires a contrast ratio of at least 4.5:1 for standard body text and 3:1 for large text (18pt or 14pt bold).

Light gray text on white backgrounds or orange text on white buttons fails contrast tests. If visually impaired visitors or older adults cannot read your text in direct sunlight, screen readers and contrast testing tools will flag the violation.

2. Missing alternative text on informative images

Screen readers rely on alt attributes inside HTML image tags to describe visual content to blind users. If your website has an image showing your office location or service rates, but the tag reads <img src="rates.jpg"> without an alt attribute, a screen reader simply reads the filename or skips it entirely.

Ensure every informative image includes concise descriptive text: <img src="rates.jpg" alt="Commercial roofing pricing tiers by square footage">. Purely decorative background shapes should use empty alt attributes (alt="") so screen readers ignore them.

3. Contact forms without explicit labels

Forms are a frequent target of accessibility lawsuits. Every input field requires a matching <label> element connected through an id attribute.

Relying solely on placeholder text inside an input field creates a barrier. Once a user clicks into the field or their browser autofills an address, placeholder text disappears. Blind users browsing via screen readers cannot determine what information the form asks for. Our guide on website forms that convert covers how to build accessible form fields with proper semantic markup.

4. Broken keyboard operation

People with motor disabilities or visual impairments often browse websites without a computer mouse, using the Tab key, arrow keys, and the spacebar to move through interactive elements.

Two common keyboard failures invite legal action:

• Missing visible focus indicators. When a user tabs through links, the browser must display a visible outline showing which button or field is currently selected. Removing this outline in CSS breaks accessibility.
• Keyboard traps. If a modal popup or dropdown menu opens and prevents the user from tabbing back to the main page or closing the window with the Escape key, the user is trapped.

5. Broken heading hierarchies

Screen reader users commonly press keyboard shortcuts to jump directly between headings to find relevant sections rather than reading entire pages sequentially.

If your page jumps from an H1 to an H4, or uses bolded body text instead of genuine heading tags, assistive devices cannot assemble a logical table of contents. Heading structure also affects mobile usability, which we cover in what is responsive web design.

Why accessibility overlay widgets do not protect you

Faced with the fear of a lawsuit, many business owners purchase third-party accessibility overlay widgets that promise instant compliance by adding a single line of JavaScript for $49 a month.

These tools claim that an artificial intelligence toolbar will automatically fix all accessibility errors on your site. In reality, overlay widgets create a false sense of security:

• Overlays cannot fix structural HTML. A JavaScript widget running in the browser cannot determine what a complex data table means or write accurate alt text for custom product diagrams.
• Screen reader users often disable them. Experienced assistive technology users configure their own software to fit their needs. Third-party widgets frequently override those preferences and create confusion.
• Overlays don't stop lawsuits. Accessibility lawsuits are regularly filed against sites that have overlay widgets installed. In some cases, plaintiff lawyers deliberately search for websites running these widgets because they signal that the underlying code has never been audited.

The only reliable way to achieve compliance is by fixing the underlying source code.

How to audit your business website today

You can check your website's baseline accessibility using free tools:

1. Run the WAVE accessibility tool. Install the free WAVE extension for Google Chrome or Mozilla Firefox and open your homepage. WAVE visually highlights missing alt tags, contrast failures, and empty button labels directly on your live page.
2. Perform the keyboard navigation test. Disconnect your mouse or turn off your trackpad. Use the Tab key to move through your entire homepage. Can you see where the focus cursor is at all times? Can you open and close your mobile menu? Can you submit your contact form using only the Enter key?
3. Check contrast ratios. Use the WebAIM Color Contrast Checker to test your brand colors against your website background colors.

Making accessibility part of your web strategy

Building an accessible website protects your business against opportunistic legal claims, but it also makes sound commercial sense. Over 60 million American adults live with a disability. Ensuring your website is easy to read and use expands your potential customer base and improves overall conversion rates for every visitor.

At Techcelerant, our web development services build websites with accessibility in mind, and our Custom website package ($7,999) includes an accessibility pass against WCAG 2.2 AA. Compare the packages on the pricing page, and for legal questions about your obligations, talk to a lawyer.