Blog Post
ADA Title II Compliance: What Web Teams Need to Know
Last updated: April 1, 2026
The ADA Title II compliance deadline is April 24, 2026 — weeks away. State and local government websites must conform to WCAG 2.1 Level AA by this date. This guide covers who is affected, what changed, the specific WCAG success criteria your team needs to meet, and a practical compliance roadmap — including how design QA catches accessibility failures that automated scanners miss.
What Is ADA Title II?
Title II of the Americans with Disabilities Act applies to all services, programs, and activities provided by state and local government entities. The 2024 DOJ final rule specifies WCAG 2.1 Level AA as the technical standard for web accessibility, replacing years of ambiguous guidance with a clear, enforceable benchmark.
Who Must Comply?
All state and local government bodies — including state agencies, counties, municipalities, public schools, universities, libraries, transit authorities, courts, and special districts. Entities serving 50,000+ people must comply by April 24, 2026. Smaller entities have until April 26, 2027.
The April 24, 2026 Deadline: What Changed
The rule names WCAG 2.1 Level AA as the explicit benchmark, sets a hard compliance deadline, and defines scope to include web content and mobile apps — including content published by third-party vendors on behalf of the entity.
WCAG 2.1 AA: What Your Team Needs to Meet
WCAG 2.1 Level AA contains 50 success criteria under four principles: Perceivable, Operable, Understandable, and Robust. Key criteria include color contrast minimums, keyboard operability, focus visibility, form labels, and proper ARIA usage.
Practical Compliance Steps for Web Teams
- Audit your current state with automated and manual testing
- Prioritize fixes by user impact and legal risk
- Fix at the design system level for maximum efficiency
- Test with assistive technology (screen readers, keyboard, zoom)
- Document everything for compliance defense
- Build accessibility into your ongoing workflow
How Design QA Catches Accessibility Failures
A large percentage of WCAG failures are visual — contrast issues, missing focus indicators, touch target sizing, and form label problems. Teams practicing rigorous design QA catch these naturally during visual comparison reviews.
The Three-Layer Testing Methodology
Effective accessibility testing combines automated scanning (axe, WAVE, Lighthouse), manual review and design QA (comparing specs against builds, checking contrast, verifying focus indicators), and assistive technology testing (screen readers, keyboard, zoom).
The Most Common Accessibility Failures
- Low contrast text (81% of home pages)
- Missing alternative text (54% of home pages)
- Missing form input labels (48% of home pages)
- Empty links and buttons
- Missing document language
ADA Title II vs. Section 508
Title II applies to state/local government (WCAG 2.1 AA). Section 508 applies to federal agencies (WCAG 2.0 AA). Meeting WCAG 2.1 AA satisfies both requirements.
Exceptions and Limitations
Limited exceptions exist for archived content, third-party user-generated content, undue burden (narrowly defined), and preexisting documents not used for current services.
| WCAG Criterion | What Design QA Catches |
|---|---|
| 1.4.3 Contrast (Minimum) | Text color does not meet 4.5:1 ratio against background — visible when comparing design against implementation |
| 1.4.11 Non-text Contrast | Form borders, icon buttons, and UI elements below 3:1 ratio — caught during component-level review |
| 2.4.7 Focus Visible | Missing or invisible focus indicators — caught when testing interactive states during design review |
| 2.5.5 Target Size | Touch targets smaller than 44px or insufficient spacing — caught when measuring element dimensions against spec |
| 1.3.1 Info and Relationships | Visual hierarchy not matching semantic structure — caught when heading sizes differ from spec |
| 3.3.2 Labels or Instructions | Form fields using placeholder-only labels — caught when comparing form design against implementation |
| ADA Title II | Section 508 | |
|---|---|---|
| Applies to | State and local government entities | Federal agencies and their contractors |
| Technical standard | WCAG 2.1 Level AA (as of 2024 rule) | WCAG 2.0 Level AA (updated in 2017 refresh) |
| Enforcement | DOJ enforcement, private lawsuits | Federal procurement requirements, GSA oversight |
| Scope | All web content and mobile apps | ICT (information and communication technology) |
Frequently Asked Questions
Does ADA Title II apply to private businesses?
No. Title II applies to state and local government entities. Private businesses fall under Title III.
Is WCAG 2.1 AA the same as Section 508 compliance?
Not exactly. Section 508 references WCAG 2.0 Level AA. Meeting WCAG 2.1 AA satisfies Section 508, but not the reverse.
What if our site uses a third-party platform we can't fully control?
The compliance obligation rests with the public entity, not the vendor. Include WCAG 2.1 AA conformance in your procurement requirements.
What happens after the April 24, 2026 deadline passes?
Enforcement begins immediately. The DOJ can open investigations, and individuals can file private lawsuits under Title II without a grace period. Courts will look at documented good-faith efforts — an accessibility roadmap, a published VPAT, and evidence of ongoing remediation — when evaluating compliance. Starting late is better than not starting, but the deadline is a hard trigger for enforcement action.