Archived content, old PDFs, and the new DOJ exception rules sit at the center of one of the most important accessibility conversations facing public entities today. Recent ADA updates and developments have changed how agencies, schools, counties, transit systems, and special districts should think about older web material that remains online but no longer supports active services. The core issue is simple: when does legacy digital content still need to meet modern accessibility standards, and when can it qualify for a narrow exception? In my work reviewing accessibility inventories for public organizations, this is where teams usually get stuck. They know inaccessible files create risk, but they also manage thousands of aging documents spread across websites, intranets, and document repositories. Understanding the new rules matters because it affects remediation budgets, migration plans, procurement decisions, and public trust.
For context, archived content generally means older web pages, reports, notices, forms, and media preserved for reference, research, or recordkeeping rather than current program participation. Old PDFs are often the biggest challenge because many were created years ago from scans, exported without tags, or posted before accessibility requirements were operationalized in daily publishing workflows. The Department of Justice has clarified limited exceptions for certain archived web content, but those exceptions are narrower than many organizations assume. This article serves as a hub for recent ADA updates and developments, explaining what has changed, what the DOJ exception rules actually cover, where public entities make mistakes, and how to build a practical compliance program around legacy content.
Why the new DOJ rules matter for archived content
The Department of Justice’s updated rule for web and mobile accessibility under Title II establishes a clear expectation: web content and mobile apps offered by state and local governments must be accessible, with technical alignment to WCAG 2.1 Level AA except where specific exceptions apply. For many agencies, the operational shock is not the homepage or current service portal. It is the long tail of old content. Boards publish meeting packets, police departments post annual reports, schools host handbooks, planning departments maintain zoning maps, and public health offices keep years of advisories online. Over time, these files accumulate into a sprawling digital archive with inconsistent formatting and little metadata.
The DOJ exception rules matter because they create a framework for triage. They do not erase accessibility duties across the board, and they do not permit agencies to label active materials as “archived” to avoid remediation. Instead, they recognize that genuinely historical content preserved only for reference may be treated differently if it is kept in a dedicated archive area, has not been altered after archival, and is not needed for current transactions, applications, decision-making, or participation in programs and services. In practical terms, a ten-year-old annual water quality report stored in an archive section may be treated differently from last month’s permit application packet, even if both are PDFs.
What qualifies as archived web content under the exception
The most important question is also the one most often answered incorrectly: what actually counts as archived content? The exception is not based simply on age. A file does not become exempt because it is five years old, because few people open it, or because the department no longer remembers who uploaded it. Archived content generally must be maintained only for research, reference, or recordkeeping; kept in a clearly identified archive area; and not altered or updated after it was archived. If staff revise a document to reflect a policy change, replace a page section, or continue using the file to support current decisions, the archival rationale weakens immediately.
Use plain examples. A city council video from 2016 preserved in an archive section for historical reference may qualify more readily than a 2016 procurement manual still linked from a current purchasing page. A scanned PDF of election notices from prior cycles may fit the archive exception if it remains solely for recordkeeping, while a 2018 benefits guide still relied on by retirees to understand current plan administration almost certainly should be accessible. The decisive factor is functional relevance, not nostalgia. If people need the content now to obtain services, understand rights, submit forms, meet deadlines, or participate in civic life, it is active content no matter when it was first posted.
Why old PDFs create the biggest accessibility risk
Old PDFs remain the highest-risk content type because they combine volume, technical defects, and user dependence. In accessibility audits I have led, legacy PDFs routinely account for the majority of severe barriers. Common failures include missing tags, incorrect reading order, untagged tables, absent document titles, image-only scans without OCR, low-contrast text embedded in graphics, and form fields that are not keyboard accessible. Screen reader users encounter these issues immediately, but people with low vision, cognitive disabilities, and mobility impairments are also affected when navigation is confusing or impossible.
PDFs are especially difficult because organizations often treat them as finished artifacts rather than service content. A public entity may invest in accessible web templates while continuing to upload inaccessible meeting agendas, enrollment packets, utility notices, and policy manuals as attachments. That creates a broken experience: the page may be accessible, but the information people actually need is not. This is why recent ADA updates and developments place so much attention on digital documents. The risk is not abstract. If a resident cannot read a sanitation schedule, a student cannot review disciplinary procedures, or an applicant cannot complete a housing form, the access barrier affects legal rights and daily life.
Common mistakes public entities make when applying the exception
The first mistake is calling everything old “archived.” I regularly see departments move files into an archive folder while preserving current links from active pages. That does not change the file’s role. If the public still reaches that PDF from pages about ongoing services, the document is operational content. The second mistake is partial remediation based on visibility alone. Agencies often fix the homepage and top-level navigation but leave board packets, staff reports, budget appendices, and legacy forms untouched even though these materials influence public participation. Third, teams overlook duplicate copies. One inaccessible PDF may appear in six places across a site, creating inconsistent remediation and ongoing confusion.
A fourth mistake is forgetting the alternative access obligation. Even when content fits an exception, public entities still need workable methods for individuals with disabilities to obtain information or equivalent access. That means documented request channels, trained staff, response timelines, and workflows for accessible conversion. Another common failure is poor records management. If departments cannot tell which files are legally required to remain online, who owns them, or whether they are still used in operations, they cannot classify archive content defensibly. The exception is useful, but only for organizations disciplined enough to separate historical preservation from current public service delivery.
How to build a defensible archive review process
A practical archive review process starts with inventory, ownership, and decision criteria. Crawl the public website, subdomains, and document repositories using tools such as Siteimprove, Pope Tech, Monsido, or Screaming Frog, then export all PDFs, Office files, videos, and legacy pages. Next, assign each asset to a department owner who can answer three questions: Is this content required to support a current service or legal obligation? Is it still being updated, referenced, or linked from active pages? Must it remain online for public use, or can it move to a true archive area? Without ownership, every document looks equally important, and nothing gets prioritized.
Then apply a classification model that distinguishes active, transitional, archived, and removable content. Active content supports current services and must be remediated or replaced. Transitional content is still online temporarily during migration and should have a short remediation or retirement timeline. Archived content is preserved only for reference or records. Removable content has no legal or operational reason to stay online. This model reduces cost because many inaccessible files do not need full remediation; they need retirement, consolidation, or HTML replacement. Agencies that skip this step spend money fixing documents no one should be using at all.
| Content category | Typical example | Accessibility action | Risk level |
|---|---|---|---|
| Active | Current application form, benefits guide, transit schedule | Remediate immediately or replace with accessible HTML/form | High |
| Transitional | Recently superseded policy during site migration | Set retirement date, provide accessible replacement | Medium |
| Archived | Past annual report preserved for recordkeeping | Store in archive area, maintain request process | Lower if truly inactive |
| Removable | Duplicate upload, obsolete flyer, expired notice | Delete and remove links | Low after removal |
What remediation should look like for legacy documents
When a document remains active, remediation must be substantive, not cosmetic. For PDFs, start with source files whenever possible because repairing exported or scanned files directly in Acrobat Pro is slower and less reliable. Use structured headings, true lists, tagged tables with proper header associations, descriptive link text, meaningful alt text, language settings, bookmarks for long documents, and verified reading order. Run OCR on scans, but do not trust OCR output without review; recognition errors can distort legal notices, financial data, and contact information. For forms, ensure keyboard access, clear instructions, programmatically associated labels, logical tab order, and error identification.
In many cases, the best solution is not remediating the PDF at all. Convert high-demand service information into accessible HTML and reserve PDFs for print convenience or formal records. A permitting checklist, paratransit eligibility instructions, or school enrollment guide is usually easier to navigate as a web page than as a twenty-page PDF. This approach improves accessibility and maintenance because updates happen once in the content management system instead of in multiple file versions. If a PDF must remain, provide an accessible source document and quality assurance review by trained staff using Acrobat accessibility tools, PAC, axe where applicable, keyboard testing, and screen reader spot checks with NVDA, JAWS, or VoiceOver.
Recent ADA updates and developments every public entity should track
This topic extends beyond archived content. Recent ADA updates and developments include the DOJ’s final Title II web accessibility rule, growing scrutiny of mobile apps, stronger expectations for digital procurement, and increasing recognition that decentralized publishing is a governance problem as much as a technical one. Public entities should also watch how courts and enforcement agencies evaluate alternative access claims. A phone number alone is rarely an adequate substitute for accessible digital access, especially when online information is available twenty-four hours a day and used for time-sensitive decisions. Operational equivalence matters.
Another major development is the shift from project-based remediation to lifecycle governance. Organizations that improve accessibility sustainably set publishing standards, train content authors, require accessible templates, embed checks in procurement contracts, and monitor compliance continuously. They also define retention schedules with records officers and legal counsel so outdated files do not linger indefinitely. This hub article connects those issues because archived content management intersects with every one of them. If procurement ignores accessible document workflows, old PDFs continue accumulating. If training is weak, departments upload scanned flyers. If retention is unclear, obsolete documents stay public and create avoidable risk. Accessibility maturity depends on these connected practices, not on one-time cleanup campaigns.
How to balance compliance, records retention, and public access
The hardest part of implementation is balancing three legitimate duties: accessibility compliance, records retention, and public transparency. These goals can conflict if handled casually, but they can work together with a clear policy. Records laws may require retention without requiring prominent public posting in active site areas. Transparency may justify preserving historical reports while still separating them from current service information. Accessibility rules may permit archival exceptions while still requiring effective processes for accessible copies on request. The answer is governance, not guesswork.
Start by coordinating legal, records, IT, communications, and program teams. Define what must remain on the public site, what can move to archival repositories, and what can be deleted under retention schedules. Create a standard archive label and dedicated archive landing pages. Remove archive files from active navigation where possible, and replace outdated links with current accessible resources. Most important, publish a clear accessibility assistance channel and test it. Submit a request as a mystery shopper, track response time, and verify that the delivered alternative format is actually usable. That final step is where many policies fail in practice.
What organizations should do next
The new DOJ exception rules do not give public entities a free pass on old digital content. They create a narrow, useful path for truly archived materials while making it clear that current services, programs, and civic participation must remain accessible. For most organizations, the immediate priorities are straightforward: inventory legacy files, classify them accurately, delete what no longer belongs online, remediate active documents, and move genuine historical records into a clearly defined archive structure. Old PDFs deserve special attention because they are often the single largest source of access barriers and enforcement risk.
As a hub for recent ADA updates and developments, this article points to the central lesson I have seen across audits and remediation programs: accessibility improves fastest when teams stop treating legacy content as a vague backlog and start managing it as a governed portfolio. The benefit is not just lower legal exposure. People can find information, complete tasks, understand rights, and participate in public life without extra friction. Review your archived content policy, document exception criteria, and build a remediation roadmap now. The agencies that act early will spend less, serve better, and be far more prepared for the next wave of accessibility enforcement.
Frequently Asked Questions
What do the new DOJ exception rules generally say about archived content and old PDFs?
The new DOJ framework has made one point much clearer for public entities: not everything that still exists on a website is treated the same way under modern accessibility expectations. The rules recognize that some older digital materials may qualify for an exception when they are genuinely archived and no longer used to provide current programs, services, or activities. In practical terms, that means an agency, school, county, transit provider, or special district may not have to fully remediate every historical PDF, legacy report, meeting packet, or outdated web page that remains online solely for reference, research, or recordkeeping purposes.
That said, the exception is not a blanket pass for anything old. The key issue is function, not age alone. A document does not become exempt merely because it was posted years ago or moved into an “archive” folder. If people still need that content to apply for services, understand current policies, access benefits, comply with requirements, participate in programs, or interact with the entity in a meaningful way, accessibility obligations are much more likely to apply. The DOJ’s approach pushes organizations to look carefully at whether older content is truly inactive or whether it still serves an operational purpose.
Old PDFs are especially important in this discussion because many public entities have large collections of scanned documents, agendas, reports, forms, and notices that were created before current accessibility practices became standard. The rules do not suggest that every such file can remain inaccessible without review. Instead, they require a more disciplined classification process: determine what is active, what is archived, what remains necessary for public access, and what can be removed, remediated, replaced, or made available through an accessible alternative process when appropriate.
The safest interpretation is this: if legacy content still matters to the public today, it should be treated as part of today’s accessibility responsibilities. If it is truly archival, segregated as such, and not needed for ongoing public interaction, it may fall within an exception. The challenge for most organizations is proving that distinction through policy, website structure, content governance, and consistent decision-making.
How can a public entity tell whether content is truly “archived” or still active?
This is one of the most important compliance questions because the label “archived” by itself is not enough. To determine whether content is truly archived, a public entity should ask whether the material exists only for historical, reference, or record-retention purposes, or whether members of the public still rely on it to obtain services, understand rules, complete transactions, or participate in current government operations. If the answer is yes to any of those functional uses, the content is likely still active, even if it is old.
For example, an annual report from ten years ago that is posted for transparency and historical reference may be a strong candidate for archived status. By contrast, an old PDF handbook that staff still direct people to, a past policy document that still describes current procedures, or a prior form that residents continue to download and submit is not functionally archived. The same is true for old board agendas or notices that remain the only place the public can find relevant decisions, deadlines, route changes, zoning history, or compliance information needed today.
Website placement and presentation also matter. If content is integrated into current navigation, surfaced in public-facing service pages, linked from current instructions, or returned prominently in site search without any archival context, it may be difficult to argue that it is truly inactive. Archived content should usually be clearly separated from live operational content, labeled in a way that signals historical status, and kept out of workflows tied to current services wherever possible.
A strong internal review process often includes a content inventory, departmental interviews, usage analysis, and legal or records-management input. Public entities should identify who owns the content, why it is still online, whether it supports any current program, and whether there is an accessible newer version or substitute. This kind of documentation is valuable not only for compliance, but also for operational clarity. In many cases, organizations discover that large amounts of “archived” material are still performing active work simply because no one has updated or replaced them.
Ultimately, archived status depends on real-world use. If the public still needs it, references it, depends on it, or is directed to it, the content is probably not archived in the sense the DOJ exception contemplates.
Do old PDFs have to be remediated if they are no longer tied to active services or programs?
Not always, but public entities should be very careful before deciding that remediation is unnecessary. If an old PDF is truly legacy material kept only for archival, historical, or recordkeeping purposes, and it is not used to support current services, programs, or activities, it may fall within an exception under the newer DOJ approach. That means the entity may not need to retrofit the file to meet current technical accessibility standards in the same way it would for active web content.
However, this conclusion depends on several facts, and each one matters. First, the PDF must genuinely be inactive. If it contains instructions, policies, applications, maps, schedules, notices, or guidance that people still use, it should not be treated as exempt simply because it is old. Second, the file should not be the only practical way for the public to access important information. If no accessible alternative exists and the information still affects current participation or decision-making, leaving the PDF inaccessible creates risk. Third, the organization should ensure that archived files are not being promoted as current materials through navigation menus, staff communications, search results, or service pages.
There is also a difference between what may technically fall within an exception and what may still be smart governance. In some cases, remediation is the better choice even for older PDFs, especially where the document has recurring public value, high traffic, legal significance, or reputational importance. In other cases, replacing the PDF with an accessible HTML page, summary, or updated document may be more efficient than remediating a complex scanned file. And sometimes removal is the best option if the document no longer serves a meaningful purpose online.
Public entities should also remember that exceptions do not eliminate the need to provide access when requested. Even if an archived PDF is not part of the active web accessibility remediation scope, an organization may still need a process to respond if a person with a disability requests the information in an accessible format. That is why many entities are pairing archival review with policies for alternate format requests, response timelines, and staff escalation procedures.
In short, some old PDFs may not need immediate remediation under the exception rules, but that decision should come after a structured analysis, not a simple assumption based on age.
What are the biggest mistakes agencies and schools make when applying the archived content exception?
The most common mistake is assuming that “old” means “exempt.” Age alone does not determine whether accessibility standards apply. A PDF from 2016 can still be active if it contains the current application process, fee schedule, transportation rules, special education guidance, or procurement requirements. When organizations apply the exception based only on publication date, they risk leaving important public-facing content inaccessible while believing they are compliant.
Another major mistake is relabeling content as archived without changing how it is actually used. Some entities move files into a folder called “archive” but continue linking to those same materials from current pages, staff emails, online forms, or service instructions. Others retain old documents in search results with no context, causing the public to rely on them as if they were current. If content remains functionally part of the user journey, a technical archive label offers very little protection.
A third mistake is failing to inventory content across departments. Accessibility decisions are often made centrally, while content is owned locally by HR, transportation, the clerk’s office, planning, procurement, student services, communications, or outside vendors. Without cross-functional review, organizations may miss the fact that supposedly inactive records are still heavily used by residents, applicants, employees, parents, contractors, or students. This creates both compliance and service-delivery problems.
Public entities also get into trouble when they focus only on PDFs and forget that archived content can include old webpages, image-based notices, historical calendars, meeting materials, and embedded documents in third-party platforms. The exception analysis should apply to the content ecosystem as a whole, not just one file type. In the same way, some organizations overlook the need for a request pathway for accessible versions of archived materials. Even where an exception may apply, failing to help users obtain information when needed can undermine the broader accessibility program.
Finally, one of the most avoidable mistakes is poor documentation. If an entity decides certain material qualifies as archived, it should be able to explain why: who reviewed it, whether it supports any active service, how it is presented online, what accessible alternatives exist, and what policy governs archival decisions. Clear documentation turns a subjective judgment into a defensible process. Without it, the exception can look less like a reasoned compliance strategy and more like a shortcut.
What is the best practical strategy for managing legacy web content under the new DOJ rules?
The best strategy is to combine legal interpretation, accessibility review, and content governance into one repeatable workflow. Start with a full inventory of older digital content, including PDFs, Word files, scanned images, meeting archives, reports, policy manuals,
