The April 2028 PDF accessibility deadline: a plain-language guide

If you run a library district, fire district, park district, or any other small
public entity, the deadline for making your web content — including the PDFs
on your website — accessible under DOJ ADA Title II is April 26, 2028.
That date was extended in April 2026 from the original 2027 deadline. The
extension gave you more time; it did not change what you're required to do.
This guide explains the rule in plain language: what changed, who it covers,
what "accessible" actually means for a PDF, and what to do first.

What changed and what didn't

In April 2024, the Department of Justice published a rule under ADA Title II
setting the first hard deadlines for state and local government web
accessibility. In April 2026, DOJ issued an
interim final rule (effective
April 20, 2026) that pushed both compliance dates back by roughly a year:

• Public entities of 50,000 or more people: April 26, 2027
• Entities under 50,000 people and all special districts: April 26, 2028

Two things didn't change. First, the technical standard: web content must meet
WCAG 2.1 Level AA, the same benchmark as
before. Second, the underlying obligation: the ADA has required effective
communication with people with disabilities all along — the rule sets a date
for a specific technical standard, but the duty to be accessible didn't take a
year off. The extension is time to get ahead of the work, not a reason to wait
on it.

Who Title II applies to

Title II covers state and local government entities — and that explicitly
includes special districts: library districts, fire protection districts, park
and recreation districts, water and sewer districts, cemetery districts, and
similar public bodies. There is no small-entity exemption, only the later
deadline. If your district publishes documents on a public website, the
Title II web rule is
written with you in mind, not just city and county web teams with dedicated
staff.

The rule covers web content your district provides or makes available, whether
you host it yourself or publish it through a vendor's platform. That's the
part that surprises many small districts: the board-minutes archive a vendor
hosts for you is still your responsibility.

What "accessible" means for a PDF

A PDF that looks fine on screen can be unusable for someone relying on a
screen reader. Meeting WCAG 2.1 AA for a PDF means the document carries the
invisible structure assistive technology needs:

• Tags that identify headings, lists, and tables, in a logical reading order
• A set document language and title
• Text descriptions (alt text) for images, charts, and figures
• Navigable tables with identified header rows
• Real text — a scanned page is a photograph of words until it's been
  converted and structured

The PDF-specific way to deliver that structure is
PDF/UA, the ISO standard for accessible
PDFs, checked with the open-source validator veraPDF. Remediating a document
to PDF/UA and validating it is how you turn "we think this file is fine" into
something you can demonstrate.

The existing-content nuances

Not every old file on your site is on the hook, and it's worth getting this
right, because the exceptions are narrower than they sound.

Archived web content is exempt only if it meets all four conditions: it
was created before your compliance date (or reproduces pre-existing physical
documents), it's kept only for reference, research, or recordkeeping, it lives
in a designated archive area, and it hasn't been changed since it was
archived. Reorganize it, update it, or keep using it, and the exception is
gone.

Preexisting conventional electronic documents — PDFs, Word files, and
similar posted before your compliance date — are exempt unless they're
currently used to apply for, access, or participate in your services. An old
newsletter likely qualifies; the meeting-room policy from 2019 that's still in
effect does not.

Two more things temper the exceptions. Anyone can still request an accessible
version of exempt material, and your district must provide effective
communication when they do. And everything you publish after your
compliance date must be accessible from day one — for districts digitizing
collections or posting minutes every month, the deadline isn't a one-time
cleanup, it's a permanent change to how documents go out the door.

A realistic timeline for a small district

• This year: inventory what's public. List the documents on your website —
  minutes, agendas, budgets, newsletters, policies — and note which are
  scans. Decide what genuinely belongs in a designated archive area and what's
  still in active use.
• Next year: remediate the active documents — the ones patrons and
  residents actually use to interact with your district — and set up a process
  so newly published documents go out accessible.
• By April 26, 2028: the public-facing backlog is remediated, new
  documents are accessible on publication, and you hold records showing the
  work was done — the difference between believing you're compliant and being
  able to show your board or an auditor.

What to do first

Start with the documents people currently use, not the deepest archive. A
flat-rate remediation subscription exists for
exactly this shape of problem: a backlog measured in years and a publishing
schedule measured in weeks, in an office where nobody has "PDF specialist" in
their job description.

The deadline moved once. The work it describes hasn't moved at all — and
districts that spread it over the next two years will have a much calmer
spring 2028 than districts that don't.