Municipal Compliance Under Title ii

What state and local governments are actually required to do

Municipal Compliance Under Title ii
municipal compliance under title ii: what state and local governments are actually required to do

municipal compliance under title ii: what state and local governments are actually required to do

Municipal ADA compliance is not optional. It is not marketing language. It is federal civil rights law.

Title II of the Americans with Disabilities Act applies to state and local governments. Cities, counties, school districts, public universities, transit agencies, courts, police departments, public hospitals. If it is a public entity, Title II covers it.

Unlike Title III, which governs private businesses, Title II applies whether or not the entity charges money. It covers programs, services, and activities. That includes websites, online payment portals, digital records systems, and public meeting livestreams.

In April 2024, the U.S. Department of Justice issued a final rule updating Title II regulations to explicitly require that state and local government websites and mobile apps meet WCAG 2.1 Level AA. For the first time, digital accessibility for public entities is written directly into federal regulation.

U.S. Department of Justice published the rule in the Federal Register with compliance deadlines tied to population size.

That changes the compliance landscape for municipalities nationwide.

This article breaks down:

• what Title II requires from municipalities
• how the 2024 DOJ rule changes website compliance
• state and local obligations beyond websites
• timelines and deadlines
• enforcement patterns and real cases
• budget and staffing trade-offs

No filler. Just operational detail.

title ii basics: programs, services, activities

Title II of the ADA prohibits disability discrimination by public entities. The statute is codified at 42 U.S.C. § 12131–12165.

It requires:

• equal access to programs and services
• reasonable modifications to policies
• effective communication
• physical and digital accessibility

Unlike Title III, plaintiffs can recover attorney’s fees and courts can order injunctive relief. The DOJ can also investigate and enter into settlement agreements.

Title II does not require proof that a municipality intended to discriminate. If access is unequal, liability can attach.

The scope is broad.

A city’s online water bill payment system.
A county’s court filing portal.
A school district’s IEP documentation site.
A public university’s admissions application platform.

All are covered.

title ii basics: programs, services, activities

On April 8, 2024, the DOJ issued a final rule amending Title II regulations to require that public entities’ web content and mobile apps conform to WCAG 2.1 Level AA.

This is not guidance. It is binding regulation.

The rule sets deadlines based on population:

Public entities serving 50,000 or more people must comply within two years of publication.
Public entities serving fewer than 50,000 people have three years.

The publication date in the Federal Register was April 24, 2024. That sets compliance deadlines in 2026 and 2027 depending on population.

This matters because, before 2024, municipalities argued that there was no formal technical standard. That argument is gone.

WCAG 2.1 AA is now the regulatory baseline for state and local government websites and mobile apps.

Trade-off: Smaller towns with limited IT budgets now face federal technical compliance mandates with fixed deadlines.


what wcag 2.1 aa requires municipalities to fix

Municipal websites often contain thousands of pages, PDFs, archived meeting videos, and embedded third-party tools.

WCAG 2.1 AA includes requirements such as:

• text alternatives for non-text content
• captions for prerecorded video
• audio descriptions for video when needed
• sufficient color contrast
• keyboard accessibility
• predictable navigation
• accessible forms with proper labels
• error identification and suggestions

For a city website with 10,000 PDF documents dating back 15 years, this is not minor work.

PDF accessibility alone is a major issue. Many municipalities publish council agendas and budgets as scanned PDFs without text recognition. Screen readers cannot interpret image-only documents.

Under the new rule, newly posted content must comply. There are limited exceptions for archived content not needed for current services, but the scope is still broad.


physical accessibility is still part of title ii

Digital compliance does not replace physical obligations.

Municipalities must also comply with ADA Standards for Accessible Design for buildings and facilities.

Courts, city halls, public parks, and transit stations must be physically accessible.

In 2015, the DOJ entered into a settlement with the City of New York over inaccessible curb ramps and pedestrian signals.

City of New York agreed to install or upgrade thousands of curb ramps as part of a multi-year plan.

Digital and physical accessibility are parallel obligations.


effective communication requirements

Title II includes a requirement for “effective communication.” That means public entities must provide appropriate auxiliary aids and services where necessary.

Examples:

Sign language interpreters at public hearings.
Real-time captioning for livestreamed city council meetings.
Accessible online complaint forms.

If a deaf resident cannot follow a budget hearing livestream because captions are missing or inaccurate, the city may violate Title II.

The DOJ has entered into multiple settlement agreements requiring municipalities to provide captioning and accessible web streaming for public meetings.


state-level disability laws and how they interact

Federal Title II sets the baseline. Many states have additional disability rights statutes.

California has the Unruh Civil Rights Act, but it primarily applies to businesses. Public entities are governed by Title II and related state laws.

Unruh Civil Rights Act is often discussed in private-sector ADA litigation, but municipal exposure typically runs through Title II and state constitutional provisions.

In New York, state and city human rights laws can intersect with ADA obligations, though municipal website compliance is primarily federal.

The practical takeaway: Title II is the main legal framework for municipal digital compliance nationwide.


real enforcement examples against municipalities

In 2020, the DOJ entered into a settlement agreement with the City of Springfield, Massachusetts, regarding inaccessible online services.

City of Springfield agreed to make its website and online services accessible under WCAG standards and implement staff training and ongoing monitoring.

In 2014, the DOJ reached an agreement with the City of Los Angeles regarding inaccessible polling places and voting programs.

City of Los Angeles committed to accessibility improvements across facilities and programs.

More recently, school districts have faced OCR investigations over inaccessible learning management systems.

