Archived content exceptions: what actually qualifies

The archived-content exception is the most misread part of the Title II rule: it is routinely treated as "old stuff doesn't count," which is not what it says. This guide walks through the actual conditions, the companion exception for preexisting documents, and a defensible process for classifying an archive.

What does the archived-content exception actually say?

Web content is excepted only if all four conditions hold: it was created before the entity's compliance date or reproduces pre-deadline physical records; it is kept only for reference, research or recordkeeping; it sits in a dedicated archive area; and it has not been changed since being archived. Miss one and the content is covered. The "compliance date" the first condition turns on is the one set for your cohort by the DOJ's April 20, 2026 interim final rule, which amended 28 CFR 35.200(b) (interim final rule, 91 FR 20902) — not the date printed in the 2024 final rule.

• The four cumulative conditions, one by one
• Organized and stored in a dedicated area or areas clearly identified as being archived (28 CFR 35.104) — what that implies for your site structure
• Editing archived content ends the exception

How is the preexisting-document exception different?

It covers conventional electronic documents — PDFs, word processor, presentation and spreadsheet files — that were available on the site before the compliance date, without requiring them to live in an archive. But it collapses the moment the document is currently used to apply for, access or participate in the entity's services.

• Which formats count as conventional electronic documents
• No archive requirement — but a sharp "currently used" limit
• Examples: an old budget report vs. an old-but-active permit form

What breaks these exceptions in practice?

Use. If a resident needs the document to do something with the government today — a form still in circulation, a fee schedule people rely on, minutes cited in a live matter — the exception does not apply regardless of the document's age. Updating a document also removes it from both exceptions.

• Currently used to apply for, gain access to, or participate in (28 CFR 35.201(b)) as the operative test
• Updates, corrections and re-publication
• Individual requests: accommodation duties survive the exception

How should an entity apply the exceptions without gambling?

Classify deliberately: inventory the documents, tag each with which exception is claimed and why, move genuinely archival material into a labeled archive section, and publish an on-request remediation commitment. A written classification you can show later beats an implicit "we assumed it was fine."

• An inventory with a recorded exception rationale per document
• Restructuring the site: a real archive section
• On-request remediation policy with a stated turnaround
• Periodic re-review as documents fall in and out of use

Should we still remediate some excepted content?

Sometimes, yes. High-interest historical material — landmark decisions, popular records — earns remediation because people use it, exception or not. The exceptions manage the long tail so the budget concentrates where access matters; they are a prioritization tool, not a goal.

• High-demand archival material worth fixing anyway
• Balancing archive cost against on-request obligations
• How DocoMatic flags exception candidates in an inventory