ADA Website Compliance: What Every Organization Needs to Know

Someone in your organization just asked, "Is our website ADA compliant?" Maybe it was your executive director. Maybe a board member. Maybe you saw it in a headline and realized you didn't actually know the answer.

You're not alone. Most organizations are still figuring out what ADA website compliance actually means, who it applies to, and what (if anything) they need to do about it. The landscape keeps shifting. The federal compliance deadline for state and local governments was recently extended into 2027 and 2028, digital accessibility lawsuits have topped 4,000 a year and keep climbing, and the technical standard everyone points to, WCAG 2.1 Level AA, sounds like it was written for engineers, not operations managers.

This guide is for you. We're going to walk through what ADA website compliance actually means, who it applies to, what the technical standard requires (in plain language), what the real risks are, and where to start. No jargon. No scare tactics. No sales pitch. This is Part 1 of a four-part series on website accessibility. This post covers the full landscape, and the rest of the series gets into practical how-to.

What ADA Website Compliance Actually Means

The Americans with Disabilities Act became law in 1990. It was originally focused on physical spaces: ramps, doorways, parking spots, signage. But the world moved online, and so did the law's reach.

The Department of Justice has taken a clear position: websites are "places of public accommodation." They confirmed this in 2018, reaffirmed it in 2022, and courts have increasingly agreed. In February 2025, a Minnesota federal judge explicitly ruled that websites qualify as places of public accommodation under ADA Title III.

So what does ADA website compliance mean in practice? It means your website works for everyone, including people who navigate with a keyboard instead of a mouse, people who use screen readers to hear content read aloud, people who need captions on video content, and people who need sufficient color contrast to read your text.

This isn't a niche concern. 28.7% of US adults (more than 1 in 4) have some type of disability. These are your donors, your clients, your community members, your volunteers.

The technical standard the DOJ points to is called WCAG 2.1 Level AA. We'll break that down in plain language in a moment.

Who Needs to Comply: Title II, Title III, and Your Organization

The ADA isn't one-size-fits-all. There are different legal frameworks depending on what type of organization you are. Here's how to figure out where you fall.

Title II: Government Entities (The 2027 and 2028 Deadlines)

Title II applies to state and local governments and their agencies, departments, and programs. On April 24, 2024, the DOJ finalized a new rule establishing WCAG 2.1 Level AA as the required technical standard for government web content and mobile apps. In April 2026 the DOJ extended the original compliance dates by one year.

The current compliance deadlines:

• April 26, 2027: State and local governments serving populations of 50,000 or more
• April 26, 2028: Governments serving populations under 50,000, plus all special purpose districts

The scope is broad: primary websites, web-based applications, mobile apps, online forms, PDF documents, and third-party content hosted on government platforms. If your organization is a government-affiliated nonprofit, a quasi-governmental agency, or a nonprofit operating government programs, this applies directly to you.

Title III: Private Businesses and Nonprofits

Title III applies to private entities that are "places of public accommodation," meaning organizations that are open to the public. There's no formal web-specific rule yet, but the DOJ has repeatedly said websites are covered, and courts agree.

Most 501(c)(3) nonprofits fall here. If your nonprofit is open to the public and serves the community, your website is likely covered under Title III.

And here's the part that surprises a lot of people: there is no blanket exemption for small businesses or small nonprofits based on size, number of employees, or annual revenue. If you serve the public, the ADA applies. The only categorical exemption under Title III is for religious organizations: churches, synagogues, mosques, and programs they directly operate.

Section 508: If You Receive Federal Funding

This is the piece most content on this topic misses entirely, and for nonprofits, it might be the most important one.

Section 508 of the Rehabilitation Act applies to any organization receiving federal financial assistance: grants, loans, or contracts. Many nonprofits receive federal funding and don't realize this triggers additional, separate accessibility requirements beyond the ADA itself.

Section 508 requires WCAG 2.0 Level AA conformance (following the 2018 update). The penalties include fines up to $55,000 for a first violation and $110,000 for subsequent violations, plus potential loss of federal funding. For a grant-funded nonprofit, losing federal funding isn't just a penalty. It's an existential risk.

