ADA Title II Deadline Is April 24, 2026 — Is Your Website Ready?
This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for guidance specific to your entity's situation.
36 days remaining
State and local governments serving populations of 50,000 or more must comply with WCAG 2.1 Level AA by April 24, 2026 under the DOJ's ADA Title II Final Rule. The time to audit and remediate is now — not after the deadline.
90,000+
Public entities affected
94.8%
Gov. sites fail WCAG checks
$30K+
Avg. legal defense cost
For years, digital accessibility in the public sector operated in a gray area — federal agencies nudged state and local governments toward accessible websites, but without a binding rule tied to a firm deadline, many entities deprioritized it. That changed on April 24, 2024, when the Department of Justice published its ADA Title II Final Rule, establishing WCAG 2.1 Level AA as the legally required standard for government websites and mobile applications — with an enforcement deadline of April 24, 2026 for larger jurisdictions.
That deadline is now weeks away. If your agency, municipality, school district, public university, or special district has not yet completed an accessibility audit, you are in a high-risk position. This guide explains exactly what the rule requires, who it applies to, what the most common failures look like, and the practical steps you need to take before April 24.
What Is ADA Title II, and Why Does It Cover Websites?
The Americans with Disabilities Act was signed into law in 1990 — before the modern web existed. Title II of that law prohibits discrimination by state and local governments across all their programs, services, and activities. As government services migrated online over the following decades, courts and federal agencies consistently interpreted "programs, services, and activities" to include websites, mobile apps, digital forms, and online portals.
For a long time, public entities operated under this understanding without a specific technical standard to meet. The DOJ's 2024 Final Rule ended that ambiguity. For the first time, Title II now explicitly requires compliance with WCAG 2.1 Level AA — giving public entities a concrete, measurable benchmark to hit.
The rule covers an enormous scope of entities: every state agency, county government, city, town, municipality, public school district, public college and university, public library, public transit authority, public housing agency, and special district in the United States. Collectively, this represents approximately 90,000 government entities — ranging from the smallest rural water district to major metropolitan governments.
| Entity Type | Compliance Deadline | Status |
|---|---|---|
| State & local governments (pop. 50,000+) | April 24, 2026 | Imminent |
| Special districts & smaller jurisdictions | April 26, 2027 | Upcoming |
Source: DOJ ADA Title II Final Rule, 28 CFR Part 35 (April 2024)
What Does WCAG 2.1 Level AA Actually Require?
WCAG 2.1 (Web Content Accessibility Guidelines) is a set of technical criteria published by the World Wide Web Consortium (W3C). In October 2025, it was adopted as an ISO international standard — ISO/IEC 40500:2025 — cementing its status as the global benchmark for digital accessibility.
The guidelines are organized around four core principles, often abbreviated as POUR:
Perceivable
All information on your site must be presentable in ways users can actually perceive — regardless of disability. This means images need descriptive alt text so screen readers can convey them, videos need synchronized captions and audio descriptions, and documents must be structured so they make sense when read aloud.
Operable
Every feature of your website must be fully operable without a mouse. Users with motor disabilities rely on keyboard navigation, switch controls, or voice commands. If a dropdown menu, modal dialog, date picker, or navigation menu can't be reached and used via keyboard alone, it fails this criterion.
Understandable
Content and navigation must be predictable and clear. Error messages on forms must explain exactly what went wrong and how to fix it. Language must be set programmatically so screen readers know which language to use. Navigation must remain consistent across pages so users with cognitive disabilities are not disoriented.
Robust
Your website's code must be clean enough that current and future assistive technologies can interpret it correctly. This means using valid HTML, proper ARIA attributes, and semantic markup — not relying on visual-only cues to convey meaning.
At Level AA, WCAG 2.1 includes 50 specific success criteria. These are not vague goals — each criterion has a precise pass/fail definition. For example, Success Criterion 1.4.3 requires that text maintain a contrast ratio of at least 4.5:1 against its background. Success Criterion 2.1.1 requires that all functionality be operable via keyboard. Meeting Level AA means passing all applicable criteria for your content type.
WCAG 2.2, which added nine new criteria (including focus appearance and target size requirements), was ratified in 2023. While the DOJ rule references WCAG 2.1, proactively meeting 2.2 future-proofs your compliance as standards continue to evolve.
Who Is Affected — and What Exactly Must Be Accessible?
The April 24, 2026 deadline applies to state and local government entities whose jurisdiction serves a population of 50,000 or more. This encompasses the vast majority of significant public entities, including:
- State executive agencies, legislative bodies, and judicial branch websites
- County and municipal governments in jurisdictions above the population threshold
- Public K–12 school districts and their individual school websites
- Public colleges, community colleges, and state university systems
- Public libraries and library systems
- Transit authorities, port authorities, and airport authorities
- Public utility districts and water districts meeting the population threshold
- Public housing authorities
Critically, "website" is interpreted broadly. The rule covers:
The Most Common WCAG Failures on Government Websites
WebAIM's annual research consistently finds that six violation types — low contrast text, missing image alt text, unlabeled form inputs, vague links, inaccessible buttons, and missing document language — account for 96% of all detected WCAG failures across public-sector websites. For the full breakdown with prevalence rates and who each violation harms, see our ADA lawsuit statistics report.
The good news: these are also among the most straightforward to fix. Most require no developer involvement — just content edits. Our step-by-step guide to fixing WCAG violations walks through each issue with plain-English instructions.
What Happens If You Miss the April 24 Deadline?
Missing the ADA Title II deadline does not automatically trigger a fine — but it creates significant legal and operational exposure. Here's what can happen after April 24, 2026 if your entity is not compliant:
DOJ-initiated compliance review
The Department of Justice can proactively investigate entities suspected of Title II violations. Following an investigation, the DOJ may issue a Letter of Findings identifying specific violations and requiring a corrective action plan. Failure to cooperate or remediate can lead to referral to the Attorney General for litigation.
Individual complaints to federal agencies
Any individual who encounters a barrier on a government website can file a complaint with the DOJ's Civil Rights Division, the Department of Education's Office for Civil Rights (for educational institutions), or the Department of Transportation (for transit authorities). These complaints trigger investigations and typically require a documented remediation plan.
Private civil rights lawsuits
Individuals can sue directly under Title II in federal court without going through a federal agency first. Successful plaintiffs can obtain injunctive relief (a court order requiring accessibility fixes), attorney's fees, and — under some state civil rights laws — compensatory damages. Legal defense costs, even when the government entity ultimately prevails, routinely exceed $30,000.
Loss of federal funding
Entities that receive federal financial assistance — including most public schools and universities, transit systems, and housing authorities — may face suspension or termination of federal grants as a consequence of sustained Title II non-compliance found through federal investigations.
5 Steps to Reach Compliance Before April 24
With weeks left on the clock, a pragmatic, phased approach beats attempting a full remediation from scratch. Here's how to get the most compliance impact in the least amount of time.
Run an automated accessibility scan today
Automated tools can identify 30–40% of WCAG failures without any manual effort. Start with a scan of your highest-traffic pages: your homepage, contact page, service portals, and any page involved in applying for or accessing a public benefit. WCAGsafe provides a free scan that generates a prioritized report showing which pages have the most critical violations — giving you a clear starting point within minutes.
Triage by impact, not alphabetical order
Not all violations are equal. A contrast issue on a page visited by 50,000 citizens per month is far higher priority than a labeling issue on an obscure administrative page. Use your scan results to rank fixes by: (1) traffic volume of the affected page, (2) severity of the violation (Level A failures before Level AA), and (3) how many users are affected. Fix in that order.
Address the six most common failures first
Based on the prevalence data above, your biggest compliance gains will come from: adding alt text to all images, ensuring text contrast ratios meet 4.5:1, labeling all form inputs correctly, making all links descriptive, ensuring buttons have accessible names, and setting the page language attribute. These six fixes address 96% of the most common failure patterns.
Supplement with manual and assistive technology testing
Automated tools cannot catch everything. Keyboard navigation testing (Tab through every interactive element — can you reach and operate all of them without a mouse?), screen reader testing with NVDA or JAWS, and user testing with people who have disabilities will surface issues that automated scans miss. Allocate time for at least keyboard and screen reader testing on your most critical pages.
Document your efforts and establish ongoing monitoring
Even if you are not fully compliant by April 24, a documented, good-faith accessibility program — with an active remediation plan, staff training records, and regular audits — demonstrates commitment that matters in complaints and investigations. Accessibility is not a one-time project; every content update is an opportunity to introduce new barriers. Schedule automated scans on a regular cadence and integrate accessibility review into your content publishing workflow.
5 Dangerous Myths About ADA Title II Compliance
Misinformation about what constitutes compliance is widespread — and acting on it can leave your entity exposed. Here are the most damaging myths circulating in 2026.
"We have an accessibility widget installed — we're covered."
✓ Reality:Accessibility overlay widgets do not achieve WCAG 2.1 AA compliance. In 2025, the FTC fined accessiBe $1 million for falsely claiming their widget guaranteed ADA compliance. More critically, 25% of all digital accessibility lawsuits in 2025 specifically targeted websites that already had an overlay installed. A widget is not a substitute for real remediation.
"Title II only applies to our main website."
✓ Reality:Every digital touchpoint is in scope: your main website, department subdomains, mobile applications, PDF forms, online permit systems, video content, social media accounts used for official communications, and third-party platforms you direct citizens to use. If it's part of a public service, it must be accessible.
"We can fix this after the deadline if we get a complaint."
✓ Reality:Waiting for a complaint is reactive and expensive. The DOJ can initiate investigations, and individuals can file civil rights complaints with federal agencies or pursue private lawsuits. Courts have consistently held that good-faith-but-late remediation does not eliminate liability for the period of non-compliance.
"Accessibility remediation will cost us hundreds of thousands of dollars."
✓ Reality:For most public entities, a phased remediation approach — starting with the highest-impact, highest-traffic pages — is far more affordable than assumed. The real cost of non-compliance (legal defense alone averages $30,000 even when you win) vastly exceeds the cost of proactive investment.
"Our site was built recently, so it should already be compliant."
✓ Reality:Modern web development does not automatically produce accessible code. Mainstream frameworks, CMS themes, and page builders regularly produce WCAG failures out of the box. A recent launch is not a compliance guarantee — only a structured accessibility audit can confirm it.
Pre-Deadline Compliance Checklist
Use this checklist to assess where your entity stands today. Every unchecked item is a gap that needs a remediation plan before April 24.
Frequently Asked Questions
Does ADA Title II apply to private businesses?
No. ADA Title II applies exclusively to state and local government entities. Private businesses are covered under ADA Title III, which has different requirements and timelines. However, private companies that contract with government entities to provide public services may have Title II obligations passed through their contracts.
What is WCAG 2.1 Level AA, and why is it the standard?
WCAG 2.1 Level AA is a set of 50 specific technical criteria developed by the W3C (World Wide Web Consortium) that define a meaningful level of accessibility for most users with disabilities. The DOJ selected it as the Title II standard because it strikes a balance between accessibility impact and implementation feasibility. It became an ISO international standard (ISO/IEC 40500:2025) in October 2025.
Are there exemptions from the April 24, 2026 deadline?
Yes. The DOJ rule includes limited exemptions: archived web content that is not actively maintained, pre-existing conventional electronic documents not currently used for a public service, third-party content not under the entity's control, and content on password-protected pages used for limited internal purposes. However, these exemptions are narrow — most public-facing content is in scope.
What happens if we miss the deadline?
Individuals can file a complaint with the DOJ, the Department of Education (for educational institutions), or other relevant federal agencies. The DOJ can investigate, issue findings, and pursue compliance agreements or litigation. Individuals can also file private lawsuits. There is no per-violation fine schedule under Title II, but court-ordered remediation, legal fees, and consent decree monitoring costs can be substantial.
Does this apply to PDFs and other documents?
Yes, with a limited exception. PDFs and electronic documents used to apply for, access, or participate in a public service or benefit must be accessible. The exemption only covers archived documents that are not actively used in any current public program — a narrow category that excludes most forms, reports, and informational documents that agencies regularly publish.
We're a small municipality with limited IT resources. What should we prioritize first?
Focus first on the pages citizens use most: your homepage, contact information, service applications, meeting agendas and minutes, emergency notifications, and payment portals. Fixing the highest-traffic pages delivers the most compliance impact per dollar spent. Run a free scan to get a prioritized list of issues ranked by severity.
Can third-party content on our site create liability?
Yes, if you link to or embed third-party content as part of delivering a public service or program. Embedding an inaccessible third-party event registration system or payment portal — even if you didn't build it — can create Title II exposure. Contracts with vendors should require WCAG 2.1 AA conformance.
Don't Wait Until April 24 to Find Out You're Not Ready
WCAGsafe scans your website against WCAG 2.1 AA criteria in minutes and gives you a prioritized report of every issue — organized by severity and page — so you know exactly where to focus your remediation effort before the deadline.
No credit card required · Results in under 2 minutes · WCAG 2.1 AA criteria
The Bottom Line
The April 24, 2026 ADA Title II deadline is not a bureaucratic checkbox — it is a legal obligation tied to one of the most foundational civil rights statutes in American history. The requirement is clear: WCAG 2.1 Level AA, across your websites, mobile apps, and digital documents, by April 24.
The entities that will navigate this well are the ones that started their audits early, built remediation into their existing workflows, and treated accessibility as an ongoing operational commitment — not a one-time project. Those that delayed are now in triage mode, and every week of inaction narrows the window further.
The practical path forward is straightforward: scan what you have, fix what matters most, document everything, and establish the monitoring infrastructure to stay compliant as your site evolves. See our breakdown of ADA compliance costs in 2026 and the latest ADA lawsuit statistics — the data is stark and should motivate action today.