The 5 Exceptions to the DOJ Title II Web Rule, Explained

1What Changed in April 2026

The original Title II web rule was published in the Federal Register on April 24, 2024. It set compliance dates of two and three years out for different entity sizes. On April 20, 2026, DOJ published an Interim Final Rule that pushed both dates back by one year. The current deadlines are:

Special districts, which include water districts, fire districts, transit authorities, and library districts, always fall into the later, 2028 deadline regardless of the population they serve. Read more about what that means for special district websites and for cities, counties, and townships under the 2027 deadline.

2Why the Rule Has Exceptions At All

DOJ built exceptions into the rule because a strict, no-exceptions reading of WCAG 2.1 AA would require agencies to retroactively rebuild decades of archived records, historical social media feeds, and case-specific paperwork that almost no one will ever request in an inaccessible format. The exceptions are narrow and specific. They exist to keep compliance efforts focused on what residents actually use today, not to excuse agencies from the rule.

3The 5 Named Exceptions, At a Glance

4Exception 1: Archived Web Content

Content qualifies as archived only if it was created before your compliance date, is kept solely for reference or recordkeeping, is stored in a designated archive section, and has not been altered or updated since it was archived. Move it, edit it, or keep linking to it from your active navigation, and it loses the exception.

5Exception 2: Preexisting Conventional Electronic Documents

Word processing files, presentations, PDFs, and spreadsheets posted before your compliance date can be exempt, with one major carve-out: if the document is needed to apply for, participate in, or access a current government service, program, or activity, the exception does not apply and the document must be remediated.

This is the exception most agencies get wrong, because most legacy government PDFs exist precisely to help residents access a service. Before you assume a document is exempt, run it through a free scan with our ADA PDF audit tool or Keyspider's AI PDF audit tool to see which of your PDFs are actually blocking a live service versus safely archival. For documents that do need fixing, our step-by-step PDF remediation guide and PDF accessibility tool walk through tagging, OCR, and HTML alternatives.

6Exception 3: Third-Party Content You Don't Control

Content posted directly by members of the public, such as public comments on a forum or a citizen-submitted photo, can fall outside the rule when your agency has no contractual relationship with the poster. This exception is narrower than it sounds: it does not cover content posted by your contractors or vendors on your behalf. That content is treated as if the agency posted it itself.

Contractor responsibility is where this exception causes the most confusion, and it is exactly what our breakdown of contractor accountability under the final rule covers in detail. If your agency runs on a CMS built by an outside vendor, ask that vendor how it handles accessibility by default, not just how it handles complaints. WPPersona's government website CMS builds WCAG 2.1 AA structure into every page template so contractor-published content is accessible from the moment it goes live.

7Exception 4: Individualized, Password-Protected Documents

Word processing files, presentations, PDFs, and spreadsheets that relate to a specific individual, account, or property, and are secured behind a password or login, can qualify for this exception. The logic is straightforward: a document meant for exactly one resident does not need the same treatment as a public-facing page, provided the agency still accommodates that resident if they request an accessible version.

8Exception 5: Preexisting Social Media Posts

Posts made to an agency's social media accounts before the compliance date are exempt, since DOJ recognized that retrofitting years of historical posts with alt text and captions is impractical. This exception only covers the backlog. Every post made on or after your compliance date needs alt text on images and captions on video, no exception.

9Three More Flexibilities Beyond the Named Exceptions

ADA.gov also outlines flexibilities that apply on top of the five exceptions. These are not exemptions from the rule, they are ways the rule is applied in specific situations.

10The Nuance Almost Every Agency Misses

None of the exceptions above cancel out the ADA's broader, older obligations. Even when content technically qualifies for an exception, or already meets WCAG 2.1 AA, your agency must still provide effective communication, reasonable modifications, and equal opportunity access through alternative means when a resident with a disability asks for one.

In practice, that means every exempt archived PDF, every old social media post, and every individualized document still needs a real, working process behind it: a phone number, an email address, or a request form where someone can ask for an accessible version and actually get it. An exception with no fallback process is not compliance, it is a gap waiting to become a complaint.

11A Quick Way to Check Any Piece of Content

12How WPPersona Helps You Apply These Exceptions Correctly

Working out which content actually qualifies for an exception is a documentation problem as much as a technical one. WPPersona is built for government teams who need to make these calls confidently and keep a record of why.

Need documentation for a procurement process or a VPAT request? Our VPAT / Accessibility Conformance Report lays out exactly how WPPersona conforms to WCAG 2.1 AA, criterion by criterion. Agencies of every size, from state government to K-12 school districts, use it to fast-track vendor accessibility reviews across the SLED sector.

Related Articles