Does Your Website Need to Be ADA Compliant?

The short answer

If your organization runs a public-facing website, plan on the Americans with Disabilities Act (ADA) applying to it. State and local government websites now have a specific, DOJ-mandated technical standard and firm compliance dates — covered below. Private businesses and nonprofits open to the public don't have a single regulation spelling out a technical standard the way governments now do, but the Department of Justice has taken the position since 1996 that the ADA's general nondiscrimination requirements extend to web content, and federal courts have applied that reasoning to business websites for years (ADA.gov web accessibility guidance).

This question comes up the same way for a one-person nonprofit and for a national retailer — "does this apply to us" — even though what happens next looks very different for each once you get into enforcement (below). Which title of the ADA reaches you, what technical standard you're actually being measured against, and what a realistic timeline looks like are three separate questions this guide answers in order, because conflating them is where most of the confusion starts.

The genuine exceptions are narrower than most organizations hope: religious organizations and private clubs not open to the general public, and a case-by-case "undue burden" defense that succeeds only for specific, disproportionately expensive fixes — not as a blanket pass. If your site serves the public, the safe starting assumption is that it's covered. The rest of this guide walks through exactly which rules apply to you, what "compliant" means in practice, and what to do about it.

Who is covered: Title II vs. Title III

The ADA reaches websites through two different titles, and which one applies to you changes both the technical standard you're measured against and the timeline you're working with.

Title II: state and local governments

Title II prohibits disability discrimination in "all services, programs, and activities" a state or local government provides — including whatever it delivers on the web, from permit applications to public-meeting agendas to a transit authority's trip planner (ADA.gov web accessibility guidance).

In April 2024, the Department of Justice published a final rule that gave Title II, for the first time, a specific technical standard for the web: WCAG 2.1 Level AA. The rule set two compliance dates based on the population an entity serves (ADA.gov: New Rule on Web and Mobile App Accessibility):

• Entities serving a population of 50,000 or more: originally April 24, 2026
• Entities serving a population under 50,000, and special district governments regardless of size: originally April 26, 2027

Those dates have since changed. On April 20, 2026, DOJ published an Interim Final Rule extending both deadlines by one year, after concluding it had "overestimated the capabilities (whether staffing or technology) of covered entities" to meet the original schedule (91 Fed. Reg. 20902; Federal Register Document 2026-07663). The current, in-force dates — confirmed directly against the regulation text itself — are:

• April 26, 2027 — public entities serving a total population of 50,000 or more
• April 26, 2028 — public entities serving a population under 50,000, and special district governments regardless of population

(28 CFR Part 35, Subpart H, current text)

The rule reaches mobile apps as well as websites: if a Title II entity ships a resident-facing app alongside its website, the same WCAG 2.1 AA standard and the same population-based dates apply to it too (ADA.gov: New Rule on Web and Mobile App Accessibility).

DOJ accepted public comment on the interim rule through June 22, 2026 and has stated it "fully anticipates implementing the regulation at the new deadline[s]" absent further rulemaking. One distinction matters more than the date itself: the extension moves the WCAG conformance deadline, not Title II's underlying nondiscrimination obligation. That obligation is in force today, and a covered entity can still face a complaint during the extension period (Federal Register 2026-07663).

Title III: private businesses and nonprofits

Title III prohibits disability discrimination by "public accommodations" — DOJ's term for businesses open to the public, a category that reaches retailers, restaurants, banks, medical offices, hotels, and most service businesses (ADA.gov web accessibility guidance). Unlike Title II, there is no DOJ regulation spelling out a specific technical standard for these businesses' websites: "the Department does not have a regulation setting out detailed standards, but the Department's longstanding interpretation of the general nondiscrimination and effective communication provisions applies to web accessibility" (ADA.gov web accessibility guidance). In practice, that ambiguity has been filled in by case law and settlement practice rather than a published rule, and the standard both sides typically argue around is the same one Title II now requires by regulation: WCAG 2.1 Level AA.

