Salomon Web Services Salomon Web Services
Get a free quote
Home/ Blog/ Web Design
Web Design

Web Accessibility for US Small Business: ADA Compliance and Why It Matters in 2026

ADA accessibility lawsuits against US small business websites went from a rare occurrence in 2018 to over 4,000 federal filings per year in 2025. Most US small business owners don't know their website is non-compliant. Most law firms specializing in this area target small businesses specifically because they're easier targets than enterprise sites. The compliance work is bounded and achievable. The legal risk of ignoring it is real and growing. Here is what you need to know.

Salomon Web Services · May 30, 2026 · 11 min read
Accessibility audit dashboard showing WCAG 2.1 AA compliance score and violation list

The Americans with Disabilities Act (ADA) was signed in 1990, before the modern web existed. Federal courts have spent the last decade establishing that ADA applies to commercial websites, not just physical premises. In 2025, the legal landscape settled to a clear position: US commercial websites must be accessible to users with disabilities, and businesses that aren’t are exposed to lawsuits.

The volume of these lawsuits has grown dramatically. Around 800 federal ADA website lawsuits were filed in 2018. By 2025, that number was over 4,000 federal cases, with thousands more demand letters that never made it to court because businesses settled quickly. The targets have shifted from large enterprises (which mostly fixed their sites in 2019-2020) to small and mid-size businesses (which mostly haven’t).

The good news is that compliance is achievable and bounded. The bad news is that the cost of getting caught non-compliant is higher than the cost of getting compliant. Most small business owners learn this when they receive the demand letter.

What ADA compliance actually means for websites

The legal standard most courts apply is WCAG 2.1 Level AA, published by the W3C. This is a set of 50 specific success criteria covering four principles:

Perceivable. Information must be presentable to users in ways they can perceive. Includes alt text on images, captions on videos, sufficient color contrast, text that can be resized.

Operable. Interface components must be operable by all users. Includes keyboard navigation for everything (no mouse-only interactions), enough time to read content, no content that triggers seizures.

Understandable. Information and operation must be understandable. Includes readable text, predictable behavior, input assistance for forms.

Robust. Content must be robust enough to work with current and future assistive technologies. Includes proper HTML semantics, ARIA labels where needed, compatibility with screen readers.

For a typical US small business website, full WCAG 2.1 AA compliance requires addressing 30-50 specific issues that almost every site has. Most are fixable in hours, not days.

The most common violations we find

After auditing hundreds of US small business websites for accessibility, the patterns are consistent. The 10 violations that show up on almost every non-compliant site:

1. Missing alt text on images. Every meaningful image needs descriptive alt text. Decorative images need empty alt attributes. Most small business sites have images with no alt text at all, which makes the page unreadable for screen reader users.

2. Insufficient color contrast. Text needs to have at least 4.5:1 contrast ratio against its background (3:1 for large text). Light gray text on white backgrounds is the most common violation. So is white text on light-colored hero images.

3. Form fields without labels. Every form field needs a programmatically associated label that screen readers can announce. Placeholders alone don’t count. Most contact forms on small business sites fail this.

4. Links without descriptive text. “Click here” and “Read more” tell screen reader users nothing about where the link goes. Every link needs descriptive text that makes sense out of context.

5. Non-keyboard-navigable interactive elements. Custom buttons, dropdowns, modals, and carousels often work only with a mouse. Keyboard users can’t operate them. WCAG requires everything to be reachable and operable via keyboard alone.

6. Missing or incorrect heading hierarchy. Pages need a logical heading structure: one H1 per page, H2s for major sections, H3s for subsections. Many sites use heading tags for visual styling rather than structure, breaking screen reader navigation.

7. Auto-playing video or audio. Anything that plays automatically without user control violates WCAG. Hero videos that auto-play with sound are a common issue.

8. Missing language declaration. The <html> tag needs lang="en" (or appropriate language code) so screen readers use the correct voice and pronunciation.

9. Images of text instead of actual text. Text rendered as part of an image isn’t readable by screen readers. Logos are acceptable. Body content rendered as images is not.

