There's a date coming up that most small business owners have never heard of: April 24, 2026.
That's the federal deadline for state and local governments serving 50,000+ people to make their websites meet WCAG 2.1 Level AA accessibility standards. It's a Department of Justice rule under ADA Title II.
"But I'm not a government agency," you're thinking. "Why should I care?"
Because the ripple effects are already hitting private businesses — hard. And if you think you're too small to be a target, the numbers say otherwise.
The Lawsuits Are Real — and They're Targeting Small Businesses
In 2025, over 5,100 ADA web accessibility lawsuits were filed in the United States. That's a 25% increase from 2024.
Here's the part that should get your attention: the majority of defendants were companies with less than $25 million in revenue. These aren't Fortune 500 companies. They're local businesses, e-commerce shops, service providers — businesses that look a lot like yours.
Nearly 70% of those lawsuits targeted online retailers. But restaurants, salons, contractors, professional services — anyone with a website that people use to interact with your business — is fair game.
And it's getting easier to sue. In 2025, self-filed lawsuits increased 40%, fueled by AI tools helping individuals draft legal complaints without a lawyer. Thirty-one plaintiffs alone were responsible for over half of all lawsuits filed in the first half of the year.
This isn't a hypothetical risk. It's an active, growing trend.
Wait — Does the ADA Actually Apply to My Website?
Here's the honest answer: there's no federal law that explicitly says "private business websites must meet WCAG 2.1 standards." The government hasn't written that rule yet for private companies.
But courts are consistently ruling that websites are places of public accommodation under ADA Title III. The landmark case was Robles v. Domino's Pizza in 2019, where the Ninth Circuit ruled that Domino's website and app were covered by the ADA because they connected to a physical business.
Since then, courts across the country have followed that reasoning. The DOJ has taken the same position. And when these cases go to court, the standard everyone points to is WCAG 2.1 Level AA — the same standard in the upcoming government deadline.
The penalties? Up to $75,000 for a first violation and $150,000 for subsequent violations under Title III. Plus attorney's fees. Plus the cost of fixing the site under a court order on someone else's timeline.
For a small business, that's not a fine. That's a catastrophe.
What Does "Accessible" Actually Mean?
WCAG 2.1 Level AA sounds technical, but the core ideas are straightforward. An accessible website means:
People can see your content.
- Images have descriptive alt text so screen readers can describe them to blind users
- Text has enough contrast against its background (at least a 4.5:1 ratio) so people with low vision can read it
- Videos have captions. Audio has transcripts.
- The layout doesn't break when someone zooms in to 200%
People can navigate your site without a mouse.
- Every button, link, and form field works with just a keyboard
- There's a visible indicator showing where you are on the page as you tab through elements
- Nothing flashes more than three times per second (seizure risk)
People can understand your content.
- Forms have clear labels and helpful error messages
- Navigation is consistent across pages
- The language of the page is declared in the code so screen readers pronounce words correctly
Your code works with assistive technology.
- The HTML is well-structured so screen readers and other tools can parse it correctly
That's it. No exotic technology. No expensive equipment. Just a website that works for everyone.
How Bad Is It Out There?
According to the WebAIM Million report — an annual analysis of the top one million home pages — 94.8% of websites have detectable accessibility failures. The average page has 51 errors.
The six most common failures account for 96% of all errors detected:
| Issue | % of Sites Affected | What It Means |
|---|---|---|
| Low contrast text | 79.1% | Text is too hard to read against its background |
| Missing image alt text | 55.5% | Screen readers can't describe images to blind users |
| Missing form labels | 48.2% | Screen readers can't tell users what to type in form fields |
| Empty links | 45.4% | Links exist but have no readable text |
| Empty buttons | 29.6% | Buttons have no accessible name |
| Missing page language | 15.8% | Screen readers may mispronounce all text on the page |
These same six issues have been the top failures for five consecutive years. The most common problems are also the most basic — and the most fixable.
If your site was built with a drag-and-drop builder, a free template, or by someone who wasn't thinking about accessibility, there's a very good chance it fails on multiple items in this list.
"But I Can Just Add an Overlay Widget, Right?"
You've probably seen them — those little accessibility icons that float in the corner of a website, promising one-click ADA compliance.
Don't.
In 2024, 25% of ADA lawsuits explicitly cited accessibility overlay widgets as barriers, not solutions. These tools don't fix the underlying code. They paint over problems with JavaScript that often introduces new ones. Courts have rejected them as evidence of compliance. Advocacy organizations for people with disabilities have openly opposed them.
An overlay widget on an inaccessible website is like putting a fresh coat of paint on a house with a crumbling foundation. It looks like you did something. You didn't.
Real accessibility means fixing the actual code — the HTML, the structure, the way content is organized and labeled. There are no shortcuts.
There's a Tax Credit Most Small Businesses Don't Know About
Here's the good news: the federal government actually wants you to make your website accessible, and they'll help pay for it.
The Disabled Access Credit (IRS Section 44) gives eligible small businesses a tax credit of 50% of accessibility expenses between $250 and $10,250 — up to $5,000 per year.
You qualify if your business had either:
- Gross receipts of $1 million or less in the previous tax year, OR
- 30 or fewer full-time employees
That covers the vast majority of small businesses in the Lowcountry — and probably yours.
The credit is claimed on IRS Form 8826 and can be used every year you incur qualifying expenses. There's also a separate deduction under Section 190 that allows up to $15,000/year for barrier removal — and you can use both in the same tax year.
So if you spend $2,000 making your website accessible, you could get $875 back as a tax credit (50% of $2,000 minus the $250 threshold). That's a significant offset for work that protects your business and serves your customers better.
Talk to your accountant about it. Most don't bring it up because they don't know it exists.
What You Should Do Right Now
You don't need to panic. But you do need to act. Here's a practical starting point:
1. Run a free audit. Go to wave.webaim.org and enter your website URL. It'll show you every detectable accessibility issue on the page — color contrast, missing alt text, empty links, all of it. It's free and takes 30 seconds.
2. Check your contrast. Use WebAIM's Contrast Checker to test your text colors against your backgrounds. You need at least a 4.5:1 ratio for normal text.
3. Try navigating your site with just your keyboard. Put your mouse away. Use Tab to move between elements, Enter to click, and see if you can get through your entire site. If you can't — or if you can't see where the focus is — that's a problem.
4. Check your images. Right-click any image on your site and inspect it. Does it have an alt attribute with a meaningful description? "IMG_4532.jpg" doesn't count. Neither does leaving it blank.
5. Talk to your developer. If you have one. If you don't, find one who understands accessibility — not someone who'll sell you an overlay widget and call it done.
How I Handle Accessibility
Every site I build includes accessibility as a baseline — not an add-on. That means:
- Semantic HTML structure that screen readers can navigate
- Proper heading hierarchy (H1, H2, H3 — in order, not for styling)
- Descriptive alt text on every image
- Labeled form fields with clear error messaging
- Sufficient color contrast across all text and backgrounds
- Keyboard-navigable interactive elements with visible focus states
- Declared page language in the HTML
- Valid, well-structured code that works with assistive technology
It's not extra work. It's just how websites should be built. And when you build them right from the start, you don't have to pay to fix them later — or worse, pay a lawyer to defend them.
The Bottom Line
Web accessibility isn't a government bureaucracy problem that doesn't affect you. It's a legal exposure, a customer experience issue, and — let's be direct — it's the right thing to do.
One in four American adults lives with a disability. That's your customers. Your neighbors. Your community. Building a website they can actually use isn't just smart business. It's basic respect.
The April 2026 deadline is for governments. But the lawsuits are for everyone. And they're not slowing down.
If you're not sure where your site stands, reach out or call me at (843) 619-7394. I'll take a look and tell you straight — no pressure, no sales pitch. Just an honest assessment of where you are and what it would take to get right.
Because fixing it now costs a fraction of what defending it later will.