If you run a business with a website, 2025 delivered a warning worth paying attention to: more than 5,000 website accessibility lawsuits were filed in the United States, up from roughly 4,000 the year before. Website accessibility now accounts for about 36% of all ADA Title III filings—and on top of the lawsuits, an estimated 35,000 to 50,000 demand letters went out to businesses in a single year. For a founder focused on shipping product and finding customers, an accessibility complaint can feel like it comes out of nowhere. It doesn't have to.

This guide explains what ADA website compliance actually requires in 2026, why small and mid-size businesses are increasingly the target, and the practical path to getting compliant without wasting money on fixes that don't hold up.

Why website accessibility became a legal risk for every business

The Americans with Disabilities Act (ADA) predates the modern web, but US courts have consistently treated business websites as "places of public accommodation" under Title III. That means the law applies whether you sell software, ship physical goods, or book appointments online. Critically, there is no small-business exemption. A ten-person startup and a national retailer face the same standard.

What changed is the volume and the economics. In the first half of 2025, just 16 law firms filed more than 90% of all US website accessibility lawsuits. This is, functionally, a high-volume legal practice: identify sites with detectable barriers, send a demand letter, and settle quickly. Small businesses are attractive targets precisely because they tend to have more compliance gaps, smaller legal budgets, and a higher likelihood of settling to make the problem go away.

A newer wrinkle makes the math worse. Through 2025 and into 2026, self-represented plaintiffs have started using AI tools to scan websites, identify WCAG violations, and draft complaints—lowering the cost of filing and widening the net.

What a claim actually costs

The numbers are sobering. A typical demand-letter settlement runs between $5,000 and $25,000. If a case proceeds to litigation, legal defense costs commonly land somewhere between $30,000 and $175,000—before any remediation work. For most founders, proactive compliance is dramatically cheaper than a reactive scramble.

The standard courts actually reference: WCAG 2.1 and 2.2 AA

The ADA statute doesn't spell out technical requirements, so courts lean on the Web Content Accessibility Guidelines (WCAG). In 2026, businesses are generally expected to conform to WCAG 2.1 Level AA or the newer WCAG 2.2 Level AA. A practical way to think about it: treat WCAG 2.1 AA as your legal floor and WCAG 2.2 AA as your target, since 2.2 reflects current best practice and full coverage of the standard courts reference.

WCAG 2.2 adds nine new success criteria aimed at users with low vision, cognitive and learning disabilities, and motor impairments—including better support for touch-screen devices. Several states, including Colorado, have signaled they intend to move their own standards from 2.1 to 2.2.

There's also a hard government deadline shaping expectations across the board. Under a Department of Justice rule, state and local governments serving 50,000 or more people must make their websites conformant with WCAG 2.1 AA by April 24, 2026, with smaller entities following in 2027. Private businesses aren't bound by that specific date, but it cements WCAG 2.1 AA as the baseline everyone is measured against.

How far off is the average website?

Further than most founders assume. The WebAIM Million 2026 report—an automated analysis of the top one million home pages—found that 95.9% had at least one detectable WCAG failure, averaging 56.1 errors per page. And automated scans only catch a fraction of real barriers. The problems are usually mundane: images without alt text, form fields with no labels, poor color contrast, headings that don't follow a logical order, and interactive elements that can't be reached with a keyboard.

The overlay trap: why the quick fix backfires

When founders first learn about accessibility risk, many reach for an "accessibility widget" or overlay—a script you paste onto your site that promises instant compliance. It's an understandable instinct, but the evidence is clear that overlays are not a shield.

In 2024, more than 1,000 businesses with widgets installed were sued anyway, making up over a quarter of all digital accessibility lawsuits that year. In the first half of 2025, 456 lawsuits specifically targeted sites that had overlays in place. Courts have repeatedly rejected the argument that installing overlay software demonstrates compliance; when expert testing shows barriers remain, the software's marketing claims are legally irrelevant. In one high-profile outcome, the Federal Trade Commission reached a $1 million settlement with the largest overlay provider over deceptive claims that its widget could make sites ADA compliant.

The technical reason is simple: overlays are automated, and automation misses roughly 70% of WCAG issues. Software can generate alt text or tweak an ARIA attribute, but it can't understand the intent of a complex interface, repair a broken form workflow, fix illogical heading structures, or ensure keyboard navigation makes sense for someone using a screen reader. Those require real judgment and real code changes.

A practical path to genuine compliance

The reliable approach is proactive and rooted in your actual codebase—not a script bolted on top. For most businesses it looks like four steps:

1. Run a real audit

Combine automated scanning with manual testing—ideally including a person navigating your site with a keyboard and a screen reader. Automated tools flag the obvious issues fast; manual testing catches the ones that actually get sites sued. This gives you a prioritized list of what to fix and where the highest-risk barriers live.

2. Remediate at the source

Fix issues in your real HTML, CSS, and components: add meaningful alt text, label every form field, correct color contrast, restore a logical heading hierarchy, and make every interactive element keyboard-accessible. For teams building custom products, this is where thoughtful product development pays off—accessibility is far cheaper to bake in than to retrofit.

3. Monitor continuously

Accessibility isn't a one-time project. Every new page, feature, or marketing campaign can introduce fresh barriers. Build automated checks into your deployment process so regressions get caught before they reach production.

4. Train the team

The most durable fix is preventing new issues. When designers, developers, and content creators understand the basics, accessibility stops being a periodic fire drill and becomes part of how you build. This is especially true if you're layering in AI-driven features, where dynamic interfaces can quietly create new obstacles for assistive technology.

Accessibility is good business, not just risk management

It's easy to frame all of this as legal defense, but the upside is bigger than avoiding a lawsuit. Roughly one in four US adults lives with a disability. An accessible site reaches more customers, tends to rank better in search, and generally offers a cleaner experience for everyone. Building inclusive technology is core to how we think about social impact—doing right by users and building durable products are usually the same decision.

Where Esipick fits

At Esipick, we've spent since 2013 building custom software and digital products for founders and businesses who care about doing things properly. Accessibility is part of that craft—whether we're auditing an existing site, remediating it at the code level, or building a new product with WCAG conformance designed in from day one. We also explore what's next in inclusive, AI-powered software at esipick.ai.

If website accessibility has been sitting on your "we'll get to it" list, it's worth moving up. A short conversation can tell you where you stand and what real compliance would take. Book a call with our team and let's map out a path that protects your business and serves every one of your users.