10. No skip navigation link. Keyboard users need a way to skip past the navigation menu to get to the main content. Most sites don’t have this.

If your site has 5+ of these (most non-audited small business sites have 7+), it’s not WCAG 2.1 AA compliant.

The lawsuit landscape

The reason ADA website compliance has become urgent is the lawsuit volume. The pattern is consistent:

  1. A plaintiff (often the same handful of repeat plaintiffs in each state) uses a screen reader to visit your website
  2. Their attorney sends a demand letter citing specific WCAG violations
  3. The demand letter offers to settle for a defined amount (typically $5,000-$25,000 plus a commitment to remediate the site)
  4. Most businesses settle because litigating costs more than the settlement
  5. Some businesses receive multiple letters from different plaintiffs over the years if the site stays non-compliant

The targets are specifically small businesses because:

In some states (California, New York, Florida especially), specialized law firms have built ADA website lawsuits into a high-volume practice. They use automated tools to scan websites for violations and file lawsuits in batches.

What compliance actually requires

For a typical US small business website, the path to WCAG 2.1 AA compliance involves:

Phase 1: Audit (1-2 weeks)

The audit produces a specific list of what needs to be fixed.

Phase 2: Remediation (4-8 weeks for most sites)

For most small business sites, the remediation is 40-80 hours of focused work. WordPress sites often take longer because page builders inject inaccessible markup that’s harder to fix without rebuilding sections.

Phase 3: Documentation (1 week)

The accessibility statement plus documentation of good-faith compliance efforts is a meaningful legal defense if a lawsuit does come.

What compliance does not require

The accessibility space has its share of misinformation and overlay tools that promise “instant compliance”. Two clarifications:

Overlay widgets (accessiBe, UserWay, AudioEye) don’t make you compliant. These tools add a floating accessibility menu to your site. They do not actually fix the underlying violations. They’ve been the subject of multiple lawsuits themselves, and many courts have rejected them as a defense. Some accessibility advocates consider them actively harmful. Real compliance requires fixing the actual code, not adding a widget.

You don’t need to make your site usable for every possible disability. WCAG 2.1 AA is the legal standard. AAA-level compliance is aspirational but not required. Some specific accessibility considerations (like sign language interpretation for videos) are AAA-level and not required for AA compliance.

You don’t need a complete rebuild. Most small business sites can be remediated within their existing structure. Rebuilding is sometimes necessary for sites with severe structural accessibility issues, but it’s not the default path.

The cost reality

The cost of compliance vs the cost of non-compliance:

Compliance:

Non-compliance (if a lawsuit comes):

The math heavily favors proactive compliance. The work is the same. The difference is timeline pressure and legal cost.

Industries with elevated risk

Some US small business industries face disproportionate ADA website lawsuit risk:

If your business is in any of these categories and your website hasn’t been audited for accessibility in the last 2 years, the risk is meaningfully higher than average.

Even setting aside legal risk, web accessibility delivers tangible business value:

Treating accessibility as purely a legal compliance burden misses the customer-side value.

Where to start this quarter

If you’ve never had your site audited for accessibility, the order of operations:

  1. Run WAVE on your homepage to get an initial sense of violation volume
  2. Run Lighthouse accessibility audit in Chrome DevTools on 5 key pages
  3. Test keyboard-only navigation on your contact form
  4. Check color contrast on your primary text against backgrounds using WebAIM Contrast Checker
  5. Based on what you find, decide whether to fix in-house or engage an accessibility-focused agency

For most US small businesses, a focused 90-day compliance project closes the gap from “exposed” to “compliant with documentation”. The work is bounded. The legal protection is real. The customer-side benefits are durable.

The cost of waiting is asymmetric. Compliance work costs the same whether you do it on your timeline or under lawsuit pressure. Choosing your own timeline is meaningfully cheaper than choosing a plaintiff’s.

Want to apply this to your business?

We'll walk you through the implementation step by step, no commitment required.

Get a free quote More articles