DOJ Title II Web Rule: What It Signals

The Department of Justice rule on web accessibility for state and local governments is the clearest federal web rule in this field, and it is also the most misread. It names a technical standard, WCAG 2.1 Level AA, and it gives dates. It does not set a deadline for a private shop, a restaurant, or an online store. That distinction is the whole point of the rule, and it shapes every practical step that follows.

Title II of the Americans with Disabilities Act covers state and local governments. The rule published on April 24, 2024, applies that duty to web content and mobile apps those governments provide or make available. The ADA fact sheet lists the covered bodies in broad terms: state and local governments, their agencies and departments, special purpose districts, Amtrak, and commuter authorities. A contractor does not change the duty. If a county hires a firm to build a parks page, or a city uses a private app for parking payments, the government stays responsible for the content and the app it makes available.

The standard and the dates

WCAG 2.1 Level AA is the technical standard in the rule. Level AA includes Level A, so the list runs from text alternatives for images and captions for prerecorded video through keyboard access, visible focus, labels for form fields, and contrast for normal text at 4.5 to 1. The rule treats web content broadly: text, images, sound, video, and documents. A PDF form a resident still uses to apply for a service is not a side file. It is part of the service.

Dates depend on population, not on budget or staff size. An interim final rule published on April 20, 2026, moved the dates by one year. The Federal Register extension sets April 26, 2027, for entities with a total population of 50,000 or more, and April 26, 2028, for entities with a smaller population and for any special district government. The ADA fact sheet now shows the same extended dates. Older guides still show the original 2026 and 2027 dates, so check the date on any summary before quoting it.

Those extended dates are the operative dates on the ADA fact sheet today, but they are not free of dispute. A secondary guide reports a federal challenge to the extension, with no merits ruling shown in that guide. This article does not predict how that challenge ends. The planning lesson is plain: a government that waits until the last month before its date has no slack if a court changes the schedule, while a government already working through templates and documents is less exposed either way.

Five exceptions, read narrowly

The rule has five exceptions, and each one carries conditions. Misreading them is a common error, because a folder named archive or a document posted years ago can look exempt when it is not.

• Archived web content must meet all four tests: created before the compliance date, kept only for reference, research, or recordkeeping, kept in a special archive area, and unchanged since archiving.
• Preexisting conventional electronic documents cover files posted before the compliance date, but not documents people still use to apply for, access, or take part in a service.
• Content posted by third parties covers content from truly unaffiliated people posting on their own behalf, not content a paid contractor posts for the government.
• Individualized, password protected documents cover a document about one person, property, or account, such as one resident bill behind a login.
• Preexisting social media posts cover posts made before the compliance date. New posts must meet the standard.

An exception also does not end the duty to communicate. The ADA fact sheet notes that even when content does not have to meet WCAG 2.1 Level AA under an exception, a government would likely still need to provide that content to a person with a disability who needs it in a format that works for them. A resident who asks for an archived report in an accessible format still needs an answer.

What the rule signals for private businesses

Private businesses fall under Title III, not Title II, and Title III has no matching web rule with a named standard and a date. That gap does not mean private sites sit outside the law. The Justice Department has long taken the position that Title III covers goods and services offered on the web, and courts and settlements often point to WCAG as the technical reference. The signal from Title II is narrower and more useful than a warning: when a federal rule does name a standard, it names WCAG 2.1 Level AA for government content, and WCAG 2.2 Level AA builds on that list without removing earlier criteria. A private business that builds to WCAG 2.2 Level AA is working to a newer list that covers the Title II standard, while a business that builds only to a script or a widget has not changed the underlying code.

That point matters for vendor choice. A government vendor, and a private business with a similar problem, should ask what changes in code, who reviews the change, and what dated record remains. Axeazy describes a scan that runs 98 automated checks and covers 14 fix categories, with fixes for a site with a GitHub repo arriving as a real pull request with a visible diff that the owner or developer reviews and merges. Paid prices are shown at checkout on Axeazy pricing, with annual billing saving 20 to 25 percent. The scope page at Axeazy capabilities lists the same fix categories and the platform limits.

A work order that fits the rule

Start with population and date. Confirm which date applies, then inventory the full estate: main site, subdomains, apps, social accounts, and the document library. The document count usually surprises a team, because forms, reports, and slide decks pile up over years. Mark genuine archive material under the four tests, and flag every older document that still forms part of a live process. Those flagged documents stay in scope.

Fix shared templates first. A broken header, a form component with no labels, or a colour pair with weak contrast repeats on every page that uses the template, so one fix clears many findings. Test colour pairs early, since contrast is a frequent failure on government pages. The contrast quiz gives a quick feel for readable pairs before a colour change is approved. Then test the tasks people actually complete: pay a bill, apply for a permit, register for a program, and find meeting times. A scan can list a missing label. Only a keyboard and screen reader pass shows whether the whole task works.

Put the same checks into procurement and publishing, and keep a dated record of scans, fixes, and retests.

Related reading on tool choice is here: How to Choose an Accessibility Tool: 10 Criteria

FAQ

Does the Title II rule apply to a private business website?

No, not directly. Title II covers state and local governments. A private business falls under Title III, which has no web rule naming a standard and a date. Courts and settlements often point to WCAG in Title III cases, so the absence of a private rule is not the same as an absence of duty.

Is WCAG 2.2 AA enough for a government site under the rule?

The rule names WCAG 2.1 Level AA. Building to WCAG 2.2 Level AA covers that list, since WCAG 2.2 builds on earlier versions without removing criteria, but the rule itself does not name 2.2. A government should confirm with its own advisers how it records that choice.

Do old PDFs get a free pass under the rule?

Only in narrow cases. A preexisting document kept only for reference and unchanged since posting may fall under an exception, but a document people still use to apply for or access a service stays in scope, and any document updated after the compliance date must meet the standard.

What should a government do if it received a demand letter or was sued?

This article gives general information, not legal advice. Talk to a qualified attorney if you received a demand letter or were sued. A dated record of scans, fixes, and retests can help that conversation, and a lawyer can advise on the exception and standing questions that turn on the facts of the case.

Last checked: October 31, 2026 Sources

• ADA.gov fact sheet on the Title II web and mobile app rule
• Federal Register interim final rule extending the compliance dates, April 20, 2026
• Secondary public sector guide to the Title II rule, for the exceptions summary and the pending challenge note Start with a free homepage scan and check the current plan scope before buying: Axeazy homepage

Related reading

• California Unruh Act: Website Basics