#That Lawsuit You Never Saw Coming
It sounds dramatic, but it’s the truth. Every single day, businesses from Houston to Fort Worth get hit with demand letters they never saw coming, all because their website isn’t accessible to people with disabilities.
I'm Cody Ewing, and at Bruce & Eddy, my dad Butch and I have been in the web game since 2004—back when "accessibility" pretty much just meant your dial-up modem was working. Things have changed. The internet isn’t the Wild West anymore, and pretending it is can get expensive fast.
My goal here isn't to scare you with legal jargon. It's to have a real conversation about what website ADA compliance requirements actually mean for your business. We'll talk about why those quick-fix widgets are mostly snake oil and how a little proactive work can save you a mountain of headaches.
Think of me as the friendly guide who points out the banana peel on the sidewalk before you slip on it. Amy, our client happiness guru, would approve of that analogy.
The Not-So-Fun Legal Reality
The Americans with Disabilities Act (ADA) was signed into law before most of us had an email address, but courts have consistently ruled that it applies to websites. Why? Because a commercial website is considered a "place of public accommodation," just like a physical storefront in downtown Austin or a restaurant in Fredericksburg.
If people with disabilities can't use your site, you're effectively putting a "Closed" sign on your digital front door for a huge chunk of the population.
This isn't some theoretical problem. In recent years, ADA website lawsuits have skyrocketed. We're talking thousands of federal filings annually, with thousands more piling up in state courts. E-commerce businesses get hit the hardest, facing a huge portion of all suits. It's become a cottage industry for some law firms to use automated scanners, spot easy-to-find violations, and fire off demand letters.
Settlements often land somewhere between $5,000 to $50,000, and that doesn't even include your own attorney's fees or the cost to actually fix the website.
What This Means For Your Business
Ignoring accessibility isn't just a legal gamble; it's just plain bad business. You’re shutting out a huge portion of the population who might want to buy your products or use your services. You can get a better sense of the broader legal landscape from this guide on Business Litigation.
Properly addressing these issues isn't a one-and-done fix. It requires a thoughtful approach that weaves accessibility into your regular operations, much like our strategy for ongoing website maintenance and support services. The real goal is to build a better, more inclusive website for everyone, not just to check a legal box and hope for the best.
Understanding WCAG Without a Law Degree
Let's cut through the alphabet soup. When people talk about website ADA compliance requirements, they’re almost always talking about the Web Content Accessibility Guidelines, or WCAG for short. It sounds a lot more intimidating than it actually is.
Think of WCAG as the official building code for your website. You wouldn’t build a new storefront in downtown Houston without a proper ramp and accessible restrooms, right? The exact same idea applies to your digital front door.
These guidelines exist to make sure people with disabilities—whether visual, auditory, motor, or cognitive—can actually use your website. This isn’t about just checking off boxes on a list; it’s about making sure a massive part of the population isn't left out in the cold.
The Four Commandments of WCAG (The POUR Principles)
To keep things from getting overly technical, the entire WCAG framework is built on four core principles. Everything ladders up to one of these ideas. My dad, Butch, loves breaking it down this way because it cuts straight through the noise.
These principles—Perceivable, Operable, Understandable, and Robust—are best remembered by the acronym POUR. Here's what they mean in plain English.
| Principle | What It Means in Plain English | A Real-World Example |
|---|---|---|
| Perceivable | Can people take in your content with their senses? This means it can be seen, heard, or otherwise perceived. | Providing "alt text" for images so a screen reader can describe the photo to a visually impaired user. |
| Operable | Can people actually navigate and use your site? The interface components and navigation have to be usable. | Making sure your entire website works with just a keyboard, which is essential for someone who can't use a mouse. |
| Understandable | Is your content clear, predictable, and easy to follow? People shouldn't have to guess what to do next. | Using simple language on your forms and providing clear error messages if someone misses a required field. |
| Robust | Can your site be reliably interpreted by different browsers and assistive technologies, both now and in the future? | Writing clean, standard HTML code so that screen readers and future technologies can understand the site's structure. |
At the end of the day, POUR just means people need to be able to see it (or have it described to them), use it, understand it, and access it with their preferred technology. That's really it.
The A, AA, and AAA Conformance Levels
Okay, one last bit of jargon. WCAG has three levels of compliance, kind of like difficulty settings in a video game. Each level builds on the one before it, adding more requirements to the list.
-
Level A: This is the bare minimum. Think of it as the foundational, non-negotiable stuff. If you’re not meeting Level A, your site has some pretty serious barriers.
-
Level AA: This is the sweet spot and the legally accepted standard in most cases. For the vast majority of businesses, meeting Level AA is the goal. It's what courts typically look for in lawsuits because it addresses the most common and significant accessibility hurdles.
-
Level AAA: This is the gold standard, the highest possible level of accessibility. It’s often very difficult and not always practical to meet for all types of content. We usually see government sites or specialized disability organizations shooting for this, but for most businesses, it’s an enhancement, not a requirement.
When we talk about making a site compliant at Bruce & Eddy, we’re always aiming for WCAG 2.1 or 2.2 Level AA conformance. It provides the perfect balance of strong accessibility and practical implementation for businesses from Katy to San Antonio. It ensures your website is truly open for business—to everyone.
The Most Common Ways Websites Fail Compliance
Here’s the part that always gets me: most websites fail their accessibility checks for the same handful of reasons. It’s not usually some deep, complicated coding flaw buried in the server room. It's the small stuff, the seemingly minor oversights that pile up into a massive barrier for users.
My dad, Butch, who is originally from Midlothian, has been looking under the hood of websites since 2004, and he sees the same patterns whether the business is in Sugar Land or Marfa.
It’s almost always the simple things. An overwhelming majority of websites have detectable accessibility errors on their homepage alone. These aren't obscure issues; they're foundational problems that make sites unusable for millions.
Fixing these doesn't just help you dodge a demand letter. It makes your site fundamentally better for every single person who visits.
The Five Horsemen of Accessibility Fails
We see these five issues pop up so often that we could probably make a bingo card out of them. If you’re worried about your own site, this is the perfect place to start your self-check.
-
Missing or Useless Alt Text: This is accessibility 101. Alternative text (alt text) is the description a screen reader reads aloud for an image. When it’s missing, a visually impaired user just gets silence. When it's bad—like
IMG_8675.jpg—it's just noise. -
Vague Link Text: Links that just say "Click Here" or "Learn More" are completely useless out of context. Someone using a screen reader often scans a list of all links on a page. A list of ten "Click Here" links tells them absolutely nothing about where they're going.
-
Terrible Color Contrast: This one drives our designers, especially Landon, crazy. When your text color is too similar to your background color, people with low vision or color blindness can't read it. It’s like trying to read gray text on a slightly-less-gray background. There are free tools to check this, so there’s really no excuse.
-
No Keyboard Navigation: Unplug your mouse and try to navigate your website using only the Tab key. Can you get to the menu? Can you fill out your contact form? If the answer is no, you’ve just locked out anyone who can't use a mouse due to a motor disability.
-
Inaccessible Forms: Forms are where business gets done, but they're often a minefield of accessibility issues. Missing labels, confusing error messages, and buttons that can't be reached with a keyboard mean lost leads and frustrated customers.
A website that isn't keyboard-friendly is the digital equivalent of a beautiful storefront with stairs but no ramp. It looks nice, but a whole group of potential customers can't even get in the door.
Why the Small Details Matter So Much
Think about it this way: each of these little failures is a paper cut. One isn't a big deal, but a dozen of them make for a miserable experience. When a user with a disability encounters one barrier after another, they’re not going to stick around and try to solve your website’s puzzles. They’re just going to leave.
These issues are often baked into a site from the very beginning, which is why a thoughtful approach is so crucial. It’s about more than just avoiding legal trouble; it’s about respect for your audience and building something that works for everyone. These principles are a core part of our thinking, and you can see how they apply more broadly in our guide to the best design practices for websites.
Ultimately, a more accessible website is a more usable website. Period. When you add clear labels, logical navigation, and readable text, you improve the experience for every single visitor, whether they have a disability or not. It’s one of those rare instances in business where doing the right thing is also the smartest thing.
Why One-Click Accessibility Widgets Don't Work
You’ve probably seen them before. Little icons hiding in the corner of a website, promising instant ADA compliance with a single line of code. These are called accessibility overlays or widgets, and to put it bluntly, they're a trap.
They dangle the promise of a cheap, quick fix for a pretty complex problem. Their marketing is slick, and the price point is definitely tempting compared to a full audit and remediation. The reality, though, is they often make your website even worse for the very people they claim to help.
The Band-Aid on a Broken Bone
Let's use an analogy. If your house has a cracked foundation, you don’t just slap a fresh coat of paint on the wall and call it a day. You hire a contractor to fix the foundation, the root of the problem. An accessibility widget is the digital version of that coat of paint. It just covers up the issue without actually solving anything.
Anjo, our lead developer and a total coding perfectionist, can tell you exactly why these widgets are doomed to fail. They work by injecting a new layer of code on top of your existing website. This approach has a few massive, unavoidable flaws:
-
They Interfere with Real Assistive Tech: People with disabilities already use sophisticated assistive technologies like screen readers (JAWS, NVDA, VoiceOver). These tools are highly customized to their specific needs. Overlays often hijack the user's experience, forcing a clunky, unfamiliar interface on them that directly conflicts with the tools they rely on every day.
-
They Don’t Fix the Source Code: A widget simply can’t rewrite your website’s underlying HTML. If your contact form is missing proper labels or your navigation can’t be used with a keyboard, the widget can only try to guess what’s wrong and apply a patch. More often than not, it guesses wrong, creating an experience that's even more confusing than the original broken one.
-
They Miss Most of the Problems: The automated scanners these widgets are built on can only detect about 30% of WCAG issues. The other 70% require human logic and hands-on testing to identify—things like whether your alt text actually makes sense or if a customer can complete the checkout process without using a mouse.
The core issue is that overlays try to bolt on a separate, "accessible" version of your site instead of making the actual site accessible. True accessibility is about building one inclusive experience for everyone, not creating a clunky side entrance.
The Legal System is Catching On
Worst of all, these widgets can actually increase your legal risk. Lawyers who specialize in ADA lawsuits know all about overlays. They specifically hunt for sites using them because the presence of a widget is often a giant red flag that the business hasn't done the real work.
Courts are increasingly seeing them for what they are—a completely inadequate solution. In fact, a huge number of recent ADA website lawsuits have been filed against companies that were using an overlay as their only compliance strategy. The plaintiffs argue, correctly, that the widget didn't actually make the site usable for them.
At Bruce & Eddy, our philosophy is simple: fix the foundation. Whether we're building a custom website from scratch for a business in Austin or helping a client in Dallas fix their existing one, our focus is always on building accessibility into the very core of the website. It’s the only way to create a truly compliant, user-friendly experience that stands up to scrutiny and, more importantly, actually serves all your customers.
Your Practical Path to a Compliant Website
Okay, we’ve talked enough about the problems. Let's get to the solutions. Getting your site compliant isn't some magical, one-and-done task; it’s a process. It requires taking a clear-eyed look at where you are and creating a roadmap for where you need to go.
The very first step is figuring out your baseline. You can't fix what you don't know is broken. This means you need a proper website accessibility audit that digs deep into the real user experience.
Starting with a Real Audit (Not Just a Scan)
A meaningful audit is a two-part harmony. First, we use automated tools to quickly scan your entire site. These are great for catching the low-hanging fruit—the obvious, widespread issues like missing alt text or empty links that might exist across hundreds of pages. They’re fast and efficient, which is a great start.
But here’s the thing: an automated scan will only catch about 30-40% of the actual problems. The other 60-70% are nuanced issues that need a human brain and real-world testing to uncover. That’s where a manual audit comes in.
This is when one of our experts sits down and actually tries to use your website just like someone with a disability would.
- Can they navigate the entire site using only a keyboard?
- Does the checkout process make sense when listened to on a screen reader?
- Are error messages on your contact form clear and helpful, or just confusing?
A robot can't answer those questions. A person can. We have to combine the efficiency of automation with the critical thinking of a manual review to get a true picture of your website’s accessibility.
Creating Your Remediation Roadmap
Once the audit is done, you'll have a list of issues. The next step is building a remediation plan. This is your roadmap for fixing everything in a logical order. You wouldn’t start by repainting the guest room when the roof is leaking, right? Same principle applies here.
We help our clients prioritize fixes based on how severe they are. The most critical issues are anything that completely blocks a user from completing a core task, like buying a product or filling out a contact form. Those get fixed first. From there, we work our way down the list, tackling everything from technical code fixes to adjustments in your content.
This whole process is a perfect illustration of why those quick-fix overlays just don't work. They're like slapping a band-aid on a structural problem instead of actually fixing the foundation.
As the diagram shows, you can go from a cracked foundation to a temporary patch, but the only real solution is a solid, structural fix. That's the only approach that holds up.
Content vs. Technical Fixes
Remediation work usually falls into two buckets:
-
Content-Level Fixes: These are often things your own team can manage once they’re trained. This includes writing descriptive headlines, adding captions to videos, making sure link text is meaningful (no more "click here"!), and writing genuinely useful alt text for images.
-
Technical Fixes: These are the deeper, code-level issues that might require a developer like Anjo to get involved. This could mean adjusting the site’s HTML structure for better screen reader navigation or fixing "keyboard traps" in a dropdown menu that prevent users from getting out.
The U.S. Department of Justice has signaled that WCAG 2.1 Level AA is the standard for government websites. While these rules don't directly apply to private businesses yet, the legal world is following their lead. Being proactive and adopting these standards now is the smartest defense.
As you develop your game plan, referencing an ultimate website accessibility checklist can help make sure you're covering all your bases. For a deeper dive, you can also check out our own comprehensive website accessibility checklist that we've tailored specifically for businesses.
The goal is to start smart, fix what’s broken, and have a solid plan to keep it that way. This is an ongoing commitment, not a one-time project.
Frequently Asked Questions About Website ADA Compliance
Let's run through some of the most common questions we get about website ADA compliance requirements. My dad, Butch, has been answering these for business owners from Richmond to Arlington for the better part of two decades, so you're getting his straightforward, no-fluff take.
Is My Small Business Website Really Required to Be ADA Compliant?
Yes. Full stop. The ADA was signed into law way before most of us had even heard of the internet, but courts have consistently ruled that commercial websites are "places of public accommodation." This means the law applies to your site just like it does to a physical storefront.
It doesn't matter if you're a small boutique in Wimberley or a national brand. If the public can access your website, the ADA applies. The threat of a lawsuit is very real, and honestly, making sure everyone can use your site is just good business.
What Is the Difference Between an Automated and Manual Audit?
This is a great question because it gets right to the heart of how to do this properly.
-
An automated audit uses software to scan your website for common WCAG failures, like missing alt text on an image or a broken link. It’s fast and fantastic for catching about 30-40% of the low-hanging fruit.
-
A manual audit is when a real person—often using assistive technologies like a screen reader—actually navigates your site to find the problems a robot would miss.
Think of it this way: an automated scan can tell you if a ramp exists. A manual audit tells you if the ramp is too steep to climb or has a giant pothole in the middle of it. You absolutely need both to get the full picture of your website's accessibility.
How Much Does It Cost to Make a Website ADA Compliant?
I know this is the answer everyone hates, but it truly depends. The cost is tied directly to the size and complexity of your site and, frankly, how many problems the audit turns up.
A simple brochure-style website might only need a few thousand dollars in remediation work. A massive e-commerce site with thousands of products and complex user accounts could cost tens of thousands to fix. This is exactly why building accessibility in from the start—like we do on all our BEGO or custom projects—is always cheaper than trying to bolt it on later. The first step is always the audit, so you understand the scope before you start writing checks.
The most expensive way to handle accessibility is to wait until you get a demand letter. Proactive investment is always a fraction of the cost of a reactive legal scramble.
Can I Get Sued Even if I Am Working on Fixing My Site?
Unfortunately, yes. Simply "working on it" isn't a legal defense that will get a lawsuit thrown out of court.
However, having a documented audit from a reputable third party and a clear remediation plan with a realistic timeline is an incredibly powerful tool. It shows you're acting in good faith to solve the problem. We often help clients create this documentation as a first step. It won’t grant you immunity, but it can significantly help in negotiations if a demand letter does arrive. Proactive, documented steps are always your best move.
If your website feels like it's held together with duct tape and hope, maybe it’s time to talk. At Bruce and Eddy, we build websites that work for everyone. Let's schedule a call and figure out your next steps.