The DOJ's 2024 Title II rule does not require every web document to comply by the deadline. It exempts five categories. The most useful, and the most misunderstood, is the archived web content exception at 28 CFR § 35.201(b).
Used correctly, the archive exception lets you preserve historical content without paying to remediate it. Used incorrectly, it provides no protection at all and may make your overall compliance posture worse by signaling to a plaintiff that you knew your content was inaccessible.
The four conditions, in plain English
For content to qualify as archived web content, all four of these must be true:
- It was created before the compliance date (or it is reproducing paper or other physical media created before the compliance date), or it reflects information that was up-to-date on a specific date in the past and has not been updated since.
- It is retained exclusively for reference, research, or recordkeeping. Not for current programs, services, or activities.
- It is kept in a special area of the website clearly identified as containing archived content.
- It has not been altered or updated since being archived.
Miss any one of these and the content is not archived. It's just inaccessible content sitting on your live website.
The label test. If a member of the public clicked from your homepage to a document and could not tell whether it was current or historical, it is not archived. The "clearly identified" requirement is real, and visual prominence matters.
What does NOT qualify
Below are the failure modes we see most often when reviewing California agency websites:
1. Documents you "haven't touched in a while"
Forgetting to update a document is not the same as archiving it. If a 2019 emergency preparedness PDF lives on your "Public Safety" page next to current materials, it is not archived — even if no one has opened the file in three years. The exception requires affirmative classification, not neglect.
2. Old agendas and minutes on your meetings page
Agenda and minute archives are the single most common source of non-compliant PDFs in California agencies. If your "Meetings" page shows the most recent meeting and links chronologically backward to 2008, the older items are not archived under the rule. They live in the same active section as the new ones, and the rule reads "clearly identified as containing archived content," not "older than the most recent."
To bring meeting minutes under the exception, you would need a separate "Archive" subsection (e.g., Meetings → Archive (pre-2025)), with clear labeling and no further updates to anything inside it.
3. Documents linked from current program pages
If your housing-assistance page links to a 2017 application form, that form is being used to apply for a current program. Even if you intended to "archive" it, the rule says archive content cannot be retained for a current program, service, or activity.
4. Things on a hidden URL
"We just unlinked it from navigation" is not archival. The content is still publicly accessible. The rule's "special area of the website clearly identified" requirement implies discoverability with a label, not hiding without one.
5. Content you changed last week
The "no alterations or updates" rule is strict. Re-uploading a PDF to fix a typo, changing the link text, or moving the file to a new URL all reset the clock. Once archived, it stays exactly as it is.
What clearly DOES qualify
- A "Historical Documents" subsection containing pre-deadline city council resolutions, formally labeled and never updated.
- Old annual reports moved to About Us → Archive (FY 2014–FY 2024), with a banner explaining the section is historical.
- Pre-deadline meeting minutes moved to a clearly labeled archive subsection separate from current meeting materials.
- News releases from before the compliance date in a labeled "News Archive" section.
The pattern: separate URL section, plain English label, no further updates.
How to use the exception in practice
The archive exception is most valuable when you front-load it. Done before remediation begins, classification can remove 20–40% of pages from your remediation budget. Done after, you've already paid to remediate things you didn't need to.
A defensible workflow:
- Inventory. Crawl your website and list every public document with its URL, title, file size, and last-modified date.
- Classify. For each document, decide: archive, remediate, replace with HTML, or remove. Document the rationale for each archive classification.
- Build the archive section. Create a clearly labeled URL path (e.g.,
/archive/) with a banner explaining the contents are historical and may not be accessible. - Move and lock. Move classified content to the archive section. Apply a CMS rule that prevents edits to anything inside it.
- Document. Keep a written record of the classification methodology, the date each document was archived, and who approved it. This is your defense if challenged.
The archive exception is opt-in, not automatic. The rule does not classify content for you. Until you affirmatively move and label content, it counts as live and inaccessible.
One thing the rule does not protect against
The archive exception is a defense to the federal Title II compliance obligation. It is not a defense to California's Unruh Civil Rights Act, which provides $4,000 in statutory damages per violation regardless of federal compliance status. Plaintiffs in California state court have alleged Unruh violations against agencies for documents that would have been archive-exempt federally.
The practical consequence is that aggressive archival reduces your federal exposure but does not eliminate state exposure. Where the document genuinely no longer serves a public purpose, archive it. Where it does, remediate it.