ADA Title II: the April 2026 deadline was extended - here is what changed

The short version

The U.S. Department of Justice published its final Title II rule in April 2024 with an original compliance date of April 24, 2026. On April 20, 2026, days before that date, DOJ issued an interim final rule pushing the deadlines out by one year, citing that it had “overestimated the capabilities (whether staffing or technology) of covered entities” to comply on the original schedule.

Covered entities must still ensure that the web content and mobile apps they offer to the public, including the PDFs they link to, meet the Web Content Accessibility Guidelines 2.1 at Level AA. The new dates are:

• April 26, 2027 - state and local government entities with a total population of 50,000 or more (was April 24, 2026).
• April 26, 2028 - public entities with a population under 50,000, and any special district government (was April 26, 2027).

The takeaway is simple: you have 12 more months, not a reprieve. The WCAG 2.1 AA bar, the PDF scope, and the enforcement regime all remain.

What changed, in plain language

• PDFs are in scope. The old guidance relied on Section 508, which many state agencies were not formally bound by. Under the new Title II rule, PDFs that communicate a service or program to the public must be accessible.
• WCAG 2.1 AA is the legal minimum. That is a step up from the commonly cited 2.0 AA. DocAccessible targets WCAG 2.2 AA (a backward-compatible superset), so meeting our output also meets the Title II bar.
• Remediate, do not just reissue. Simply posting the same PDF in a new format is not a remedy. The rule contemplates the underlying structure, not the file extension.

Who is affected

State governments, county and city governments, public universities, public school districts, municipal utilities, transit agencies, state courts, public hospital authorities, and the contractors that publish on their behalf. Federal agencies already follow Section 508 and are not directly covered by Title II.

What counts as a PDF "on your website"

• PDFs linked from public pages (policies, permits, forms, reports).
• PDFs served from services on your domain (e.g. permit portals).
• PDFs attached to emails that complete a public transaction - once linked, they are in scope.

Internal-only PDFs, archived records no longer used for current services, and preserved versions that comply with narrow exemptions are lower risk. Do not assume something is exempt without a legal review.

A 12-month remediation plan (new deadline: April 26, 2027)

Don't read the extension as a reason to slow down. Twelve months is enough time to do this properly - once. The program below assumes a typical municipal or university site with a few hundred to a few thousand public PDFs.

1. Month 1 - inventory and ownership. Crawl your public site, export every PDF URL, and assign a department owner to each one. Group into “forms”, “policies”, “reports”, and “other”. Baseline each with an automated score so you can measure progress.
2. Month 2 - triage and policy. Prioritise by traffic and regulatory weight (forms and policies first). Publish an internal remediation policy so new content after today is required to be accessible at publish time.
3. Months 3 – 6 - bulk remediation. Run documents through an automated pipeline to add tags, language, alt text, and reading order. Use a documented, risk-based manual review sample and expand it when recurring failures appear. Publish an accessible format that meets the rule for the document and context.
4. Months 7 – 9 - complex and legacy. Tackle complex tables, scanned documents needing OCR, and multi-column technical reports. Route truly unremediable assets (historical scans, handwritten records) through the alternative-format process your policy defines.
5. Months 10 – 11 - CMS integration. Bake remediation into the publishing workflow so nothing new goes live untagged. Train communications and department authors on the one-page checklist.
6. Month 12 - document and attest. Keep a register with the original score, remediated score, remediation date, and reviewer. Publish an accessibility statement. This creates an internal record of the organization's decisions and follow-up.

Why you should not wait until 2027

Two reasons. First, the substantive requirements did not change - every PDF you publish between now and April 2027 should already be accessible because it is the right thing to do, not because the calendar demands it. Second, a large document backlog still requires inventory, ownership, remediation, and manual verification. Teams that delay reduce the time available for those steps. Plan against the current published dates and monitor the DOJ source for changes.

Common mistakes

• Treating accessibility as a one-off project. Every new PDF published between now and April 2027 - and every one published after - is in scope. Bake remediation into the CMS publishing workflow instead of running a one-time sprint and calling it finished.
• Treating the extension as a pause. The substantive requirements did not change; only the enforcement date moved. Residents with disabilities still need to read your documents this year.
• Using "reader mode" as the accessible version. Reader mode is a browser setting and does not by itself establish that an alternate version meets the applicable requirements.
• Relying on a single automated tool. Automated tooling can catch the structural problems. A human still needs to confirm alt text quality and reading order for content-heavy documents.

Frequently asked questions

What exactly did the DOJ change on April 20, 2026?

The DOJ published an interim final rule extending the Title II web and mobile app compliance dates by one year. The substantive accessibility requirements (WCAG 2.1 Level AA) are unchanged; only the timeline moved. The rule was effective on publication, April 20, 2026.

What are the new deadlines?

State and local government entities with a population of 50,000 or more now have until April 26, 2027 (was April 24, 2026). Public entities with a population under 50,000 and special district governments now have until April 26, 2028 (was April 26, 2027).

Why did the DOJ extend the deadline?

The Department stated it 'overestimated the capabilities (whether staffing or technology) of covered entities' to meet the original timeline. The extension gives covered entities additional time to plan and budget, but enforcement posture on the underlying WCAG 2.1 AA requirements has not changed.

Do I have to comply with the new Title II rule?

State and local government entities, and any public higher-education institution that receives state or federal funding, are covered. Public entities with a population of 50,000 or more must comply by April 26, 2027. Public entities with a population under 50,000 and special district governments have until April 26, 2028.

Do scanned PDFs count as web content?

Yes. If a PDF is hosted on a public website or made available through a public service, it is in scope, regardless of whether it was scanned or born-digital. Scanned PDFs need OCR plus tagging to become accessible.

What exactly is the technical standard?

WCAG 2.1 Level AA is the legal minimum named in the DOJ rule. WCAG 2.2 AA is a backward-compatible superset and the current W3C recommendation; DocAccessible targets 2.2 AA. For PDFs, this typically also means meeting ISO 14289-1 (PDF/UA-1).

Is there a difference from Section 508?

Section 508 applies to federal agencies and already uses WCAG 2.0 AA. The Title II rule applies to state and local government, sets WCAG 2.1 AA as the minimum, and covers documents that many agencies previously overlooked. We ship at WCAG 2.2 AA to stay ahead of future amendments.

Are there any exemptions for legacy documents?

Archived documents that predate the rule and are not actively used for current services may be exempt, as are specific classes of pre-existing documents on password-protected portals. The safest interpretation is to treat the exemption as narrow.

How DocAccessible fits in

DocAccessible automates the repetitive parts of the plan above. Upload a PDF and we publish a hosted HTML page at a URL you can share in minutes; a rebuilt PDF/UA-aligned file is generated from the same remediated structure. That automated PDF may not retain the source layout. Documents that must stay visually identical need separately scoped manual PDF remediation. The in-browser editor lets a human reviewer fix alt text and reading order, and every save produces a new version with a re-scored automated report.

Primary sources

• U.S. Department of Justice: Title II web and mobile accessibility rule and current dates
• U.S. Department of Justice: rule fact sheet and document exceptions
• W3C: Web Content Accessibility Guidelines 2.1