What the rule requires and what it covers
The DOJ's April 24, 2024 final rule (28 C.F.R. Part 35, Subpart H) adopted WCAG 2.1 Level AA as the enforceable technical standard for state and local government digital content. The coverage is broader than most agencies initially assumed. It includes every public-facing website, mobile application, and online document the agency makes available — PDFs, fillable forms, online permit portals, benefit applications, court e-filing systems, and meeting archives. It includes content made available through third-party systems when that system delivers the agency's programs and services. Procuring an inaccessible vendor portal does not transfer the compliance obligation to the vendor; it stays with the agency.
Exceptions exist but are narrow. Truly archived content that was never updated for current use, some genuinely third-party content entirely outside agency control, and content whose accessibility would require a fundamental alteration to a program may qualify. These exceptions do not cover most of a state agency's historical document library or a vendor-operated portal the agency uses for core service delivery.
The four WCAG 2.1 Level AA principles — perceivable, operable, understandable, robust — translate to practical requirements: text alternatives for images, captions for video, keyboard navigation without traps, sufficient color contrast, readable page structure, accessible form error handling, and valid code that works with screen readers and other assistive technologies. WCAG 2.1 Quick Reference, W3C
Why the extension happened — and what it signals
The 2026 Interim Final Rule (Docket CRT150, FR Doc 2026-07663, RIN 1190-AA82) cited several reasons for the delay: state and local resource constraints, staffing limitations, and slower-than-expected availability of technology tools. The DOJ noted specifically that generative AI-assisted remediation tools, which many entities had anticipated would accelerate their compliance work, had not developed as far as initially anticipated. Federal Register, April 20, 2026, 91 Fed. Reg. 20902
WCAG 2.1 Level AA remains the enforceable standard under the 2024 rule. WCAG 2.2, published by W3C in October 2023, adds several Level AA provisions not in 2.1 — including requirements for drag-and-drop alternatives (SC 2.5.7), minimum touch target sizing (SC 2.5.8), and keyboard focus visibility (SC 2.4.11). Agencies building compliance programs against WCAG 2.1 are well-positioned to absorb any future regulatory update to 2.2; the 2.1 foundation does not need to be rebuilt.
Disability rights organizations, including the American Council of the Blind, opposed the extension on the grounds that it delays equal access to public services for people with disabilities. The practical consequence is real: residents who rely on screen readers, switch access devices, or alternative input methods are navigating inaccessible government portals today, regardless of the compliance date.
The scope problem most agencies underestimate
The gap between "knowing the rule exists" and "knowing what compliance requires" is large for most state agencies.
The PDF problem. The single largest category of work is historical PDFs — benefit notices, policy manuals, application forms, program guidance accumulated over years. A PDF scanned as an image file is entirely inaccessible to a screen reader. Making it accessible requires rebuilding it with proper tagging, structure, reading order, and form field labels, then verifying the result manually. A mid-sized state health and human services agency may have tens of thousands of documents in its public-facing library. A realistic remediation program identifies them by traffic and legal significance, processes the high-priority documents first, and establishes a workflow for new documents before they enter the library inaccessible.
Third-party portals. Online permitting systems, benefits enrollment portals, child support payment systems, and professional licensure databases are often operated by commercial vendors under multi-year contracts. The state's obligation follows the program. Agencies that discover their vendor contracts contain no accessibility requirements, no conformance warranties, and no remediation obligation — which describes many contracts signed before the 2024 rule — face a procurement and contract management problem alongside a technical one.
Mobile applications. Mobile apps are separately covered and often separately contracted. They are subject to WCAG 2.1 Level AA requirements for mobile environments, including touch target sizing and orientation support. An agency with multiple apps procured through different vendors has multiple separate remediation tracks.
Legacy CMS and template issues. Many state websites run on content management platforms whose default themes and templates introduce WCAG failures — poor color contrast in the default palette, non-semantic heading structure, insufficient focus indicators — that recur every time new content is published. Point-in-time remediation of specific pages does not address a structural CMS problem. The fix requires template and theme updates, which may require a vendor or rebuilding the CMS configuration.
The H.R. 1 displacement risk
One specific pressure on state IT teams is worth naming. Research from the Beeck Center at Georgetown's Digital Benefits Network, based on interviews with seven states, found that agencies are actively moving accessibility work to the backlog in order to meet benefit eligibility system deadlines required by the July 2025 reconciliation legislation, H.R. 1. SNAP administrative cost-sharing changes took effect in October 2026. Medicaid community engagement requirements take effect January 1, 2027, with states needing systems completed before then. States are building and testing new eligibility verification and tracking systems under significant time pressure. Digital Government Hub, Beeck Center for Social Impact and Innovation, updated March 2026
The near-term prioritization is understandable. The risk is structural: accessibility work that moves to the backlog in October 2026 may stay there through March 2027. An agency that arrives at April 26, 2027 having completed no baseline audit, no vendor contract review, and no PDF remediation pipeline will be in exactly the same position as it was before the extension. The extension used as a delay mechanism rather than an implementation window does not produce compliance.
Both obligations are real. The question for program and IT leaders is not which one counts — it is how to stage the accessibility work so it does not start from zero in early 2027.
A sequencing framework for the next six months
The following is not a one-size-fits-all remediation plan. It is a prioritization logic for agencies that need to make meaningful progress without halting other work.
Months 1–2: Audit and inventory. Run automated accessibility scans against the top 200 to 300 most-visited pages and every online benefit application, permit form, and service portal. Automated tools (axe, WAVE, Lighthouse) identify a substantial fraction of WCAG failures quickly at low cost; they do not catch everything, and manual keyboard and screen reader testing is required for the highest-risk content. Separately, build a document inventory: identify which PDFs are structured files with machine-readable text versus scanned image files, and sort by page view volume and legal significance. Audit third-party vendor contracts for accessibility provisions.
Months 2–4: Remediate high-risk content and fix structural issues. Prioritize service delivery pages — forms, applications, account management, appointment scheduling — over informational pages. These are where accessibility failures have the most direct impact on residents and the most legal exposure for the agency. Fix CMS template and theme failures that generate recurring violations rather than addressing only the individual page instances. Begin the PDF remediation pipeline with the highest-volume documents.
Months 4–6: Procurement, monitoring, and institutional process. Add WCAG 2.1 Level AA conformance requirements and Accessibility Conformance Reports (ACR/VPAT) to all new solicitations and renewals. Establish accessibility monitoring — automated scanning on a scheduled cadence — and integrate accessibility review into the content publishing workflow so newly published content does not re-introduce failures. Publish an accessibility statement with a mechanism for users to request accessible alternatives and report problems.
Decisions to make before December
- Which agency pages and portals have been manually tested, not just scanned, for WCAG 2.1 Level AA conformance?
- What percentage of current vendor contracts include explicit WCAG 2.1 AA requirements and a remediation mechanism?
- Is there a documented PDF remediation pipeline with an owner, a backlog, and a processing rate?
- Who owns enterprise accessibility compliance — a named person, a team, a governance structure — and do they have authority over vendor contracts and CMS configuration?
- Does a public accessibility statement exist with an active complaint pathway?
The first of these questions is the most important. An automated scan that produces a clean result is not the same as a manually tested page. Automated tools catch a significant portion of WCAG failures; they miss the failures that require a human to navigate the page with keyboard-only access or a screen reader. Agencies that rely on automated scans alone will discover additional failures in the manual testing phase — which is better learned before the compliance deadline than after.
Sources and further reading
- DOJ 2024 final rule, 28 C.F.R. Part 35, Subpart H: Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities
- DOJ Interim Final Rule extending compliance dates, 91 Fed. Reg. 20902 (April 20, 2026), FR Doc 2026-07663
- WCAG 2.1 Level AA Quick Reference, W3C Web Accessibility Initiative
- Implementing Benefits Eligibility + Enrollment Systems: State Responses to H.R. 1, Beeck Center for Social Impact + Innovation / Digital Government Hub (Oct. 2025, updated Mar. 2026)
- DOJ ADA Title II overview, ADA.gov
Spartan X's work on state technology platforms has consistently treated federal compliance requirements as design constraints that need to be built in during procurement and architecture, not identified after deployment. In digital services modernization, accessibility is most efficiently addressed at the point where requirements are written and vendor contracts are negotiated — the same point where every other program compliance requirement gets resolved. Retrofitting it later costs more, takes longer, and tends to produce point-in-time fixes that erode as content and systems change. The compliance calendar creates a forcing function; the institutional processes are what make the result durable.