If your business is open to the public and provides goods or services, you should assume Title III applies. In practice that reaches a wide range of everyday categories — retail stores, restaurants and bars, hotels, banks and insurance offices, medical and dental practices, gyms and recreation facilities, theaters, and private schools and daycare centers among them (ADA.gov web accessibility guidance). The one area of genuine, ongoing legal uncertainty is the online-only business with no physical location — courts don't agree with each other on whether a website alone can be a "place of public accommodation," and how strictly that gets enforced still varies from one federal circuit to the next. Some circuits have read "public accommodation" to include a website on its own; others have looked for some connection between the website and a physical location before treating it as covered. A business with even one storefront, office, or other physical location removes most of that ambiguity — the connection to a physical place of public accommodation is what several circuits have said they're looking for in the first place. A purely online business doesn't get a pass; it just falls into the part of the map where the answer depends more on where you'd be sued than most organizations would like. Nonprofits aren't automatically exempt either: a nonprofit that operates something open to the public (a clinic, a school, a shelter) is generally treated the same way a for-profit business would be.

The exemptions that do exist are genuinely narrow. Religious organizations and private clubs not open to the general public fall outside Title III entirely — but a religious organization that runs a secular, public-facing service (a day care, a school) can still be covered for that service. "Undue burden" is a real defense, but it's decided case by case against an organization's actual resources, not claimed in advance as a category-wide exemption. See our full answer on whether small businesses need to comply with the ADA.

A quick self-check

Put the two titles together and you're very likely covered if any of the following describes you:

• You're a state agency, city, county, school district, public university, transit authority, or any other unit of local or state government.
• You run a business — physical, online-only, or both — that's open to the public and sells goods or services.
• You're a nonprofit operating a public-facing program: education, healthcare, social services, or recreation.
• You're a federal agency or federal contractor, in which case Section 508 applies alongside (or instead of) the ADA — see "What 'ADA compliant' actually means," next.

What "ADA compliant" actually means

No federal agency issues an "ADA compliance certificate" for a private website, and no automated scan can truthfully claim to confer one. What both DOJ's Title II rule and the overwhelming majority of Title III settlement practice point to is the same technical standard: the Web Content Accessibility Guidelines (WCAG), version 2.1, Level AA — a set of testable success criteria, published by the World Wide Web Consortium (W3C), covering how content is perceived, operated, understood, and built to work with assistive technology such as screen readers, voice control, and switch access. WCAG organizes its criteria under four principles: content must be Perceivable ("information and user interface components must be presentable to users in ways they can perceive"), Operable ("user interface components and navigation must be operable"), Understandable ("information and the operation of the user interface must be understandable"), and Robust enough to keep working reliably as browsers and assistive technology change (W3C: WCAG 2.1). In practical terms that covers things like text alternatives for images, full keyboard operability, predictable navigation, sufficient color contrast, and underlying code that names its own form fields and page language correctly. WCAG itself defines three conformance levels of increasing strictness; Level AA — the middle level — is what both DOJ's Title II rule and Title III settlement practice reference, not the strictest of the three. WCAG 2.1 has been a stable W3C Recommendation since June 2018. The newer WCAG 2.2 adds a handful of additional criteria but doesn't replace or supersede 2.1 — content that meets 2.2 also meets 2.1 (W3C: WCAG standards and guidelines).

"Conforms to WCAG 2.1 AA" describes a specific website at a specific point in time, checked against a fixed list of criteria — it isn't a status a site earns once and keeps. A new page, a template change, or a third-party widget can reintroduce a failure the very next day, which is why treating accessibility as a one-time project rather than an ongoing practice is the most common way sites drift back out of conformance. The scale of the underlying problem is well documented: the WebAIM Million project's 2026 report on the top one million home pages found that 95.9% had at least one detectable WCAG 2 failure — up from 94.8% the year before, reversing several years of small improvement (WebAIM: The WebAIM Million, 2026).

Two adjacent standards get confused with ADA compliance and are worth telling apart. Section 508 of the Rehabilitation Act applies to federal agencies and, through flow-down contract clauses, many federal contractors; it uses its own WCAG-based technical standard and is a separate law from the ADA, though a vendor selling into government can easily carry obligations under both. A VPAT (Voluntary Product Accessibility Template) is a standardized disclosure document — not a law, and not a certification — that vendors use to describe how a specific product conforms to WCAG and Section 508 criteria for enterprise and government buyers who ask for one. See our full breakdown of Section 508 vs. the ADA.

How to check your own site

Two different checks answer two different questions, and treating them as the same thing is where most organizations go wrong.

An automated scan — the kind our free ADA audit runs — reads your page's underlying code and flags a portion of WCAG issues in minutes: missing image descriptions, unlabeled form fields, insufficient color contrast, empty links or buttons, and other patterns a script can detect from markup alone. That's genuinely useful as a starting point, and it's free, but it is a starting point. Automated tools cannot tell you whether your site is actually usable with a keyboard alone, whether a screen reader announces your content in a sensible order, whether a multi-step checkout genuinely works for someone who can't see it, or whether your page still makes sense when zoomed in or reflowed to a narrow viewport — that category of failure requires a person to test it, not a script to scan it.

