How to Make Your Website ADA Compliant (Without Panic or Overlays)

Introduction: The Overlay Won't Save You

Somewhere along the way, the accessibility overlay widget became the small-business answer to ADA compliance. Install it in five minutes, check the box, move on. Except it doesn't work that way.

Some ADA complaints specifically cite the overlay as evidence that the site owner was already aware of accessibility problems and chose a cheap workaround instead of an actual fix. That's the part nobody in the overlay marketing materials mentions.

A quick note before we go further: Sproutbox is a Portland-based full-service digital marketing agency specializing in website design and development. We are not a law firm, and nothing in this post is legal advice. If you've received a demand letter, talk to an attorney before you do anything else, including installing an overlay.

What this post does cover: how to make your website ADA compliant in a way that actually holds up. We'll walk through what the law actually requires, who's getting sued and why, why overlays are a false solution, and what real remediation looks like. No scaremongering. Just the practical picture.

And honestly, most of the fixes are cheaper than you think.

What ADA Website Compliance Actually Means

The ADA does not contain specific website regulations for private businesses. What courts and settlements reference is WCAG 2.1 Level AA, a set of technical guidelines published by the W3C. Meeting WCAG 2.1 AA is the closest thing to a legal safe harbor available today, even though no formal DOJ rule requires it for Title III businesses.

ADA website compliance is genuinely complicated territory for private businesses, not because the accessibility standards themselves are ambiguous, but because the legal framework around them is still being sorted out in courts.

Title III and the Private-Business Gray Zone

Title III of the ADA covers "places of public accommodation", physical locations like stores, restaurants, and hotels. Courts are split on whether websites count. The DOJ has never issued a formal regulation requiring private-business websites to meet any specific accessibility standard under Title III.

Plaintiffs sue anyway. And most businesses settle, because the cost of defending an ADA lawsuit typically exceeds the cost of settling one. That's not a flaw in the system, it's a predictable outcome that plaintiff attorneys understand well. The ADA website accessibility litigation analysis from DarrowEverett LLP lays out the landscape clearly: the legal question is unresolved, but the litigation risk is very real.

The practical upshot is that "no formal rule exists" is not a defense that makes the lawsuit go away cheaply.

Why WCAG 2.1 Level AA Is the Standard Everyone Uses

