1. What is ADA Title II?
The Americans with Disabilities Act (ADA) was signed into law in 1990. Title II specifically covers state and local government entities — including city websites, county portals, public schools, universities, transit agencies, libraries, courts, and any other entity that receives federal funding or exercises governmental power.
For decades, the ADA's application to websites was implied but never codified into specific technical standards. Government agencies faced an unclear patchwork of case law and DOJ guidance letters. That changed on April 24, 2024, when the Department of Justice published its final rule under Title II explicitly requiring digital accessibility compliance to WCAG 2.1 Level AA standards.
This was a landmark moment. For the first time, there is a specific federal rule with specific technical standards (WCAG 2.1 AA) and a specific compliance deadline. The ambiguity is gone.
2. The April 24, 2026 Deadline Explained
The DOJ built a tiered compliance timeline based on population served:
| Entity Type | Population | Compliance Deadline |
|---|---|---|
| Large public entities | > 50,000 | April 24, 2026 |
| Small public entities | ≤ 50,000 | April 26, 2027 |
The April 24, 2026 date is exactly two years after the rule was finalized — the DOJ gave large entities 24 months to come into compliance. This sounds like a long runway, but web accessibility remediation at scale takes significant time: auditing, prioritizing, fixing development backlogs, training teams, and re-testing.
The deadline is firm. Unlike previous DOJ guidance, this is a codified rule in the Code of Federal Regulations (28 CFR Part 35). It's legally enforceable.
3. Who Is Covered (And Who Isn't)
Directly covered under Title II:
- City, county, and state government websites
- Public schools and school districts (K-12)
- Public colleges and universities
- Public transit agencies (MTA, BART, metro systems)
- Public libraries and library systems
- Courts, courthouses, and judicial websites
- Public health agencies
- Fire departments, police departments, emergency services
- Public parks and recreation departments
- Any entity receiving federal financial assistance
Not directly covered — but still at risk:
Private businesses are covered under ADA Title III, not Title II. Title III covers "places of public accommodation" — retail stores, restaurants, hotels, hospitals, gyms, theaters, and their websites and mobile apps. Courts have increasingly ruled that private business websites must be accessible under Title III even without a specific regulation equivalent to Title II's new rule.
In 2025, over 4,600 ADA website accessibility lawsuits were filed against private businesses — a 37% increase from the prior year. The average settlement cost is $25,000 to $100,000 plus plaintiff attorney fees. Even small businesses with no government contracts face real legal exposure.
4. WCAG 2.1 AA Requirements
WCAG 2.1 (Web Content Accessibility Guidelines, version 2.1) is organized around four core principles, remembered as POUR:
Perceivable
Content must be presentable to users in ways they can perceive. This includes text alternatives for images, captions for video, and sufficient color contrast.
Operable
Users must be able to operate the interface. All functionality must be available via keyboard, no timing-dependent interactions, and no content that causes seizures.
Understandable
Information and UI must be understandable. Readable text, predictable navigation, and clear error identification and instructions.
Robust
Content must be robust enough to be interpreted by assistive technologies including screen readers, braille displays, and voice control software.
WCAG 2.1 Level AA includes 50 success criteria. The most commonly violated ones are:
- 1.1.1 Non-text Content: All images need descriptive alt text
- 1.3.1 Info and Relationships: Structure conveyed through proper HTML semantics
- 1.4.3 Contrast (Minimum): 4.5:1 ratio for normal text, 3:1 for large text
- 1.4.4 Resize Text: Text can be resized to 200% without loss of content
- 2.1.1 Keyboard: All functionality available via keyboard alone
- 2.4.3 Focus Order: Logical tab order that preserves meaning
- 2.4.7 Focus Visible: Keyboard focus indicator is visible
- 3.3.1 Error Identification: Form errors described in text
- 4.1.2 Name, Role, Value: Proper ARIA roles for custom UI components
5. Penalties and Legal Risk
For government entities, non-compliance post-deadline triggers DOJ investigation, which can result in:
- Formal consent decrees with remediation timelines and reporting requirements
- Civil monetary penalties ($75,000 for first violation, $150,000 for subsequent)
- Loss of federal funding in severe cases
- Required third-party audits at the entity's expense
- Public reporting requirements
For private businesses, ADA Title III cases rarely involve the DOJ directly but are instead driven by serial litigants and disability rights organizations filing in federal court. Most cases settle before trial. Beyond financial cost, there's reputational harm — ADA lawsuits are public record and often picked up by local press.
6. How to Achieve Compliance
Achieving WCAG 2.1 AA compliance is a process, not a single event. Here's a practical roadmap:
Audit Your Current State
Run an automated accessibility scan on every key page of your site. Prioritize pages with highest traffic: homepage, contact/booking, checkout, forms. PageGuard gives you a free accessibility score in 30 seconds.
Prioritize Issues by Severity
Focus on Critical issues first: missing alt text, keyboard traps, missing form labels, color contrast failures. These block users entirely. Then address Warnings: ARIA issues, focus indicators, heading structure.
Manual Testing
Automated tools catch 30–40% of issues. Supplement with: keyboard navigation testing (Tab through every element), screen reader testing (NVDA free, VoiceOver built-in on Mac/iOS), browser zoom testing at 200%.
Document Your Conformance
Create an Accessibility Statement page listing your conformance level, known limitations, and contact method for users to report issues. This demonstrates good faith and is required under the DOJ rule.
Monitor Continuously
Websites change. New content, new features, CMS updates — any can introduce new accessibility issues. Set up automated monitoring (like PageGuard's weekly/daily scans) so you catch regressions before they become complaints or lawsuits.
7. The 10 Most Common Accessibility Failures
Based on the WebAIM Million annual report analyzing the top 1 million websites, these are the most prevalent WCAG failures:
| # | Failure Type | % of Sites | WCAG Criterion |
|---|---|---|---|
| 1 | Low color contrast text | 80.8% | 1.4.3 |
| 2 | Missing image alt text | 54.5% | 1.1.1 |
| 3 | Missing form input labels | 48.6% | 1.3.1 |
| 4 | Empty links (no text) | 44.6% | 2.4.4 |
| 5 | Missing document language | 17.1% | 3.1.1 |
| 6 | Empty buttons | 26.9% | 4.1.2 |
| 7 | Missing skip navigation | ~90% | 2.4.1 |
| 8 | Non-descriptive link text | ~40% | 2.4.4 |
| 9 | Keyboard traps in modals | ~25% | 2.1.2 |
| 10 | No visible focus indicator | ~30% | 2.4.7 |
The good news: fixing the top 3 failures (color contrast, alt text, form labels) alone dramatically reduces your legal exposure and makes your site usable for the vast majority of users with disabilities.
8. Ongoing Monitoring After the Deadline
Achieving compliance by April 24, 2026 is not the finish line — it's the starting gate. The DOJ rule requires ongoing accessibility. Websites are living systems: content editors add images without alt text, developers push features that break keyboard navigation, plugins update and introduce new barriers.
Best practice after the deadline:
- Run automated accessibility scans on every deployment (shift-left in CI/CD)
- Maintain a public Accessibility Statement with a contact method for user feedback
- Conduct full WCAG audits annually or after major redesigns
- Train content editors on accessible image, heading, and link text practices
- Monitor your accessibility score weekly — catch regressions before users (or lawyers) do