Blog
An Extension, Not an Exemption: Digital Accessibility and the Limits of AI in Document Remediation
Abstract
In April 2026 the United States Department of Justice (DOJ) extended the compliance dates of its Title II web accessibility rule under the Americans with Disabilities Act (ADA) by one year, and the Department of Health and Human Services (HHS) followed with a comparable extension under Section 504 of the Rehabilitation Act. This article examines what those extensions changed and, more importantly, what they did not. It considers the reasoning the DOJ gave for the delay, particularly its acknowledgment that artificial intelligence (AI) cannot yet automate the remediation of inaccessible content at scale; the position of conventional electronic documents under the rule; the technical reasons that Portable Document Format (PDF) remediation continues to require human expertise; and the continuing legal exposure of organizations in both the public and private sectors.
Introduction
When a regulator moves a deadline, organizations tend to hear permission to pause. The announcements of April and May 2026 were widely reported as a reprieve, and in many boardrooms the digital accessibility program that had been assembled through 2025 was quietly returned to the shelf.
This is a misreading, and an expensive one. The extensions altered two dates in a schedule. They did not alter the technical standard, the scope of covered content, or the underlying statutory duty. The Web Content Accessibility Guidelines (WCAG) 2.1, Level AA remain the benchmark. Documents remain within scope. The general obligation under the ADA, which has existed since 1990, had no deadline capable of being extended, and the DOJ said so in the rule itself: “Regardless of the compliance dates, covered entities have an ongoing obligation to ensure that their services, programs, and activities offered using web content and mobile apps are accessible to individuals with disabilities in accordance with their existing obligations under title II of the ADA.”
The more accurate description of what happened in 2026 is that no organization was excused, and every organization was given twelve additional months. Those months were granted because the work proved more manual and more demanding of resources than the federal government had assumed. That is not an argument for delay. It is the clearest argument available for beginning now, while the calendar still allows an orderly program of work rather than an emergency one.
In this article I will set out what the rules now require, why the DOJ moved the dates, why document remediation continues to resist automation, and what organizations in both sectors should expect from the litigation that follows.
The extended compliance dates
Two federal rules moved in the spring of 2026, and a third category of organization was never subject to a date at all.
Under the DOJ interim final rule published on April 20, 2026, public entities serving populations of 50,000 or more must now comply no later than April 26, 2027, rather than April 24, 2026. Public entities serving fewer than 50,000 people, together with special district governments, must comply no later than April 26, 2028, rather than April 26, 2027. In both cases the standard remains WCAG 2.1, Level AA. Population is taken from the 2020 Census, and a body with no census figure of its own, such as a city library, takes the population of the entity it belongs to.
The HHS Office for Civil Rights made a parallel adjustment under Section 504 of the Rehabilitation Act, in an HHS interim final rule issued on May 7, 2026 and published in the Federal Register on May 11. Recipients of federal financial assistance from HHS with fifteen or more employees must now comply by May 11, 2027, rather than May 11, 2026, and those with fewer than fifteen employees by May 10, 2028, rather than May 10, 2027. The two rules sort their covered organizations by different tests, and the distinction is easy to miss: Title II divides public entities by the population they serve, while Section 504 divides recipients by the number of people they employ. An organization can sit in the larger bracket under one rule and the smaller bracket under the other. The Department stated in its announcement that a significant number of recipients, among them community health centers and hospitals of all sizes, would not be able to meet the original deadlines, and that the change aligns the revised timing with the DOJ’s one-year extension under Title II. The two regimes remain distinct in their covered entities, legal authority, and exceptions; it is the timetable that has been brought into step. As in the Title II rule, the technical standard itself is unchanged, and recipients retain an ongoing obligation to make their programs and activities accessible irrespective of the compliance dates.
Private businesses operating places of public accommodation under Title III of the ADA were unaffected, because no technical standard was ever codified for them and no compliance date was ever set. Their obligation is already live, and has been for many years. The absence of a codified standard has not kept WCAG out of Title III practice, where courts and settlement agreements have drawn on it for more than a decade.
Three points are worth emphasizing. First, the Title II change was issued as an interim final rule, with a comment period that closed in June 2026, and the DOJ contemplates in the rule itself that it may issue a notice of proposed rulemaking reconsidering the substantive requirements. An interim measure is not a permanent one, and the possibility of reconsideration is not a promise of relaxation. Building a compliance program around the hope of a second extension is a poor strategy.
Second, the obligation follows the work to contractors, though not by the same route. Title II binds the public entity, and the entity remains answerable for web content and mobile apps delivered on its behalf by a supplier. In practice it meets that responsibility by passing the requirement down, and procurement teams are increasingly writing conformance requirements and remediation warranties into their agreements. Suppliers should expect to provide evidence rather than assurances.
Third, none of these dates displaces the general nondiscrimination duty that sits beneath them.
Why the DOJ moved the dates
The reasoning the DOJ set out for the extension is more instructive than the extension itself, because it describes the conditions organizations are actually working in.
The Department gave three reasons. It had overestimated the technological and staffing capabilities of covered entities. It had received submissions from higher education associations, school districts, and the Small Business Administration’s Office of Advocacy describing limited financial and staff resources, with one survey indicating that many school districts would need to hire in order to comply. And it judged that additional time would allow entities to concentrate on compliance itself rather than on assessing whether the fundamental alteration and undue burden defenses might apply to them.
The first of those reasons is the one that merits close attention. In the Department’s words, “Advanced technology, such as generative AI, does not yet reliably automate the remediation of inaccessible content at scale, and staff resources and availability continue to pose significant challenges.”
This is a federal regulator stating, in the Federal Register, what accessibility practitioners have been telling clients for several years. In reconsidering the timetable, the Department concluded that neither the available technology nor the staffing capacity of covered entities was sufficient for the original schedule, and the dates moved as a result. Any organization currently being offered a one-click remediation product should read that sentence before signing.
That finding cuts both ways. If AI cannot compress the work, the work has to be resourced. Of the twelve additional months granted, barely seven now remain before the first deadline of April 26, 2027, and those months are of value only to the organizations that spend them remediating. For those that spend them waiting, the extension will have achieved nothing except to move the crisis forward by a year.
Documents in scope
The phrase “web accessibility rule” invites organizations to picture a website. The Title II rule, however, names documents explicitly, and it is at this point that the scale of the task usually becomes apparent.
The rule uses the term conventional electronic documents, which it defines on ada.gov as word processing, presentation, PDF, and spreadsheet files. Such documents, where they form part of a covered entity’s web content or mobile app content, must meet WCAG 2.1, Level AA, subject to the exceptions set out below. This encompasses board packets, permit applications, tax forms, course syllabi and assigned readings, patient intake sheets, meeting minutes, benefit notices, and annual reports.
An exception exists for preexisting documents, and it is the most frequently misread provision in the rule. It applies to files in those four formats that were already published before the relevant compliance date. It ceases to apply where a document is, in the rule’s words, “currently being used to apply for, access, or participate in” a public entity’s services, programs, or activities.
The practical effect of that condition is considerable. A permit application published in 2019 is preexisting, but residents use it to apply for a permit, and it is therefore within scope. The same reasoning captures financial aid forms, enrollment packets, health plan summaries, and tax appeal notices. A document newly published after the compliance date cannot be preexisting at all, and republication or substantive revision will generally take a document outside the exception, though the line between routine maintenance and republication is a question of fact. The exception protects the dormant archive; it does not protect the forms through which an organization delivers its services.
This is where the substantial volume of work lies, and it is why document remediation is so often the item that surprises a budget. A mid-sized city or a single university department may hold tens of thousands of PDFs, and a hospital system’s patient-facing library can run to thousands of items across several languages. Few organizations hold a complete inventory at the outset, and in my experience the true figure is routinely a multiple of the first estimate.
An honest inventory is therefore the most valuable early step available, because it converts an unbounded anxiety into a countable list. Remediation programs that succeed begin there; those that fail have generally skipped it.
The limits of AI in document remediation
This is not an argument against automation. Automation is used daily in remediation work and it has made that work considerably faster. It is an argument about a specific limitation, and understanding that limitation is what protects an organization from procuring the wrong solution.
A PDF is fundamentally a description of marks on a page. It records that a particular character should be drawn at a particular point on the page, in a particular font and size. It does not natively record that a line of text is a second-level heading, that a grid of numbers is a data table with defined row headers, or that a given cell belongs to a given column. Accessibility depends largely on a second layer, the tag tree, which carries the structure and meaning that a screen reader announces to the user. Remediating a PDF means constructing that layer correctly, against WCAG 2.1, Level AA for the conformance obligation and against ISO 14289-1, known as PDF/UA-1, for the requirements specific to the file format.
Automation performs parts of this task well. It can detect the absence of tags, identify a missing document language or title, find untagged images, propose heading candidates, run conformance checks, and carry out mechanical repetition across large volumes of files. That contribution is real and organizations should take advantage of it.
What automation cannot do is determine meaning, and nearly every remaining decision in a remediation is a decision about meaning.
The principal areas in which human judgment remains necessary are these:
- Reading order: a two-column newsletter containing a pull quote and a sidebar has one correct narrative sequence, and it is the sequence the author intended. Layout analysis can only infer it, and where the inference is wrong a screen reader user receives a sentence from the first column followed by part of a caption.
- Heading structure: large bold text is not necessarily a heading, and a genuine heading is not necessarily large or bold. The hierarchy must reflect the logic of the document rather than its typography.
- Tables: correct markup requires knowing which cells are headers, what scope those headers govern, how merged cells are mapped, and whether a grid represents tabular data or is being used for layout. Complex financial tables and multi-level headers routinely defeat automated inference.
- Alternative text: this is the area in which generative AI appears most convincing and is most often quietly wrong. A model can describe the appearance of a chart. It cannot know why the author placed that chart in the document. “Bar chart with five blue bars” is a description; “emergency department wait times fell from 47 minutes to 31 minutes between 2022 and 2025” is the information a sighted reader receives. Only a person who understands the purpose of the document can supply the second, and confidently incorrect alternative text is worse than none, because no one is prompted to check it.
- Forms: field labels, tab order, indication of required fields, and error messaging must correspond to the task the user is actually completing.
- Scanned documents: optical character recognition produces text, not structure. A scanned planning document from 1998 requires reconstruction rather than repair.
There is a further trap here. A file can pass an automated checker and remain unusable. Checkers verify that tags exist and are well-formed; they cannot verify that the tags are correct. A document with a complete tag tree in the wrong reading order will pass the check and fail the reader.
The same reasoning applies to website accessibility overlays, which organizations would be well advised to avoid. A script injected at page load cannot determine what the content means either, however confident the marketing material may be. The DOJ has in effect reached the same conclusion, having moved a federal deadline by a year in part because the automation is not yet capable.
The defensible model is human-led and tool-assisted. Automation handles detection, triage, and mechanical repetition. Trained remediators make the structural and semantic decisions. A final pass includes testing with assistive technology rather than with a conformance checker alone.
Many organizations will need to supplement in-house capacity, whether through training, better processes, tools, or outside specialists. iAccessDigital has specialized in digital accessibility for many years, remediating PDF and EPUB content to WCAG 2.1, Level AA and to PDF/UA, and auditing websites and mobile applications against the same standard. Its clients include publishers, public sector bodies, educational institutions, translation and localization providers, and health insurance companies, including work under major contracts covering very large document libraries. Organizations facing a document backlog and a fixed deadline are welcome to get in touch.
The state of website accessibility
While the sector discussed deadlines, the accessibility of the web itself deteriorated.
The WebAIM Million study analyzes the home pages of the top one million websites each year. Its 2026 report detected WCAG failures on 95.9 percent of those pages, an increase from 94.8 percent in 2025, with an average of 56.1 errors per home page, which is 10.1 percent higher than the previous year. Pages also grew more complex: the average number of elements per home page rose 14.3 percent in a single year, to 1,437, and Accessible Rich Internet Applications (ARIA) attributes rose 27 percent.
The distribution of failures has remained largely unchanged across the eight years of the study. Low contrast text was detected on 83.9 percent of home pages, missing alternative text for images on 53.1 percent, missing form input labels on 51 percent, empty links on 46.3 percent, empty buttons on 30.6 percent, and a missing document language declaration on 13.5 percent. These six categories account for 96 percent of all errors detected. None of them is obscure, and each is preventable at the point of authoring, which indicates that the difficulty lies in process rather than in knowledge.
Two conclusions follow for any organization planning an audit.
The first is that an automated scan is a starting point and not an audit. The figures above represent machine-detectable barriers that WebAIM judges very likely to be WCAG conformance failures, and WebAIM is explicit that the absence of detected errors does not mean a page is accessible. The criteria a machine cannot evaluate, including whether the reading order is coherent, whether a keyboard user can complete a task, whether an error message conveys what has gone wrong, and whether alternative text carries the right information, lie outside the scan entirely. A credible audit combines automated coverage, manual expert review against WCAG 2.1, Level AA, keyboard-only testing, and testing with assistive technology across the organization’s genuine user journeys.
The second is that remediation without correction of the publishing pipeline buys no more than a year. Where a content management system ships low-contrast components and authors continue to publish untagged PDFs, the backlog rebuilds as quickly as it is cleared. Organizations that remain compliant embed accessibility in their design systems, component libraries, document templates, procurement requirements, and author training, so that subsequent content is accessible at the point of creation.
Legal and commercial exposure
A regulatory compliance date and legal exposure are distinct matters, and treating them as one is how organizations come to harm.
According to Seyfarth Shaw’s annual analysis of federal court dockets, website accessibility filings rose to 3,117 in 2025, an increase of 27 percent on the 2,452 filed in 2024, following two years of decline. Website cases now represent 36 percent of all federal filings under Title III of the ADA, against 28 percent the previous year, with New York and Florida accounting for the majority. These figures exclude state court actions and the considerably larger volume of demand letters that never reach a court docket.
None of that litigation was contingent on a DOJ rule, and none of it is suspended by an interim final rule concerning compliance dates.
For public entities the position is more pointed still. The extension defers the date on which the technical standard becomes enforceable through that particular rule. It does not defer the ADA. A resident who cannot complete a permit application has the same recourse under the statute today as before the rule was made. “We have until 2027” is a statement about a regulation; it is not a defense.
For recipients of HHS funding, Section 504 obligations run on their own track and attach to the federal financial assistance itself. Enforcement runs through complaint and investigation by the Office for Civil Rights, which will first seek a voluntary resolution agreement. Where voluntary compliance cannot be secured, OCR issues a letter of findings, and the steps that follow may include referral to the Department of Justice or proceedings to terminate federal financial assistance. For many organizations that prospect is more serious than a private lawsuit.
There is also a commercial dimension that seldom appears in the legal briefing. The Centers for Disease Control and Prevention reports that more than one in four adults in the United States, over 70 million people, had a disability in 2022. Procurement teams increasingly require an accessibility conformance report before they will sign. Organizations selling specified products and services into the European Union may also fall within the scope of the European Accessibility Act, which has applied since June 28, 2025 and is enforced through the law of each member state. Its scope is narrower than a general web accessibility statute, but for organizations that fall within it there has been no equivalent extension, and the stricter clock is already running.
The litigation ahead
Will the plaintiffs’ bar treat April 2027 as an opportunity? The evidence suggests that it will, and organizations are better served by understanding what is coming than by hoping it does not.
The practice is narrow and highly active. Seyfarth Shaw attributes part of the 2025 increase to new plaintiff attorneys entering the field and to the relative ease of filing these cases remotely. A practice area that is recruiting its own lawyers does not tend to contract when a new federal standard arrives.
Title II changes the calculus for public entities. Until now, a claim concerning an inaccessible government website had to be constructed from the general effective communication and program access obligations of the ADA, without a codified technical standard to measure against. From the compliance date, a specific, federally adopted benchmark applies. That should make technical conformance far easier to evaluate, and in my view it will produce a body of case law quickly. It does not dispose of the other questions a claim must survive, among them standing, sovereign immunity, remedies, and the particular facts of program access. State and local governments, school districts, and public universities should expect to encounter what private businesses have faced for more than a decade.
The DOJ has effectively said as much. In explaining the extension it warned that entities unable to meet the original dates “would face significant litigation risks,” and it noted that private litigants may pursue injunctive relief and attorney’s fees under the Title II private right of action. It also stated that, absent a further notice of proposed rulemaking and absent circumstances suggesting another delay, it “fully anticipates implementing the regulation at the new deadline.” The extension grants relief from a date. It does not grant immunity, and it does not suspend the obligations sitting beneath the rule.
It is tempting to dismiss all of this as opportunism, and that temptation should be resisted, for a reason more practical than fairness to the legal profession. The supply of valid claims is effectively unlimited, because 95.9 percent of home pages contain detectable failures. Filings concentrate among a small number of firms because the underlying defect is close to universal, not because the grievances are manufactured. Sustained and demonstrable accessibility will not guarantee that an organization never receives a demand letter, but it removes the substance on which a claim depends.
The lesson for both sectors is the same. Litigation exposure is not managed by a deadline, a disclaimer, or a script injected at page load. It is managed by being accessible. Organizations that arrive at the compliance dates in that condition will have little reason to care who is filing.
Conclusion
It is convenient to discuss this subject as a compliance problem, because compliance has dates and dates can be placed in a plan. The legislation, however, exists for a reason that has nothing to do with dates.
Someone is attempting to renew a license, enroll a child in school, understand a diagnosis, apply for assistance, or read an agenda before a meeting at which a decision affecting their neighborhood will be taken. Where the form is an untagged scan, that person cannot act independently. They must ask for help, and in doing so they must often disclose something private to a stranger in order to obtain a service that everyone else receives without a conversation.
That is the practical effect of an inaccessible PDF. It is not a technical defect but an exclusion, delivered quietly, to a person whose only distinguishing characteristic is that they need the same service as everyone else.
WCAG, the ADA, Section 504, PDF/UA, and the European Accessibility Act exist because organizations, left to their own devices, largely did not do this work. The standards establish a floor rather than an aspiration. An organization that treats them as a finishing line will produce content that conforms technically and still serves people poorly. An organization that understands why they exist will pass its audits almost incidentally.
The additional year should therefore be taken and used. It was granted honestly, for a genuine reason, and it is of real value. It should simply be understood for what it is: time in which to complete work that was always going to have to be done, carried out by people who know how to do it, for users who have already waited long enough.
The organizations that will be well placed in April 2027 are those that began in 2026. Accessibility is not simply a legal requirement to be satisfied; it is how an organization decides who it is prepared to serve.
This article provides general information on regulatory developments and does not constitute legal advice. Organizations should confirm their own compliance position with their counsel.