There is a comforting rumor going around clerk's offices and IT departments: old PDFs are exempt, so the backlog does not really count. The archived-content exception in the ADA Title II rule is real — but it is narrower than the rumor, and most of the documents people hope it covers do not qualify. Here is what the exception actually says, and how to apply it without gambling.
What does the archived-content exception actually cover?
Web content is excepted only if it meets all four conditions: it was created before your compliance date (or reproduces paper records that predate it); it is kept only for reference, research or recordkeeping; it lives in a dedicated, clearly identified archive area; and it has not been changed since it was archived (ADA.gov fact sheet).
All four. Miss one and the content is covered like everything else. The condition entities most often fail is the third: a ten-year-old PDF sitting in the same documents folder as this month's agenda is not in a dedicated archive area, no matter how old it is.
What about the preexisting-document exception?
There is a second, separate exception for conventional electronic documents — PDFs, word processor files, presentations and spreadsheets — that were available on your site before your compliance date (final rule, Federal Register). Unlike the archived-content exception, it does not require the file to live in an archive section.
But it carries a sharp limit: the exception does not apply if the document is currently used to apply for, gain access to, or participate in your services, programs or activities. An old budget report probably qualifies. An old permit application form that residents still download and submit does not — its age is irrelevant, because it is in active use.
Why won't these exceptions save most of your PDFs?
Because use breaks them, and public document collections are full of use. The fee schedule people check before paying, the form still linked from a service page, the minutes cited in a current dispute, the policy staff email to residents — none of that is excepted, whatever its date. And the moment you update or correct an excepted document, it leaves the exception and must be made accessible.
There is one more thing the exceptions never remove: the duty to respond to individuals. If someone needs an archived document in an accessible format, the underlying obligation to provide access to your programs still applies. The exceptions manage the long tail; they do not close the door.

Which documents typically do qualify?
The genuinely archival material: minutes from closed matters kept for the historical record, superseded budgets and plans, reports from programs that ended, correspondence retained purely for recordkeeping. The pattern is content whose only remaining job is to document the past — nobody needs it to do anything with your government today.
Two quick self-tests help. First, the link test: if a current service page still links to the document as part of how residents use a program, it is not archival, whatever its date. Second, the update test: if you would need to correct or refresh the document for it to stay useful, it is a living document, and updating it would end the exception anyway. Documents that pass both tests are the honest candidates for a labeled archive section.
How should you apply the exceptions without gambling?
Deliberately, and in writing. Inventory the documents, tag each one with which exception you are claiming and why, move genuinely archival material into a labeled archive section, and publish an on-request remediation commitment with a stated turnaround. A recorded classification you can show later is worth far more than an assumption that old meant exempt.
Then re-review on a schedule. Documents fall in and out of use — a dormant form gets re-linked, an archived report becomes part of live business — and a classification from last year is only as good as its last check.
What's the honest takeaway?
Treat the exceptions as a prioritization tool, not an escape hatch. They exist so you can concentrate budget on the documents people actually need — which is exactly where a remediation plan should start anyway. Sort your backlog into covered, excepted and retire-entirely, and you will usually find the covered pile is still large, but finally finite.
This article is not legal advice. For your organization's compliance obligations, consult your counsel.
Topicsada-title-iiexceptionsarchivecompliance
About the author
Rakesh Patel — CEO & Founder
Rakesh Patel is the founder and CEO of DocoMatic and the founder of Space-O Technologies (2010), the engineering company behind it. He brings 32 years of leadership experience in business strategy, operations and IT, and has overseen the delivery of more than 3,000 software projects. DocoMatic applies that delivery experience to one specific problem: making public documents accessible, verifiably.



