In 2025, plaintiffs filed 8,667 ADA Title III federal lawsuits targeting businesses over inaccessible digital properties — a 37% year-over-year increase according to UsableNet's mid-year report. The phrase "digital properties" is no longer limited to websites. Mobile apps are in the crosshairs, and the legal framework to target them has been strengthening since the DOJ's 2024 Title II final rule.
If your business has a mobile app and you haven't run an ADA compliance checker on your digital presence, you need to understand what makes an app a lawsuit target — and why settling once without fixing the code gets you sued again.
What the Law Actually Says About Mobile Apps
The ADA was signed into law in 1990, nearly 30 years before smartphones existed. Courts have been filling the gap through case-by-case rulings ever since. Here is where the law currently stands:
ADA Title II (public entities): In April 2024, the DOJ published a final rule explicitly requiring state and local government websites and mobile apps to conform to WCAG 2.1 Level AA. This is the first time the DOJ formally set a WCAG standard as the binding requirement for digital content. Compliance deadlines have been extended — larger public entities now have until April 26, 2027; smaller ones until April 26, 2028 — but the standard is set.
ADA Title III (private businesses): No equivalent final rule yet. However, courts have consistently ruled that Title III applies to digital properties when those properties have a sufficient "nexus" to a physical place of business. In California, New York, and Florida — the three states with the highest lawsuit concentration — courts have interpreted this nexus broadly. Private mobile app lawsuits proceed under this judge-made doctrine.
The EAA wildcard: The European Accessibility Act has been in enforcement since June 28, 2025. It explicitly covers mobile apps in scope. If your app is available to EU users, EAA compliance is not optional.
Lawsuit Volume: The Numbers Behind the Risk
The 2025 ADA lawsuit figures reveal patterns that directly affect mobile app owners:
| Metric | 2025 Data | Source |
|---|---|---|
| Total ADA Title III federal lawsuits | 8,667 | UsableNet |
| Digital property cases (web + app) | 5,000+ | UsableNet |
| Year-over-year increase | 37% | UsableNet |
| Repeat defendants (sued before) | 45–46% | UsableNet |
| Sites with overlays that were still sued | 22.64% of H1 2025 cases | UsableNet |
| Average demand letter settlement | $1,000–$25,000 | AccessibilityChecker.org |
| Average out-of-court settlement | ~$25,000–$100,000 | AccessibilityChecker.org |
The repeat-defendant figure is particularly important: nearly half of all 2025 digital accessibility lawsuits targeted companies that had already been sued. Settling without remediating the underlying code doesn't reduce your risk — it confirms to plaintiff attorneys that you're a viable target who pays.
What Makes a Mobile App a Lawsuit Target
Plaintiff law firms use automated scanning tools to identify violations at scale before filing. They look for patterns that are detectable programmatically: missing image labels, inaccessible form fields, keyboard navigation failures, and contrast violations. The same errors that trigger a website lawsuit trigger an app lawsuit.
The most commonly cited violations in mobile accessibility lawsuits include:
Unlabeled interactive elements. Buttons and icons without accessible names (WCAG 4.1.2). A shopping cart icon that says nothing to a screen reader. A checkout button labeled only with a graphic. These are trivially detectable and appear in virtually every demand letter.
Inaccessible forms. Registration, login, payment, and checkout forms with missing labels (WCAG 1.3.1). When a screen reader user cannot complete a purchase because the credit card field has no accessible label, you have an ADA violation and a documented transaction failure.
No alternative to gesture-based interactions. Swipe-to-delete, pull-to-refresh, and pinch-to-zoom must have button alternatives (WCAG 2.5.1). If your app's only way to perform a core function is a multi-finger gesture, it excludes users who rely on switch access or voice control.
Video content without captions. Any video with audio must have synchronized captions (WCAG 1.2.2). Tutorial videos embedded in apps are frequently cited.
Color contrast failures. Contrast below 4.5:1 for normal text (WCAG 1.4.3) is the most common violation across all digital properties.
Which Industries Are at Highest Risk
Not all app categories face equal exposure. Plaintiff law firms concentrate on apps where inaccessibility blocks a commercial transaction — because the economic harm to the plaintiff (inability to purchase, book, or access a service) is clearest.
| Industry | Primary Lawsuit Trigger | Risk Level |
|---|---|---|
| Retail / e-commerce | Inaccessible checkout | Very High |
| Food delivery / restaurants | Menu and ordering flow | Very High |
| Banking / fintech | Account access, transfers | High |
| Healthcare | Patient portal, appointment booking | High |
| Travel / hospitality | Search, booking, confirmation | High |
| SaaS / B2B tools | Login, onboarding flows | Moderate |
| Gaming | Varies — often lower unless it includes purchases | Lower |
The DOJ's October 2025 Position Shift
In October 2025, the DOJ announced it would "re-examine" all ADA Title II and Title III regulations on an unspecified timetable. Some interpreted this as a signal that enforcement would relax. However, DOJ enforcement and private plaintiff lawsuits are separate mechanisms — and private lawsuits under Title III do not require DOJ involvement. The 8,667 filings in 2025 were almost entirely driven by private plaintiff attorneys, not the DOJ. A DOJ policy change has no direct effect on your exposure to private litigation.
What to Do Before a Demand Letter Arrives
You cannot control whether a plaintiff's law firm scans your app. You can control how many violations they find when they do.
The first step is understanding your current violation baseline across all digital properties — web and app together. Run an ADAGuard scan on your marketing site, login page, and any web-based account flows at adaguard.io. No signup required. ADAGuard's ada compliance checker covers 22 automated check categories, surfacing the unlabeled buttons, contrast failures, and form issues that plaintiff attorneys look for programmatically.
On the native app side, enable iOS VoiceOver and navigate through your three most critical user flows — authentication, core function, and any in-app purchase or booking. Document what VoiceOver announces at each step. If it says "button" with no label, that's WCAG 4.1.2 violation. If it skips an element entirely, that's 4.1.2 and potentially 2.4.3. If the modal doesn't trap focus and VoiceOver can navigate behind it, that's 2.1.2.
Hand your developer the WCAG criterion numbers, the screen where each violation occurs, and the screen reader behavior. That framing gets fixes shipped faster than vague accessibility feedback.
The 30-Second Fix
Check your website now before a plaintiff attorney does. Paste your URL at adaguard.io — no account required — and get a full WCAG 2.2 AA report in under 30 seconds. ADAGuard's 22 check categories cover ~78% of detectable violations, giving you a clear picture of your current exposure across web and giving you the data you need to prioritize your mobile remediation roadmap.