ADA Website Compliance: What Small Businesses Should Know

The Americans with Disabilities Act (ADA) requires that people with disabilities have equal access to services. For websites, this means people using screen readers, keyboard navigation, or other assistive technologies must be able to navigate and use your site. Courts have repeatedly ruled that websites are public accommodations under the ADA, and lawsuits have targeted businesses of every size—from large retailers to small local services.

Many business owners assume ADA compliance is optional or only matters if litigation risk is high. This is wrong. Compliance has become a baseline expectation, and the cost of legal action exceeds the cost of fixing accessibility problems.

What Accessibility Means

Accessibility is about making your site usable by people with various disabilities:

Visual impairments: People who are blind or have low vision use screen readers that read text aloud. Colors and small fonts create problems.

Motor impairments: People who can't use a mouse rely on keyboard navigation. Sites that require clicking might be unusable.

Cognitive disabilities: People with dyslexia, ADHD, or intellectual disabilities benefit from clear writing, consistent navigation, and logical structure.

Hearing impairments: People who are deaf need captions for video and audio.

Color blindness: Using color alone to convey information (red for errors, green for success) excludes people who can't perceive certain colors.

WCAG Guidelines

The Web Content Accessibility Guidelines (WCAG) are the standard for web accessibility. Most legal accessibility requirements reference WCAG 2.1 at level AA conformance.

WCAG is built on four principles:

Perceivable: Information is presented in ways users can perceive. Text must be readable, images need descriptions, colors aren't the only way to convey meaning.

Operable: Users can navigate and interact. Sites must work with keyboard only, not just a mouse. Users need time to read and respond.

Understandable: Users understand the content and how to use the site. Language should be clear, pages should be logically organized, errors should provide helpful messages.

Robust: The site works across assistive technologies. HTML should be valid, code shouldn't rely on outdated techniques.

Common Accessibility Problems

Images without alt text: A screen reader can't describe an image, so alt text is essential. For decorative images, alt text should be empty. For informative images, alt text should describe the content and function.

Keyboard navigation not working: A visitor using a keyboard can't access a button or link that requires a mouse click.

Poor color contrast: Text that's too light or too close in color to its background is hard to read for people with visual impairments or color blindness.

No captions for video: Deaf visitors and people watching without sound can't understand video content.

Complex tables without headers: Screen readers can't parse a table if headers aren't properly marked.

Forms without labels: A form field without a visible or programmatic label is confusing, especially for screen reader users.

Auto-playing audio or video: People using screen readers can't pause it, and it interferes with their ability to hear the screen reader.

Outdated or incorrect HTML: Screen readers rely on proper semantic markup. A button styled as a div won't be recognized as a button.

No skip navigation link: Keyboard users have to tab through every menu item to reach content. A "Skip to main content" link lets them bypass navigation.

Time-limited content: A form that expires after 30 seconds is inaccessible to people who need more time to read or navigate.

Quick Audit

You don't need to be an expert to spot problems:

Images: Check whether images have alt text. Right-click, inspect element, and look for alt="description". Missing alt attributes are a common problem.

Color: Ask whether color alone conveys information. If an error message is only red text, that's a problem. If an error message is red text that says "Error", that's fine.

Keyboard navigation: Try navigating your entire site using only the Tab key. Can you reach every button, link, and form field? Can you submit forms? If you get stuck, that's a problem.

