Your agency has a real deadline now. Not a guideline, not a best practice, not a "should probably get to this" — a date, published in the Federal Register, with your jurisdiction's population size deciding which one applies to you.
Under DOJ's Interim Final Rule (Federal Register 2026-07663), state and local government entities serving 50,000 people or more must reach WCAG 2.1 AA conformance by April 26, 2027. Smaller entities and special districts have until April 26, 2028. That gap — one year — sounds like breathing room. It isn't, unless it's spent on something more structured than the same accessibility item sitting at the bottom of an IT backlog, quietly rolling over from one quarter's planning meeting to the next.
The agencies that hit their deadline calmly are the ones that turned the date into a sequence of phases now, while there's still time for each phase to actually happen. The agencies that don't are the ones still treating it as a single, undifferentiated task called "fix accessibility" — which is not a task anyone can start, schedule, or finish.
What the Deadline Actually Requires
The rule is specific about the standard: WCAG 2.1 Level AA, evaluated across your public-facing digital services. It is not specific about how you get there, which is exactly where most agencies stall. Auditors and internal compliance teams have historically had to invent their own evaluation process, borrow one from a vendor, or apply an older methodology that was written for websites at a time when "your digital footprint" meant a website and not much else.
That gap has narrowed. The W3C published WCAG-EM 2.0 as a Group Note on July 23, 2026 — an updated, official methodology for structuring conformance evaluations. Critically, it extends beyond websites to cover apps and other digital products, which matters enormously for government agencies whose real digital footprint includes permit portals, benefits applications, mobile apps, kiosks, and PDF-heavy document libraries alongside the main website. If your evaluation plan only accounts for your homepage and a few landing pages, it isn't accounting for what the rule actually covers.
The Stat: State and local government entities serving a population of 50,000 or more must reach WCAG 2.1 AA conformance by April 26, 2027, while smaller entities and special districts have until April 26, 2028. (Source: DOJ Interim Final Rule, Federal Register 2026-07663)
A Real Roadmap, Not a Countdown
A deadline by itself is not a plan — it's a boundary. The plan is what fills the space between now and that boundary, and for a government agency it breaks into five phases that have to happen in order, because each one depends on the output of the last.
Phase 1: Full Digital Inventory
Before anything can be audited, it has to be listed. This is the step agencies most often shortcut, and the one that causes the most painful surprises later, because the inventory is rarely just "the website." It includes every subdomain, every microsite spun up by an individual department, every mobile app, every third-party portal used for permits, payments, benefits, or public records requests, and every PDF library that constituents actually use. If it's public-facing and digital, it's in scope, and it needs to be on a list before you can plan around it.
Phase 2: Baseline Conformance Audit
This is where WCAG-EM 2.0 does its job. Structuring the audit against a published, official W3C methodology — rather than an internal checklist improvised by whoever drew the short straw — means the result is defensible, comparable across departments, and, importantly, extends properly to apps and digital products rather than stopping at the website. The output of this phase is a documented baseline: exactly which WCAG 2.1 AA success criteria are failing, where, and how consistently.
Phase 3: Prioritized Remediation
No agency remediates everything at once, and no agency should try to. The baseline audit should produce a prioritized list, with the barriers that block entire tasks — a form that can't be submitted with a keyboard, an application that can't be completed with a screen reader — addressed before cosmetic contrast issues on a rarely visited page. Fixing the highest-impact barriers first is what makes the difference between a remediation phase that improves real access for real constituents and one that just burns down a checklist in an arbitrary order.
Phase 4: Verification Re-Testing
Remediation isn't done when a developer says it's done. It's done when it's re-tested against the same structured methodology used for the baseline audit, confirming the fix actually resolved the barrier without introducing a new one elsewhere. Skipping this phase is how agencies arrive at their deadline believing they're compliant and discovering otherwise only after a complaint or an audit proves them wrong.
Phase 5: Published Conformance Documentation
The rule doesn't just ask you to be accessible — it expects you to be able to demonstrate it. Published conformance documentation, produced from the audit and re-test data your team has already generated, is the artifact that turns "we worked on this" into a defensible record.
| Phase | Focus | Primary Output |
|---|---|---|
| 1. Digital Inventory | Catalog every public-facing site, app, portal, and document library in scope | Complete inventory of in-scope digital properties |
| 2. Baseline Audit | Structured conformance evaluation against WCAG 2.1 AA, per WCAG-EM 2.0 | Documented baseline conformance report |
| 3. Prioritized Remediation | Fix the highest-impact barriers first, across the full inventory | Remediated pages, apps, and documents, tracked by priority |
| 4. Verification Re-Testing | Re-audit remediated properties against the same WCAG-EM 2.0 structure | Confirmed conformance status |
| 5. Conformance Documentation | Publish results ahead of the April 2027 or 2028 deadline | Published conformance report / accessibility statement |
Why the Order Matters More Than the Speed
It's tempting to treat this as a race — start remediating tomorrow, worry about documentation later. That ordering fails for a specific reason: without a baseline audit structured against a consistent methodology, remediation has no way to prioritize itself. Teams end up fixing whatever's easiest or most visible rather than what actually blocks the most constituents, and by the time re-testing happens, there's no clean baseline left to compare against. Working backward from the real deadline — inventory, then baseline audit, then remediation, then verification, then documentation — is the only sequence where each phase actually produces what the next one needs.
The Scale of What's at Stake
This isn't an edge-case compliance exercise. Roughly 1 in 4 US adults has a disability, according to the CDC, which means a meaningful share of every agency's constituents interact with government digital services through assistive technology, screen readers, or accommodations that depend on the underlying page or app being built correctly. Color contrast alone matters to more people than most planning documents assume: the WHO estimates that around 8.3% of men and 0.5% of women have some form of color vision deficiency, which is why relying on color alone to convey status — an error in red text with no icon or label, for instance — routinely fails a large slice of the public.
And the baseline most public-facing digital properties start from is not good. The WebAIM Million analysis found that roughly 95.9% of home pages have detectable WCAG 2 failures. Agencies aren't unusual in starting from a flawed baseline — nearly everyone does. What separates agencies that hit their deadline from agencies that don't is whether that starting point gets measured now, against a real methodology, or discovered later, against a real complaint.
Start the Clock Now, Not in Month Eleven
April 26, 2027 and April 26, 2028 are fixed points. Everything useful happens in the phases between now and then, and every phase — inventory, baseline audit, remediation, verification, documentation — takes real calendar time that doesn't compress well under pressure. The agencies that treat this as a five-phase project starting today are the ones that reach their deadline with a defensible, documented record. The agencies that treat it as a future problem are the ones still auditing when the deadline arrives.
If your agency doesn't yet have a structured baseline against WCAG-EM 2.0, that's the place to start. Get a full accessibility audit from WCAG.World and turn your deadline into a working roadmap instead of a date you're hoping to be ready for.