Title II Defense: For Governments

Most Title II actions don’t begin in court.

They start with complaints to the U.S. Department of Justice, the Office for Civil Rights, or state-level civil rights agencies.

Complainants don’t need lawyers. They don’t need money. They don’t need standing in the same way a federal plaintiff does.

That changes defense posture from day one.

Ignoring a complaint is not neutral. It’s read as noncooperation.

the legal standard governments face

Title II uses an “effective communication” standard.

The question is not whether a site meets WCAG line by line. The question is whether people with disabilities can access programs and services in a way that’s as effective as access for others.

Courts and regulators still use WCAG as a measuring stick. Usually WCAG 2.0 or 2.1 Level AA. Increasingly WCAG 2.2 shows up in investigations.

But the legal hook is effective communication. Not checklists.

That gives governments less wiggle room than private businesses.

sovereign immunity doesn’t save you

States sometimes assume sovereign immunity blocks ADA claims.

It doesn’t. Title II claims for injunctive relief move forward. Damages are limited in some contexts. Enforcement still happens.

Local governments don’t have that argument at all.

Defense strategies built on immunity waste time and irritate investigators.

how doj actually investigates title ii websites

DOJ investigations follow a pattern.

They request policies. Training records. Accessibility statements. Audit reports. Vendor contracts. Testing logs.

Then they test the site themselves or through contractors. Screen readers. Keyboard-only navigation. Mobile devices.

They don’t care if an overlay is installed. They don’t care about scores.

They care whether a blind resident can complete the task that triggered the complaint.

common trigger points for title ii complaints

Most Title II web complaints don’t involve obscure edge cases.

They involve:

Online utility payments
Court filing portals
Employment applications
School enrollment forms
Meeting agendas and PDFs
Public notices
Emergency alerts

These are high-impact services. When they fail, complainants don’t wait.

a real example from a city website

In 2022, a mid-sized U.S. city rolled out a new online permitting portal. The vendor promised accessibility support.

Blind users couldn’t submit applications. Required fields weren’t labeled. Error messages weren’t announced.

A resident filed a DOJ complaint. The city responded with screenshots of an accessibility widget.

DOJ asked for user testing evidence. There was none.

The city entered a settlement agreement requiring a full audit, remediation, staff training, and three years of reporting.

The widget stayed installed. It didn’t matter.

why overlays are worse for governments

Overlays are risky for private companies. They’re worse for governments.

Government sites carry implied authority. When a city posts an “accessible” badge or claims compliance, that statement carries weight.

If the claim is false, the exposure isn’t just ADA. It’s misrepresentation.

DOJ has explicitly rejected overlays as a substitute for accessibility. Installing one doesn’t show good faith. It shows misunderstanding.

That shows up in settlement language.

documentation is the core of title ii defense

Governments defend Title II cases with paper, not arguments.

Investigators want to see:

Accessibility policies adopted by leadership
Procurement language requiring accessibility
Training records for staff
Audit reports with dates
Remediation timelines
Ongoing monitoring processes

A government that fixes issues but can’t show process still loses leverage.

A government that shows process, even with gaps, negotiates better outcomes.

procurement is where most failures start

Cities don’t code everything. They buy systems.

Permitting software. Court systems. Payment processors. LMS platforms.

If procurement doesn’t require accessibility, vendors don’t deliver it. Then the city owns the failure.

DOJ doesn’t care that the vendor built it. The obligation sits with the government.

Contracts without accessibility clauses weaken every defense.

third-party platforms don’t shift liability

Governments often argue that third-party platforms control accessibility.

That argument fails.

If the government chooses the platform and requires residents to use it, the government is responsible.

DOJ settlements regularly require governments to fix or replace inaccessible third-party tools.

Blaming vendors delays resolution and increases monitoring requirements.

title ii timelines are long and expensive

Title II settlements last years.

Two-year remediation timelines are common. Three-year reporting periods aren’t rare. Annual audits. Status updates.

