ADA Website Compliance: What Every Business Owner Needs to Know

In 2025, over 4,600 ADA-related web accessibility lawsuits were filed in the United States — a number that has grown every year since 2017. The targets are not just Fortune 500 companies. Small businesses, local restaurants, medical practices, and e-commerce stores of every size have been named in these suits. The average settlement ranges from $5,000 to $150,000, not including legal fees.

Beyond the legal risk, inaccessible websites exclude roughly 26% of American adults who live with some form of disability. That is not a niche audience — it is one in four potential customers. Making your website accessible is not just about compliance. It is about reaching everyone who wants to do business with you.

What the Law Actually Says

The Americans with Disabilities Act (ADA), enacted in 1990, prohibits discrimination against individuals with disabilities in all areas of public life. Title III covers "places of public accommodation." Courts have increasingly ruled that websites fall under this definition, particularly for businesses that also have physical locations.

The Department of Justice issued its final rule in April 2024 explicitly requiring state and local government websites to conform to WCAG 2.1 Level AA. While this rule directly applies to government entities, it has strengthened the legal foundation for applying the same standard to private businesses.

In practice, WCAG 2.1 Level AA has become the de facto legal standard for web accessibility in the U.S. If your website meets these guidelines, you are in a strong legal position. If it does not, you are exposed.

WCAG 2.1 Level AA: What It Requires

The Web Content Accessibility Guidelines (WCAG) are organized around four principles, remembered by the acronym POUR: Perceivable, Operable, Understandable, and Robust.

Perceivable

Users must be able to perceive the information being presented. It cannot be invisible to all of their senses.

• Text alternatives: Every non-text element (images, icons, charts) needs a text description. Screen readers depend on alt text to convey visual information to blind users.
• Captions and transcripts: Video content requires synchronized captions. Audio content requires written transcripts.
• Color contrast: Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). Light gray text on a white background — a common design choice — often fails this requirement.
• Responsive presentation: Content must be viewable at 200% zoom without losing information or functionality.

Operable

Users must be able to operate the interface. It cannot require interactions that some users cannot perform.

• Keyboard navigation: Every function must be accessible using a keyboard alone. This is critical for users who cannot use a mouse, including those with motor disabilities and blind users who rely on screen readers.
• Focus indicators: When tabbing through a page, the currently focused element must be visually obvious. Removing the default focus outline (a common CSS practice) creates a major accessibility barrier.
• Sufficient time: If content has time limits (auto-rotating carousels, session timeouts), users must be able to extend or remove those limits.
• No seizure triggers: Content must not flash more than three times per second.
• Skip navigation: Provide a "Skip to main content" link so keyboard users do not have to tab through the entire navigation on every page.

Understandable

Users must be able to understand the information and the operation of the interface.

• Language declaration: The page language must be declared in the HTML (for example, lang="en"). Screen readers use this to determine pronunciation.
• Consistent navigation: Navigation should appear in the same location on every page.
• Form errors: When a form submission fails, the error must be clearly identified, described in text, and associated with the specific field that caused it.
• Labels: Every form input needs a visible, descriptive label. Placeholder text disappears when the user starts typing and does not substitute for a label.

Robust

Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.

• Valid HTML: Clean, semantic HTML ensures screen readers and other assistive tools can parse your content correctly.
• ARIA usage: When standard HTML elements are insufficient, ARIA (Accessible Rich Internet Applications) attributes provide additional context. But the first rule of ARIA is: do not use ARIA if a native HTML element will do the job.
• Status messages: Dynamic content updates (form confirmations, error messages, loading indicators) must be announced to assistive technologies using ARIA live regions.

The Most Common Violations

WebAIM's annual analysis of the top 1 million home pages consistently finds the same issues dominating. In their 2025 report, the average page had 55 detectable accessibility errors. The top offenders:

1. Low contrast text (81% of pages): The most pervasive issue. Often caused by design trends that prioritize aesthetics over readability.
2. Missing alt text for images (54% of pages): Every informational image needs descriptive alt text. Decorative images need empty alt attributes (alt="").
3. Missing form labels (48% of pages): Inputs without associated labels are unusable for screen reader users.
4. Empty links (44% of pages): Links that contain only an icon or image without text alternatives are meaningless to screen readers.
5. Missing document language (17% of pages): The easiest fix on this list — one attribute in the HTML tag.
6. Empty buttons (26% of pages): Buttons with only icons and no accessible name.

Practical Steps to Improve Accessibility

You do not need to achieve perfection overnight. Start with the highest-impact changes and build from there.

Immediate Actions (This Week)

1. Add lang="en" (or your language) to the <html> tag on every page.
2. Run an automated scan to identify the worst offenders. Tools like Claros, axe DevTools, or WAVE can surface the most common issues in minutes.
3. Add alt text to all informational images. For decorative images, set alt="".
4. Ensure every form input has a visible <label> element.

Short-Term Improvements (This Month)

1. Fix color contrast issues. Use a contrast checker and adjust your color palette where needed.
2. Add visible focus indicators for keyboard navigation. If your CSS includes outline: none, replace it with a visible focus style.
3. Add a "Skip to main content" link as the first focusable element on every page.
4. Review all links and buttons to ensure they have descriptive text, not just "Click here" or a bare icon.

Ongoing Practices

1. Make accessibility part of your development process, not an afterthought. Test with a keyboard and a screen reader before launching new pages.
2. Include users with disabilities in usability testing when possible.
3. Train your content team to write meaningful alt text and use heading hierarchies correctly.
4. Audit quarterly. Accessibility can regress as new content and features are added.

Accessibility Overlays: A Word of Caution

You may have encountered companies selling JavaScript "accessibility overlay" widgets that claim to make your site compliant with one line of code. The accessibility community, advocacy organizations, and legal experts broadly agree: these tools do not deliver on their promises. Multiple lawsuits have been filed against websites that relied on overlays, and the National Federation of the Blind has publicly opposed them.

True accessibility requires fixing the underlying code, content, and design. There are no shortcuts.

Scan Your Site for Accessibility Issues

The first step is understanding where you stand. Run a free Claros scan to get a detailed accessibility assessment of your website, including specific violations, their severity, and actionable guidance on how to fix them.