Five forces are reshaping government document management right now: accessibility rules that cover PDFs and forms as well as web pages, a compliance deadline that moved in April 2026, new federal guidance on when an AI prompt becomes a record, public records requests at a documented all-time high, and an electronic records transition that passed its deadline unfinished.
Most writing about the future of government document management is a list of adjectives. This is not that. Every item below is anchored to a rule with a date on it, a federal report published in the last nine months, or a dataset an agency put its own name to. Where a widely repeated claim turns out not to be true, we say so, because two of the most repeated claims in this space are wrong.
Start with the one that catches almost everyone.
The Accessibility Deadline Everyone Is Quoting Has Moved
The Department of Justice extended the ADA Title II web and document accessibility compliance date on 20 April 2026, four days before it would have taken effect. Entities with populations of 50,000 or more now have until 26 April 2027. Smaller entities and special districts have until 26 April 2028.
If your compliance plan says 24 April 2026, it is working from a superseded date. The interim final rule published at 91 FR 20902 moved both tiers by one year, and it took effect the day it published. Practically every article, vendor page and law firm briefing written before that date still quotes the old deadline.
The reason DOJ gave is worth reading in the original, because it is unusually candid for a regulator. The department wrote that it found the compliance concerns raised to be compelling and, on its own review, determined that it had overestimated the capabilities, whether staffing or technology, of covered entities to comply in the time frames provided. That is not a policy reversal. It is a capacity finding.
Twenty-one days later, the Department of Health and Human Services did the same thing to its parallel rule under Section 504, which binds any recipient of HHS financial assistance. That sweeps in state Medicaid agencies, public health departments, child welfare and human services. The HHS extension moved recipients with fifteen or more employees to 11 May 2027, and smaller recipients to 10 May 2028.
Note the thresholds are different. DOJ counts population, HHS counts employees. A county government can be a small entity under one rule and a large one under the other at the same time, which is a real trap for anyone running a single compliance calendar.
Two things have not changed. The regulation itself has been legally effective since 24 June 2024; only the compliance dates moved. And DOJ said plainly in the same document that no matter the deadline, the rule’s substantive requirements bind covered entities. Title II also carries a private right of action, with attorney fee recovery available to prevailing parties, so the deadline is the point at which the obligation becomes easy to enforce, not the point at which it begins.
Accessibility Is a Records Management Problem, Not a Web Problem
The rule defines PDFs, word processor files, presentations and spreadsheets as web content. And the exception for archived material only applies to content that is retained exclusively for reference, is not altered after archiving, and sits in a dedicated area clearly identified as archived. An agency without records discipline cannot claim it.
Here’s the part that surprises people the first time they read the actual text. Accessibility landed in most agencies as a web team problem, which is how it gets scoped, staffed and budgeted. But 28 CFR 35.104 defines conventional electronic documents as portable document formats, word processor formats, presentation formats and spreadsheet formats, and then folds them into the definition of web content. Every permit application, every board packet, every published inspection report is in scope. The web team does not own those. Program teams and records staff do.
The archived content exception is where this becomes an argument about records management rather than remediation budgets. To qualify, content has to meet four conditions: it was created before the compliance date or reproduces older paper, it is retained exclusively for reference, research or recordkeeping, it is not altered or updated after archiving, and it is organized and stored in a dedicated area clearly identified as being archived.
Read that fourth condition again. An agency with forty thousand legacy PDFs scattered across a public site cannot claim the exception, because nothing about that arrangement is a dedicated, clearly identified archive. An agency that has actually done the work, separated active from inactive, applied a retention schedule and put the inactive material behind a labeled boundary, can. The exception rewards records discipline specifically. That is unusual in a civil rights rule and it is the single most useful thing in the regulation for anyone planning a document program.
There is a related trap in the other exception. Individualized documents that are about a specific person, their property or their account are excepted only if they are password protected or otherwise secured. Case files sitting behind a login are out of scope. The same case files published to a public portal are not.
Federal Guidance Now Defines When an AI Prompt Becomes a Record
The National Archives issued guidance on 21 August 2026 explaining how the Federal Records Act applies to AI materials. Using an AI platform does not by itself create a record. What creates a record is capturing the prompt or output in an agency system and using it for official business.
This is a week old at the time of writing and it is the clearest official statement yet on a question every records officer has been asked. NARA AC 11.2026 and the guidance it transmits set out the tests directly. Prompts are records when they are captured and saved within an agency system and either circulated to other employees or used for official purposes beyond personal convenience. Outputs are records when captured, saved and used for official business, and the applicable schedule is whatever schedule already applies to that output.
The subtle one is audit trails. NARA is explicit that mere retention of an audit trail inside the AI system does not make it a federal record, but that it becomes one if the agency decides to capture it and use it, for example to conduct an investigation. Copies of agency records used to train a model, and algorithms or code written by or for the agency, are also records.
Two cautions before anyone builds policy on this. The guidance binds federal agencies under the Federal Records Act, not state and local ones. And NARA scoped it deliberately: the memo says it addresses records management requirements only and does not establish policy on AI governance, e-discovery, privacy, security or ethical use.
At state level the position is thinner than the noise suggests. There is no enacted state statute we could find that creates a distinct retention category for AI prompts or outputs. What exists is state archives guidance applying existing public records law, and the clearest is Washington’s, which answers the question with a flat yes: if a generative AI interaction relates to public business it is a public record, and it makes no difference whether the employee used a personal account or an agency one. Separately, Texas now requires a government agency to disclose to a person that they are interacting with an AI system, under a statute effective 1 January 2026, but that is a disclosure duty, not a retention duty. If you see a claim that states are passing AI records retention laws, it is not supported.
Public Records Demand Is at a Documented Record High
The federal government received 1,707,197 FOIA requests in fiscal 2025, a 13.7 percent increase and the fifth consecutive annual rise. Administrative appeals rose 59.38 percent in a single year, which is the sharper signal, because appeals are what happens when the first response does not satisfy.
The Department of Justice summary of fiscal 2025 annual FOIA reports, published 2 July 2026, records both a request record and a processing record: 1,707,197 received and 1,635,055 processed. Agencies are broadly keeping pace on volume. The appeals figure is the one that should worry an operations lead: 32,059 administrative appeals, 59.38 percent above the prior year. That is a quality and completeness signal, not a throughput one.
Federal numbers are a proxy for a state and local reality that is much less consistently measured, but Washington publishes a genuine equivalent. Its 2024 public records reporting, released in December 2025 by the legislature’s audit committee, found agencies received 483,861 requests and estimated spending more than $127 million and 1.7 million staff hours responding to them. Around 57 percent of requests closed within five days; the average from receipt to closure was 24 days.
Treat that as scale rather than trend. The committee notes that different agencies report each year, so annual results may not be comparable. But 1.7 million staff hours in one state, on one function, is the number to put in front of a finance director who thinks records management is an administrative overhead rather than a service line.
The Electronic Records Transition Passed Its Deadline Unfinished
The federal deadline to manage all permanent records electronically hit on 30 June 2024. By NARA’s own December 2025 assessment, 71 percent of agencies met it, at least 75 had filed exception requests, and 47 percent of agencies that said they had an approved schedule for other electronic messages were wrong about it.
Before the numbers, correct a claim you will see constantly: NARA did not stop accepting paper in 2024. What M-23-07 actually says is that after 30 June 2024 NARA will no longer accept new transfers of analog records unless it has granted a limited exception, that it will continue to store and service analog records transferred before that date until their disposition, and that when those reach disposition it will accession the permanent ones in their original analog format. Exceptions are available where digitization would burden the public, where cost exceeds benefit, where statute or regulation blocks it, or where the original has exceptional intrinsic value. Paper was gated, not ended. A records officer will notice immediately if you get this wrong.
NARA’s 2024 annual records management report, published 17 December 2025, is the agency grading itself in public. Seventy-one percent of agencies said they met the deadline. Eighteen, or 12 percent, missed it with no exception request in place. At least 75 agencies and offices had filed for an exception by publication.
Two findings in that report matter more than the headline compliance rate. Only 29 percent of agencies said their records management staff actively participate in ensuring that systems development, maintenance and operations include electronic records management processes. And of the agencies that said they had an approved general records schedule, GRS 6.1, for other electronic messages, validation found 47 percent had answered incorrectly. Nearly half did not accurately know their own retention position.
That is the honest state of the transition, and it is the useful one. The deadline did not fail because agencies lacked intent. It slipped because records management sat outside the systems work, which is exactly the pattern the accessibility rules are now about to repeat.
What This Adds Up To for the Next Two Years
Two federal departments independently concluded in the spring of 2026 that the regulated community could not do this work on schedule. The extensions bought roughly a year. The organizations that use it well will spend it on the records layer underneath, because every one of these obligations resolves to knowing what documents you hold, which are active, and where they live.
State CIOs are already pointing the same direction. In their ranking of priorities for 2026, artificial intelligence sits at number one and accessibility at number six, with the accessibility entry naming DOJ compliance explicitly. Both of the pressures described above were on that list before either federal deadline moved.
This is where government digital transformation stops being a slogan and becomes a work order. The practical sequence is not complicated, and it is the same sequence for all five forces. Inventory what you actually publish and hold. Separate active from inactive and put the inactive behind a real, labeled archive boundary, which is what the accessibility exception requires and what a retention schedule requires anyway. Decide which document types are individualized and secured, because those are treated differently. Then build remediation and AI policy on top of that inventory rather than beside it.
The agencies that will struggle in April 2027 are not the ones with the worst PDFs. They are the ones that still cannot answer, in a week, what documents they publish and which of them are still in use.
Frequently Asked Questions
When do state and local governments have to meet the ADA web accessibility requirements?
The Department of Justice extended both compliance dates by one year in an interim final rule published on 20 April 2026. Public entities with a total population of 50,000 or more now have until 26 April 2027. Entities under 50,000, and any special district government, have until 26 April 2028. The underlying regulation has been legally effective since 24 June 2024, and DOJ stated that the substantive requirements bind covered entities regardless of the deadline.
Do accessibility rules apply to PDFs and other documents, or only to web pages?
They apply to documents. The regulation defines conventional electronic documents as portable document formats, word processor formats, presentation formats and spreadsheet formats, and treats them as web content subject to the WCAG 2.1 Level A and AA standard. There are exceptions, including one for archived content and one for individualized documents that are password protected or otherwise secured, but there is no general carve out for documents as a category.
Is an AI prompt a government record?
Under federal guidance issued on 21 August 2026, using an AI platform does not by itself create a record. A prompt becomes a federal record when it is captured and saved in an agency system and is either circulated to other employees or used for official purposes beyond personal convenience. Outputs become records when captured, saved and used for official business, retained under whatever schedule already applies to that output. State positions vary; Washington treats any generative AI interaction relating to public business as a public record regardless of whether a personal or agency account was used.
Did the National Archives stop accepting paper records in 2024?
No, though the claim is common. Federal policy stopped new transfers of analog records after 30 June 2024 unless the National Archives grants a limited exception, on grounds such as burden to the public, cost exceeding benefit, statutory barriers, or exceptional intrinsic value in the original. Analog records transferred before that date continue to be stored and serviced, and permanent ones are still accessioned in their original analog format when they reach disposition.
How many public records requests do governments actually receive?
The federal government received 1,707,197 Freedom of Information Act requests in fiscal year 2025, a 13.7 percent increase and the fifth consecutive annual rise, with administrative appeals up 59.38 percent year over year. At state level, Washington’s legislative audit committee reported that agencies there received 483,861 requests in 2024 and estimated spending more than $127 million and 1.7 million staff hours responding to them.
Build the Layer Underneath
Every obligation above resolves to the same foundation: an inventory of what you hold, a working distinction between active and inactive, and retention rules the system enforces rather than a policy document describes. That is what government document management has to mean over the next two years. VisualVault gives state and local agencies that layer as configurable software rather than a project, across case management, licensing and permitting, and compliance programs, with process automation that program teams build and change themselves. See the public sector platform, or request a demo and we will walk it through against a program you actually run.