Website Accessibility Compliance: What Small Businesses Must Know

If you think ADA lawsuits over inaccessible websites only happen to big-box retailers, the numbers say otherwise. Website accessibility compliance has quietly become one of the most expensive blind spots in small business web development — and in 2026, the exposure is bigger than ever.

Research from UsableNet found that 64% of sued companies had annual revenue under $25 million, meaning the clear majority of targets are small and mid-sized businesses, not national chains. That statistic alone should change how every small business owner thinks about their website — not as a marketing brochure, but as a legal asset that needs to meet a real, testable standard.

Why Website Accessibility Compliance Suddenly Matters So Much

Accessibility lawsuits aren't a new phenomenon, but the pace has accelerated sharply. More than 5,000 federal and state lawsuits over website accessibility were filed in the United States in 2025, according to litigation tracker UsableNet's 2026 lawsuit trends report. The businesses getting hit aren't random either — nearly 70% of those suits targeted e-commerce and retail sites, many of them small operations selling through WooCommerce, Shopify, or Magento.

These cases rarely start with a courtroom summons. Most cases don't start in court. They start with a demand letter from a plaintiff's attorney, typically asking for $10,000 to $25,000 to settle before filing. And this isn't a scattershot problem — a small group of just 16 law firms filed more than 90% of all website accessibility lawsuits in the first half of 2025, meaning this is a volume business model, not scattered individual complaints.

The Cost Compounds If You Ignore It

• Demand letter settlements typically run from $5,000 to $25,000, before factoring in legal defense costs of $30,000 to $175,000 and the required remediation work.
• Fixing the letter doesn't end the exposure: 46% of federal ADA website cases in 2025 involved a defendant who had already been sued at least once before, and fixing the underlying issue is what actually stops the cycle.
• Certain industries are especially exposed — restaurants, food, and beverage businesses made up over 30% of filings in the first half of 2025.

What Standard Are Courts Actually Using?

There's no single accessibility law written specifically for private business websites, which creates a lot of confusion. In practice, courts generally expect businesses to conform to WCAG 2.1 Level AA or WCAG 2.2 Level AA standards, and failure to meet these specific technical criteria is routinely interpreted as a violation of the ADA's mandate to provide equal access.

WCAG 2.2 added several new requirements that many older sites simply don't meet. Two of the most commonly missed:

• Focus visibility: when keyboard users tab through interactive elements, the focus indicator must not be completely hidden by other page content — something that commonly fails when sticky headers, cookie banners, or chat widgets cover the currently focused element.
• Target size: buttons, links, and other interactive elements must meet a minimum target size of 24x24 CSS pixels, and small buttons that are difficult to tap on mobile are now a compliance issue.

A Quick Word of Warning on "Overlay" Widgets

If you've searched for a fast fix, you've probably seen one-click accessibility overlay widgets advertised as instant compliance. Be skeptical. A lot of business owners respond to compliance fears by installing an accessibility overlay widget, but in 2025 the FTC fined overlay vendor AccessiBe $1 million for misrepresenting its widget as guaranteed ADA compliance. These tools can even flag a site as a target, since plaintiffs' firms know overlays rarely fix underlying code issues.

Custom Build, Website Builder, or Developer? What to Ask

Whether you're launching a new site or auditing an existing one, the platform you choose changes how accessibility gets handled — and who's responsible for it.

Questions to Ask Any Web Developer or Agency

• Do you test manually with a screen reader, or only run an automated scanner? (Automated tools miss a large share of real issues.)
• Will the site be built to WCAG 2.2 Level AA from the start, not retrofitted later?
• How do you handle color contrast, alt text, form labels, and keyboard navigation in the build process?
• What's your plan for ongoing monitoring as I add new pages, images, or plugins?
• Can you provide a written accessibility statement and remediation report?

Builders vs. Custom Development

Website builders like Wix, Squarespace, and Shopify have improved their built-in accessibility features, and some vendors now offer specialized accessibility certification for site builders working within those platforms. But templates alone don't guarantee compliance — plugins, custom scripts, image galleries, and third-party checkout widgets are frequently where violations creep in. Custom-built sites give a developer full control over markup and interaction patterns, which is valuable for complex sites, but only if accessibility is treated as a build requirement, not an afterthought bolted on right before launch.

A Realistic Starting Checklist

• Run a manual accessibility audit against WCAG 2.2 AA, not just an automated scan
• Add descriptive alt text to every meaningful image
• Verify color contrast ratios on text, buttons, and links
• Test full keyboard navigation without a mouse
• Label every form field clearly for screen readers
• Document your fixes in case a demand letter ever arrives

The Bottom Line

Website accessibility compliance isn't a niche legal issue anymore — it's a core part of responsible small business web development. The good news is that most fixes are well understood, reasonably affordable when built in from the start, and they make your site genuinely better for every visitor, not just a legal checkbox. Waiting until a demand letter shows up is the most expensive way to solve this problem.

If you're planning a new site, redesigning an existing one, or just want to know where your current site stands, don't guess. Talk to a developer who treats accessibility as a build standard, not an add-on — your future self (and your legal budget) will thank you.