A complete picture requires a manual review layered on top of the automated one: someone unplugging their mouse and navigating your key paths with a keyboard alone, running your primary flows through a screen reader, checking that focus order and visible focus indicators actually make sense, and confirming the result against the WCAG 2.1 AA criteria automated tools can't reach by themselves. If you'd rather have that done for you than build the expertise in-house, the ADA agency directory we publish — also a Grow Wild Agency property — profiles agencies and consultants by the standards they state they work to, so you can compare options before you hire one.

Either way: start with the free automated scan, fix what it finds, and treat that as the floor for your work, not the finish line.

What happens if you don't comply

For Title II entities, the extended deadlines above don't pause the underlying obligation. Title II's nondiscrimination requirement is in force today, and a covered entity can still face a complaint over an inaccessible site during the extension period, regardless of which WCAG conformance date applies to it (Federal Register 2026-07663).

For Title III businesses, the realistic exposure runs through two channels. Advocacy organizations and plaintiffs' firms use automated scanning at scale to identify likely targets, and many cases begin with a demand letter — a notice alleging specific accessibility barriers and proposing a settlement — well before anything is filed in court. Most of these resolve without ever becoming a public court filing; the ones that do tend to share a few traits, including e-commerce or other transactional functionality and a prior complaint that went unanswered. Whether a demand letter or an actual lawsuit is more or less likely for a given business varies meaningfully by industry, state, and prior history, and the honest picture changes year to year. Rather than restate a single figure here that will be out of date within a year, we track the filing data separately at /statistics/ada-website-lawsuits (in progress). What the term itself means, and how a claim typically proceeds once one is filed, is covered in our ADA lawsuit glossary entry.

None of this is really about avoiding a letter, though. The same barriers a scanner or a plaintiff's expert finds are the ones your own customers with disabilities are running into every time they try to use your site — the legal exposure and the practical exclusion are two views of the same underlying problem, not two separate ones.

State-level rules on top of federal law

The ADA is a federal floor, not a ceiling: nothing about complying with federal law relieves an organization of separately complying with state law, and the ADA doesn't preempt states from going further. A number of states — Colorado, California, New York, and Texas among them — layer their own accessibility or anti-discrimination statutes on top of it, sometimes with different enforcement mechanisms, different damages rules, or coverage that reaches further than federal Title III does on its own. Which of these actually apply to you depends on where your organization is based, where your customers or constituents are, and in some cases where a claim gets filed — three different questions that don't always point to the same state. Our guide to Colorado's website accessibility law covers that state in full; dedicated guides to the others named here are in progress. Until they publish, treat the federal analysis in this guide as the floor, and confirm your specific state's requirements with counsel if you operate in one of them.

What to do this quarter

If you're not sure where your organization stands today, this is a reasonable amount of work to get through in the next few months, regardless of size or sector:

1. Run the free scan. Start with our free ADA audit to get a baseline read on the code-detectable issues across your most important pages.
2. Prioritize by traffic and function, not by page count. Your homepage, primary navigation, account and contact forms, and anything transactional — checkout, booking, applications — matter more than a static page almost nobody reaches.
3. Fix what a keyboard-only pass and a screen-reader pass actually catch, not only what the automated scanner flags. This is where manual testing earns its keep.
4. Write down what you did and when. A dated record of audits and fixes is what demonstrates good-faith progress if you're ever asked about it later.
5. Publish an accessibility statement describing what you've done, what you know still needs work, and how someone can report a barrier they've hit.
6. If Title II applies to you, put April 26, 2027 or April 26, 2028 on a calendar now — not because the date is close, but because remediation work at any real scale, including the remediation itself, reliably takes longer than teams expect.
7. If you'd rather hand this off, Grow Wild Agency's ADA web design services — also a Grow Wild Agency property — can scope and carry out the remediation work directly.
8. Loop in whoever ships new pages or features, not just whoever built the site originally. A content author publishing an image without a text alternative, or a developer shipping a new component without keyboard support, can undo the rest of this list within a week — accessibility holds only as long as it's part of how new work gets shipped, not a one-time project.

No program like this can promise a specific outcome in a specific court; nobody honestly can. But it's the difference between a documented, good-faith program and starting from zero the day a complaint arrives.