On this page
What just changed (April 2026)
On April 20, 2026, DOJ published an Interim Final Rule (IFR) extending the ADA Title II web and mobile app accessibility compliance dates by one year.
What changed:
- Compliance for entities serving 50,000+: pushed from April 24, 2026 → April 26, 2027.
- Compliance for entities serving under 50,000 and special district governments: pushed from April 26, 2027 → April 26, 2028.
What did not change:
- The technical standard is still WCAG 2.1 Level AA.
- The scope of covered content (websites, mobile apps, PDFs) is unchanged.
- All other substantive provisions of the April 24, 2024 final rule remain in force.
- The underlying ADA obligation to provide equally effective communication to people with disabilities still applies today — independent of the WCAG technical deadline.
The 60-day public comment period runs through June 22, 2026; DOJ has signaled further rulemaking may follow.
What is ADA Title II?
ADA Title II covers state and local governments and the services they provide. DOJ's April 24, 2024 final rule made the digital standard explicit: websites, mobile apps, and public PDFs must meet WCAG 2.1 Level AA. The April 20, 2026 IFR kept the rule and moved the deadlines.
Who is covered
ADA Title II applies to US state and local government entities, including:
- States, counties, cities, towns, and villages
- Public schools, colleges, universities, and libraries
- Public transit authorities
- Special districts such as water, fire, parks, irrigation, and hospital districts
Federal agencies fall under Section 508. Private vendors are usually covered through procurement requirements.
What the rule requires for PDFs
For PDFs, ADA Title II compliance means WCAG 2.1 Level AA. In practice, that requires:
- Properly tagged structure — headings, lists, tables, paragraphs all marked as what they are.
- Logical reading order — content reads in the order a sighted person would read it.
- Alt text on meaningful images; decorative images marked as decoration.
- Document metadata — title and language set.
- Color contrast meeting 4.5:1 for body text, 3:1 for large text.
- Accessible forms — every field labeled, with clear instructions.
- Embedded fonts with text mapped to Unicode (so screen readers can read it).
- No security settings that block screen readers.
The clearest technical path is PDF/UA-1 (ISO 14289-1:2014), which translates WCAG into PDF's native tagging model. See our PDF/UA guide.
How ADA Title II is enforced
ADA Title II is enforced by the US Department of Justice. Even with the extension, two risks remain:
- The underlying ADA obligation applies today. A user can still challenge inaccessible tax forms, school registrations, court filings, or public notices before the technical deadline.
- Private lawsuits. Individuals can sue under Title II directly, and successful plaintiffs can recover attorney's fees.
How to use the extra year
Use the extension to reduce backlog risk before vendor capacity tightens.
Step 1: Inventory your PDFs
Count public PDFs across your website and document systems. Use our free audit to start with a categorized inventory, then prioritize legally required, high-traffic, and frequently updated files.
Step 2: Prioritize by impact
Fix public forms, applications, notices, agendas, and other high-impact PDFs first.
Step 3: Decide on an approach
Choose whether in-house work, platform remediation, or service support is the right path for the existing backlog.
Step 4: Document progress
Keep remediation records, audit reports, and a public feedback channel for accessibility issues. Each PDF you remediate with us comes with a free report for your records.
ADAComply can inventory your public-facing PDFs and prepare a categorized dashboard so you can see scope, priorities, and likely remediation needs before you spend budget.
Primary sources to verify
Use these official references when you review deadlines, exemptions, and technical requirements.
How ADAComply helps with ADA Title II
ADAComply prepares a free dashboard audit, flags likely exempt files, and remediates the documents that need work. It is designed to remediate PDFs to WCAG 2.1 AA, PDF/UA-1, PDF/UA-2, and WTPDF, with reports stored in the dashboard.
$4 per PDF page and $4 per table. No subscription or minimums.
Frequently asked questions
Did the substantive requirements change?
No. The technical standard is still WCAG 2.1 Level AA. Only the deadlines moved.
Should we wait until 2027 to start?
No. The underlying ADA obligation to provide accessible content applies today. Entities that wait until close to the deadline typically face higher costs and constrained vendor capacity. Use the extra year to build sustainable practices, not to delay.
Does this apply to PDF documents?
Yes. The rule covers all digital content, including PDFs — meeting agendas, public notices, application forms, court records, school documents, permit applications, anything published to the public.
What standard do PDFs need to meet?
WCAG 2.1 Level AA. The most established technical path for PDF files is remediating and testing toward PDF/UA-1 (ISO 14289-1:2014).
Are private contractors covered?
Not directly. But contracts with state and local governments increasingly require vendors to meet the same standards — often through accessibility clauses or VPAT requirements.