Guide · Digital services
ADA Title II deadlines explained
Published May 15, 2026 · 8 min read
Who faces which Title II web compliance dates, what WCAG 2.1 AA means in practice, and how to turn the calendar into an operational checklist — without treating automation as a certificate.
The ADA Title II web rule adopts WCAG 2.1 Level AA as the technical standard for covered web content and mobile apps. The Department of Justice set staggered compliance dates so large entities move first. Always confirm dates against the ADA.gov fact sheet.
Who is in scope
Title II reaches state and local government entities and the services they deliver to the public. That includes counties, cities, special districts, many public authorities, and the digital properties they operate or substantially control — not only your primary .gov homepage.
The two headline deadlines
- April 26, 2027 — entities with a total population of 50,000 or more (as defined in the rule).
- April 26, 2028 — special-district governments and entities under the 50,000 population threshold.
Population counts and special-district definitions matter for where your organization lands. Your counsel or policy office should validate classification; engineering teams should treat the dates as planning anchors, not legal advice.
What WCAG 2.1 AA means operationally
Meeting the technical standard is more than a one-time audit. It implies repeatable detection on the pages you ship, prioritization when hundreds of failures share a root cause, retesting after fixes, and evidence that shows what was scanned, what changed, and what is still open. Automated checks cover on the order of 30–40% of WCAG failures; meaningful alt text, reading order, and complex interaction patterns still require human review.
A practical checklist
- Inventory every public web property and major PDF library you own or control.
- Baseline WCAG 2.1 AA against that inventory on a cadence, not a single snapshot.
- Deduplicate work — group findings by template and shared components so teams fix root causes once.
- Verify fixes with rescans and spot-check high-risk journeys manually.
- Report with dated exports your oversight body can file — with explicit scope disclaimers.
Where Parity fits
Parity is built for the detection, deduplication, workflow, and reporting loops above. It does not certify conformance or replace your accessibility subject-matter experts; it gives them continuous signal and audit-ready artifacts.