The WCAG 2.1 Level AA standard is published by the W3C, and it's what courts, DOJ consent decrees, and plaintiff attorneys all reference when evaluating whether a website is accessible. It's organized around four principles: perceivable (users can see or hear the content), operable (users can navigate with whatever input device they're using), understandable (content and controls make sense), and robust (the site works with assistive technologies like screen readers).

Level AA is the middle tier, more stringent than Level A, less demanding than the edge-case requirements in Level AAA. It's the level cited in virtually every ADA settlement and consent decree involving website accessibility.

Government Deadlines and the Healthcare Exception

For context: the DOJ's 2024 Title II rule requires state and local governments to meet WCAG 2.1 AA. Those deadlines were extended, per the DOJ Title II deadline extension published by Jackson Lewis, to April 26, 2027 for entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special districts.

Healthcare organizations receiving HHS funding face a separate rule with a May 11, 2026 compliance date that was not extended alongside the Title II deadlines. If that applies to your organization, the stakes are higher and the timeline is tighter, our healthcare digital marketing page is a good starting point.

For private businesses, the government context matters because plaintiffs use government standards as the benchmark in litigation. WCAG 2.1 AA is the target that makes practical sense for everyone, even without a formal rule requiring it.

The Lawsuit Landscape: What the Numbers Actually Tell You

More than 3,100 ADA website accessibility lawsuits were filed in U.S. federal court in 2025, a 27% jump over 2024. Most targeted e-commerce retailers, and the majority of sued companies were small and mid-sized businesses with revenues under $25 million. A typical demand-letter settlement runs $5,000 to $15,000 before legal or remediation costs.

These numbers aren't meant to alarm you. They're meant to give you an accurate picture of who's actually in the crosshairs, because the answer is not "big companies with big legal teams."

Who Gets Targeted (And Why Small Businesses)

Plaintiffs filed 3,117 website accessibility lawsuits in U.S. federal court in 2025, a 27% increase over 2024's 2,452. Nearly 70% targeted e-commerce retailers, many of them small businesses with annual revenues under $25 million.

Geographically, New York led with roughly 31.6% of all filings, Florida accounted for about 24.2%, and California came in at 18.9%. Illinois stood out with a 746% year-over-year increase in filings, a number that surprised us when we first saw it.

Small businesses get targeted for the same reason any opportunistic litigation concentrates on a group: the math works. Settlement costs are relatively low, defense costs are high, and most small businesses don't have an accessibility lawyer on retainer. That doesn't mean you're being singled out. It means the risk is broad-based, not limited to enterprises.

The Failures That Trigger Complaints

Most ADA website complaints don't cite exotic technical failures. They cite the same handful of things, over and over:

• Missing alt text on images, screen readers have nothing to describe
• Insufficient color contrast between text and background
• Unlabeled buttons and form fields, a submit button with no accessible label is invisible to assistive technology
• Keyboard navigation that breaks or traps focus, users who can't use a mouse get stuck
• Inaccessible checkout flows, the most litigated failure type for e-commerce

These are fixable. None of them require a ground-up rebuild. That's the whole point.

What a Demand Letter Actually Costs

A typical ADA website demand letter resolves for $5,000 to $15,000 in quick-settlement territory, before attorney fees and before any remediation costs. Add those, and the total cost climbs fast.

The counterintuitive part: for most small-business sites, fixing the high-frequency failures costs significantly less than that settlement figure. An ada website lawsuit is expensive not because the remediation is hard, but because by the time you get the letter, you're also paying for legal counsel, negotiation, and lost time. Fixing the code before the letter arrives is almost always the cheaper path, by a wide margin.

Why Accessibility Overlay Widgets Don't Work, And Can Backfire

Accessibility overlay widgets, the scripts that inject a toolbar onto your site claiming to make it compliant, do not make a website ADA compliant. Automated overlays catch a fraction of accessibility failures, leave the underlying code broken, and do not satisfy WCAG 2.1 AA. Some complaints specifically cite an overlay as evidence the site owner was already aware of accessibility problems.

This is the one place in this post where we'll take a hard position: overlays are not a solution. They're a liability dressed up as a product.

What Overlays Actually Do (And Don't Do)

An overlay works by injecting a JavaScript layer on top of your existing site. It can adjust some visual presentation for users who activate the toolbar, font size, contrast toggling, that kind of thing. What it cannot do is fix the underlying HTML, ARIA structure, keyboard focus order, or form labeling that screen readers and assistive technologies actually interact with.

Screen reader testing reveals this quickly. A screen reader navigates the DOM, the document structure of your page, not the overlay's visual adjustments. If your form fields don't have programmatically associated labels, the overlay doesn't change that. If your keyboard focus traps on a modal, the overlay doesn't fix that either. Automated overlays catch perhaps a third of accessibility issues at best, and that's a generous estimate.

The $10/month price point exists because the product doesn't do what it claims to do. Real remediation costs more because real remediation fixes the code.

The Overlay Trap

We call this The Overlay Trap: some ADA complaints have named the overlay itself as evidence that the site owner already knew about accessibility barriers and chose a cheap workaround instead of an actual fix. From a legal standpoint, knowing about a problem and failing to fix it is worse than not knowing it existed.

Installing an overlay in response to a complaint, or pre-emptively, hoping it creates a safe harbor, may actually be cited against you. The only real remediation is fixing the underlying code.

We're a marketing agency, not lawyers. If you're evaluating your legal exposure, an attorney is the right call. But we can tell you exactly what code-level remediation looks like, and we build it into every site we touch through our custom website design and development work.

The Sproutbox Accessibility Fix List: How to Make Your Website Actually Compliant

This is the practical part. The Sproutbox Accessibility Fix List is the five-step approach we use when auditing and building sites, it's how to make your website ADA compliant in a way that addresses the actual failures, not the surface presentation.

Step 1, Audit Before You Fix Anything

Before you touch a line of code, run an audit. Automated tools are a starting point, not a finish line, they catch roughly a third of accessibility failures. Here are the three we use:

1. Google Lighthouse, Built into Chrome DevTools. Run an accessibility audit on any page and get a scored report with specific failure callouts.
2. WAVE (Web Accessibility Evaluation Tool), Browser extension from WebAIM. Great for visual overlay of errors directly on your page.
3. axe accessibility checker, Browser extension from Deque. Developer-friendly, low false positives, integrates into CI pipelines if you want to automate testing going forward.

After the automated scan, do manual testing. Tab through every interactive element on the page, links, buttons, form fields, modals, and confirm that focus is visible and nothing traps. Then run a screen reader. NVDA on Windows is free; VoiceOver is built into Mac. Listen to how your site reads. You'll find failures the automated tools missed.

The Lighthouse accessibility audit is where most people stop. The screen reader testing is where the real issues show up.

Step 2, Fix High-Frequency Failures First

Start with the failures that show up in complaints most often. Work through these in order:

1. Alt text on every meaningful image. Blank alt attribute (alt="") for decorative images; descriptive alt text for content images. Don't stuff keywords, describe what's actually there.
2. Color contrast. Body text needs a minimum 4.5:1 contrast ratio against its background. Large text (18px bold or 24px regular) requires at least 3:1. Use a contrast checker, this fails more often than people expect.
3. Form field labels. Every input needs a visible, programmatically associated label, not just placeholder text. Placeholder text disappears when the user starts typing. A `<label>` element tied to the input stays.
4. Focus states. Every interactive element must show a visible focus ring when tabbed to. Don't remove the CSS `outline` property without replacing it with something equally visible.
5. Keyboard navigation. Confirm every piece of functionality on the site is reachable and operable without a mouse. If you can't get to it by tabbing, a keyboard-only user can't use it.
6. Video captions. Any video with meaningful audio content needs closed captions. Auto-generated captions from YouTube are a reasonable starting point, but they need review.

Step 3, Build Accessibility Into Your Design System

Patching a live site is fine. Building a system where accessibility failures can't slip through is better.

When we work on new builds or redesigns, we establish color tokens with minimum contrast ratios baked in. Every new color choice made by a designer or client either passes or gets flagged automatically, it's not a manual check every time. We add reduced-motion support in CSS so users with vestibular disorders aren't hit with animations they can't control. Semantic HTML and correct heading hierarchy go in from the first component, with ARIA labels added where the HTML semantics alone aren't enough.

We build on Astro for performance-first marketing sites and WordPress for content-heavy projects, and on both platforms, accessibility is addressed in the code itself, not bolted on afterward with a widget. Accessibility checks are part of our standard website audits because a site that passes WCAG 2.1 AA at launch should still pass six months later.

This is the difference between a one-time fix and a site that stays accessible as it grows.

Step 4, Add an Accessibility Statement Page

An accessibility statement is a page that describes your commitment to accessibility, lists any known barriers you're actively working to fix, and gives users a way to contact you if they hit a problem. It's not a legal shield on its own, but it is good-faith evidence, and it gives users with disabilities a path forward instead of a dead end. Two to three sentences about your approach and a contact email is enough to start.

Step 5, Retest After Every Redesign

Accessibility decays. New content, new page templates, new third-party embeds, each one can introduce failures that weren't there before. Treating accessibility as a one-time project instead of an ongoing practice is how sites that passed an audit two years ago end up in a complaint today.

For sites that need a ground-up rebuild with accessibility baked into the foundation, that's exactly where we start. Our Portland web design and development process builds accessibility in from the wireframe stage, not as a checklist item at the end.

What to Do If You've Already Received a Demand Letter

If you receive an ADA website demand letter: don't ignore it, don't pay the settlement without legal review, and don't panic-install an overlay. The first call you make should be to an attorney who handles ADA litigation, not to a website vendor. Then start remediation in parallel. Most demand letters are resolvable, but the timing matters.

We get this question a lot, and the honest answer is: the letter itself is less important than what you do in the next 72 hours.

The Three Things to Do Immediately

This is general practical guidance, not legal advice. An attorney who handles ADA accessibility cases will give you actual legal guidance for your specific situation.

1. Read the letter carefully and note any response deadlines. Demand letters often have short windows, missing a deadline can limit your options.
2. Call an attorney who handles ADA accessibility cases before you respond or pay anything. Defense options exist, the facts of the complaint matter, and an attorney can assess both. Don't negotiate without counsel.
3. Begin documenting your accessibility remediation plan. Courts and opposing counsel look more favorably on defendants who can show they took the complaint seriously and acted in good faith. Start the audit. Start the fixes. Write it down.

The One Thing You Should Not Do

Don't install an overlay in response to the letter. It doesn't remediate the failures named in the complaint, and it may be read as an attempt to obscure the problem rather than fix it. The overlay won't make the complaint go away. Code-level remediation is the right response.

The demand letter is answering the question of whether your website is ADA compliant. Now the question is what to do about it, and the answer is fix the underlying code, in parallel with legal counsel, as fast as you reasonably can.

We're marketers, not lawyers. The guidance above is general context, not legal advice. If you've received a demand letter, an attorney is your first call. Full stop.

Frequently Asked Questions

Does the ADA actually require my business website to be accessible?

Technically, no formal DOJ regulation requires private-business websites to meet any specific standard under Title III of the ADA. But courts have found websites to be places of public accommodation, and thousands of lawsuits are filed each year under that theory. Most businesses settle because defense costs exceed settlement costs, which makes the legal risk real even without a formal rule.

The legal landscape for private-business websites is genuinely unsettled, courts in different circuits have reached different conclusions. The practical takeaway: the absence of a formal rule doesn't make the litigation risk go away, and a proactive approach to accessibility is far cheaper than a reactive one.

What is WCAG 2.1 AA and do I have to meet it?

WCAG 2.1 Level AA is the Web Content Accessibility Guidelines published by the W3C, the technical standard courts, the DOJ, and plaintiff attorneys reference when evaluating website accessibility. Private businesses are not legally required to meet it under any current federal rule, but it is the de facto compliance target and the closest thing to a safe harbor available.

The four principles behind WCAG: Perceivable means users can see or hear your content. Operable means they can navigate it with a keyboard, switch device, or other input. Understandable means the content and controls behave predictably. Robust means the site works reliably with assistive technologies like screen readers. Level AA is the middle tier, practical to achieve, and the standard referenced in virtually every ADA web accessibility settlement.

Do accessibility overlay widgets protect me from ADA lawsuits?

No. Accessibility overlay widgets do not make a website ADA compliant, do not satisfy WCAG 2.1 AA, and have not prevented lawsuits against the businesses using them. Some complaints cite the overlay itself as evidence of awareness. The only real protection is fixing the underlying code.

The overlay section above covers the mechanism in detail, including why the presence of an overlay can sometimes work against you rather than for you.

How much does it cost to make a website ADA compliant?

Cost depends on the site's current state and complexity. For most small-business sites, addressing the high-frequency failures, alt text, contrast, form labels, keyboard navigation, focus states, runs far less than the $5,000 to $15,000 typical quick-settlement figure on a demand letter. A site built with accessibility in the code from the start costs no more than a standard site build.

A free Lighthouse accessibility audit or WAVE scan gives you a starting point in about ten minutes. Sproutbox includes accessibility checks as part of standard website audits, it's not a separate line item. If you want a professional eye on where your site stands, our website design and development services include that review as part of the process.

I got an ADA website demand letter. What should I do?

Call an attorney who handles ADA accessibility cases before you respond, pay anything, or make changes based on pressure from the letter. Then begin code-level remediation in parallel, not an overlay install. Courts look favorably on defendants who can show a good-faith remediation effort. Do not ignore the letter; most have response deadlines.

Sproutbox is a marketing agency, not a law firm. This is general context, not legal advice. The attorney call comes first. We can help with the remediation piece once you have legal guidance on how to proceed.

Accessibility Is Cheap Relative to the Alternative

The litigation risk is real. The fix is practical. And the overlay is not the answer, we've said it several times because the overlay industry spends a lot of money saying the opposite, and it's worth being clear.

The common advice is to treat website accessibility as a compliance burden, something you address under pressure. In practice, the businesses that treat it as a baseline standard of how sites should be built are the ones who never have to scramble. Baking WCAG 2.1 AA into a new site costs nothing extra. Retrofitting it after a demand letter costs a lot.

A quick note: we're a marketing agency. Nothing here is legal advice, and if you've received a demand letter, an attorney is your first stop.

If you're not sure where your site stands, we can help with that part. Accessibility is built into how we audit and build sites, not an add-on, not a checkbox at the end of the project. Schedule a call and we'll take a look. For a full picture of how we approach Portland website design and development, that's the place to start.