If you run a small business in Shelby, Kings Mountain, Boiling Springs, or anywhere in Cleveland County and you have a website -- which you do, because no business survives without one in 2025 -- you need to understand something that most local business owners I talk to don't know: your website is a place of public accommodation under federal law. And there are law firms making a living suing small businesses exactly like yours for ADA violations on their websites. Have you ever thought about whether a screen reader can navigate your site? Most owners haven't. The lawyers have.
This isn't a hypothetical warning. In 2025, plaintiffs filed 3,948 federal ADA website accessibility lawsuits -- a 23.84% increase from the prior year. Over 5,000 total digital accessibility lawsuits were filed across all venues. The projection for 2026 is north of 5,500. This isn't slowing down. This is accelerating. And the most jarring statistic in the data: approximately 77% of all defendants in these federal cases are small businesses with annual revenues under $25 million. These aren't Amazon, Walmart, or Target getting sued. These are independent restaurants, local retailers, family-owned service businesses. Businesses exactly like the ones I work with every day in Cleveland County. If you're wondering whether your small business website is at risk, the answer -- looking at the data -- is almost certainly yes.
I've spent the last several weeks going through the UsableNet 2025 digital accessibility report, court filings, the Department of Justice's new April 2026 rule on web accessibility for state and local governments, and the WebAIM Million report. Here's exactly what's happening, why overlay widgets don't protect you, what the most common violations are, and what your small business needs to do about it -- with specific context for North Carolina. Because ignoring this won't make it go away. It'll make it more expensive.
- 3,948 federal ADA website lawsuits filed in 2025 -- up 24% year over year. 77% targeted businesses under $25M revenue.
- Average settlement: $25,000 to $30,000 -- not counting your attorney fees, remediation costs, or the hit to your reputation.
- Overlay widgets don't protect you -- 456 lawsuits successfully targeted sites that already had them installed. The underlying code was still non-compliant.
- 95.9% of the top million websites fail WCAG -- the four most common violations are fixable in an afternoon: low contrast text, missing alt text, unlabeled forms, and empty links.
| Metric | Value | Implication |
|---|---|---|
| Federal ADA website lawsuits (2025) | 3,948 | Up 24% year over year |
| Small business defendants | 77% | Revenue under $25M |
| Average settlement cost | $25K-$30K | Plus legal fees |
| Restaurant share of lawsuits | 35% | Most-sued industry |
| Top websites failing WCAG | 95.9% | 51 errors per page average |
| Lawsuits targeting overlay-widget sites | 456 | Widgets do not protect you |
In 2025 alone, plaintiffs filed 3,948 federal ADA website accessibility lawsuits, representing a 23.84% year-over-year increase. Crucially, approximately 77% of all defendants in these federal cases are small businesses with annual revenues under $25 million. Most of these entities lack dedicated in-house legal teams and are entirely blindsided when served with a federal complaint.
ADA Title III now applies to your website
Yes - federal courts have ruled that websites are places of public accommodation under the Americans with Disabilities Act. The same law that requires a wheelchair ramp at your front door now applies to your URL. If a screen reader cannot navigate your site or a keyboard-only user cannot complete a form, you are legally exposed regardless of your business size or location. The technical standard courts use is WCAG 2.1 AA, and the DOJ's April 2026 rule has formally codified that standard into federal regulation.
What WCAG 2.1 AA compliance requires
The Web Content Accessibility Guidelines 2.1 at the AA level covers a broad range of technical requirements: sufficient color contrast between text and backgrounds at a minimum ratio of 4.5:1, alternative text for every image, proper heading hierarchies that screen readers can navigate, labels on all form fields, keyboard-accessible navigation and interactive elements, captions on videos, and meaningful link text that describes the destination. These are the specific technical criteria that plaintiffs' attorneys scan for using automated tools. They are also the same violations I find on website redesign projects around Cleveland County every week. The most common failures - low contrast text, missing alt text, unlabeled forms, and empty links - account for the majority of WCAG failures on the web and appear on 95.9% of the top million homepages.
Why geography no longer protects small-town businesses
New York leads with 637 cases filed in the first half of 2025 alone. Florida had 487. California had 380. But the real story is Illinois, which saw a 746% year-over-year increase jumping from 28 cases to 237. This is no longer a coastal problem. Right here in North Carolina, the EEOC sued Butterball in Mount Olive over ADA violations, demonstrating that federal ADA enforcement is active and aggressive in our state. The idea that nobody enforces ADA requirements in small towns is false. Federal agencies and private plaintiffs' attorneys are paying attention to North Carolina businesses, and the lawsuits follow the money wherever a non-compliant website exists. Your location does not protect you. Only your website's code does, and with 3,948 lawsuits filed last year, ignoring accessibility is a bet that gets harder to win every quarter.
The Americans with Disabilities Act was passed in 1990, long before anyone was thinking about websites. Title III of the ADA requires places of public accommodation to be accessible to people with disabilities. For decades, that meant physical spaces: wheelchair ramps, accessible restrooms, Braille signage. But federal courts have increasingly ruled that websites are places of public accommodation under Title III. If your website isn't accessible to someone using a screen reader, navigating by keyboard only, or using voice navigation software, you are -- in the eyes of federal courts -- operating an inaccessible place of public accommodation.1 Think about that. The same law that requires a ramp at your front door now applies to your URL.
The technical standard that courts use to evaluate accessibility is the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level. This covers a broad range of requirements: sufficient color contrast between text and backgrounds, alternative text for images, proper heading hierarchies that screen readers can navigate, labels on form fields, keyboard-accessible navigation and interactive elements, captions on videos, and a host of other technical criteria. I'll walk through the most common violations shortly, because these are the ones getting small businesses sued -- and they're the same ones I find on website redesign projects around Cleveland County every week.2
The geographic spread of these lawsuits tells an important story. New York still leads with 637 cases filed in the first half of 2025 alone. Florida had 487. California had 380. But the real story is Illinois, which saw a 746% year-over-year increase -- jumping from 28 cases to 237. This is no longer a coastal problem. It's spreading everywhere, and North Carolina isn't exempt from this trend.
Right here in North Carolina, the EEOC sued Butterball in Mount Olive over ADA violations. That suit alleged Butterball failed to accommodate employees with disabilities and fired workers because of their disabilities. While that case involved employment discrimination rather than website accessibility specifically, it demonstrates that federal ADA enforcement is active and aggressive in North Carolina. The idea that "nobody enforces ADA stuff around here" is wrong. Federal agencies and private plaintiffs' attorneys are paying attention to North Carolina businesses.4
For a small business owner in Shelby or anywhere in Cleveland County, the takeaway is straightforward: you're not immune just because you're not in Manhattan or San Francisco. The lawsuits follow the money, and the money follows wherever there's a website that doesn't comply. Your location doesn't protect you. Only your website's code does. And if your site hasn't been audited for accessibility, you're betting your business that no one will notice. With 3,948 lawsuits filed last year, that's a bet getting harder to win.
Key point: The same federal law that requires a wheelchair ramp at your front door now applies to your website. Courts have ruled that websites are places of public accommodation. If a screen reader can't navigate your site, you're legally exposed -- no matter how small your business or how far you are from New York.
Accessibility overlay widgets don't protect you from lawsuits
No - overlay widgets do not protect you from ADA lawsuits, and the data proves it. In the first half of 2025 alone, 456 lawsuits successfully targeted websites that already had accessibility overlay widgets installed. That is 23% of all cases filed during that period. Plaintiffs' attorneys are not deterred by the presence of an overlay widget. If anything, the data suggests they may be targeting sites with overlays precisely because the overlays create a false sense of security while leaving the underlying code just as non-compliant.
Why overlays fail to fix the underlying code
Over the last few years, a cottage industry has grown up around accessibility overlay widgets. The little blue accessibility icon floating in the corner of a website promises to make the site ADA compliant with a single line of JavaScript. Companies like accessiBe, AudioEye, UserWay, and EqualWeb market these products aggressively to small business owners who are rightly concerned about compliance but lack the budget for a full audit. The problem is technical: an overlay widget sits on top of your existing code and tries to patch issues at runtime, but it cannot fix the underlying Document Object Model structure. It cannot repair broken ARIA hierarchies that screen readers rely on to navigate your site. It cannot add proper heading structures, fix missing form labels, add alt text to images that lack them, or ensure keyboard focus order makes logical sense. These are foundational issues in your HTML, CSS, and JavaScript that no runtime patch can resolve.
This is the single most important section of this article. If you read nothing else, read this.
Over the last few years, a cottage industry has grown up around accessibility overlay widgets. You've probably seen them -- the little blue accessibility icon that floats in the corner of a website, promising to make the site "ADA compliant" with a single line of JavaScript. Companies like accessiBe, AudioEye, UserWay, and EqualWeb market these products aggressively to small business owners who are rightly concerned about compliance but don't have the budget for a full accessibility audit and remediation. Sounds like a quick fix, right? That's the pitch.
Here's what the data shows: these widgets don't work. In the first half of 2025 alone, 456 lawsuits successfully targeted websites that already had accessibility overlay widgets installed. That's 23% of all cases filed during that period. Plaintiffs' attorneys aren't deterred by the presence of an overlay widget. If anything, the data suggests they may be targeting sites with overlays precisely because the overlays create a false sense of security while leaving the underlying code just as non-compliant as it was before the widget was installed.1 An overlay on a non-compliant site is like putting a sticker over your check engine light. The light's still on. The engine's still broken. You just can't see it anymore -- until it seizes on the highway.
The reason overlays fail is technical. An overlay widget sits on top of your existing website code and tries to patch accessibility issues at runtime. But it can't fix the underlying Document Object Model structure. It can't repair broken ARIA hierarchies that screen readers rely on to navigate your site. It can't add proper heading structures, fix missing form labels, add alt text to images that lack them, or ensure keyboard focus order makes logical sense. These are foundational issues in your HTML, CSS, and JavaScript -- not cosmetic problems an overlay can paper over. Automated accessibility testing tools detect roughly 30% of WCAG issues. An overlay widget catches even less, because it runs after the page loads and can only modify what's already broken.3 If you're planning a website redesign, this is the moment to build accessibility into the foundation -- not bolt it on afterward and hope nobody checks.
When I talk to small business owners in Shelby who've installed these widgets, they almost always tell me the same thing: "I thought I was covered." They spent $50 to $500 a month on a subscription and believed their legal exposure was resolved. The data from 2025 proves otherwise. An overlay widget on a non-compliant website is like putting a Band-Aid on a broken leg. It might make you feel better, but it doesn't fix the problem -- and it certainly won't hold up in federal court. The subscription fee you're paying every month? That money would go further paying a developer to actually fix the code.
Key point: 456 lawsuits targeted sites WITH overlay widgets installed. Overlays can't fix broken HTML structure, missing ARIA labels, or keyboard navigation problems. They create a false sense of security while leaving you just as exposed. Remove the widget. Fix the code.
Restaurants: 35% of all ADA website lawsuits in 2025
Yes - restaurants are the single most-targeted industry for ADA website lawsuits, accounting for 34.65% of all 3,948 federal cases filed in 2025. That is 1,368 lawsuits aimed at restaurants alone. If your restaurant has an online menu, a reservation form, or an ordering system on your website, you are operating in the most-litigated category. Fashion and apparel came second at 25.96%, followed by beauty and personal care at 8.03%.
The industry breakdown tells a clear story about who's being targeted. Restaurants are far and away the most-sued category at 34.65% of all cases -- 1,368 lawsuits in 2025. The fashion and apparel industry came second at 25.96%. Beauty and personal care was third at 8.03%. Home goods and furniture at 7.67%. Health and wellness at 7.17%. These five categories alone account for over 83% of all ADA website lawsuits.1 If you're running a restaurant in Shelby and your menu, reservation form, or ordering system lives on your website, you're in the crosshairs of the single most-litigated category. Does your online menu have alt text on the photos? Can a keyboard-only user place an order? If you don't know, now's the time to find out.
The reason for this concentration isn't random. Restaurants and retail businesses share several characteristics that make them attractive targets for plaintiffs' attorneys. They typically have small legal budgets. They operate websites with interactive elements like menus, ordering systems, reservation forms, and e-commerce functionality -- each of which introduces potential accessibility barriers. And they're numerous. There are hundreds of thousands of small restaurant and retail websites nationwide, which means the pool of potential defendants is enormous.2 It's a numbers game, and your restaurant website is a number in the pool.
If you run a restaurant in Shelby, Boiling Springs, Kings Mountain, Forest City, or anywhere in Cleveland County, and your website has an online menu, a reservation form, or an online ordering system, you're in the single most-targeted industry category. That's not fear-mongering. That's what the 2025 lawsuit filing data says. And if you've been thinking about whether your website needs a redesign, accessibility compliance is the reason to do it now rather than later -- before a demand letter arrives in the mail.
An additional data point that should concern any business owner: 1,427 of the 2025 lawsuits targeted companies that had been previously sued. Serial litigation is a documented feature of this legal environment. If a plaintiff's attorney finds your website non-compliant and sues you, the odds are high that they'll return in subsequent years to check whether you actually fixed the problems. Paying a settlement without remediating the underlying accessibility issues doesn't close the door. It opens it wider for round two. And round three.1
95.9% of top websites fail WCAG - here are the four biggest violations
Yes - 95.9% of the top one million homepages have at least one detectable WCAG 2.1 failure, with an average of 51.4 errors per page. These are not exotic, hard-to-fix issues. They are fundamental problems in HTML and CSS that any competent developer can fix. The four most common violations - low contrast text, missing alt text, unlabeled form fields, and empty links - account for the majority of all WCAG failures and are the same issues plaintiffs' attorneys scan for with automated tools.
The WebAIM Million report, which runs automated scans across the homepages of the top one million websites, found that 95.9% of those homepages had at least one detectable WCAG 2.1 failure. The average number of detectable errors per homepage was 51.4. These aren't exotic, hard-to-fix issues. These are fundamental problems in the HTML and CSS that any competent developer can address.3 51 errors per page. On average. How many do you think your site has?
The four most common violations break down like this. Low contrast text appears on 83.9% of homepages. This means the color of text against its background doesn't meet the minimum contrast ratio of 4.5:1 for normal text or 3:1 for large text. Gray text on a white background, light gray text on a slightly darker gray background, white text over a photo without a sufficient dark overlay -- these are design choices that look clean and modern but fail WCAG. And they're among the easiest violations for automated scanners to detect, which means they're among the easiest for plaintiffs' attorneys to find.3 Low-hanging fruit for a lawsuit. Don't let it be your fruit.
Missing alternative text appears on 53.1% of homepages. Every image on your website needs an alt attribute that describes the image for screen reader users. Decorative images need an empty alt attribute (alt="") so screen readers skip them. Images that contain text need alt text that conveys that text. Images that are links need alt text that describes the link destination. I audit small business websites in Cleveland County all the time, and missing alt text is almost always the most frequent issue I find. A five-minute scan. Hundreds of missing descriptions. Every one of them a potential line item in a lawsuit filing.3
Missing form input labels appear on 51% of homepages. Every form field -- contact forms, newsletter signup boxes, search bars, reservation forms, checkout fields -- must have a properly associated label element so screen readers can tell users what information to enter. A placeholder attribute inside an input field isn't a substitute for a label. This is one of the most litigated WCAG failures because it's trivially easy to detect programmatically and it blocks a core function: submitting forms. If a blind user can't complete your contact form, they can't become your customer. And a plaintiff's attorney can prove it in thirty seconds with free software.3
Empty links appear on 46.3% of homepages. A link element must contain text or an image with alt text that describes the link's purpose. Links that contain only an icon with no accessible name, links that are visually hidden with no text alternative, and links where the href points to nowhere meaningful -- these all fail. Screen reader users navigating by links get nothing useful from empty link elements. Imagine tabbing through a page and hearing "link" over and over with no description of where it goes. That's what 46.3% of the top million sites are serving to users who rely on assistive technology.3
These four violations alone account for the majority of WCAG failures on the web. If your small business website fixes these four things, you've addressed the most common, most detectable, and most frequently litigated accessibility barriers. This isn't a complete WCAG 2.1 AA compliance program -- accessibility goes deeper than these four items -- but it's the practical starting point for any small business that can't afford a full audit upfront.
Key point: The four most common WCAG violations -- low contrast text, missing alt text, unlabeled form fields, and empty links -- account for the majority of lawsuits. Fix them and you've addressed the low-hanging fruit that plaintiffs' attorneys scan for first.
The DOJ's April 2026 rule makes WCAG 2.1 AA the legal standard
On April 24, 2026, the DOJ formally codified WCAG 2.1 AA as the legal standard for digital accessibility under the ADA. While the rule directly applies to state and local governments, its impact on private businesses is immediate: plaintiffs' attorneys now have a federal regulation to cite in Title III lawsuits against private companies. The argument went from persuasive guidance to codified law, and that shift makes defending non-compliant websites significantly harder.
On April 24, 2026, the DOJ published a final rule under Title II of the ADA requiring all state and local government websites and mobile applications to conform to WCAG 2.1 AA. The compliance deadlines vary by entity size -- some have two years, some have three -- but the standard itself is now formally codified in federal regulation.4 This is the line in the sand. No more ambiguity about which standard applies.
This rule matters for private businesses even though it doesn't directly apply to them. Here's why: when a federal court adjudicates a Title III ADA website lawsuit against a private business, the judge needs a standard to measure accessibility against. Before the DOJ rule, there was no formal federal regulation defining that standard. Courts referenced WCAG 2.1 AA as persuasive guidance, but it wasn't codified. Now, the DOJ has formally stated that WCAG 2.1 AA is what digital accessibility means under federal law. That gives plaintiffs' attorneys a much stronger argument in Title III cases: "The federal government has already determined that WCAG 2.1 AA is the accessibility standard for digital services. This private business website fails that standard." The argument just got a lot harder to fight in court.
When I explain this to business owners in Shelby, I put it this way: the DOJ just drew a bright line in the sand. On one side of that line is WCAG 2.1 AA compliance. On the other side is legal exposure. If your website is on the wrong side of that line, you're betting that no one will notice. The 3,948 plaintiffs who filed suit in 2025 suggest that's not a safe bet. And if the FTC fake review rules taught us anything, it's that federal regulators are done with warnings. They're enforcing.
What Cleveland County small businesses should do right now
Start with a free automated accessibility scan using tools like WAVE or axe DevTools. They take five minutes and catch roughly 30% of WCAG issues including the four most common violations. If your site flags on low contrast text, missing alt text, unlabeled forms, or empty links, you have detectable and fixable problems that make you a lawsuit target. Remove any overlay widget and redirect that subscription cost into fixing your actual code. Then get a manual audit from a developer who understands WCAG 2.1 AA for keyboard navigation, focus order, and screen reader testing.
I want to be clear about something: I'm a web designer and developer, not an attorney. Nothing in this article is legal advice. What I can tell you is what the data says and what I do for my own clients in Shelby and across Cleveland County.
First: run an automated accessibility scan on your website right now. Free tools like WAVE (wave.webaim.org) and the axe DevTools browser extension will catch roughly 30% of WCAG issues -- including the four most common violations I described above. These scans take five minutes and they'll immediately show you whether you have low contrast text, missing alt text, unlabeled form fields, or empty links. If your site flags on any of these, you have detectable, fixable problems that make you a lawsuit target. Five minutes. That's how long it takes to find out if your site is a sitting duck.3
Second: don't rely on an overlay widget. The 456 lawsuits that hit sites with overlays installed in the first half of 2025 speak for themselves. Remove the overlay and invest the subscription cost into actually fixing your site's code. The overlay companies will tell you their product makes you compliant. The federal court docket says otherwise. Who are you going to believe -- the marketing copy or the judge?
Third: get a manual accessibility audit. Automated tools catch the easy stuff. They don't catch keyboard navigation problems, logical focus order issues, proper heading hierarchy, meaningful link text, or whether your forms can actually be completed by a screen reader user. A manual audit by a developer who understands WCAG 2.1 AA is the only way to know whether your site is genuinely compliant. For a small business website, a manual audit on core pages -- homepage, menu page, contact page, and any e-commerce or booking flow -- is generally sufficient as a starting point. You don't need to boil the ocean. You do need to check the water temperature.
Fourth: make accessibility part of your ongoing website maintenance. Accessibility isn't a one-time fix. Every time you add a new page, upload a new image, change a color, or install a new plugin, you can introduce new accessibility barriers. If you work with a web developer, accessibility testing should be part of every update. If you maintain your own site, run an automated scan every month and fix what it finds. Think of it like changing the oil in your truck. You don't do it once and forget about it. Same logic applies to your website.
The average ADA website lawsuit settlement ranges from $25,000 to $30,000. That doesn't include your attorney fees, the cost of the remediation work you'll need to do anyway, or the ongoing monitoring costs that are typically part of settlement agreements. For most small businesses in Cleveland County, a $25,000 unplanned expense is catastrophic. The cost of proactive remediation -- fixing the issues before you get sued -- is a fraction of that amount.1 $25,000 buys a lot of proactive development work. Or it buys one settlement check and a website that's still broken. Your choice.
I think about it this way. A Shelby restaurant owner will spend $15,000 on kitchen equipment without hesitation because broken equipment stops the business. A website with accessibility barriers is broken equipment. The difference is you can't see it until the lawsuit arrives. But by then, the repair bill includes legal fees, settlement costs, and still the same code fixes you could've done for a fraction of the price six months earlier. If you haven't checked your signs your website needs a redesign, start there. This article is part of our broader Technical SEO & Compliance Guide, which also covers Core Web Vitals, website migration best practices, and the full technical foundation your business website needs. Accessibility compliance might be the push you've been waiting for to build the site your business actually deserves.
Frequently asked questions
Do I need to make my entire website WCAG compliant or just the homepage?
Plaintiffs' attorneys typically scan the homepage first because it is the most accessible page and serves as the primary entry point. However, if a lawsuit is filed, the plaintiff will test all pages they interacted with, including contact forms, menus, and checkout flows. Fixing your highest-traffic pages first reduces risk while you work toward full compliance across the entire site.
Can I get sued for ADA violations if I am a very small business?
Yes - 77% of ADA website lawsuits in 2025 targeted businesses with under $25 million in annual revenue. There is no small business exemption under Title III of the ADA. The only exception is if compliance would pose an undue burden, but that defense is difficult and expensive to prove in court and offers no protection against being sued in the first place.
How much does it cost to make a small business website ADA compliant?
The cost varies widely based on the current state of your site. A basic audit of core pages runs $500 to $1,500. Remediation of common issues like contrast, alt text, and form labels typically costs $1,500 to $4,000 for a standard small business website. This is a fraction of the $25,000 to $30,000 average settlement cost of defending a lawsuit.
Do accessibility overlays really not protect me from lawsuits?
456 lawsuits in the first half of 2025 targeted websites that already had overlay widgets installed. Overlays cannot fix broken HTML structure, missing ARIA labels, or keyboard navigation problems because they run after the page loads and can only modify what is already broken. Remove the widget and invest the subscription cost into fixing the underlying code.
Does the DOJ rule from April 2026 apply to my private business?
The DOJ rule directly applies to state and local government entities under Title II of the ADA. However, it establishes WCAG 2.1 AA as the federal standard for digital accessibility, which plaintiffs' attorneys now cite in Title III cases against private businesses. The rule eliminates the ambiguity about which standard applies and strengthens arguments against non-compliant sites.
Check Your Site's Compliance
We build accessible, WCAG 2.1 AA-compliant websites for small businesses in Shelby and across Cleveland County. Every site we design includes proper heading structures, accessible forms, keyboard navigation, sufficient color contrast, and all the foundational code that overlay widgets cannot fix. If you are not sure whether your current site puts you at risk, let us take a look.
Sources: 1. UsableNet, "2025 Digital Accessibility Lawsuits Report (No longer available)." 2. Accessibility.com, "2025 Digital Accessibility Lawsuit Data." 3. Bureau of Internet Accessibility / WebAIM, "The WebAIM Million Report." 4. EEOC, "EEOC Sues Butterball for Disability Discrimination (North Carolina)."