A demand letter is how most small business owners learn that website accessibility is a legal issue. By the time it arrives, the cheap window has already closed.
In 2024, plaintiffs filed 4,187 digital accessibility lawsuits in the United States, according to UsableNet's tracking. Roughly two-thirds of them named companies earning under $25 million a year. Your storefront does not need to be famous to get sued. It needs a form field without a label.
This is a plain-English map of what the law points to in 2026, who is now in scope, and the short list of fixes that removes most of the risk.
Why this landed on your desk in 2026
The volume keeps climbing. UsableNet counted 2,019 digital accessibility suits in the first half of 2025 and projected the full year to run nearly 20% ahead of 2024, which would push the annual total toward 5,000.
The targets are not just national brands. An analysis by TestParty found that 67% of 2024 ADA website lawsuits named companies with under $25 million in revenue, many of them merchants on common e-commerce platforms. UsableNet's mid-2025 data tells the same story: about 64% of sued companies sat below that line.
Settlements usually run between $5,000 and $20,000 before legal fees, per Accessible.org, and very small businesses sometimes settle for less if they resolve early and commit to fixes. The trap is that the money rarely ends the work. A settlement still obligates you to remediate the site, often with an outside auditor, and paying one plaintiff does not stop the next one from filing.
Small businesses are especially exposed to demand letters, the pre-lawsuit version, because they rarely have in-house counsel or an accessibility team and may not know the rules exist until the envelope shows up.
What the law actually points to: WCAG
No US statute spells out a line-by-line web standard. Instead, courts, regulators, and settlement agreements keep pointing to the same reference: the Web Content Accessibility Guidelines, or WCAG, published by the W3C.
WCAG is built on four ideas. Content should be perceivable, operable, understandable, and robust. It sets testable criteria at three levels: A, AA, and AAA. AA is the level that laws and contracts almost always cite.
The version matters. WCAG 2.1 arrived in 2018. WCAG 2.2 became the current recommendation in 2023, adding criteria and retiring the old 4.1.1 Parsing rule. The new 2.2 items at AA are practical, not academic:
- Focus Not Obscured (2.4.11): the keyboard focus outline cannot be fully hidden behind a sticky header, a cookie banner, or a chat widget.
- Target Size (2.5.8): tap targets need a minimum size or enough spacing, which matters most on mobile.
- Dragging Movements (2.5.7): sliders and drag-and-drop need an alternative that does not require a precise drag.
- Accessible Authentication (3.3.8): login cannot depend on a memory or puzzle test with no accessible path, which puts pressure on hard CAPTCHAs.
The US government has now codified a version. In April 2024 the DOJ adopted WCAG 2.1 AA as the binding standard for state and local government sites under ADA Title II. The compliance dates were later extended by a year, so larger entities have until 2027 and smaller ones until 2028. Title II covers government, not your shop, but it sets a benchmark that courts and plaintiffs read across to private businesses.
The practical takeaway is simple. Build to WCAG 2.2 AA. You meet the newest guidance and the 2.1 AA baseline that current rules name, in one body of work.
The European Accessibility Act now reaches across the Atlantic
If EU shoppers can buy from you, the rules are no longer only American.
The European Accessibility Act, Directive (EU) 2019/882, became enforceable through national laws on 28 June 2025. It covers mainstream consumer digital products and services, including e-commerce, and legal guidance from firms like Bird & Bird is clear that it can apply to sellers based outside the EU who serve EU consumers. The functional requirements echo WCAG: services must be perceivable, operable, understandable, and robust.
The penalties are not symbolic. Analysis from Fieldfisher notes that non-compliant operators can face administrative fines up to 1,000,000 EUR in some member states, alongside restrictions on selling a product or service. Micro-enterprises get limited relief from certain service obligations, but that carve-out is narrower than most owners assume, so do not treat "we're small" as a clearance.
Two ways to handle accessibility. One is far cheaper.
The technical work is similar either way. The cost, the timing, and the stress are not.
Wait for the demand letter
You pay a settlement first
Most ADA website settlements land between $5,000 and $20,000, before legal fees. You spend the money and you still have to fix the site afterward.
You fix on someone else's clock
A complaint usually names around 15 issues and gives you a deadline. Now the same remediation happens under pressure, with a lawyer billing hours.
Settling once does not protect you
A second plaintiff can file over the same site. Incomplete fixes invite repeat suits in the same industry and region.
Customers were already turned away
Every barrier that triggered the claim also lost you real buyers, quietly, for as long as it sat there.
Build it in from the start
Fixes cost a fraction of a settlement
High-contrast text, alt text, labeled forms, and keyboard support are design decisions, not emergencies. They cost the most when retrofitted in a panic.
You set the timeline
An audit and a punch list let you fix the high-impact items first and schedule the rest. No deadline imposed by a stranger.
One standard covers most jurisdictions
Aim at WCAG 2.2 AA and you satisfy US ADA expectations and the EU's functional requirements with a single body of work.
You win the customers instead
An accessible checkout and a readable page convert the same shoppers a barrier would have sent to a competitor.
The failures that actually get cited
You can predict most complaints, because the issues are the same ones automated tools catch. The 2026 WebAIM Million study scanned the top one million home pages and found detectable WCAG failures on 95.9% of them, with an average of 56.1 errors per page. The most common problems:
- Low-contrast text: on 83.9% of home pages, the single biggest category.
- Missing image alt text: on 53.1% of pages; about 16.2% of all home page images had no alt text.
- Missing form labels: on 51% of pages; a third of form inputs were not properly labeled.
- Empty links: on 46.3% of pages.
- Empty buttons: on 30.6% of pages.
Now compare that to what plaintiffs actually allege. Accessible.org reports that complaints usually name around 15 issues, and the top three are missing alternative text, missing form labels, and lack of keyboard navigability. The overlap is not a coincidence. The cheapest tools to scan a site are also the first ones a plaintiff's firm runs.
The barriers that get you sued are the same ones turning away paying customers. Fix them once and you reduce legal risk and recover revenue in the same move.
That overlap is the good news. The most-cited failures are the most detectable, and the most fixable.
A realistic plan for a small team
You do not need a compliance department. You need a defined project and a short punch list.
- Run an audit. Start with free scanners like WAVE, axe, or Lighthouse to find contrast, alt text, label, and empty-element problems. They catch the high-volume issues fast.
- Fix the big four first. Raise text contrast to AA, write meaningful alt text for every non-decorative image, label every form field, and give links and buttons real accessible names. That clears most of what shows up in complaints.
- Test the keyboard by hand. Unplug the mouse. Tab through the whole site. Can you reach every menu, open every modal, complete checkout, and always see where focus is? Keyboard navigability is the top issue scanners miss and lawyers love.
- Publish an accessibility statement. State your target standard, how to report a problem, and how to reach you. It signals good faith and gives users a path that is not a lawsuit.
- Re-test after every redesign. WebAIM links rising errors to rising page complexity and heavier use of ARIA. New features quietly reintroduce barriers, so accessibility is a routine, not a one-time cleanup.
If you are rebuilding anyway, bake these rules into your components and tokens once. A shared system means contrast, focus styles, and labeled fields ship correct by default instead of being patched page by page.
The market you are leaving at the door
Risk is only half the case for doing this. The other half is demand.
The WHO estimates that about 1.3 billion people, roughly 16% of the world, live with a significant disability. The Return on Disability Group puts the disposable income of people with disabilities above $2.6 trillion. That is before counting the friends and family whose buying decisions bend toward businesses that are easy to use.
An inaccessible site is not neutral. It is a checkout that quietly rejects a sizable share of shoppers, then never tells you why your numbers are soft. If you have wondered why your site isn't converting, accessibility belongs on the list of suspects.
Accessibility is not a plugin you install the week a letter arrives. It is built into the markup, the contrast, the labels, and the keyboard paths of the site itself. We bake WCAG 2.2 AA into every build through our web design work, and we run accessibility audits on existing sites before a demand letter forces the timeline. If you want to know where you stand, tell us about your site and we will give you a straight read.
FAQ
Questions, answered.
The questions business owners ask us once a demand letter, or the fear of one, shows up.
US courts increasingly treat the websites of businesses that serve the public as covered by the ADA, even though the law predates the web and names no specific standard. In practice, plaintiffs and the DOJ both point to WCAG as the benchmark. If you sell or book or inform customers online, assume you are in scope.
Target WCAG 2.2 Level AA. It is the current W3C recommendation, it builds on 2.1, and meeting it also satisfies the WCAG 2.1 AA that current US rules reference. You get the newest criteria and the older legal baseline in one pass.
It can. The EAA applies to businesses that sell goods or services to consumers in the EU, including sellers based outside the EU. If EU shoppers can buy from your store, the functional accessibility requirements that took effect on 28 June 2025 may reach you.
Far less than a lawsuit if you do it deliberately. An audit plus remediation of the common failures is a defined project. Compare that to a settlement of $5,000 to $20,000 plus legal fees plus the remediation you would still owe.
Overlays do not reliably fix the issues most often cited in complaints, and several have themselves been named in lawsuits. Real conformance comes from accessible markup, contrast, labels, and keyboard support in the page itself, not a bolt-on script.
