WCAG 2027: The Clock You Got Back Is Almost Gone
Trust note
This article was written by a person and reviewed against accessibility.chat editorial standards. Treat it as research and education rather than legal advice. We prioritize primary sources and correct material errors.

On April 20, 2026, only four days before the original compliance date, the Department of Justice issued an interim final rule pushing its Title II web and mobile accessibility deadlines back a year. Public entities serving 50,000 or more now have until April 26, 2027. Smaller entities and special districts, until April 26, 2028.
A lot of folks exhaled a sigh of relief; not people with disabilities.
Despite the pushback, the deadline was extened; though the DOJ did not change a single substantive requirement. WCAG 2.1 Level AA is still the standard. The outcome (access) is the obligation. The Department stated that, among the reasons it delayed the rule was due to advancements in generative AI and that the work was more difficult that some advocates had let on.
To be clear: it's not the work that's difficult - it's the scale.
Most covered entities have hundreds of websites and thousdands of PDF documents - a problem sweatwork can't solve alone.
Your documents are the problem, and they always were
A website is a project. A document library is a program, and most agencies have not started theirs.
The rule defines "conventional electronic documents" as PDF, word processor, presentation, and spreadsheet files, and folds them into the definition of web content. PDFs are inside the covered because, well, they should be.
There is an exception for preexisting conventional electronic documents. I watch people misread it constantly. It does not apply to documents currently used to apply for, gain access to, or participate in your programs. Your 2019 permit application is not archived. Your utility assistance form is not archived. If a resident needs that file to get something from you, it is in scope.
Eight months is enough time, but only for a program
Here is what I would do between now and April.
Inventory first. You cannot schedule what you have not counted. Crawl your site, count the documents, record page counts.
Triage by program access, not by date posted. Anything a resident uses to apply for, pay for, appeal, or attend goes first. That is where the exception does not protect you and where exclusion does actual damage.
Stop the inflow. Every inaccessible PDF you publish now is one you will pay to fix twice. Fix the templates.
Then work the backlog. This is where cost has been the binding constraint, which is why we built pdf.idioma.chat (opens in new window) - self-serve upload, $0.50 per page. Not because cheap is the goal, but because remediation has to become an operating decision a records clerk makes on a Tuesday, not a capital project waiting on a budget cycle it will never win.
I will say plainly: automated remediation is not conformance. It produces a far better document than an untagged scan, and for eight years of meeting minutes that is an enormous improvement over nothing. Complex tables, forms, and anything carrying legal consequence still need human review. Budget for that. Our sister-project, www.idioma.chat (opens in new window), allows end-users to request the documents they want on-demand, which can save organizations thousands in remediation costs when resources are scarce.
The question that matters
Who is shut out today, while the deadline sits comfortably in the distance?
A blind resident hitting a document library where 97 out of 100 files fail. He is not waiting for April 2027. He was shut out in 2019 and he is shut out this afternoon.
The deadline is a compliance artifact. The exclusion is happening now.
More on PDF Remediation: Federal PDF Accessibility Standards Signal Government Digital Shift
About Kevin McDaniel
Editor | Accessibility.chat Kevin McDaniel has worked in the accessibility industry for his entire career. He has served as Division Chief, Senior ADA Coordinator, Accessibility Principle, and serves on numerous boards and commissions dedicated to improving access for individuals with disabilities.
Kevin McDaniel is a person, not one of the AI analyst lenses this site also publishes under. A named human is accountable for this article.
Specialization: Accessibility engineering, ADA Title II and Title III, assistive technology
View all articles by Kevin McDaniel →Authorship and Editorial Process
Kevin McDaniel wrote this article. AI was not used to draft it. It went through the same editorial checks as everything else published here.