This isn’t a one-check problem. It’s a multi-year obligation.

Defense strategy has to account for that horizon.

the role of wcag in title ii defense

WCAG isn’t law. It’s still the standard.

DOJ, OCR, and courts rely on WCAG published by the World Wide Web Consortium because it’s specific and testable.

Governments that ignore WCAG invite vague enforcement. Governments that align to it control scope.

Most Title II settlements reference WCAG explicitly even though the statute doesn’t.

wcag 2.2 is already creeping in

WCAG 2.2 became a W3C Recommendation in October 2023.

DOJ hasn’t formally mandated it yet. Investigators are already referencing it in audits.

Focus appearance. Target size. Dragging alternatives.

Governments that remediate only to 2.0 or 2.1 now risk rework within the same settlement period.

That’s a trade-off. Remediate faster with older standards or remediate slower with newer ones.

training is not optional in practice

Most Title II settlements include training requirements.

Not one-time webinars. Role-based training. Recurrent training.

Designers. Developers. Content editors. Procurement staff.

DOJ understands that untrained staff recreate barriers. Training clauses exist to stop that loop.

Skipping training increases reporting burdens later.

internal resistance is predictable

Government teams push back.

Legacy systems. Budget cycles. Procurement rules. Union roles. Staffing limits.

DOJ doesn’t accept those as excuses. They shape timelines, not obligations.

Defense strategies that acknowledge constraints early get more flexibility. Denial doesn’t.

cost is real and unbalanced

Accessibility remediation costs money. Training costs money. Monitoring costs money.

There’s no dedicated federal funding stream for most Title II compliance work.

That’s the criticism. The mandate exists without matching resources.

Courts and DOJ don’t solve that. They enforce access anyway.

Defense planning has to account for funding gaps honestly.

emergency content failures carry higher risk

Emergency alerts, disaster updates, public health notices.

When these are inaccessible, DOJ responds faster. OCR responds faster. Media attention follows.

Title II defense fails fast in emergencies.

Governments that pre-remediate emergency channels face fewer penalties.

mobile apps are now routine targets

City apps. Transit apps. Campus apps.

Many were built years ago. Few were audited. Most rely on third-party SDKs.

DOJ treats apps the same as websites. Governments that ignore them create obvious exposure.

Defense strategies that exclude apps are incomplete.

accessibility statements can hurt or help

A vague accessibility statement does little.

A detailed statement with contact methods, known issues, and response timelines helps.

DOJ looks at whether complaints were answered and resolved before escalation.

Silence hurts. Overpromising hurts more.

monitoring is part of defense, not a bonus

Title II defense assumes sites change.

Weekly or monthly automated scans. Periodic manual testing. Documented fixes.

Monitoring shows intent to maintain access.

Governments without monitoring look negligent even after remediation.

record retention matters

Governments already retain records. Accessibility records need retention too.

Training logs. Audit reports. Vendor correspondence. Issue trackers.

When complaints arrive years later, missing records weaken defense.

This is boring. It’s also decisive.

what title ii defense does not do

It does not eliminate violations.
It does not guarantee no complaints.
It does not prevent enforcement.
It does not replace remediation.

Defense manages damage. It doesn’t erase duty.

why waiting for final rules fails

Governments often wait for DOJ to issue formal web accessibility regulations.

Those rules have been “coming” for years.

Enforcement didn’t wait. Complaints didn’t wait. Settlements didn’t wait.

Defense based on waiting fails every time.

the actual shape of effective title ii defense

Policies adopted and enforced.
Procurement language with teeth.
Audits that lead to fixes.
Training that changes behavior.
Monitoring that catches regressions.
Documentation that survives scrutiny.

None of this is elegant. All of it is practical.

the uncomfortable reality

Title II compliance is not optional. Defense is not adversarial theater. It’s administrative survival.

Governments that treat accessibility as a side project lose leverage. Governments that treat it as infrastructure negotiate better outcomes.

That’s not theory. It’s how DOJ has enforced Title II for years.

End.