On April 24, 2024, the U.S. Department of Justice published the final rule implementing Title II of the Americans with Disabilities Act for state and local government web content. After a one-year extension issued in April 2026, the operative compliance dates are now:
- Public entities serving 50,000+ people: April 26, 2027
- Public entities under 50,000 and special districts: April 26, 2028
For California agencies, the federal deadline is only part of the story. The Unruh Civil Rights Act has provided $4,000 in statutory damages per violation since long before the DOJ rule existed, and California's plaintiff bar files more disability-access lawsuits than any other state. Federal compliance is the ceiling. State exposure is the floor.
Who is covered
Title II applies to "public entities," which the ADA defines broadly. In California, that includes:
- Cities and counties (including charter cities)
- Special districts (water, fire, irrigation, transit, school, community college)
- Public housing authorities
- Joint powers authorities and councils of government
- State agencies, boards, and commissions
- Public universities, colleges, and K-12 districts
Population thresholds determine which deadline applies. The 50,000 threshold uses U.S. Census Bureau population estimates for the political subdivision served by the entity, not the entity's own headcount.
What needs to comply
The rule covers web content and mobile applications the entity provides or makes available to the public. In practice, this means:
- Every page on your public-facing website
- Every PDF, Word document, or other downloadable document
- Every video, audio file, and image (with their alt text and captions)
- Every public-facing mobile app the agency publishes
- Online forms, applications, and self-service portals
Content posted on third-party platforms (e.g., agency social media accounts, YouTube videos, public meeting livestreams hosted by a vendor) is also covered when the agency uses them to communicate with the public.
Common scope mistake: agencies assume "the website" means the homepage and main navigation. The rule applies to every URL accessible to the public — including the 50,000-page document archive your records team has been quietly maintaining since 2003.
The technical standard: WCAG 2.1 Level AA
WCAG 2.1 Level AA is the technical standard the rule adopts. It is published by the World Wide Web Consortium and contains 50 success criteria across four principles: Perceivable, Operable, Understandable, and Robust. For PDFs and documents, the most commonly violated criteria are:
- 1.1.1 Non-text Content: images need alt text; decorative images need to be marked as artifacts
- 1.3.1 Info and Relationships: headings, lists, and tables need proper structure tags
- 1.4.3 Contrast: text needs sufficient contrast against its background (4.5:1 for normal, 3:1 for large)
- 2.4.4 Link Purpose: links need meaningful text ("View 2026 budget" not "Click here")
- 3.1.1 Language of Page: the document language must be set programmatically
A typical untagged PDF from a Word export will fail at least 8–12 of the 50 criteria.
What the exceptions actually cover
The rule provides five categories of exceptions. Each is narrower than agencies often assume:
- Archived web content: only if it predates the compliance date, is kept solely for record-keeping, is moved to a clearly labeled archive section, and is no longer used or updated.
- Preexisting conventional electronic documents: only if they predate the compliance date and are not currently used to apply for, gain access to, or participate in agency programs.
- Third-party content: content posted by users (e.g., comments) is exempt; content the agency itself posts is not.
- Individualized password-protected documents: e.g., a person's specific medical record or tax return.
- Preexisting social media posts: posts made before the compliance date.
Critically: a 2024 PDF you keep on your "Documents" page is not archived. Moving it to a labeled archive section, marking it clearly as historical, and stopping all updates — that's archived. The label and behavior matter, not just the date.
A realistic 12-month rollout
Agencies that try to remediate everything in the last 60 days run out of money, time, and goodwill with their vendors. A methodical 12-month plan looks roughly like this:
- Months 1–2: Inventory. Crawl your website, count PDFs, classify by program area, identify archive candidates.
- Months 3–4: Triage. Prioritize by traffic, regulatory exposure (e.g., agendas/minutes under the Brown Act), and complexity.
- Months 5–9: Remediate. Convert high-priority PDFs to accessible HTML; remediate or replace must-have PDFs; archive the rest with proper labels.
- Months 10–11: Verify. Run automated and manual accessibility audits; fix outliers.
- Month 12: Document. Publish your accessibility statement; publish remediation methodology for procurement and audit defense.
What to do this month
The single highest-leverage action you can take is to quantify your problem. Most agencies do not know how many pages of PDF content they actually publish. The number is almost always 5–10x larger than staff estimates. Until you have that number, every cost projection is a guess and every vendor proposal is sized to their capacity, not your actual scope.
SentraCheck offers a free corpus audit for California agencies: in 5 business days we count every public document on your website, classify what could qualify for archive exemption, identify duplicates (we routinely find that 30–40% of pages are duplicates of other pages), and deliver a prioritized remediation plan. No commitment.