Contrast: Use an online contrast checker (like WebAIM's tool) to test whether text is readable against its background. WCAG AA requires a ratio of at least 4.5:1 for normal text.

Forms: Check that form fields have visible labels or labels in the code. Try submitting a form with missing required fields and see whether the error message tells you what's wrong.

Headings: Look at your page structure. Do headings make sense hierarchically? A page shouldn't jump from H1 to H3 to H2—that confuses screen reader users.

How to Fix Accessibility

Start with alt text for all images. This is foundational and catches many problems. Informative images need descriptive alt text. Decorative images can have empty alt text.

Ensure keyboard navigation works. Test your site using only Tab to navigate. Every interactive element should be reachable. Use CSS to style the focus indicator (the highlight that shows which element has keyboard focus) so it's clearly visible.

Improve color contrast. Text should meet WCAG AA standards (4.5:1 for normal text, 3:1 for large text). This also improves readability for everyone.

Add captions to video. Services like YouTube have auto-captioning, which is a starting point but often needs editing for accuracy.

Use semantic HTML. Use <button> for buttons, not <div>. Use <label> for form labels. Use proper heading levels (H1, H2, H3 in order). This is how screen readers understand page structure.

Write clearly. Short sentences, simple words, and logical organization help everyone, not just people with cognitive disabilities.

Test with screen readers. NVDA (free, Windows) and JAWS (commercial, Windows and Mac) are the most common. Testing with a screen reader reveals problems that visual inspection misses.

Tools and Resources

Automated tools: axe DevTools, WAVE, and Lighthouse (built into Chrome) can scan pages and flag common problems. They're useful starting points but won't catch everything.

Manual testing: Some problems require human judgment. Does alt text actually describe the image? Is the page logically organized? Automated tools can't answer these.

Screen reader testing: Download NVDA and test your site with it. This catches accessibility issues that other methods miss.

Contrast checker: WebAIM's contrast checker lets you test text and background colors.

Legal Risk

Accessibility lawsuits have increased over the past five years. They typically allege that a site violates Title III of the ADA by being inaccessible to people with disabilities.

Plaintiffs claim damages, attorney fees, and sometimes settlements. Many settle for tens of thousands of dollars and a commitment to remediate within a certain timeline.

Your business size doesn't protect you. Lawsuits have targeted small local services, nonprofits, and large corporations equally. The cost of fixing accessibility proactively is typically much lower than the cost of litigation and settlement.

Practical Approach

If you're just starting:

1. Audit your site's most-visited pages.
2. Add alt text to all images.
3. Test keyboard navigation and fix anything that doesn't work.
4. Run a contrast checker and fix any text that's hard to read.
5. Ensure forms have proper labels.

If you have budget for professional help:

1. Hire an accessibility consultant to do a comprehensive audit.
2. Prioritize fixes based on severity and impact.
3. Implement changes methodically.
4. Test with assistive technology to confirm fixes work.

FAQ

Is my site required to be accessible? If you serve the public in any way (e-commerce, services, information), yes. The ADA applies to websites. Some exemptions exist for very small businesses or specific circumstances, but these are rare and narrow.

Do I need to be 100% compliant with WCAG? Practical compliance requires good-faith effort to meet WCAG 2.1 level AA. Perfect compliance isn't always possible, but you should be able to demonstrate you've addressed major issues.

What if I can't afford to fix everything? Prioritize. Alt text on images is quick and catches many problems. Keyboard navigation and color contrast are high-impact. Captions for video takes more effort but is important if you have video. Start somewhere and improve incrementally.

Can I rely on automated testing? Automated tools catch obvious problems but miss many accessibility issues. Use them as a starting point, then supplement with manual testing and screen reader testing.

What about third-party tools and plugins? You're responsible for everything on your site, including third-party code. If a plugin isn't accessible, either fix it, use an accessible alternative, or remove it. Relying on third-party code isn't a defense against accessibility claims.

Do I need to hire an accessibility expert? For a simple site, careful manual testing and attention to WCAG guidelines might suffice. For complex sites, hiring a consultant pays for itself through avoiding litigation risk.

Summary

ADA compliance for websites is legally required and increasingly enforced. It's not complex—it's about descriptive alt text, keyboard navigation, readable color contrast, and proper HTML structure. Most accessibility improvements benefit everyone: readable text helps people with low vision and people reading on small screens; keyboard navigation helps people with motor disabilities and power users; clear writing helps people with cognitive disabilities and people in noisy environments. Starting with a simple audit and fixing the most obvious problems is a reasonable approach. The cost is typically low, and the benefit—avoiding litigation and serving more users—is substantial.