Standard
ADA Title II PDF deadlines: April 2027 and April 2028
What the rule requires of documents, which entities it covers, why the deadlines moved by a year, and what the regulator said about automation while moving them.
U.S. Department of Justice · technical standard: WCAG 2.1 Level AA
Dates that matter
What the rule says
The Department of Justice’s Title II web and mobile accessibility rule sets a single technical standard — WCAG 2.1 Level AA — and applies it to web content and mobile apps provided by state and local government entities.
Two compliance dates, both moved a year by the interim final rule of 20 April 2026:
- 26 April 2027 for public entities serving a population of 50,000 or more.
- 26 April 2028 for smaller entities and special district governments.
A PDF published on a covered entity’s website is web content. Meeting the standard means meeting WCAG 2.1 AA for that document.
The sentence worth reading twice
The Department’s stated reason for the extension was that it had overestimated the capabilities — whether staffing or technology — of covered entities.
That is the regulator putting on the record that this cannot be automated away. Every vendor selling one-click compliance is selling against the explicit finding of the agency that wrote the rule.
It is also why Taggart is positioned the way it is. The product’s promise is that it cuts a forty-minute remediation to eight and produces the audit trail — not that it makes the problem disappear.
What this means for a document backlog
If you are a covered entity with several thousand PDFs, the practical questions are:
How many actually need work? Most backlogs are less uniform than they feel. Run a validator across all of them and you typically find a third are fine, a third need mechanical fixes, and a third need real work. Knowing which is which is the difference between an achievable plan and a panic.
Which documents matter? Nothing in the rule prioritises for you, but the same triage applies as anywhere else: forms people must complete, documents required to access a service, and anything with a legal effect come first.
Who decides the judgement calls? Whoever it is, their decisions should be recorded. Not for the regulator’s sake — for the sake of the person who inherits the backlog in two years and needs to know why a particular table was accepted as-is.
What Taggart contributes
The free validator will tell you the state of the backlog at no cost, which is the number you need before you can plan anything. Its report is JSON, so triaging several thousand documents is a script rather than a project.
For the documents that need work, the remediation report records what was found, what was fixed, what was accepted with a justification, who decided each judgement call, when, the tool version, and the SHA-256 of both files.
What it will not do is tell you that you comply. That determination belongs to counsel, and any tool claiming to make it for you is creating a liability rather than removing one.
Frequently asked questions
Does this cover PDFs, or only web pages?
Both. The rule covers web content and mobile applications, and documents delivered through them are web content. A PDF on a county website is squarely in scope.
Why did the deadlines move?
The Department of Justice issued an interim final rule on 20 April 2026 extending both compliance dates by one year. Its stated reason was that it had overestimated the capabilities — staffing and technology — of covered entities. That is the regulator saying, on the record, that the tooling is not where people assumed it was.
What about archived content?
The rule includes exceptions, including one for archived web content meeting specific conditions, and one for individual documents posted by third parties. They are narrower than people hope. Read the actual text before relying on one.
Does a remediation report help if we are investigated?
It demonstrates a documented process: what was checked, what was fixed, what was accepted and on whose authority, and when. That is not a defence in itself, but 'we have no idea what state our documents are in' is a materially worse position than 'here is the record for every document we published'.
Related failure conditions
- 09-001 Tags are not in logical reading order The order of elements in the structure tree does not match the order a human would read the page. This is the single most common substantive defect in tagged PDFs and the one Acrobat's own tooling handles worst.
- 13-004 Figure tag alternative or replacement text missing A Figure element has neither /Alt nor /ActualText. Every Figure must have one or the other; if the image is decorative it should be an artifact instead of a Figure.
- 11-001 Natural language for text in page content cannot be determined No /Lang is in effect for some text: neither on the catalog, nor on an enclosing structure element, nor on a marked-content sequence.
- 28-005 A form field has neither a TU entry nor an alternative description The /TU tooltip is the accessible name of a PDF form field. Without it the field has no name at all — the visible label printed next to it is not connected to the control.
- 26-002 The 10th bit position of the P entry is false Bit 10 of the permissions flags is the "extract for accessibility" permission. Clearing it tells assistive technology it may not read the file.
Check your own file. Taggart's validator is free and unlimited — no page cap, no watermark, no account.
Primary source: https://www.ada.gov/resources/2024-03-08-web-rule/. This page is a working summary, not legal advice.
Last updated .