Web Accessibility: ADA, WCAG, and the Law

Over one billion people worldwide live with some form of disability. Many rely on assistive technologies — screen readers, keyboard navigation, voice recognition, captioning — to access websites and digital services. When a website isn't designed with accessibility in mind, it can effectively lock out a significant portion of the population. Beyond the human impact, there are serious legal consequences. ADA website accessibility lawsuits have exploded in recent years, with thousands filed annually, and courts have consistently ruled that the ADA applies to websites even when there's no physical location involved.

Why Accessibility Matters

The business case for accessibility is straightforward. Accessible websites tend to be better designed overall — clear navigation, readable text, logical structure benefit everyone, not just users with disabilities. Search engine optimization improves when sites use proper semantic HTML and alt text. Customers who encounter accessibility barriers take their business elsewhere, often without telling you why. And the legal risk of non-compliance has become substantial, with plaintiffs' attorneys filing website accessibility cases as a business model, targeting deep-pocketed defendants with websites that weren't designed with accessibility in mind.

The ADA and Web Accessibility

Title III of the Americans with Disabilities Act prohibits discrimination on the basis of disability in places of public accommodation. The question that courts have wrestled with is whether a website constitutes a place of public accommodation. The ADA was passed in 1990, before the commercial internet existed, and uses the phrase "place of public accommodation," which implies a physical location. But courts have increasingly held that websites are covered under the ADA's broad definition of "goods, services, and facilities" — especially when a website is closely connected to a physical business.

The most significant developments came from the Ninth Circuit, which ruled that Domino's Pizza's website had to be accessible because it was integrated with its physical restaurants. This reasoning has been applied broadly, and while the legal landscape varies by circuit, the trend clearly favors applying the ADA to websites. State laws in California, New York, and elsewhere have added requirements, and the DOJ has signaled for years that it plans to issue formal web accessibility regulations under the ADA, though those rules have not yet been finalized.

WCAG Standards

The Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium, are the de facto standard for web accessibility. WCAG 2.1, the current version, organizes requirements into four principles: Perceivable (users must be able to perceive information), Operable (users must be able to navigate and use the interface), Understandable (information and operation must be understandable), and Robust (content must be interpretable by a wide variety of assistive technologies).

Within those principles, WCAG defines three conformance levels. Level A is the minimum — basic accessibility requirements like providing alt text for images and captions for videos. Level AA is what most accessibility lawsuits and regulations reference — it's the practical target for most businesses. Level AAA is the highest level and is generally not required for entire sites, though some organizations aim for AAA in specific areas.

The EU's Web Accessibility Directive requires public sector websites and apps to meet WCAG 2.1 AA. Section 508 of the Rehabilitation Act applies WCAG 2.0 Level AA to federal agencies and contractors. While private companies aren't formally required to follow these frameworks, they're the standard against which courts measure compliance. If your website doesn't meet WCAG 2.1 AA, you have significant exposure.

Mobile App Accessibility

Mobile apps are increasingly subject to accessibility requirements under both the ADA and Section 508. Apple's iOS and Google's Android platforms provide accessibility APIs and guidelines that developers should follow. Apps that are difficult or impossible to use with VoiceOver or TalkBack — the screen readers built into iOS and Android — can create the same ADA liability as inaccessible websites.

Enforcement and Lawsuits

The plaintiffs' bar has been active in this space. ADA website accessibility lawsuits are now common in federal courts, and settlement costs — which can run from $5,000 to $50,000 or more per case — add up quickly even when individual cases settle for modest amounts. The incremental cost of building accessibility in from the start is almost always less than the cost of litigation and remediation after a lawsuit. DOJ enforcement of Title III has historically been limited, but the agency has signaled increased attention to web accessibility.

Making Your Site Accessible

The practical path forward starts with an audit. Automated tools like axe and WAVE can catch many issues — missing alt text, contrast problems, empty links — but automated testing only catches about 30-40% of accessibility issues. The rest require manual testing with actual assistive technologies and human review. Many organizations use a combination of automated scanning as a first pass, followed by expert manual auditing.

The fixes are often straightforward once you know what to look for. Every image needs meaningful alt text. Videos need captions. Color contrast needs to meet minimum ratios. Forms need proper labels. Navigation needs to work with a keyboard alone. ARIA landmarks and semantic HTML help screen readers understand page structure. But the architecture matters too — building accessibility into a site that's already live and deeply inaccessible is far more expensive than building it in from the start.