A plain English guide to web accessibility law, WCAG standards, real lawsuit data, and what it actually takes to protect your business. Written by the team that built Includeify.
The Americans with Disabilities Act (ADA) was signed into law in 1990 to prohibit discrimination against people with disabilities. While the original law focused on physical spaces such as ramps, accessible bathrooms, and parking, courts have consistently ruled that websites are also "places of public accommodation" subject to the ADA.
This means your website must be accessible to people who are blind, have low vision, are deaf, have motor disabilities, or those who rely on assistive technology like screen readers and keyboard navigation. If it isn't, your business can be sued.
Any business with a website that serves the public: restaurants, dental practices, law firms, retailers, real estate agencies, healthcare providers, and more. There is no revenue threshold or size exemption. A single location restaurant faces the same exposure as a national chain.
The specific section that applies to websites is Title III, which covers "places of public accommodation." Courts in multiple federal circuits have ruled that websites operated by businesses open to the public fall under this definition, regardless of whether the business has a physical location.
While Congress has not passed specific website accessibility legislation, the Department of Justice (DOJ) has issued guidance confirming that the ADA applies to websites, and courts have consistently enforced this interpretation.
WCAG stands for Web Content Accessibility Guidelines, the international technical standard that courts and the DOJ use to evaluate whether a website is accessible. The current standard is WCAG 2.1 Level AA.
WCAG is organized around four core principles, often summarized as POUR.
Based on scan data across thousands of websites, these are the violations that appear most frequently and are most commonly cited in lawsuits:
Missing image alt text: images with no description for screen readers.
Insufficient color contrast - text too similar in color to its background.
Missing form labels: input fields with no associated label element.
No keyboard navigation: interactive elements unreachable without a mouse.
Missing page language: HTML lang attribute not set, which confuses screen readers.
WCAG 2.1 AA contains 50 success criteria in total. Most websites fail multiple criteria across multiple pages, making the cumulative exposure significant.
ADA website litigation has grown dramatically over the past decade, driven largely by a small number of plaintiff law firms that file cases in volume. Understanding the data helps business owners assess their actual exposure.
Plaintiff firms tend to target industries where websites play a central role in the customer relationship through booking appointments, viewing menus, reading service information, and making purchases.
| Rank | Industry | Risk Level | Primary Reason |
|---|---|---|---|
| 1 | E-commerce | Very High | Online purchasing requires full accessibility |
| 2 | Restaurants | Very High | Online menus, reservations, ordering |
| 3 | Retail | High | Product listings, checkout flows |
| 4 | Hospitality | High | Booking systems, room information |
| 5 | Healthcare / Medical | High | Patient portals, appointment booking |
| 6 | Dental | High | Appointment booking, patient forms |
| 7 | Legal Services | Moderate–High | Contact forms, service descriptions |
| 8 | Real Estate | Moderate–High | Listings, search tools, contact forms |
ADA website lawsuits rarely go to trial. The vast majority settle quickly, with defendants paying legal fees, plaintiff attorney fees, and damages. Typical ranges:
Demand letter settlement: $5,000–$20,000
Filed lawsuit settlement: $25,000–$75,000
Contested or multi plaintiff case: $75,000–$150,000+
These figures do not include the cost of remediating your website after settlement, which is typically required as part of the agreement.
Many business owners assume that because they haven't received a complaint, their website isn't a target. This is a misconception. Plaintiff firms do not identify targets through complaints. They use automated scanning tools to identify noncompliant websites at scale, and file demand letters in volume.
Under the ADA, there are no statutory damages caps for Title III violations. Attorney fee shifting provisions can mean plaintiffs' legal fees can be added to your liability. The financial exposure grows the longer a case is contested.
Accessibility overlay widgets such as AccessiBe, UserWay, and AudioEye's overlay tier are JavaScript scripts that attempt to modify your website's accessibility in real time without changing the underlying code. They are widely marketed as compliance solutions.
The legal and technical reality is more nuanced.
Multiple courts have allowed ADA lawsuits to proceed against businesses that had overlay widgets installed, ruling that the widget did not constitute meaningful accessibility compliance. The National Federation of the Blind and other disability rights organizations have formally opposed overlay widgets as ineffective and sometimes harmful to disabled users.
A widget may reduce your visible violation count on a surface scan, but it does not fix the underlying code and does not reliably protect you legally. Real compliance means fixing violations in the source and maintaining documentation to prove it.
Genuine ADA/WCAG compliance is not a one time event. It is an ongoing process. Websites change, content gets added, and new violations can appear any time a page is updated. Here's what a real compliance program looks like:
Start with a comprehensive automated scan of every page on your website. This identifies all detectable WCAG violations, categorizes them by severity, and gives you a compliance score. This is your starting point.
Fix violations in order of severity: critical violations first (missing alt text, contrast failures, missing form labels), then serious, then moderate. Fix instructions should be specific to your platform because a WordPress site requires different steps than a Squarespace site.
This is the step most tools skip. Completed does not mean compliant. Once you mark a violation as fixed it needs to be rescanned and confirmed by the scanner. Self reported fixes are not meaningful documentation. Verified fixes are.
Includeify distinguishes between Completed (self reported by the user) and Verified (confirmed by rescan). Only Verified status represents real documentation of remediation. This distinction matters if you ever need to demonstrate compliance to a plaintiff or court.
Your website changes over time. New pages get added, images get uploaded without alt text, plugins get updated, templates get modified. Monthly monitoring catches new violations before they accumulate and before anyone else finds them.
Maintain a record of your compliance activity including scan dates, violations found, remediation steps taken, verification dates, and your compliance score over time. Courts have recognized documented good faith effort as a meaningful factor in ADA cases.
Automated tools are highly effective at detecting structural violations. But automated scanning typically catches 30 to 40% of all real accessibility issues. The rest can only be found through human testing.
The issues automated tools miss include:
Our Premium Manual Audit is an optional service performed by our team. It covers everything automated scanning misses and includes a personal walkthrough of every finding. It is available at an additional cost and can be requested at any time alongside your standard plan.
If your site has complex interactive features, custom navigation, dynamic content, or if you have received a demand letter, a manual audit provides the most defensible documentation of your compliance effort. It is also recommended for any business in a high-risk industry category.
Contact us to learn more about the Premium Manual Audit →
Get a free scan of your website. See your violations, severity, compliance score, and estimated exposure. No credit card required.
Get My Free Scan →