You probably landed here for one of three reasons: a competitor got sued, someone mentioned a demand letter, or you ran a free scanner and got back a report that looked like a ransom note.
Whichever it was, take a breath. The first thing to know is that almost no website is fully compliant, and the second thing is that you can absolutely fix this without panicking, hiring a lawyer, or installing one of those overlay widgets that you've already started seeing ads for.
This guide will walk you through what ADA compliance and WCAG actually mean, whether you're at real risk, and the first practical steps to take this week. No jargon, no fear-mongering, no upsell.
First, the plain-English version
There are two phrases you'll hear constantly, and they're not the same thing:
ADA (Americans with Disabilities Act) is the federal law. It says people with disabilities have to be able to access goods, services, and information — including online. The ADA itself doesn't actually spell out the technical details of what an "accessible website" looks like.
WCAG (Web Content Accessibility Guidelines) is the technical standard that does spell out the details. It's published by the World Wide Web Consortium (W3C), the organization that effectively writes the rules of the web. Courts, the Department of Justice, and most settlement agreements all reference WCAG as the practical benchmark.
The current standard you'll be measured against is WCAG 2.1, Level AA. The Department of Justice formally adopted this as the technical standard for state and local governments under the 2024 Title II rule, and courts have used it as the de facto benchmark for private businesses for years.
If you remember nothing else from this post, remember this: the goal is WCAG 2.1, Level AA.
Are you actually at risk?
Short answer: probably, especially if you sell anything online.
The longer answer requires looking at the data. ADA website accessibility lawsuits have been climbing for nearly a decade, and 2025 set new records:
Roughly 3,948 to 5,100 federal lawsuits were filed against websites in 2025 alone, depending on which dataset you look at, with reports tracking a 23–37% increase over 2024. (EcomBack 2025 Annual Report, Seyfarth Shaw via ADA Title III blog)
Website lawsuits made up 36% of all ADA Title III federal filings in 2025. (Seyfarth Shaw)
E-commerce sites accounted for roughly 70% of digital accessibility lawsuits. (UsableNet 2026 Trends Report)
Settlements typically run from $5,000 to $75,000, plus attorney fees, remediation costs, and ongoing monitoring. (Clym)
And here's the one nobody likes to hear: 22.6% of lawsuits filed in early 2025 targeted websites that already had an accessibility widget installed. (DarrowEverett LLP)
That last stat is important. The widgets and overlays you see advertised as "one-line ADA compliance" do not stop you from being sued. In fact, they're a known target.
A few things that increase your risk specifically:
You operate in New York, Florida, California, or Illinois (these four states account for the overwhelming majority of filings)
You sell physical goods or services through your website
You're a restaurant, apparel brand, or food service business (these dominate the filings)
You've already received a demand letter (statistically, a prior claim makes future lawsuits much more likely)
Your business does over $25 million in annual revenue (larger targets get sued more)
If none of those apply, your risk is lower — but it's not zero, and waiting until you receive a demand letter to start working on accessibility is a much more expensive plan than getting ahead of it now.
How do I actually check if my site is compliant?
There are three layers of testing, and you need all three for a real answer. Skipping layers is how businesses end up thinking they're fine right up until the demand letter arrives.
Layer 1: Free automated scan (5 minutes)
Start with a free automated scanner. These catch the most obvious issues — missing alt text, color contrast, missing form labels, and so on. The good free options:
WAVE by WebAIM — paste your URL and get a visual report
axe DevTools — a browser extension from Deque, the gold standard in accessibility tooling
Google Lighthouse — built into Chrome DevTools (right-click your page → Inspect → Lighthouse tab)
Run all three if you have time. They overlap but each catches things the others miss.
Here's the catch: automated tools only find about 30–40% of WCAG issues. The rest require human judgment. So passing an automated scan means the easy stuff is fine. It does not mean you're compliant.
Layer 2: Manual keyboard testing (15 minutes)
This one you can do yourself with zero tools. Open your website and put your mouse away. Try to do everything using only the keyboard:
Press Tab to move forward through interactive elements
Press Shift + Tab to move backward
Press Enter or Space to activate buttons and links
Use arrow keys inside menus, dropdowns, and form controls
Now try to:
Navigate to your main menu and into a submenu
Fill out and submit your contact form
Add a product to cart and check out (if you sell anything)
Close any popup or modal that appears
If you get stuck anywhere — if focus disappears, if you can't see where you are on the page, if you literally can't reach a button — that's a real accessibility failure that an automated scan likely missed. Keyboard accessibility is covered under WCAG 2.1.1 Keyboard, and it's one of the most commonly cited issues in lawsuits.
Layer 3: Screen reader testing (advanced)
Screen readers are the assistive technology used by people who are blind or have low vision. Try navigating your homepage with one:
VoiceOver on Mac (press Cmd + F5 to turn on)
NVDA on Windows (free download from nvaccess.org)
This takes practice, and honestly, doing it well is where professional auditors earn their fee. But even a clumsy first attempt will surface obvious issues — like a homepage that announces "button button button image image" instead of telling you what's actually on the page.
The six issues that show up in nearly every lawsuit
When you look across thousands of accessibility lawsuits, the same handful of WCAG failures appear over and over. According to industry reports, six categories of issues account for the vast majority of cited violations:
Missing or incorrect alt text on images (WCAG 1.1.1)
Low color contrast between text and background (WCAG 1.4.3)
Form fields without labels (WCAG 4.1.2)
Empty or vague link text like "click here" or "read more" (WCAG 2.4.4)
Content that isn't keyboard accessible (WCAG 2.1.1)
Missing or broken page structure — no proper headings, missing landmarks, or skipped heading levels (WCAG 1.3.1)
Fix these six and you've addressed the lion's share of legal exposure on most websites. That doesn't mean you're done — true WCAG 2.1 AA conformance covers 50 success criteria — but it does mean you've handled the things plaintiffs' law firms are most likely to find first.
What about those accessibility widgets and overlays?
You will see ads for them. The pitch is irresistible: install one line of JavaScript and you're ADA compliant overnight.
It does not work that way.
These tools — accessiBe, UserWay, EqualWeb, AudioEye, and others — sit on top of your website and attempt to programmatically fix accessibility issues. They have improved over the years, but they share a fundamental problem: they cannot fix what they cannot understand. A widget cannot know what an unlabeled image is supposed to depict. It cannot decide whether a button's purpose is clear from context. It cannot rewrite the underlying code that makes your checkout flow impossible to complete with a keyboard.
The data backs this up. As noted above, 22.6% of website accessibility lawsuits in early 2025 were filed against sites that had widgets installed. (DarrowEverett LLP) These tools are not a legal defense. In some cases, they actively interfere with the real assistive technology that disabled users rely on.
If you've already installed one, don't panic — just don't treat it as the finish line. Real accessibility lives in your underlying HTML, CSS, and content.
Your first week: a practical starting plan
If you're starting from zero, here's what to do in the next seven days.
Day 1: Run free scans on your homepage and your three most important pages (probably home, contact, and either checkout or services). Use WAVE, axe DevTools, and Lighthouse. Save the reports.
Day 2: Do the keyboard-only walkthrough described above on those same pages. Write down everywhere you got stuck.
Day 3: Identify your top three most fixable issues from the scans. If you have a developer, send them the WAVE report and ask them to start with missing alt text, missing form labels, and color contrast — they're usually the cheapest wins.
Day 4: Read through the W3C's "Introduction to Web Accessibility". It's short and written for non-developers. You'll learn more in 30 minutes than from any sales-pitch blog post.
Day 5: If you're a government entity (state, local, school district), read the ADA.gov small entity compliance guide. The April 2026 and April 2027 deadlines apply to you.
Day 6: Draft a basic accessibility statement for your site. Even a few sentences acknowledging that you're working on accessibility, with a contact email for issues, shows good faith. The W3C provides a generator if you want a template.
Day 7: Decide whether you can keep going internally or whether you need outside help. If your business is in one of the high-risk categories, or if the issues you found feel beyond what your team can fix, it's worth getting a professional audit before you get a demand letter — those costs scale fast.
When to bring in a professional
You can absolutely do meaningful accessibility work yourself, especially if you have a developer on staff. But there are a few situations where a professional audit is worth the money:
You sell anything online and operate in NY, FL, CA, or IL
You've received a demand letter or been contacted by a plaintiff's firm
Your site uses heavy JavaScript or custom interactive components (these are where automated tools fail hardest)
You handle anything regulated — healthcare, financial services, government services
You want a Letter of Conformance or VPAT for procurement or RFP purposes
A real accessibility audit combines automated scanning, manual expert review, keyboard testing, and screen reader testing by people who actually use assistive technology. Industry sources note that automated tools alone miss 60–70% of issues, which is why a serious audit is never just a scan with a logo on it.
The mindset shift that helps
Most business owners come into accessibility work thinking of it as a legal compliance chore. That framing makes the whole project feel miserable. The shift that helps — and the one I'd push you toward — is treating accessibility as part of building a website that actually works.
Captions help everyone in a noisy office. Keyboard navigation helps power users. Clear headings help SEO. Readable color contrast helps anyone on a phone in sunlight. The 26% of American adults living with a disability (CDC, 2024) are not a separate market — they're your existing customers, and currently your site might be making it harder for them to spend money with you.
Compliance is the floor. Real accessibility is just better web design.
Sources: EcomBack 2025 Annual Report · Seyfarth Shaw ADA Title III Blog · UsableNet 2026 Trends Report · DarrowEverett LLP · ADA.gov Small Entity Compliance Guide · W3C / WCAG 2.1 · Accessible.org WCAG 2.1 AA Guide