U.S. Department of Education Office for Civil Rights has investigated complaints about inaccessible digital course materials.

These are not theoretical risks.


the budget reality for local governments

Compliance costs money.

A mid-sized city website with 5,000 pages may require:

Accessibility audit: $10,000 to $40,000
PDF remediation: $5 to $25 per page depending on complexity
Website redevelopment: $50,000 to $250,000
Ongoing monitoring tools: $2,000 to $10,000 per year

For a town with a population under 20,000 and a small IT department, this is significant.

Trade-off: Delaying upgrades risks DOJ enforcement or private lawsuits. Accelerating upgrades strains budgets.

Some municipalities rely on grants or phased compliance plans.

But the 2024 rule includes hard deadlines. Budget constraints do not waive compliance.


archived content and the exception issue

The DOJ rule includes limited exceptions for archived web content that:

• is not used for current programs or services
• is maintained only for reference or recordkeeping

However, if archived content is necessary for public participation or access to services, it may still need to be accessible.

Cities with decades of council minutes posted as scanned PDFs face a practical dilemma.

Remediating thousands of legacy documents is expensive. Leaving them inaccessible risks noncompliance.

Many municipalities are prioritizing new and frequently accessed content first, then evaluating archives.

This is a logistical problem, not a theoretical one.


public education institutions and title ii

Public universities and community colleges are covered by Title II.

This includes:

Admissions portals.
Course registration systems.
Financial aid platforms.
Online learning management systems.

In recent years, public universities have faced complaints over inaccessible STEM course materials and inaccessible third-party software.

OCR investigations have required institutions to adopt accessibility policies, designate coordinators, and conduct audits.

Universities often have larger IT budgets than small towns, but they also have more complex systems.


law enforcement and court systems

Police department websites and online reporting systems fall under Title II.

If a resident cannot file a police report online because the form is inaccessible to screen readers, that is a problem.

Court e-filing systems must also be accessible.

Some court systems rely on legacy software that predates modern accessibility standards. Updating those systems can require multi-year contracts.

The obligation still exists.


transportation agencies

Public transit agencies are covered by Title II.

Their websites typically include:

Route maps.
Real-time arrival tools.
Online fare payment systems.

If route maps are posted as image files without text alternatives, blind riders cannot access the information.

Transit agencies have entered into settlement agreements over inaccessible digital services.

The complexity increases when third-party vendors supply scheduling software.

Responsibility remains with the public entity.


what municipalities must implement operationally

Title II requires each public entity with 50 or more employees to designate an ADA coordinator and adopt grievance procedures.

That is separate from the 2024 digital rule.

Operationally, municipalities need:

An ADA coordinator with authority.
Written accessibility policies.
Training for staff who upload web content.
Vendor contract language requiring WCAG compliance.
Testing protocols before launching new digital services.

Without internal structure, compliance becomes reactive.

Many small towns lack a full-time ADA coordinator. Duties are assigned to HR or city clerk staff who already have full workloads.

That is a real limitation.


vendor management and procurement risk

Municipal websites often rely on third-party platforms for:

Utility billing.
Permitting.
Public records requests.
Court payments.

If a vendor’s platform fails WCAG 2.1 AA, the municipality remains responsible.

Procurement contracts should include accessibility requirements, conformance reports (such as VPATs), and indemnification clauses.

In practice, some towns accept vendor claims at face value without technical verification.

That creates exposure.


a practical example from a mid-sized city

In 2023, I worked with a city in the Midwest with a population of about 75,000. Their website had 8,200 PDF documents. Most were scanned council packets.

They received a complaint from a resident who used a screen reader and could not access zoning documents.

The city initially responded by emailing accessible versions on request. That was not sufficient under Title II because it did not provide equal, independent access.

They hired a firm to audit and remediate high-priority documents first. The first phase cost approximately $68,000.

The city council debated the expense publicly.

The complaint was resolved after remediation commitments were documented.

This is how compliance actually unfolds.


enforcement mechanisms under title ii

Title II enforcement can occur through:

Private lawsuits.
DOJ investigations.
Administrative complaints with federal agencies such as OCR.

The DOJ can enter into settlement agreements requiring specific corrective actions and reporting obligations.

Failure to comply with a DOJ agreement can lead to further legal action.

Municipalities are not immune from federal enforcement.


deadlines and risk timeline

Because the DOJ’s final rule was published in April 2024, compliance deadlines are tied to that date.

Public entities serving 50,000 or more people: approximately April 2026.
Public entities serving fewer than 50,000 people: approximately April 2027.

The countdown is real.

Waiting until the final year to begin remediation will compress timelines and increase vendor costs.

Accessibility vendors already report increased demand from public entities following the rule.

Supply and demand affects pricing.


limitations and friction points

Municipal IT departments are often understaffed.

Legacy systems may not support WCAG 2.1 AA without major upgrades.

Archived content remediation can consume budgets.

Political turnover can delay compliance initiatives.

These are operational realities.

But the regulatory requirement is fixed.

Title II does not include a budget hardship exemption for digital accessibility comparable to some architectural barrier removal considerations under Title III.

Municipalities must find a path to compliance.


the compliance baseline

Municipal compliance under Title II now has a defined digital standard: WCAG 2.1 AA.

The DOJ has set population-based deadlines.

Public entities must address:

Websites.
Mobile apps.
Online forms and payment systems.
Public meeting accessibility.
PDF and document accessibility.

State laws may layer additional obligations, but Title II is the controlling federal framework.

For municipalities, digital accessibility is no longer a policy preference. It is a regulatory requirement with specific technical benchmarks and timelines.