All state guides » California Title II accessibility
California Title II accessibility: April 2026 deadline + Unruh Act compounding
California state and local government websites sit under two stacked accessibility pressures. At the federal level, the Department of Justice's April 2024 Title II web rule sets a WCAG 2.1 Level AA conformance deadline of April 24, 2026 for public entities serving populations of 50,000 or more (April 24, 2027 for smaller entities and special-purpose districts). At the state level, California's Unruh Civil Rights Act (Cal. Civ. Code section 51) incorporates ADA violations into state law, allowing plaintiffs to recover statutory damages of at least $4,000 per violation per visit in state court. The combination has made California the highest-volume state in the country for digital accessibility cases. This page covers what the rules require, what California-specific exposure looks like, and how to test your site against the standard.
Short answer: if your entity is a California city, county, special district, state agency, K-12 district, community college, CSU, or UC campus, you are covered by DOJ Title II and must meet WCAG 2.1 Level AA on your website by April 24, 2026 (population 50,000+) or April 24, 2027 (smaller). California's Unruh Civil Rights Act adds a parallel private right of action with statutory damages, so the litigation pressure is higher in California than in most other states. The fix is to audit your site against WCAG 2.1 Level AA, remediate the findings, and document the work. Site Brace runs that audit for $149 flat. Try a free single-page check on your homepage first.
The federal Title II deadlines:
- April 24, 2026: public entities (state and local government) serving populations of 50,000 or more.
- April 24, 2027: public entities serving populations under 50,000, and all special-purpose districts regardless of population.
Both deadlines apply to website content and mobile apps. WCAG 2.1 Level AA is the named conformance standard. Source: 28 CFR Part 35, published in the Federal Register April 24, 2024.
The two rules that apply in California
1. ADA Title II (federal)
The Americans with Disabilities Act Title II applies to all state and local government activities. The DOJ's April 2024 final rule made the web-content requirements explicit: covered entities must ensure web content and mobile apps conform to WCAG 2.1 Level AA, with the deadlines listed above. The rule covers entity-operated content, third-party content used in the entity's services (e.g., embedded videos, embedded forms), and content password-protected behind logins.
Exceptions in the rule are narrow: archived content posted before the compliance date that is not actively used, preexisting conventional electronic documents (PDFs, Word docs) created before the compliance date unless actively used, and content posted by third parties whose presence is unauthorized.
2. Unruh Civil Rights Act (California state)
The Unruh Civil Rights Act, codified at California Civil Code section 51, prohibits discrimination by business establishments and incorporates ADA violations as Unruh violations. The remedy provisions at Cal. Civ. Code section 52 set statutory damages at no less than $4,000 per violation. California courts have applied Unruh to both private-sector ADA Title III cases (commercial websites) and to public-entity websites where the entity operates as a business establishment.
The practical effect: a California plaintiff can sue under both the federal ADA and Unruh in the same complaint. Where federal ADA enforcement focuses on injunctive relief and attorney's fees, Unruh adds the $4,000-per-violation statutory damages floor. Plaintiff-side firms in California have built repeat-filer practices around this multiplier, with the same plaintiff filing dozens of cases against different entities over a year. A single ADA claim under Unruh on a high-volume site is rarely a single $4,000 outcome - the per-visit multiplier and the fees can push settlement values into five and six figures.
Which California entities are covered
Coverage is broad. The DOJ Title II rule covers any state or local government entity. In California that includes:
- All 482 incorporated cities and 58 counties
- State agencies, boards, and commissions
- The University of California (10 campuses), California State University (23 campuses), California Community Colleges (116 colleges)
- K-12 districts (over 1,000 districts)
- Special districts (water, fire, transit, library, healthcare, recreation, etc.)
- Joint powers authorities
- California Department of Technology and the technology functions it operates
The population threshold determines which deadline applies. A city with 60,000 residents has until April 24, 2026; a town with 12,000 has until April 24, 2027. The threshold is measured by the entity's served population, which for cities and counties is straightforward and for special districts may need separate calculation.
What we typically find on a California municipal site
Across California public-entity sites Site Brace has scanned (or that we have reviewed in published lawsuit complaints), the same WCAG failures recur.
| Finding | axe-core rule | Typical cause |
|---|---|---|
| Untagged PDFs (council agendas, meeting minutes, RFPs, permit forms) | Manual finding (axe does not test PDF interiors) | PDFs exported from Word without accessibility tagging |
| Color contrast on the navigation, calls to action, and table cells | color-contrast |
Vendor-provided CMS template colors (CivicPlus, Granicus, etc.) that fail 4.5:1 |
| Form fields without labels on permit applications, service requests, comment forms | label |
Custom form builders or vendor form tools that style placeholder text as label |
| Calendar widgets and meeting agendas not keyboard-reachable | Manual finding | Third-party agenda-management vendors that produce inaccessible widgets |
| Streaming-video meeting archives without captions | Manual finding | Live-streamed council meetings posted to the site without post-production captioning |
| "Translate" tools generating low-contrast or unlabeled output | color-contrast, label |
Google Translate widget or similar inserted without accessibility verification |
| aria-label on generic elements | aria-prohibited-attr |
CMS theme customizations or accessibility-overlay injection. See aria-label on a div. |
| Heading hierarchy mistakes on department pages | heading-order |
CMS WYSIWYG editors that allow staff to skip heading levels |
The PDF category is the largest in volume for most California public entities because the entity is required to publish meeting agendas, packets, and minutes for every public body it operates, and those documents are typically generated as PDFs without accessibility tagging. PDF remediation is a separate workstream from the HTML audit but the audit will list the affected pages so the entity knows where the PDF exposure sits.
Why overlays are an especially bad bet for a California public entity
Accessibility-overlay vendors (accessiBe, UserWay, AudioEye, EqualWeb) are marketed heavily to municipal and special-district websites. We have written about why accessibility overlays do not actually make sites WCAG-compliant in detail. For California public entities specifically, three additional factors make overlays a poor fit:
- Title II is a substantiation regime under DOJ enforcement, not a marketing claim. The DOJ can request evidence of WCAG conformance during a Section 504 or Title II investigation. An overlay subscription is not evidence; the underlying HTML is what the regulator tests.
- Unruh damages accrue per visit. An overlay that fails to fix the underlying issue does not stop the per-visit statutory damages from accruing every time a plaintiff visits the site.
- The FTC fined accessiBe $1 million in April 2025 for marketing the kind of compliance claim the overlay category has been making. A California entity citing an overlay subscription as evidence of compliance in response to a DOJ investigation or an Unruh complaint would have a thin defense.
How Site Brace audits a California public-entity site
The standard page mix for a municipal audit covers the high-risk surfaces:
- Homepage
- Department landing pages (top 4-6: Public Works, Planning, Finance, Police/Fire, Parks and Recreation, City Manager)
- City Council or governing body page (agendas, minutes, members)
- Most-trafficked service pages (permits, utility billing, business licenses, code enforcement)
- Public records request page
- Calendar / public meeting page
- Translate / language access page (if applicable)
- ADA accessibility statement page (if one exists)
- Privacy policy, terms of use, contact
That mix covers up to 25 pages depending on the entity's specific structure. The audit runs axe-core 4.10 against each page, captures element-level screenshots of every contrast failure, and packages the findings into a written report with copy-paste fix code and 12 re-scans included over 12 months.
Pricing is $149 flat, one-time. To see what the report looks like, view a sample report we built for a fictional municipality. The findings, the LLM prompts, and the verification steps are representative of what a California public-entity report contains.
Want to check your own site first? Run a free single-page check on your homepage or your most-trafficked service page - one URL, about a minute, no signup needed to see the result.
Notes for entities on common California municipal CMS platforms
Most California cities and counties run on one of a small set of municipal-CMS vendors: CivicPlus, Granicus (formerly Vision), OpenCities, Streamline, OpenGov, or a custom WordPress/Drupal install. Each platform has its own accessibility profile. The audit findings are vendor-agnostic (axe-core tests the rendered page regardless of platform), but the remediation path depends on whether you can edit the theme directly or are limited to vendor-provided customization options. If your audit surfaces a finding that is structural to the vendor template, the fix may need to come from the vendor as a platform update rather than from your IT staff.
Start a California public-entity audit, $149
Related:
- DOJ Title II web rule primer - what the federal rule says and what to do
- Free single-page WCAG check
- Why accessibility overlays do not make sites WCAG-compliant
- axe-core vs WAVE vs Lighthouse