Document accessibility is not a badge attached at the end of a project. It is a chain of structural decisions, made file by file, that determines whether a reader can navigate a meeting packet, understand a benefits notice, or verify what a scanned budget report actually says.
The deadline changed; the archive did not
The Department of Justice (DOJ) finalized new regulations under Title II of the ADA in 2024, and the rule does not set a single compliance date for every government website and document. Public entities serving a population of 50,000 or more must comply by April 24, 2026, while entities serving fewer than 50,000 residents and special district governments of any size have until April 24, 2027, according to the ADA.gov Title II web rule overview. That tiered structure matters more than the collapsed shorthand of "sometime in 2027 or 2028" suggests, because a mid-sized school district and a major transit authority can land on entirely different clocks even when their websites look identical from the outside.
Either date arrives sooner than the calendar makes it feel, and neither date makes the underlying document problem smaller. City councils, school boards, transit agencies, courts, libraries, and special districts already have years of PDFs online: agendas, maps, notices, forms, budgets, emergency plans, scanned packets, and vendor-generated reports.
The practical question is not only whether the website redesign will meet its deadline. It is whether the document archive behind that website can be inventoried, prioritized, remediated, replaced, or retired without pretending every file carries the same public value.
Documents are part of the service surface
A resident does not experience a PDF as a backend record. They experience it as the permit form, board packet, fee schedule, bus map, school policy, public notice, or emergency instruction they need to act on. If that document is scanned, untagged, unlabeled, or impossible to navigate by headings, the service can fail even when the surrounding page looks modern.
That is why document accessibility is not simply a PDF cleanup project. It crosses records management, communications, procurement, legal, content management system (CMS) governance, source templates, and vendor deliverables. A contractor can remediate a batch of files today while the agency continues exporting the next batch from broken source documents tomorrow.
What a tagged PDF actually promises
A PDF that reads cleanly to a sighted eye and a PDF that is genuinely accessible are not the same artifact, and the gap between them is usually invisible until someone uses assistive technology to navigate it. A properly tagged PDF carries a logical structure tree, meaning headings, paragraphs, lists, and tables are marked as what they are, plus a reading order that tells a screen reader which text comes next regardless of how it is positioned visually on the page. Export a document from a word processor without checking that structure, and the reading order can silently follow the sequence in which objects were placed on the canvas rather than the sequence a person would read them, which is how a two-column budget table ends up narrated as one scrambled sentence.
Scanned packets fail differently. A board packet run through a copier and saved as a PDF is, structurally, a stack of images. Optical character recognition (OCR) can lay an invisible text layer underneath so the file becomes searchable and readable aloud, but OCR accuracy depends heavily on scan quality, font choice, and layout complexity, and a misread header or a garbled table is not something a document owner will notice from a visual proofread. Neither failure mode shows up by looking at the page. Both require someone to actually run the file through a screen reader or a structure checker before calling the remediation finished.
Build the inventory around public consequence
Do not start by counting every PDF equally. Start by identifying the documents tied to rights, deadlines, money, safety, eligibility, public meetings, required forms, and high-volume services. Then mark each file with a practical disposition: keep and remediate, replace with HTML, archive with an accessible alternative on request where allowed, remove because it is obsolete, or route back to the document owner because the source process itself is broken.
The ADA.gov Title II web rule overview is worth bookmarking for the plain-language scope of what counts as covered web content, since PDFs and other documents are included even when they sit outside the main website template. WCAG2ICT is the companion reference for understanding how WCAG success criteria, written with web pages in mind, translate to non-web documents such as PDFs and Office files.
The inventory should also distinguish a public-record obligation from a public-service obligation. Some files must remain available because they document government action and belong to the permanent record. Others are active instructions people need today to complete a task, meet a deadline, or exercise a right. Those categories can overlap, but they should not be managed as one undifferentiated pile with a single remediation priority.
The retest trail is the deliverable
A document fix that cannot be retested is not a stable operating practice. For each priority file, keep the original URL, document owner, source file, remediation method, checker output, manual review notes, publication date, and retest result. If the document is recurring, record how the next version will be created so the same structural problem does not reappear at the next meeting cycle.
That trail matters because public-sector document work ages quickly. Staff change, vendors change, templates change, and emergency updates happen under pressure that does not leave time for careful export settings. The evidence trail is how a team proves it is not merely buying a one-time repair that expires the moment someone edits the source file in the wrong program.
This is where procurement language earns its keep. A remediation contract should specify whether the supplier returns corrected PDFs only, corrected source files, documented test evidence, or a repeatable publishing workflow that the agency's own staff can run going forward. If the contract buys only the corrected output, the city may be back in the same place the next time an agenda packet is exported from the same broken template.
What to fix before the clock runs out
Pick one service area with real public consequences and map its documents from the resident's point of view. Which PDFs are required to understand the service, complete the task, meet a deadline, or preserve proof of eligibility? Those files go first. The rest of the archive can be sequenced against policy and budget, but the service-critical documents need named owners now, not after the next compliance deadline arrives.
The deadline moved. The documents did not. The work now is to make the archive governable before an unmanaged pile of PDFs becomes an emergency inventory during an audit, a lawsuit, or a disaster response.