ADA Title II Web Rule: 2027/2028 PDF Deadlines for State & Local Government

For years, state and local governments operated in a gray zone: the ADA clearly required accessible communication, but no rule said exactly what "accessible" meant for a website or a PDF, or by when. That gray zone is gone. On April 24, 2024, the Department of Justice published a Title II rule that sets a concrete technical standard — WCAG 2.1 Level AA — and firm compliance deadlines in 2027 and 2028, and it applies directly to the PDFs, Word files, spreadsheets, and presentations governments publish. This is general information, not legal advice.

What the rule actually requires

The DOJ's 2024 Title II rule adopts WCAG 2.1 Level AA as the required standard for the web content and mobile apps of public entities. Crucially, it does not stop at HTML pages. The rule reaches conventional electronic documents that an entity makes available to the public, which is where most government accessibility work actually lives.

In plain terms, a covered government entity must ensure that its web content and electronic documents:

• Conform to WCAG 2.1 AA success criteria.
• Are available to people using screen readers, magnification, keyboard-only navigation, and other assistive technology.
• Meet the standard by the entity's applicable deadline (below).

WCAG 2.1 AA is the same benchmark that courts and settlements already used as a de facto standard; the rule's contribution is to make it mandatory and explicit for government, with no room left to argue that the obligation is undefined.

Who is covered

Title II covers state and local government entities — broadly. If a body is part of, or an instrumentality of, state or local government, it is generally in scope. That includes:

• State agencies and departments, and their county and municipal counterparts.
• Special district governments — independently operating bodies such as water, utility, fire, and transit districts.
• Public colleges and universities (private institutions fall under different rules; see how this plays out for education in higher-ed and K-12 PDF accessibility).
• Courts and the documents they publish — forms, notices, filings, dockets.
• Public libraries, including the digital materials and documents they distribute.

Note that this is the public-sector track. Recipients of federal funding face a parallel obligation under Section 504, and federal agencies under Section 508 — overlapping but distinct regimes. The differences are worth understanding if your entity receives federal money; see Section 508 vs Section 504. Healthcare entities funded by HHS have their own deadlines under a separate 504 rule, covered in healthcare PDFs and HHS Section 504.

The standard: WCAG 2.1 AA

The rule pins compliance to WCAG 2.1 Level AA specifically — not 2.0, and not the newer 2.2. For a PDF, conforming to WCAG 2.1 AA means, among other things:

• The document is properly tagged so assistive technology can interpret its structure.
• Reading order follows the logical flow of the content.
• Images that convey meaning have alt text; decorative images are marked as artifacts.
• Contrast and color use meet the AA thresholds.
• Forms have labeled fields, a logical tab order, and clear instructions.

Even though the rule cites 2.1, building to the more recent WCAG 2.2 is a reasonable forward-looking choice since it is a superset that adds nine success criteria over 2.1 — meeting 2.2 generally means you have met 2.1.

The population-based deadlines

The most important operational detail is when you must comply. The rule phases compliance by the size of the population the entity serves. After an April 2026 interim final rule, the deadlines are:

Two things to watch:

• Special district governments get the later date (April 26, 2028) regardless of the population they serve.
• The deadline is based on population served, not internal headcount — a small agency serving a large metropolitan area can land in the earlier 2027 group.

Given how long a full PDF inventory and remediation effort takes, even the 2028 date is closer than it looks for an entity with thousands of legacy documents.

Conventional electronic documents are explicitly covered

This is the part many entities underestimate. The rule names conventional electronic documents directly, and the category is exactly what you would expect:

If your entity posts a benefits application as a PDF, a budget as a spreadsheet, or a council presentation as a slide deck, those files are squarely in scope. A government website can pass an automated page scan while still hosting hundreds of non-compliant documents behind its links — which is precisely where remediation effort tends to concentrate.

The limited exceptions

The rule includes a handful of narrow exceptions. They are real, but they are far narrower than entities often hope, and the burden is on the entity to show an exception applies:

• Archived web content — content that is outdated, kept only for reference or recordkeeping, not currently used, and stored in a designated archive area.
• Certain preexisting electronic documents — documents created before the deadline that are not currently used to apply for, access, or participate in the entity's services. The moment a "preexisting" document is still in active use, the exception evaporates.
• Third-party content — content posted by outside parties that the entity does not control (with important caveats; content a third party posts on the entity's behalf generally does not qualify).

The common thread: anything a member of the public actually needs to interact with your services is not exempt. A 2019 application form that residents still submit is covered no matter how old it is.

Enforcement reality

It is tempting to read "no penalty listed in the rule" as "low risk." That misreads how Title II is enforced. The rule does not create the obligation — the ADA's nondiscrimination mandate already did — it operationalizes it. Enforcement comes through:

• DOJ investigations and enforcement actions, which can result in agreements requiring remediation, monitoring, and reporting.
• Private litigation and complaints brought by affected individuals and advocacy organizations.
• Reputational and operational fallout when residents cannot access essential services.

The practical posture for most entities is not to wait. Inventory your documents, prioritize the ones tied to active services, and work backward from your deadline. For a step-by-step framework that fits into this timeline, the complete ADA compliance guide lays out the audit-remediate-verify-maintain cycle.

Key takeaways

• The 2024 DOJ Title II rule requires WCAG 2.1 Level AA for state and local government web content and conventional electronic documents.
• Deadlines are population-based: April 26, 2027 for entities serving 50,000+, and April 26, 2028 for smaller entities and special district governments.
• PDF, Word, Excel, and PowerPoint files are explicitly covered — a clean website is not enough if the linked documents fail.
• Exceptions for archived content, certain preexisting documents, and third-party content are narrow; anything tied to active services is in scope.
• Enforcement runs through DOJ actions and private complaints, so the safe move is to inventory and remediate well before your deadline.