What State and Local Governments Must Do, and By When
Digital accessibility is the law
On April 24, 2024, the U.S. Department of Justice issued a Final Rule confirming that websites, mobile applications, and digital documents are covered services under ADA Title II. For state and local governments, digital accessibility is no longer advisory or interpretive. It is codified, with fixed compliance deadlines and active enforcement.
Every public entity is covered regardless of budget, staffing, or federal funding. Population size determines when compliance must be complete, not whether the obligation applies. Entities serving 50,000 or more people must comply by April 24, 2026. Smaller jurisdictions have until April 24, 2027. After those dates, non-conforming digital content is presumptively unlawful.
This page sets out the legal basis, scope, deadlines, enforcement mechanisms, and practical expectations so that leadership, technology, risk, and compliance teams can understand what is required and act accordingly.
"You cannot discriminate online. ADA is both a legal requirement and societal commitment. The choice is when to comply; take control now or await your demand and then address."
Role-Based Summaries
Executive and Senior Leadership
By April 24, 2026 or April 24, 2027, your organization must deliver accessible websites and digital services under ADA Title II. This is a compliance obligation with fixed deadlines, not a discretionary improvement.
Failure to meet the deadline exposes the organization to DOJ enforcement, complaints, and litigation. Executive leadership is accountable for ensuring governance, funding, vendor oversight, and assurance mechanisms are in place to evidence compliance and protect public trust.
Digital and Technology Leadership
ADA Title II requires that by April 24, 2026 or 2027, all public-facing websites, apps, forms, and PDFs meet WCAG 2.1 Level AA. Accessibility must be built into platforms, templates, workflows, and vendor systems.
One-off audits are insufficient. Digital leaders are responsible for implementing continuous controls, preventing regression, and ensuring compliance can be demonstrated at any time once the deadline passes.
Risk Manager and Compliance
Title II digital accessibility carries fixed compliance deadlines and active enforcement. By April 24, 2026 or 2027, inaccessible digital services are presumptively unlawful.
Liability cannot be delegated to vendors, and intent does not mitigate exposure. Risk and compliance functions must ensure audits, documentation, monitoring, and governance are in place to evidence compliance, manage vendor risk, and withstand DOJ investigation or litigation.
"Executive leadership is accountable for ensuring governance, funding, vendor oversight, and assurance mechanisms are in place."
Regulatory Timeline and Compliance Thresholds
Mandatory and central
April 24, 2024
The DOJ issued the Final Rule titled: Nondiscrimination on the Basis of Disability; Accessibility of Web Content and Mobile Apps Provided by State and Local Governments.
April 24, 2026
Compliance deadline for public entities serving 50,000 or more people.
April 24, 2027
Compliance deadline for public entities serving fewer than 50,000 people.
Key clarifications:
These are compliance deadlines, not planning milestones.
DOJ enforcement actions and public complaints can occur before these dates.
After the applicable deadline, non-conforming digital content is presumptively unlawful.
Legal Basis and Applicability
Why this applies now
ADA Title II requires state and local governments to ensure that individuals with disabilities are not excluded from participation in, or denied the benefits of, public programs, services, and activities.
The statutory basis is ADA Title II, 42 U.S.C. §§ 12131-12165, implemented through 28 CFR Part 35.
On April 24, 2024, the U.S. Department of Justice issued a Final Rule that explicitly confirms that websites and mobile applications are covered digital services under Title II. This rule removes any remaining ambiguity. Digital accessibility under Title II is no longer interpretive. It is codified.
Public sector websites and apps are legally treated as part of service delivery.
"Public sector websites and apps are legally treated as part of service delivery."
Who Must Comply and Enforcement Thresholds
Who is measured, and how
All state and local government entities are covered by ADA Title II.
There are no exemptions based on:
Budget
Staffing levels
Receipt of federal funding
Population size affects the compliance deadline only, not the obligation itself. Every covered entity must comply with the same standard.
Coverage determines who must act. Population determines when compliance must be complete.
"Coverage determines who must act. Population determines when compliance must be complete."
What the Deadline Actually Means
Explicit compliance conditions
By the applicable deadline, the following must already be true:
Public-facing websites conform to WCAG 2.1 Level AA
Mobile applications conform to WCAG 2.1 Level AA
In-use PDFs, forms, and posted documents are accessible
Accessibility does not depend on individual accommodation requests
An accessibility statement and feedback mechanism are live
Ongoing compliance controls can be demonstrated
The following are not sufficient:
Having a remediation plan
Promising future fixes
Fixing only high-traffic pages
Offering alternative formats on request
The DOJ rule requires accessibility to be in place, not merely planned.
"The DOJ rule requires accessibility to be in place, not merely planned."
Scope of Digital Content Covered
Anchored to enforcement language
The following content is covered when in use on or after the compliance date:
Public websites and subdomains
Web-based applications and service portals
Online forms and transactions
PDFs and documents required to access services
Third-party platforms used to deliver government services
"Archived" content is only exempt if it is not required to access a service, benefit, or legal obligation. Legacy content that remains in active use stays in scope after the deadline.
"Legacy content that remains in active use stays in scope after the deadline."
Third-Party and Vendor Digital Risk
Liability cannot be delegated
ADA Title II responsibility cannot be transferred to vendors.
Contracts do not shift liability. If a third-party platform is inaccessible, the public entity remains responsible.
Vendor-provided systems must meet WCAG 2.1 Level AA by the applicable deadline. Procurement teams are expected to assess accessibility risk and manage it as part of vendor selection and oversight.
Vendor non-compliance exposes the public entity to enforcement and legal action.
"Contracts do not shift liability."
Common Digital Failures That Trigger Enforcement
Recurring complaint drivers
The DOJ routinely encounters enforcement actions arising from:
Inaccessible PDFs used for applications, notices, or public records
Forms that cannot be completed using a keyboard or screen reader
Navigation that traps or blocks assistive technology users
Missing labels, instructions, or error identification
Content updates that reintroduce failures after remediation
These are not edge cases. They are common causes of complaints and investigations.
"These are not edge cases. They are common causes of complaints and investigations."
Enforcement, Complaints, and Legal Exposure
Aligned to DOJ practice
The DOJ enforces Title II through investigations and settlement agreements. Public complaints frequently initiate enforcement.
DOJ settlements typically require:
Fixed remediation deadlines
Independent verification
Ongoing monitoring
Public reporting of progress
Private lawsuits may proceed independently of DOJ action.
Intent is irrelevant once discrimination exists. Enforcement does not wait for good faith efforts or future commitments.
"Intent is irrelevant once discrimination exists."
Practical Compliance Expectations Before the Deadline
What should already be happening now
Before April 24, 2026 or April 24, 2027, the DOJ expects to see:
A complete inventory of websites and digital services
Baseline audits aligned to WCAG 2.1 Level AA
Prioritized remediation actively underway
Clear governance and ownership defined
Accessibility assessed across vendor platforms
Documentation retained as evidence of compliance activity
Delay increases exposure. Waiting until the deadline creates enforcement risk.
"Delay increases exposure. Waiting until the deadline creates enforcement risk."
What Must Be True by the Deadline
Unambiguous compliance frame
By April 24, 2026
For entities serving 50,000 or more people
Public digital services conform to WCAG 2.1 Level AA
In-scope documents are accessible
Accessibility is embedded into publishing workflows
Ongoing monitoring is active
Compliance can be evidenced on request
By April 24, 2027
For entities serving fewer than 50,000 people
The same requirements apply
The later date does not reduce scope or standard
Delay without progress increases enforcement risk
"The later date does not reduce scope or standard."
Authoritative References
DOJ Final Rule on Digital Accessibility (April 24, 2024)
Establishes mandatory accessibility requirements for websites and mobile applications operated by state and local governments under ADA Title II. This rule confirms WCAG 2.1 Level AA as the required standard and sets fixed compliance deadlines.
The formal implementing regulations for ADA Title II. These regulations define nondiscrimination obligations, program accessibility, enforcement authority, and the legal basis for digital accessibility requirements.
Official guidance explaining how Title II applies to websites, mobile applications, and digital services. Includes explanations, examples, and clarifications used by the DOJ in enforcement and compliance evaluations.
The Web Content Accessibility Guidelines version 2.1, Level AA. This is the technical accessibility standard explicitly required by the DOJ Final Rule for state and local government digital services.
Practical resources used by the DOJ to explain compliance expectations and inform settlement agreements. These materials reflect how accessibility obligations are interpreted in real enforcement scenarios.