The Bottom Line

If your organization serves the public, your website should be accessible. If you receive federal funding, you have additional obligations under Section 508. The Title II deadline applies directly to government entities, but the precedent and awareness it creates affect everyone.

What WCAG 2.1 AA Actually Requires (In Plain Language)

WCAG stands for Web Content Accessibility Guidelines. It's the international standard published by the W3C, the same organization that sets standards for the web itself. There are three conformance levels: A (the minimum), AA (the standard target, which is what the DOJ requires), and AAA (the highest, typically not required in full).

WCAG 2.1 Level AA has 50 success criteria. That sounds like a lot. But they're organized under four principles that are genuinely intuitive once you hear them in plain language. The framework is called POUR.

Perceivable: Can People Perceive Your Content?

Every image needs descriptive alt text so screen readers can describe it to someone who can't see it. Videos need accurate, synchronized captions. Text needs at least a 4.5:1 contrast ratio against its background, and 81% of home pages fail this one. Content can't rely on color alone to convey meaning (so "click the red button" doesn't work). And everything should remain readable when text is resized up to 200%.

Here's a real-world test: if someone who is blind visits your homepage, can their screen reader describe the images? If those images don't have alt text, the answer is no. (We explore this specific issue in detail in Part 4 of this series, which looks at a workflow that trips up more organizations than almost anything else.)

Operable: Can People Use Your Interface?

Every function on your site must work using only a keyboard, with no mouse required. Users need enough time to read and use content, which means no auto-advancing slideshows without controls. Nothing should flash more than three times per second (seizure risk). Navigation should be logical and predictable. Link text needs to make sense on its own. "Download our annual report" works, "click here" doesn't. And focus indicators must be visible so users can see which element is selected as they tab through.

Here's something you can try right now: navigate your own website using only the Tab key. Can you reach every link, every button, every form field? Can you tell where you are on the page? If not, you've just experienced what a keyboard-only user experiences every time they visit your site.

Understandable: Can People Understand Your Content?

Your page language needs to be identified in the code so screen readers pronounce words correctly. Forms need clear labels and instructions. Error messages should be specific and helpful, like "Please enter a valid email address" instead of just "Error." And navigation should be consistent across all pages.

Robust: Does It Work with Assistive Technology?

Your HTML needs to be well-structured, with proper heading hierarchy (H1, then H2, then H3, no skipping levels), correct use of semantic elements, and properly implemented ARIA landmarks. Content should work across different browsers and assistive technologies. Status messages need to be available to assistive technology without requiring focus.

We'll cover the most common WCAG issues, and how to fix them, in Part 2 of this series. Most are easier than you'd expect.

A Quick Note on WCAG 2.2

WCAG 2.2 was released in October 2023, adding 9 new success criteria for a total of 87. It's fully backward-compatible with 2.1, so meeting 2.2 automatically means you meet 2.1. The federal rule references WCAG 2.1 AA specifically, but building to 2.2 is forward-thinking. We won't deep-dive into the differences here, but you should know it exists so you're not confused if you see it referenced elsewhere.

The Title II Deadline: What You Need to Know

On April 24, 2024, the DOJ finalized a new rule under Title II establishing WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile apps. In April 2026, the DOJ issued an interim final rule that pushed the compliance dates back by one year, citing limited staffing, the slower-than-expected progress of automated remediation tools, and ongoing litigation. The standard did not change. The timeline did, and the requirements are concrete and enforceable.

The current deadlines:

• April 26, 2027: for state and local governments serving populations of 50,000 or more
• April 26, 2028: for governments serving populations under 50,000 and all special purpose districts

The scope covers primary websites, web-based applications, mobile apps, online forms, PDF documents, and third-party content hosted on government platforms.

Here's the thing. This is a Title II rule. It applies to government entities. If your organization is a private business or nonprofit, this ADA website compliance deadline does not directly apply to you.

But here's why it matters anyway.

The Title II rule signals the DOJ's clear direction: web accessibility is not optional, and WCAG 2.1 AA is the standard. It creates legal precedent. And the awareness it generates drives more private plaintiff lawsuits under Title III. When government is required to comply, private organizations become easier targets for attorneys who can argue, "If the standard is good enough for government, it's good enough for your organization." The ripple effect is already visible in the 2025 lawsuit numbers.

The Real Risk: Lawsuits, Fines, and What's Actually Happening

Let's look at the numbers.

• 4,187 digital accessibility lawsuits filed in 2024
• 37% increase in filings in the first half of 2025
• ~70% of ADA web lawsuits target e-commerce

In 2024, over 4,187 digital accessibility lawsuits were filed across federal and state courts. In the first half of 2025 alone, 2,014 lawsuits were filed, a 37% increase over the same period in 2024. Pro se (self-represented) filings increased 40% in 2025 compared to the previous year, partly because AI-powered tools are making it easier to identify violations and file complaints.

Geographically, New York and California accounted for about 40% of all cases, but filings are expanding into Pennsylvania, Minnesota, and Missouri, states that previously saw limited activity. And 41% of federal filings were against companies that had already been sued before. Repeat defendants.

E-commerce accounts for nearly 70% of all ADA web lawsuits, but food and service businesses make up roughly 21% of targets. Nonprofits are not exempt. If you're wondering whether nonprofits are targets: they can be. Title III applies to places of public accommodation, and most nonprofits serving the public qualify.

What the Fines Actually Look Like

The maximum DOJ civil penalties for Title III violations are up to $75,000 for a first violation and up to $150,000 for subsequent violations. Adjusted for inflation in 2024, those numbers are up to $115,231 and $230,464.

In practice, most cases aren't DOJ enforcement actions. They're private plaintiffs seeking injunctive relief (meaning the court requires the website to be fixed) plus attorney's fees. Settlements typically range from $5,000 to $50,000 or more per case.

Some states add their own penalties. California's Unruh Civil Rights Act allows $4,000 or more per violation per visit, which compounds rapidly. And for organizations receiving federal funding, Section 508 penalties can reach $55,000 for a first violation and $110,000 for subsequent violations, plus potential revocation of federal grants.

This can feel overwhelming. But understanding the risk is the first step toward managing it, and the numbers make a clear case for being proactive rather than reactive.

Why Accessibility Overlay Widgets Are Not the Answer

If you've been researching ADA website compliance, you've probably come across overlay widgets, tools that promise to make your site accessible by adding a JavaScript toolbar. Install one line of code, pay $50 a month, and your accessibility problems are solved.

The appeal is understandable. A subscription that handles compliance sounds a lot better than a $9,000 remediation project. But the evidence is clear: overlays don't deliver what they promise.

The 30/70 Problem

Automated tools, including overlays, can only detect approximately 30-40% of WCAG accessibility issues. The remaining 60-70% require human judgment. An automated script can verify that an image has an alt attribute, but it can't determine whether that alt text actually describes the image. It can check contrast ratios, but it can't evaluate whether your navigation is logically organized. It can find missing form labels, but it can't assess whether the label makes sense.

The accessibility overlay limitations are fundamental, not fixable with a software update.

Overlays Attract Lawsuits

In 2024, 25% of all digital accessibility lawsuits (1,023 cases) targeted websites using overlay widgets. In January 2025 alone, 85 defendants were sued while using a third-party overlay. Companies aren't being sued despite the overlay. In many cases, the overlay is what draws attention.

Enforcement Is Catching Up

In April 2025, the FTC fined AccessiBe $1 million for false advertising and fake customer reviews. The FTC found their compliance claims were "not supported by competent and reliable evidence."

UserWay is facing a class action lawsuit from Bloomsybox, which was sued for ADA violations six months after installing the UserWay widget. When Bloomsybox sought the promised legal support, UserWay sent a generic "Legal Action Guide" and closed the ticket. Bloomsybox incurred $4,000 in attorney fees and settled with a monetary payment.

The Technical Problem

There's also a fundamental technical reason overlays fail: they run JavaScript after the page loads, but screen readers parse the HTML before JavaScript executes. The overlay "fixes" literally never reach the users who need them most.

The Overlay Fact Sheet, signed by hundreds of accessibility professionals, documents these failures in detail.

What Accessibility Actually Costs (Honest Numbers)

Let's talk real numbers, because budgeting for something you can't see clearly is almost impossible.

• Professional accessibility audit (manual, expert-conducted): $2,500 - $10,000
• Technical remediation: $5,000 - $20,000+, depending on site complexity
• Per-page remediation: $250 - $550 per page
• Ongoing maintenance: $200 - $1,000/month

A practical example: a 10-page website might cost approximately $3,500 for the audit and $5,500 for remediation, around $9,000 total. For a small nonprofit, that's a significant budget line. That's real, and there's no point pretending otherwise.

Here's the thing. Building with accessibility in mind from the start costs a fraction of retrofitting an existing site. Basic accessible development practices during the build process, such as proper heading structure, alt text workflows, form labels, and contrast checking, prevent the most expensive remediation scenarios. It's the difference between regular oil changes and an engine rebuild.

If your budget doesn't allow for a full remediation project right now, that's okay. Accessibility is a spectrum, not a switch. You don't have to do everything at once. Prioritize the highest-impact changes, make incremental progress, and build accessibility into your process for new content going forward.

Progress over perfection.

Beyond Compliance: Why Accessibility Matters for Your Mission

Everything above is about legal obligations, financial risks, and technical standards. All of that matters. But for a lot of organizations, especially nonprofits, it's not the reason that sticks.

If your organization's mission is to serve your community, an inaccessible website excludes over a quarter of that community from your services, your information, your donation page, your volunteer sign-up form. This isn't hypothetical. It's the person trying to apply for your program who can't navigate your forms with a screen reader. It's the potential donor who can't read your impact report because the contrast is too low. It's the community member who can't access the resources you built specifically for them.

Accessibility improvements also benefit everyone: better SEO performance, better mobile usability, clearer content, faster load times. An accessible website is simply a better website. (The accessibility-SEO connection is significant enough that we dedicated Part 3 of this series to it.)

Where to Start: Practical Next Steps

If you've read this far, you know more about ADA website compliance than most people at your organization. The question now is: what do you do with that knowledge?

The answer isn't "fix everything immediately." The answer is: progress over perfection. Start somewhere. Keep going.

1. Understand where you stand. Run a basic self-assessment with a free tool like WAVE to get a starting picture of your site's accessibility. Just remember the 30/70 limitation: automated tools catch some issues, but not all. For a complete picture, a professional manual audit is the gold standard.

2. Prioritize the highest-impact fixes. Focus on:

   • Alt text on images (the most common issue and one of the easiest to fix)
   • Heading structure (proper H1, H2, H3 hierarchy)
   • Color contrast (4.5:1 ratio for text)
   • Keyboard navigation (can you Tab through your entire site?)

3. Start with alt text. It's the single most common accessibility issue, and it's something you can start fixing today, no developer required.

   If your site runs on WordPress, we built a free plugin for exactly this. Alt Tag Manager surfaces every image on your site that's missing alt text and lets you update each one right there, with no digging through the media library and no extra clicks. It's free, and it takes about five minutes to see where you stand.

4. Build accessibility into your process going forward. Don't just fix the backlog, prevent new issues. Every new page, every new blog post, every new image: check the alt text, check the heading structure, check the contrast.

5. Know when to bring in help. A manual expert audit is the gold standard for understanding your full compliance picture. When your budget allows, it's a worthwhile investment.

   This is where we come in. Accessibility is built into both of the ways we work. On the WordPress sites we build and manage, it is structural from the first day, and on the sites we custom develop from the ground up, it is part of the foundation. Because a custom build has no third-party theme or plugin layer to work around, bringing it to full compliance is usually less work, and less cost, than retrofitting a typical WordPress site. We can also audit and remediate a site you already have, whichever way it was built.

6. Keep going. Next in this series: the most common accessibility mistakes, and the fixes are easier than you think. We'll walk through a practical WCAG compliance checklist you can work through at your own pace.