Most businesses facing ADA website lawsuits had never documented their accessibility work. US courts have consistently ruled that commercial websites are places of public accommodation under ADA Title III. Federal filings exceeded 4,600 in 2023, the highest annual total on record. This article covers why litigation keeps rising, what the law actually requires, and what a defensible compliance programme looks like.
Why are ADA website lawsuits increasing — and who is actually being targeted?
Federal ADA website accessibility litigation has grown every year since 2018. Three forces are driving it. Courts in key jurisdictions have ruled that websites are covered under Title III. The Department of Justice published formal guidance in 2022 confirming the ADA applies to websites. And an organised plaintiff bar has developed efficient processes for targeting sites with no evidence of accessibility compliance monitoring of any kind.
The defendants are not a predictable set. Retailers, healthcare providers, restaurants, financial services firms, law practices, and hospitality businesses all appear on plaintiff lists. The pattern is not industry or size. It is one shared characteristic: no evidence that they had ever systematically reviewed whether their websites worked for people with disabilities.
The human dimension is concrete. Approximately 61 million adults in the United States live with some form of disability, according to the CDC. Many rely on screen readers, keyboard navigation, and voice control to access information, compare prices, complete transactions, and book appointments online. When a website lacks image descriptions, breaks under keyboard navigation, or uses colour contrast ratios below the standard threshold, those users are not inconvenienced. They are excluded. The lawsuit is the legal symptom. The underlying problem is a website that fails a significant portion of the population on every visit.
What does ADA Title III actually require from a website?
ADA Title III requires places of public accommodation to provide equal access to people with disabilities. Courts and the Department of Justice have pointed consistently to WCAG 2.1 AA as the operative technical standard for what equal access means in practice.
WCAG 2.1 AA defines four core principles. Websites must be perceivable, meaning content is accessible through multiple senses. They must be operable, meaning navigation works without a mouse. They must be understandable, meaning content and interface behaviour are clear. They must be robust, meaning content works reliably with assistive technology. The failures courts most frequently cite are specific: missing image descriptions, broken keyboard navigation, unlabelled form fields, and colour contrast ratios below the 4.5:1 minimum for standard text.
Website accessibility compliance is not a certification event. It is an ongoing obligation. Websites change. Content is updated. New pages are built. A remediation pass applied in Q1 can be undone by a platform update in Q3. Any programme that treats accessibility as a one-time project is structurally incomplete.
Why documented effort matters more than perfection in ADA litigation
Courts and regulators do not require perfect websites. They examine whether an organisation can demonstrate it took accessibility seriously. This distinction is operationally significant.
Organisations with a documented programme are materially better positioned in settlement negotiations than those with no evidence of any accessibility activity. Regular scanning, tracked issue remediation, and a published accessibility statement change the character of a case. An organisation that received a demand letter while actively tracking and remediating issues presents a fundamentally different liability profile than one receiving its first notification that the problem exists.
Welcoming Web, a web accessibility platform built for digital teams, operates on this principle. Its core functions include automated page scanning against WCAG 2.2, ADA Title III, and EN 301 549; a monitored dashboard of open and resolved issues; exportable PDF and CSV reports. It provides evidence of sustained, structured accessibility work: the documented programme that separates organisations who can demonstrate effort from those who cannot.
What the European Accessibility Act adds for businesses with international operations
For organisations operating across markets, the compliance landscape changed materially in 2025. The European Accessibility Act became enforceable on 28 June 2025 for most product and service categories. It requires websites serving EU customers to meet WCAG 2.1 AA via EN 301 549, publish a specific accessibility statement, and provide a mechanism for users to report accessibility failures.
France saw the first formal enforcement actions shortly after the deadline. Disability organisations issued legal notices to major grocery retailers. Germany and the Netherlands have active enforcement bodies. The EAA applies to any organisation serving EU residents regardless of where the business is incorporated. A US business with European customers is within scope.
Organisations managing websites for UK, EU, and US markets are now operating simultaneously under ADA Title III, the EAA via EN 301 549, and the UK Equality Act 2010. Each framework shares WCAG as the underlying technical reference. The remediation work substantially overlaps. The documentation requirements differ by jurisdiction and require separate attention.
What a defensible accessibility programme actually looks like in practice
A structured accessibility programme does not require rebuilding a website. It requires a systematic approach to identifying issues, remediating them, and maintaining the record.
Organisations managing this effectively follow a consistent pattern. They run automated scans at regular intervals — monthly at minimum, more frequently for high-traffic or frequently updated sites. They triage by severity, prioritising failures that block assistive technology users entirely before addressing lower-severity items. Absent keyboard navigation, screen reader incompatibility, and missing form labels are fixed first. They maintain a dashboard of open and resolved issues that becomes the dated compliance record. And they deploy an accessibility widget that gives each site visitor immediate, personal control over how the site renders for them — text size, contrast, motion, spacing — while underlying issues are systematically resolved.
The more defensible approach combines systematic scanning with genuine remediation. Identify what is broken. Apply fixes through supported automated or manual processes. Maintain a record of what was found and what was done. That is what an accessibility programme looks like, as opposed to an accessibility product.
What organisations should do before the next quarter ends
The lowest-cost, highest-information first step for any organisation without a current baseline is to scan their website. A baseline scan produces a factual view of which issues exist, how many, what type, and which pages are affected. Without this, any prioritisation decision is arbitrary.
From the baseline, the sequence is clear. Blocking failures are fixed first. Lower-severity issues are scheduled. Results are documented and tracked. An accessibility statement is drafted and published. The record builds over time.
