Skip to content
wcagc
←Back to blog
ADATitle IIIWCAG

ADA website compliance in 2026: the factual guide

Does the ADA apply to your website in 2026? A plain guide to which WCAG standard, Title II vs III, deadlines, and how to actually comply.

P

Pavel Charkasau

If your website is part of how the public buys from you or reaches your services, the ADA applies to it. That has been the Justice Department's position for years, and it holds in 2026 (ADA.gov). The part that trips people up: for private businesses there is still no federal regulation naming a version of WCAG or a deadline. DOJ says so plainly, and adds that "existing technical standards provide helpful guidance," pointing to WCAG and the Section 508 standards (ADA.gov). Courts read it the same way, so in practice WCAG 2.2 Level AA is the target to build toward. State and local governments are different: they have a dated rule under ADA Title II requiring WCAG 2.1 AA, with deadlines now in 2027 and 2028 (ADA.gov). This guide separates what is law from what is benchmark, and gives you a working order of operations. Short version: scan your key pages, fix what blocks real users, and get a human to check the rest.

Does the ADA apply to my website?

For most businesses open to the public, yes. Title III of the ADA covers "public accommodations," and DOJ has "consistently taken the position that the ADA's requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web" (ADA.gov). Retailers, restaurants, banks, healthcare providers, hotels, and the online storefronts attached to them fall inside that definition. Size does not exempt you; a five-person shop selling online is a public accommodation the same as a national chain.

Two honest caveats. First, courts have split on whether a purely online business with no physical location counts as a public accommodation, so the edge cases are genuinely unsettled. Second, "applies to" is not the same as "here is the exact standard you must meet," which is the next question and the one that causes the most confusion.

Is there an official ADA standard for websites?

Not for private businesses. This is the fact most compliance pages get wrong. DOJ states it directly: "The Department of Justice 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). The same guidance says businesses "have flexibility in how they comply."

So where does WCAG come from? It is the yardstick courts and DOJ actually use. In consent decrees and settlements, WCAG 2.1 Level AA is the standard defendants get held to, and DOJ's own guidance names WCAG as helpful reference. WCAG 2.2 AA is the version I would build toward now. It adds nine success criteria on top of 2.1, including a 24-by-24 CSS pixel minimum for touch targets (2.5.8), accessible authentication that does not force a memory test (3.3.8), and an alternative to drag-only interactions (2.5.7) (W3C). Meeting the newer version means you also meet the older one, so aiming at 2.2 AA covers the 2.1 AA that litigation cites. If the A/AA/AAA distinction is fuzzy, WCAG levels explained lays it out.

Title II vs Title III: which one applies to me?

They are two different regimes, and mixing them up is where a lot of the "new 2026 deadline" panic comes from.

  • Title II — state and local governments. Since 2024 there is an actual regulation. It requires WCAG 2.1 Level AA for public entities' web content and mobile apps (ADA.gov). This is the one with hard dates.
  • Title III — private businesses open to the public. No dated regulation, no codified WCAG version. You are held to the general duty of nondiscrimination and effective communication, with WCAG as the practical benchmark (ADA.gov).

If you run a company, Title III is your world, and the 2027 government deadlines below do not set your clock. They still matter to you as a signal: WCAG 2.1 AA is now the federally-endorsed floor for public bodies, which makes it harder for any private defendant to argue that WCAG is an unreasonable expectation.

What are the ADA Title II deadlines in 2026?

For governments, the dates moved. DOJ's 2024 Title II rule originally set compliance for April 2026 and April 2027. In an interim final rule published April 20, 2026, DOJ extended both by one year, citing resource and staffing constraints and the limits of generative AI for remediation (Federal Register). The substantive standard, WCAG 2.1 AA, did not change. The current dates:

Public entityCompliance deadline
Population of 50,000 or moreApril 26, 2027
Population under 50,000April 26, 2028
Special district governmentsApril 26, 2028

Those are the only ADA web deadlines with a date attached, and they bind governments, not shops. If you sell to public agencies, expect them to ask for a conformance report as their own deadline nears; I cover that discipline under Section 508, the parallel federal-procurement standard.

