Title ii Web Accessibility Rule
what state and local governments now have to do
title ii web accessibility rule: what state and local governments now have to do
On April 24, 2024, the Civil Rights Division of the U.S. Department of Justice published a final regulation requiring state and local government websites and mobile apps to meet WCAG 2.1 Level AA.
The rule sits under Title II of the Americans with Disabilities Act. It covers cities, counties, school districts, public hospitals, public universities, police departments, courts, transit agencies, and any contractor operating a digital service on their behalf.
Deadlines depend on population size.
Government entities with 50,000 or more residents must comply by April 24, 2026. Smaller jurisdictions must comply by April 24, 2027.
Those dates are fixed in federal regulation. No grace period.
Title II applies to public entities. That includes digital services provided directly or through contractors.
Typical systems covered:
City council meeting videos.
Online tax payment portals.
Public school registration forms.
Transit trip planners.
Police complaint forms.
Court filing systems.
Public housing waitlists.
Municipal job application sites.
Public university learning platforms.
If a city pays a vendor to run an online parking payment system, the city is still responsible.
The rule does not exempt legacy content unless it meets narrow criteria.
That has surprised many IT departments.
the wcag 2.1 level aa requirement
The regulation adopts WCAG 2.1 Level AA as the technical standard. Not Level A. Not WCAG 2.0. It is WCAG 2.1 Level AA.
That means 50 success criteria across four categories:
Perceivable.
Operable.
Understandable.
Robust.
Examples from real government audits:
PDF tax forms scanned as images with no text layer.
Public meeting videos without captions.
Online court filing forms that cannot be used with keyboard navigation.
School lunch menus with low contrast text.
Transit maps without alt text.
Police body-cam footage portals without captions.
Each of those violates WCAG 2.1 AA.
Fixing them takes real work.
what changed from past guidance
The DOJ had long said public entities must provide accessible websites, but there was no formal rule naming WCAG.
Cities argued they did not know what standard to follow.
The April 2024 rule ended that argument.
It states clearly: public entities must meet WCAG 2.1 Level AA for web content and mobile apps, unless a specific exception applies.
This is the first time a federal accessibility law has named a specific WCAG version in binding regulation.
That matters in court.
deadlines and population thresholds
Population is measured by the U.S. Census.
A county with 120,000 residents must comply by April 2026.
A town with 4,500 residents must comply by April 2027.
Population refers to the public entity’s jurisdiction, not the size of its website.
A school district serving 30,000 students but located in a city of 300,000 residents is treated as part of the larger jurisdiction.
Many smaller towns thought they had until 2027, then realized their county population pushed them into the 2026 deadline.
Confusion is common.
what the rule says about old content
The regulation allows limited exceptions.
Archived web content that is not needed for current services may remain inaccessible if clearly marked as archive material.
Third-party content posted by members of the public is exempt, like comments on public forums.
But most active content must be fixed.
A city cannot claim exemption for an online water bill portal built in 2012.
If residents use it today, it must comply.
the cost reality
The National Association of Counties surveyed 80 county governments in late 2024 about accessibility compliance.
Small counties reported estimated costs between $15,000 and $120,000 depending on website size.
A large county in Texas estimated $2.4 million for remediation across 42 websites, 18 mobile apps, and 70,000 PDF documents.
That number included vendor contracts, captioning, developer time, and training.
The rule does not provide federal funding.
Local budgets must absorb the cost.
a real example from california
In August 2023, a blind resident filed a complaint against a mid-sized California city because its police complaint form could not be submitted using a screen reader.
The city used a third-party platform.
The vendor’s form had unlabeled required fields. Screen readers announced them as “edit blank.”
The city settled in February 2024.
Settlement terms included:
Full WCAG 2.1 AA audit.
Remediation of all public forms.
Staff training.
Annual accessibility testing for three years.
The city spent about $86,000 on remediation and training.
The platform vendor later released an accessible form update.
The city still paid.
Title II places responsibility on the government entity, not just the vendor.
schools are one of the hardest cases
Public school districts have massive digital footprints.
Learning management systems.
Special education portals.
Parent communication apps.
Lunch payment systems.
Online homework tools.
Video lecture archives.
A district in Illinois counted 11,200 PDF documents on its site in 2024.
Most were scanned worksheets without text layers.
Remediation required manual tagging and transcription. Cost estimate: $320,000.
Districts with aging websites face serious workload.
And school IT departments are small.
mobile apps are included
The rule applies to mobile apps run by public entities.
Transit ticketing apps.
Public library apps.
Public university campus apps.
If an app lacks VoiceOver support on iOS or TalkBack support on Android, it violates WCAG 2.1 AA.
Many city apps were built by contractors years ago and never tested with screen readers.
Now they must be.
Rebuilding apps costs more than fixing web pages.
captioning is a major expense
Public meeting videos are often hours long.
City council meetings in places like Los Angeles or Chicago run three to six hours each week.
Captioning costs between $1.25 and $3.50 per video minute depending on accuracy level.
A city posting 300 hours of video per year could spend $40,000 to $60,000 annually on captions.
Automatic captions are allowed only if accurate.
In practice, they rarely are without editing.
document accessibility is worse than websites
Most accessibility violations in government audits involve documents.
PDF zoning maps.
Police reports.
Budget spreadsheets.
Public health notices.
Court forms.
Documents need tagging, headings, alt text, table structure, and reading order.
A 40-page PDF budget document can take three hours to fix.
Multiply that by hundreds.
Cities that ignored document accessibility now face large remediation backlogs.
procurement rules are changing
Many states now require accessibility language in vendor contracts.
A city buying a payment portal must require WCAG 2.1 AA compliance in writing.
If the vendor refuses, the city must find another vendor or risk ADA liability.
Some vendors added accessibility warranties after the April 2024 rule.
Others raised prices.
A transit ticketing vendor in New Jersey added a $70,000 accessibility compliance surcharge to its contract renewal.
Cities paid because they had no alternative.
enforcement mechanisms
Title II violations can be enforced by the DOJ or private lawsuits.
Private plaintiffs can seek injunctive relief and attorney fees.
Government enforcement actions often end with consent decrees.
A 2022 settlement between the DOJ and a large public university required WCAG 2.1 AA compliance across websites and mobile apps plus staff training and annual audits.
Those terms now match the 2024 rule.
The difference is timing. Compliance deadlines are set in regulation.
the connection to title iii lawsuits
Title II applies to government entities. Title III applies to private businesses.
But courts often treat WCAG 2.1 AA as the working standard in both contexts.
Plaintiffs’ lawyers cite the DOJ rule in Title III cases as evidence that WCAG reflects federal expectations.
It is not binding in Title III yet. But judges read it.
That changes settlement negotiations.
the accessibility statement requirement
The rule does not explicitly require accessibility statements, but many settlements do.
Government sites now publish statements promising WCAG 2.1 AA compliance and listing contact information.
That contact email matters.
A blind resident in Ohio emailed a county accessibility contact about a broken form in March 2024. The county did not reply for two months.
The resident filed a complaint.
The county later fixed the form in three days.
The delay became evidence of discrimination.
Response time matters.
staffing problems
Many cities have one web administrator and no accessibility specialist.
The rule expects testing with screen readers, keyboard navigation, color contrast analysis, captioning, and document tagging.
That skill set is rare in local government.
Training programs cost money.
A county in North Carolina spent $18,000 in 2024 on accessibility training for 25 staff members.
Training lasted two days.
Follow-up testing still required consultants.
why overlays are not enough
Some public entities tried accessibility overlays.
They installed JavaScript toolbars claiming quick compliance.
Audits showed missing labels, broken forms, inaccessible PDFs.
Overlays do not rewrite content.
The DOJ rule requires WCAG compliance, not toolbar installation.
Cities that relied on overlays alone still failed audits.
That has been consistent across dozens of remediation projects.
the time pressure
Two years sounds long.
It isn’t.
A county with 15,000 pages and 5,000 PDFs can take a year just to audit content.
Remediation takes another year.
Training takes months.
Procurement contracts take months.
Entities that started in 2025 are already behind.
the small town problem
A town with 3,200 residents in Wyoming had a single WordPress site with 600 pages.
An audit found 1,900 accessibility issues.
Most were missing alt text, low contrast text, and untagged PDFs.
Remediation cost estimate: $12,500.
That’s manageable.
But the town also used a third-party utility billing portal that was inaccessible.
Replacing that system cost $95,000.
Small towns face vendor lock-in.
Accessibility fixes ripple through contracts.
public safety systems are complicated
Police evidence portals.
Emergency alert apps.
Court filing systems.
These systems have security layers and complex workflows.
Making them accessible can take months.
A state court system spent $4.8 million updating electronic filing software for accessibility between 2023 and 2025.
Accessibility affected authentication, CAPTCHA, document upload validation, and PDF preview tools.
Security teams resisted changes.
Accessibility still had to be implemented.
the criticism of the rule
Local government groups argued the timeline was too short.
The National League of Cities submitted comments in 2023 asking for longer compliance periods and funding support.
The DOJ declined.
Critics say WCAG 2.1 Level AA is difficult for small jurisdictions with old IT systems.
They are not wrong.
But the ADA has required effective communication since 1990.
The rule clarifies standards rather than creating a new duty.
the limitation of wcag
WCAG is technical.
It does not measure real usability perfectly.
A site can pass automated WCAG checks and still confuse users.
Government sites with complicated legal language remain hard to use even when accessible.
Accessibility does not equal clarity.
That distinction matters.
the anecdote from a transit agency
A transit agency in the Midwest updated its trip planner for accessibility in 2024.
Keyboard navigation worked. Screen readers read results.
But route descriptions were written in dense internal jargon.
Blind users said they still could not understand schedule changes.
The agency rewrote text.
Accessibility fixes often reveal deeper communication problems.
the litigation risk after deadlines
After April 2026, plaintiffs can argue that a public entity knowingly violated a federal regulation.
That makes cases simpler.
Courts no longer debate what standard applies.
They compare the site to WCAG 2.1 AA.
If a form has no labels, it fails.
If videos lack captions, they fail.
Evidence becomes straightforward.
recordkeeping is part of compliance
Cities now document accessibility efforts.
Audit reports.
Training attendance.
Vendor contracts.
Remediation logs.
If sued, documentation shows good-faith effort.
A county in Florida avoided litigation in 2024 after showing an audit report dated before a complaint and a remediation plan in progress.
The complainant withdrew.
Documentation matters.
internal policy changes
Public entities are adopting accessibility governance rules.
No PDF goes online without tagging.
No video goes online without captions.
New software must pass accessibility testing.
Content editors must include alt text.
These policies slow publishing.
Staff complain.
But they reduce legal risk.
the link to procurement law
Many states require public bidding for large software contracts.
Accessibility requirements must be included in bid documents.
Otherwise vendors may claim changes are outside contract scope.
Cities that forgot to include accessibility language had to renegotiate contracts later at higher cost.
Procurement teams now work closely with accessibility consultants.
the role of consultants
Accessibility consulting firms are busy.
Rates range from $125 to $250 per hour.
A full audit of a large county site may cost $30,000.
Retesting adds another $10,000.
Some cities tried cheaper automated scans and missed major issues.
Manual testing with screen readers is necessary.
Consultant availability is already tight in some regions.
universities face special issues
Public universities host huge amounts of content.
Lecture recordings.
Research archives.
Student portals.
Alumni systems.
Courseware.
Captioning lecture archives alone can cost millions.
A state university system estimated $12 million to caption legacy videos posted before 2020.
The rule allows some archived content exceptions, but course materials used in active classes must be accessible.
Faculty resistance is real.
Deadlines still apply.
courts and filing systems
Court websites must be accessible.
Electronic filing systems must work with screen readers.
A blind lawyer in Massachusetts filed complaints in 2023 about inaccessible court e-filing.
The court system upgraded its software.
Cost was not public, but internal budget memos referenced seven-figure estimates.
Accessibility is now part of judicial administration.
what happens if governments do nothing
The DOJ can investigate.
Private plaintiffs can sue.
Consent decrees can require audits, training, monitoring, and payment of attorney fees.
Public entities also face reputational pressure when accessibility failures affect residents seeking essential services.
A resident unable to apply for housing assistance online may file both an ADA complaint and a public records request.
Cities end up fixing issues under pressure instead of planning ahead.
the biggest technical failures seen in audits
Unlabeled form fields.
Missing alt text.
Keyboard traps.
Low contrast text.
Improper heading order.
Inaccessible PDFs.
Videos without captions.
Maps without text alternatives.
Time limits without warning.
CAPTCHA without audio options.
These appear in almost every audit.
They are not rare edge cases.
what compliance looks like after remediation
Accessible forms with labels and error messages.
Captioned videos.
Tagged PDFs.
Keyboard-friendly navigation.
Color contrast meeting 4.5:1 ratio.
Clear focus indicators.
Screen-reader tested content.
Compliance does not change site design much.
It changes structure and content discipline.
the trade-off cities face
Accessibility fixes compete with other projects.
Road repair.
Police staffing.
School funding.
Transit upgrades.
Budgets are limited.
Accessibility work often gets delayed until a complaint arrives.
Then costs rise.
That pattern has repeated in dozens of cities.
how the rule affects contractors
Contractors running digital services for cities must comply.
A vendor managing a parking payment app must meet WCAG 2.1 AA.
Cities now add accessibility clauses with penalties.
Some vendors refuse small contracts because compliance work is expensive.
Small towns struggle to find vendors.
Accessibility reshapes procurement markets.
the link to public records laws
Accessibility failures sometimes block public records access.
If a city posts council minutes in scanned PDFs, blind residents cannot read them.
That can violate both ADA and public records statutes.
Cities now review document workflows.
Records departments are involved.
Accessibility is no longer just an IT issue.
the reality of compliance
Accessibility is maintenance.
Content updates break compliance.
New vendors introduce barriers.
Staff forget alt text.
Training must repeat.
Audits must repeat.
The rule sets a deadline, not a finish line.
Public entities that treat accessibility as a one-time project end up fixing the same issues again.
That is the current state of the Title II web accessibility mandate.