GovTech publishes 9-step walkthrough of DOJ accessibility ruling

GovTech this week published 9 Steps to Navigate the DOJ Accessibility Ruling, a step-by-step framework aimed at the state and local agencies now racing to meet the Department of Justice's digital-accessibility deadline. The piece lands roughly 21 months after DOJ finalized the Title II web rule on April 24, 2024, and just under a year before the April 24, 2026 compliance date that catches roughly 91,000 government entities in its scope.

What is the DOJ actually requiring?

The Title II rule, signed by Attorney General Merrick Garland in the final weeks of the Biden administration, extends the Americans with Disabilities Act of 1990 to the web. It requires state and local government digital content to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA — the same benchmark long enforced in litigation against private firms. DOJ estimated in its rulemaking notice that compliance would cost covered entities roughly $6.8 billion in the first year and about $1.7 billion annually thereafter; industry groups pushed back, and the eventual deadline was pushed from April 2025 to April 2026 to absorb the load.

A framework pitched as nine steps implicitly accepts that WCAG 2.1 AA is not one task but a stack of obligations — perceivable, operable, understandable, robust across 4 principles and roughly 50 success criteria. A clean enumeration gives editors a checklist. It also risks turning compliance into a paperwork exercise that misses the underlying user.

Why count the steps at nine?

The newsroom did not publish a methodology note alongside the guide. Readers should assume the count reflects an editorial decision about granularity rather than a regulatory carve-up. DOJ's own rule does not itemize nine obligations. WCAG 2.1 does not itemize nine obligations. That is worth flagging because procurement officers tend to copy list structures into RFPs, and list structures make poor test plans.

What does the guide probably cover?

GovTech's audience skews toward CIOs, digital-services directors, and records officers inside city halls and state agencies — the exact buyers who must translate WCAG 2.1 AA into vendor contracts by next April. A nine-step format in that context typically walks readers from audit through remediation through attestable sign-off. The publication has not released a table of contents as of writing, so treat any third-party recap with suspicion.

What does the ruling actually change for users?

For the 1 in 4 U.S. adults who live with a disability, the rule formalizes a right that courts had been spelling out case by case. Success Criterion 1.4.3 (Contrast Minimum) means a benefits portal can no longer ship with a 3.5-to-1 contrast ratio on body text. Success Criterion 2.1.1 (Keyboard) means a permit-renewal flow can no longer trap a screen-reader user behind a custom slider. Success Criterion 3.3.1 (Error Identification) means a court-date lookup can no longer fail silently when a ZIP code has five digits instead of nine. Those are the measurable user outcomes — not the existence of a nine-step list on a vendor blog.

What's missing from the framing?

The DOJ rule covers web, but it does not stand alone. Section 508 of the Rehabilitation Act already binds federal agencies. State laws — including California's Unruh Act and the New York State Human Rights Law — create parallel exposure that WCAG 2.1 AA does not extinguish. A guide that names only the federal rule underplays how many front doors a plaintiff can knock on. Watch for that gap if the published steps never mention private litigation or state-level analogues.

The compliance clock now reads roughly 350 days. By then, expect a second wave of guides, this time from the law firms that will bill hourly to litigate what the checklists miss.