How do I make my website ADA compliant in 2026?

There is no certificate to earn and no checkbox that ends the work. What you can do is meet WCAG 2.2 AA on the paths people actually use, and keep evidence that you are maintaining it. A sane order of operations:

  1. Scan to get the map. Run your templates and highest-traffic pages against WCAG 2.2 AA so you know the shape of the problem. Automated testing is fast at the machine-detectable barriers that most demand letters cite first, like unlabeled form fields and missing image text. Start with a free accessibility scan.
  2. Fix the journeys, not the count. A checkout or a login form a keyboard user cannot complete matters more than a hundred decorative-image warnings. Triage by whether the issue blocks a task, not by how many rows it adds to a report.
  3. Get a human on the rest. Automated tools catch somewhere between 30 and 57% of issues depending on the study; Deque's own analysis put full automated coverage at 57% (Deque). Whether an error message makes sense read aloud by a screen reader is not something a scanner can judge. This is the split I go into in manual vs automated testing.
  4. Write an accessibility statement and date it. A statement documents effort and gives users a way to report problems. It is not a claim of perfection, and it should never pretend to be one. The accessibility statement pillar covers what belongs in one.
  5. Re-scan on a schedule. Sites change every sprint, and a fix from March regresses in June. A dated trail of scans and remediation notes is what your counsel wants if a demand letter ever arrives.

Use the WCAG checklist as the working reference for the criteria by level while you triage.

Do accessibility overlays make my site ADA compliant?

No, and the regulator has said as much with money attached. In January 2025 the FTC ordered overlay vendor accessiBe to pay $1 million over marketing claims that its accessWidget product would "automatically" make a site compliant with WCAG (FTC). An overlay runs on top of your markup at page load; it cannot rewrite the underlying HTML a screen reader reads. Suits against sites already running a widget keep getting filed. Overlays do not fix code, and we built the opposite on purpose. If you inherited one, accessiBe alternatives that fix code walks through the difference.

FAQ

Is my business website legally required to be ADA compliant?

If your business is open to the public, the ADA applies to your website, per DOJ's longstanding interpretation of Title III (ADA.gov). There is no dated federal regulation naming a WCAG version for private businesses, but courts treat WCAG 2.1 AA as the benchmark, and WCAG 2.2 AA is the safer target to build toward.

Which WCAG version do I need for ADA compliance?

For private businesses, no version is legally mandated, but WCAG 2.1 Level AA is what litigation and DOJ guidance point to, so WCAG 2.2 AA is the practical target since it includes everything in 2.1 (ADA.gov). For state and local governments, the Title II rule requires WCAG 2.1 AA specifically (ADA.gov).

What are the ADA website compliance deadlines?

Only Title II (governments) has dated deadlines: April 26, 2027 for entities of 50,000 or more people, and April 26, 2028 for smaller ones and special districts, after DOJ's 2026 one-year extension (Federal Register). Private businesses under Title III have no dated deadline.

Can a tool make my website fully ADA compliant automatically?

No. Automated testing catches roughly 30 to 57% of accessibility issues, and the rest needs human review (Deque). Overlay widgets that claim automatic compliance drew a $1 million FTC penalty against accessiBe in 2025 (FTC).

Does the ADA apply to small business websites?

Yes. Title III covers public accommodations regardless of size, so a small online store has the same obligation as a large one. Federal court data shows most website accessibility defendants are businesses under $50M in revenue, not household names (Seyfarth ADA Title III).

See where your site stands

There is no ADA certificate, but there is a clear first step: know which WCAG issues are on your pages today. A scan gives you a ranked, specific list with the exact selector for each finding, so you fix the barriers that block real users before you touch the cosmetic ones. Run a free accessibility scan and start with the map.

Written by Pavel Charkasau, founder of wcagc.com. I keep an eye on what DOJ actually publishes so the guidance here matches the source, not the marketing around it.

Last updated: July 29, 2026

Sources