Your website is either accessible or it's a liability. There's not much middle ground left in 2026. More than 5,000 digital accessibility lawsuits were filed in 2025 alone — a 37% surge over 2024 — and the legal pressure keeps accelerating. The businesses that treat accessibility as a design principle rather than a checkbox are quietly watching their conversion rates climb. Here's what changed, what the law expects, and what to do about it.
The Lawsuit Landscape: Numbers That Should Get Your Attention
The data from UsableNet's 2024 Year-End ADA Web Lawsuit Report is blunt: over 4,000 ADA lawsuits related to digital properties were filed in 2024, split 60% federal and 40% in New York and California state courts. Then 2025 outpaced it. According to WCAGsafe's 2025 ADA Lawsuit Statistics, full-year 2025 saw 5,000+ digital accessibility lawsuits and 8,667 total ADA Title III federal filings — roughly three times the 2013 baseline.
A few numbers every business owner should sit with:
- 45–46% of 2025 defendants were repeat targets — once you're in a plaintiff firm's crosshairs, you stay there.
- 94.8% of websites still fail basic WCAG checks (WebAIM Million 2025 report).
- Average out-of-court settlements run ~$30,000; Fashion Nova settled one case for $5.15 million.
- An estimated 35,000–50,000 demand letters were sent in 2025 — roughly seven to ten for every lawsuit filed.
E-commerce sites are the primary targets, and smaller businesses are increasingly in scope as larger brands shore up their compliance.
What WCAG 2.2 Actually Requires (Without the W3C Jargon)
WCAG 2.2 was finalized in October 2023. If you're already meeting WCAG 2.1 AA — the standard most U.S. courts reference — you're close, but there are six new Level AA criteria to address:
- Focus Not Obscured (2.4.11): Sticky headers and chat widgets can't completely hide the element a keyboard user is focused on.
- Focus Appearance (2.4.13): The focus indicator must be visually obvious — a solid outline, sufficient contrast, no more barely-visible dotted borders.
- Dragging Movements (2.5.7): Every drag-and-drop interaction needs a single-pointer alternative (e.g., up/down buttons alongside a draggable list).
- Target Size Minimum (2.5.8): Interactive elements must be at least 24×24 CSS pixels. Tiny icon buttons are the usual offender.
- Redundant Entry (3.3.7): Don't ask users to re-enter the same data in one session. Auto-populate billing when it matches shipping.
- Accessible Authentication (3.3.8): CAPTCHAs that require cognitive puzzles must have an alternative. Support password managers.
These aren't edge cases — they address real friction for people with motor, visual, and cognitive disabilities, and they make forms and navigation better for everyone.
The EU Just Added Another Reason to Care
The European Accessibility Act (EAA) enforcement deadline of June 28, 2025 has already passed for new products and services. According to Global Policy Watch, the EAA requires websites and mobile apps offered to EU consumers to be accessible, with market surveillance authorities in each Member State empowered to investigate complaints. If your site has been updated since June 2025, you're in scope now. Existing products have until June 2030 — but that window closes fast when dev cycles are counted.
Why That Accessibility Widget Isn't Saving You
The most common shortcut is an overlay widget — the little icon that opens a panel to adjust font sizes and contrast. It's tempting. It's cheap. It doesn't work.
In 2024, over 1,000 businesses were sued while actively running an accessibility widget — more than 25% of all ADA digital lawsuits that year, per UsableNet. In April 2025, the FTC fined AccessiBe $1 million for compliance claims "not supported by competent and reliable evidence," as documented in TestParty's court records analysis. Some plaintiff firms now specifically target overlay users because the widget signals a shortcut without the fix.
The technical reason: overlays inject JavaScript after the browser parses your HTML. Screen readers read the source code. A missing form label in the markup stays missing — no overlay can retroactively associate it. Overlays can't restructure heading hierarchies, repair focus traps, or rewrite the semantic HTML assistive technologies depend on. Only code-level remediation works.
The Practical Remediation Checklist
- Alt text: Every meaningful image needs a concise description. Decorative images get
alt="". WCAG 1.1.1 is one of the most-cited violations in lawsuits. - Color contrast: Body text needs a 4.5:1 ratio; large text 3:1. Your brand's light gray on white likely fails.
- Keyboard navigation: Tab through the entire site without a mouse. Every link, button, field, and modal must be reachable. Focus should never disappear or get trapped.
- Form labels: Every input needs a visible
<label>— not placeholder text, which vanishes when the user starts typing. - ARIA for custom components: Dropdowns, sliders, date pickers, and carousels need ARIA roles and states. Don't use ARIA to patch what proper HTML would handle natively.
- Captions and audio descriptions: Any video with speech needs accurate captions. Pre-recorded visual content needs audio descriptions if the audio track doesn't convey it.
Accessible Sites Convert Better
Accessibility and conversion optimization solve the same problems. Siteimprove's business case analysis found that accessible forms are simply easier forms — for everyone. Clear heading hierarchies help all visitors find information faster. Openreach doubled monthly visits from 250,000 to 450,000 after pairing accessibility improvements with SEO work.
The Elementor ROI analysis documented a company whose conversion rate among accessibility-feature users more than doubled, with annual revenue growing tenfold relative to the project cost. Legal & General saw a 90% conversion increase post-remediation. Every friction point you remove from navigation or checkout helps every user — not just those using assistive technology.
There's also the market-size argument: 1.3 billion people globally live with a significant disability, controlling trillions in purchasing power. An inaccessible site turns away one in six potential customers before they read a single word. And clean, semantic HTML is what search engines prefer too — accessibility improvements routinely lift technical SEO performance alongside conversions, a point we explore in our post on technical SEO for AI-driven search.
How IseMedia Builds Accessibility In From the Start
At IseMedia, accessibility isn't a post-launch audit or an add-on — it's built in from the first wireframe. Semantic HTML structure, proper ARIA implementation, and contrast verification happen in the design phase. Keyboard and screen reader testing happen before launch. We don't install a widget and call it compliant. We fix the code.
If your current site was built without accessibility in mind — and the 94.8% failure rate suggests most were — remediation is manageable when approached systematically. As part of our web design and development services, we prioritize the highest-impact issues first: forms, navigation, images, and contrast. You get a site that's legally defensible and converts better.
Ready to make your site accessible and convert better at the same time? Get in touch with IseMedia — we'll audit what you have and build a remediation plan that actually works.