Most small-business owners meet website accessibility in the worst possible order: a letter first, the rules second. This guide reverses that: what the Americans with Disabilities Act and the European Accessibility Act actually ask of a small website, what the 2025 lawsuit numbers say, what it costs on both sides, and the order in which a builder would fix a typical small site — written by a web-development team, not by lawyers. It is general information about the technical side. It is not legal advice, and if you have received a demand letter or a complaint, the first call belongs to an attorney; the checklist near the end covers evidence and the fix, not how to respond.
Does my small business website need to be ADA compliant?
If your business is open to the public, the US Department of Justice’s answer is yes. In its guidance on web accessibility and the ADA, published on ada.gov in March 2022 and still live, the Department states that it has held since 1996 that the ADA applies to web content — the goods and services a business offers online are covered by Title III’s ban on discrimination by places of public accommodation (retail stores to medical offices). Is there a small-business exemption? No. Title III contains no size carve-out; the employee thresholds people half-remember belong to employment law and to the tax credit discussed below, not to the duty itself. Is there a checklist I can be certified against? Also no. The Department says it “does not have a regulation setting out detailed standards” for private-business websites, and that businesses “have flexibility in how they comply”. As the technical yardstick it points to WCAG and the federal Section 508 standards. In practice, WCAG Level AA is the benchmark audits, settlements and court orders use — the Department wrote WCAG 2.1 Level AA into its 2024 rule for state and local government websites (governments, not your business), which is why “2.1 AA” is the phrase the industry works to. Aim at WCAG 2.2 AA, the current version, and you cover it.
What the 2025 lawsuit numbers actually say
Two trackers count these cases and count different things; any guide quoting one number without its scope is selling you something. Both, labelled:
| Tracker (2025) | Count | What it covers |
|---|---|---|
| Seyfarth Shaw LLP, ADA Title III tracker | 3,117 | Website accessibility lawsuits in federal court only — up 27% on 2024’s 2,452 |
| UsableNet, 2025 Year-End Report | 5,114 | Digital accessibility lawsuits — federal courts (3,195) plus New York and California state courts (1,919); websites, apps and video; 1 Jan – 15 Dec 2025 |
The pattern inside UsableNet’s count is the part a small business should read twice. About 70% of filings targeted ecommerce businesses, with food service second at about 21%. 64% of the companies sued had under $25 million in annual revenue — small and mid-sized businesses are the main defendants, not collateral damage. And 1,427 of the 2025 suits targeted companies that had already faced a claim, which kills the comforting idea that one settlement buys permanent peace: the fix is the protection, not the payment. Finally, almost every site is technically exposed — WebAIM’s 2026 scan found detectable WCAG failures on 95.9% of the top one million home pages, an average of 56.1 errors per page.
What it costs to be sued vs what it costs to fix
Settlements are confidential, so every figure below is a practitioner-reported range — an informed estimate, not a statistic.
| Route | Reported cost | Source of the range |
|---|---|---|
| Demand letter, settled before any filing | Commonly $5,000–$20,000; smaller businesses often settle for under $5,000 | Accessible.org’s settlement explainer, cited in TestParty’s 2026 cost breakdown |
| Lawsuit filed, all-in (settlement + your lawyers + their fees + deadline remediation + your team’s hours) | Modelled at roughly $15,000–$90,000 for a small or mid-sized business | TestParty’s line-item cost model |
| Proactive remediation of a typical small online store | $1,500–$3,000, once (12–23 hours of work) | One agency’s published worked example (a typical Shopify store brought to WCAG 2.2 AA) |
| An overlay widget subscription, for contrast | $49–$99/month — $600–$1,200 a year, indefinitely | Same worked example |
Two things soften the proactive side further. The federal Disabled Access Credit (IRC §44, claimed on Form 8826) returns 50% of eligible access spending above $250 and up to $10,250 — a maximum credit of $5,000 a year — to businesses that meet either size test: prior-year gross receipts of $1 million or less, or no more than 30 full-time employees. The economics are not subtle: nearly every settlement requires the same remediation anyway, on the plaintiff’s timetable — the fix costs the same money in both columns; in one of them it arrives with lawyers attached. Confirm with your tax adviser whether your website work qualifies for the credit.
The overlay trap: why a widget is not compliance
The product most small businesses reach for first is an accessibility overlay — one line of JavaScript, a toolbar button, a promise of instant compliance. That promise is now a documented enforcement record. In January 2025 the Federal Trade Commission announced an order against accessiBe over claims that its product could make any website compliant with WCAG; the final order, issued in April 2025, requires accessiBe to pay $1 million and bars it from claiming its automated product can make a website WCAG-compliant — or keep it compliant — without competent and reliable evidence. The complaint also alleged that accessiBe’s apparently independent reviews were paid placements. accessiBe neither admitted nor denied the allegations, and the order does not make overlays illegal; it makes the core sales pitch — install this and you are compliant — a claim the federal government has formally treated as deceptive. The litigation data agrees with the regulator: UsableNet counted 1,416 lawsuits in 2025 against companies whose websites had an accessibility widget installed — nearly a quarter of cases, on one tracker’s count. Overlays adjust the rendered page for some users and can be a genuine convenience feature, but they cannot repair the underlying markup: they do not write your missing alt text, label your checkout fields, or fix a keyboard trap in your menu — the failures complaints actually cite.
WCAG 2.2 AA in plain English
WCAG — the Web Content Accessibility Guidelines, published by the W3C — is a list of testable requirements organised under four ideas: content must be perceivable (a screen reader can speak it; text has real contrast), operable (everything works from a keyboard; nothing traps focus), understandable (labels and error messages make sense) and robust (standard code that assistive technology can parse). Each requirement sits at Level A, AA or AAA; Level AA is the conformance level laws and settlements reference. Version 2.2 (October 2023) is current; meeting it also meets 2.1, and in October 2025 WCAG 2.2 was approved as the international standard ISO/IEC 40500:2025. Your site needs to pass its AA checks — for a small site, a finite, mostly mechanical list:
The fix-first checklist: a small-site WCAG triage
Automated scans find perhaps a third of WCAG issues, but they find the ones complaints are built from. Analyses of filed complaints put the same failures at the top — missing alt text first, then contrast, unlabelled forms and keyboard problems — and the DOJ’s guidance names the same barriers. Fix in this order:
- Images that say nothing. Every meaningful image needs a text alternative; decorative images need an empty one so screen readers skip them. Start with product photos, banners and image buttons. (WCAG 1.1.1 — the single most-cited failure in complaints.)
- Text nobody can read. Body text needs a contrast ratio of at least 4.5:1 against its background (3:1 for large text). Light-grey text on white, text over photos and pale brand colours are the usual offenders.
- Forms that cannot be completed blind. Every field in your contact, checkout and booking forms needs a visible, linked label — a placeholder is not a label — and errors must be announced in text, not by a box turning red alone.
- Keyboard traps and invisible focus. Tab through your whole site: every link, menu and button must be reachable, focus visible, menus and pop-ups openable and closable, with no traps. Cookie banners and chat widgets are frequent offenders.
- Links and buttons that say “click here”. Screen-reader users navigate by link lists; every link and icon button needs a name that states its purpose (“Size guide”, not a bare magnifier icon).
- Headings and page structure. One clear page heading, headings in order, the page language set — cheap theme fixes that make the fixed content navigable.
- Video and audio. Captions for video with speech, transcripts for audio. If you publish neither, record that and move on.
- The paper trail. Publish an accessibility statement naming the standard you target, the date of your last check and a contact route for barriers — then keep the audit and fix records. A statement is not a legal shield, but a business that can show dated, genuine remediation work is in a different conversation from one that cannot.
On WordPress, items 1–6 mostly live in your theme and your content habits; on Shopify, in your theme and product data. Folding the list into a rebuild is cheaper still — which is why our website redesign scorecard scores accessibility basics and our website development work builds to WCAG 2.2 AA from the start.
Sell to Europe? The EAA in five minutes
The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025, through each member state’s national law. Three points decide whether it concerns you. Scope: it covers a defined list of consumer services — e-commerce, consumer banking, e-books, electronic communications, access to audiovisual media and parts of passenger transport. A general brochure site is not on the list; an online shop selling to EU consumers is. It is market-based, not address-based: a US or other non-EU business offering a covered service to EU consumers is in scope exactly as a local one is. There is a genuine small-business exemption here — the one the ADA does not have: microenterprises providing services — fewer than 10 people and turnover or balance-sheet total of no more than €2 million — are exempt from the service requirements. It covers services only — not the directive’s product rules — and lapses as you cross either threshold. The technical standard referenced for the EAA is EN 301 549, which tracks WCAG — a site remediated to WCAG 2.2 AA has done the substantive work for both regimes. Penalties are set by each member state; the summary: the duty is live, the exemption is narrow, and “we are not in Europe” is no exemption if your checkout is.
Got a demand letter? The first 72 hours, technically
This section is deliberately not about the letter itself — responding, and any negotiation, is your attorney’s work, and the ranges above are why taking one early is cheaper than taking one late. What follows is the technical half:
- Do not “fix” anything yet, and do not delete anything. Changing the site before it is documented can look like destroying evidence. Take dated screenshots and a full backup of the site as it stands.
- Run and save a scan. Run a free automated audit of the pages the letter names and save the dated report. It will not be complete; it is the start of the record — and the same scan the other side likely ran.
- Write down what exists. Any prior accessibility work, audits, statements or vendor contracts — including that overlay subscription and what it promised you — goes in the same folder.
- Then start the triage above, in order, and keep the records. Remediation begun promptly and documented honestly is the one asset every account of these cases agrees on — the site has to be fixed anyway, and dated work is worth more than undated intentions.
FAQ
Is there a small-business exemption from the ADA for websites?
No. Title III’s duties apply to businesses open to the public regardless of size, and the DOJ’s web guidance has no size carve-out. The exemptions owners half-remember are real but elsewhere: the EAA exempts microenterprises providing services, and the Disabled Access Credit has size tests. Neither switches off the ADA duty.
How much does ADA compliance cost for a small business website?
There is no certification fee and no official price — the cost is the remediation work. One agency’s published worked example prices a typical small online store at $1,500–$3,000, once (12–23 hours to WCAG 2.2 AA). Complex catalogues, custom booking flows and video libraries cost more; the Disabled Access Credit can return up to $5,000 a year of eligible access spending for qualifying businesses.
Is an accessibility widget or overlay enough to comply?
No. The FTC’s 2025 order against accessiBe — $1 million, and a bar on claiming an automated product makes a website WCAG-compliant without evidence — addresses the marketing claim; the litigation data addresses the practical one: UsableNet counted 1,416 lawsuits in 2025 against sites that had a widget installed. It is not remediation, and it is not a defence.
What is WCAG 2.2 AA in plain English?
The W3C’s current accessibility standard, at its middle conformance level: content that can be perceived, operated, understood and parsed by people using screen readers, keyboards and other assistive technology. It is the level the DOJ points to, the level in the government’s rule (as 2.1 AA) and the level named in settlements — and since October 2025, an ISO standard: ISO/IEC 40500:2025.
The short version
If you sell to the public, the ADA reaches your website; there is no small-business exemption, and the benchmark everyone works to is WCAG 2.2 AA. In 2025 that duty produced 5,114 tracked lawsuits on UsableNet’s count, about 70% of them against ecommerce and about two-thirds against companies under $25 million in revenue — while the typical small store’s proactive fix is priced in the low thousands, once, against five-figure demand settlements, with the same fix still owed at the end. A widget does not change any of this; the FTC has the order to prove it. Sell into the EU and the EAA adds its own duty, with a real but narrow microenterprise exemption. Work the triage list in order, keep the records, and if a letter has already arrived, preserve first and fix second — with a lawyer on the legal track from day one. If you want the technical half done properly, our website development team audits and remediates to WCAG 2.2 AA — get a quote and we will scan your site and price the fix list first.
A note on what this article does and does not claim
This article is general information written by a web-development team. It is not legal advice, and nothing in it predicts how a court, the Department of Justice or an EU authority would treat a specific business; obligations depend on facts this article cannot know, and a business that has received a demand letter or complaint should take its own counsel. The legal summaries are the DOJ’s published guidance on web accessibility and the ADA (ada.gov, March 2022 — rendered for this article through three independent summaries of that guidance, which agree; ada.gov was not fetched directly in this pass) and Directive (EU) 2019/882 as rendered in article-by-article summaries of the official text. The lawsuit counts are the trackers’ own — Seyfarth Shaw’s federal-only count and UsableNet’s broader federal-plus-two-state count measure different things and are labelled as such wherever they appear; neither counts demand letters, which all trackers agree outnumber filings. Settlement figures are confidential in practice; every range here is attributed to the practitioner source that published it and is an estimate, not a statistic. The proactive-remediation price is one agency’s published worked example for a typical small store, not a market survey, and it is labelled that way in the table. The Disabled Access Credit figures are the IRS Form 8826 rules (50% of eligible spending above $250 and up to $10,250, maximum $5,000 a year, either size test sufficient); whether a given business’s website expenditure qualifies is a question for its tax adviser, and the article says so where the credit is introduced. The FTC’s accessiBe order is stated from the FTC’s January 2025 announcement and the final order of April 2025, including that accessiBe neither admitted nor denied the allegations. WebAIM’s failure rates are from its 2026 Million report as published. No client’s site, audit or legal matter was used anywhere in this article.
— AI Dev Expert. Researched and drafted with AI assistance; reviewed against those sources.
