ADA Priority Fixes

Plaintiffs don’t win by pointing at a missing alt attribute in isolation. They win by showing they couldn’t complete a task.

That task might be:

• Scheduling an appointment
• Submitting a contact form
• Completing a purchase
• Accessing account information

Courts care about denial of access. Tools don’t.

This is why ADA compliance work that starts with automated scans usually fails under pressure. It optimizes for reports, not for use.

What shows up most often in complaints

Across hundreds of complaints filed between 2020 and 2025, the same failures repeat. Different industries. Same problems.

Keyboard access failures come first.

A user presses Tab and gets stuck. Or focus disappears. Or a modal opens and traps them inside with no escape. These are not edge cases. They’re routine failures in modern JavaScript-heavy sites.

Screen reader users then hit unlabeled controls. Buttons announced as “button.” Links announced as “click here.” Form fields with no programmatic name.

After that, error handling. Forms submit. Nothing happens. Or something happens visually, but nothing is announced. The user thinks the site froze.

These are priority lawsuit fixes because they stop task completion cold.

Automated tools don’t see most of this

Automated scanners are good at syntax. They’re bad at experience.

They can tell you if an input lacks a label. They can’t tell you if the label makes sense in context. They can tell you if contrast ratios pass. They can’t tell you if placeholder text disappears and leaves the field unusable.

Most automated tools catch maybe 30 percent of WCAG 2.1 AA failures. That number comes from repeated comparisons between tool output and manual audits across retail, healthcare, professional services, and automotive sites.

That missing 70 percent is where lawsuits live.

The false comfort of high Lighthouse scores

Google Lighthouse accessibility scores get waved around like proof. A score in the high 90s looks reassuring. It shouldn’t.

Lighthouse checks a narrow slice of WCAG success criteria. It doesn’t test keyboard workflows. It doesn’t test screen reader output. It doesn’t test dynamic error messaging.

A site can score 100 and still block a blind user from checking out.

Plaintiffs’ attorneys know this. They don’t care about Lighthouse screenshots.

Priority fix one: keyboard access through real workflows

Keyboard access is not theoretical. It’s physical. A user presses Tab. Something should happen. Predictably.

Priority fixes here include:

• Logical focus order that matches visual order
• Visible focus indicators that aren’t removed by CSS resets
• No keyboard traps in menus, modals, or carousels
• Escape paths from overlays and dialogs

In a 2024 case involving a regional service provider in the Midwest, the entire complaint centered on a scheduling widget. The widget opened in a modal. Focus entered. Focus never left. The user couldn’t reach the close button.

The rest of the site didn’t matter. Standing was established on that failure alone.

Priority fix two: screen reader names, roles, and states

Screen readers rely on programmatic information. Visual clues don’t help.

Common failures that appear in complaints:

• Buttons without accessible names
• Icons used as controls without labels
• Custom components with no ARIA roles
• State changes not announced

A toggle that visually switches from “off” to “on” but never announces that change is functionally broken for a screen reader user.

This is not about adding ARIA everywhere. Bad ARIA makes things worse. It’s about using native elements where possible and exposing state changes when custom components are unavoidable.

Priority fix three: forms that actually communicate errors

Forms are lawsuit magnets.

The pattern is consistent. A user fills out a form. Submits it. The page reloads or updates. Errors appear in red text. Nothing is announced.

From the user’s perspective, the site did nothing.

Priority fixes include:

• Programmatic association between errors and fields
• Error summaries that receive focus
• Live region announcements for validation feedback

In a 2023 settlement involving a healthcare provider in California, the remediation list focused almost entirely on intake forms. Not the homepage. Not marketing pages. Forms.

Priority fix four: dynamic content announcements

Modern sites change without page reloads. Screen readers don’t notice unless told.

Shopping carts update. Prices change. Availability messages appear. None of it matters if it’s silent.

ARIA live regions exist for a reason. They’re rarely implemented correctly.

Priority fixes here include:

• Announcing added or removed cart items
• Announcing success or failure messages
• Announcing loading states when actions take time

These aren’t nice extras. They’re the difference between a usable site and a broken one.

Priority fix five: third-party tools are not exempt

This is where many vendors quietly stop.

Scheduling systems. Chat widgets. Payment processors. Inventory feeds. If it’s embedded, it’s in scope.

Plaintiffs don’t care who built it. Courts don’t either.

A common defense argument is “we don’t control that vendor.” That argument loses regularly.

Priority fixes require either selecting accessible vendors or providing accessible alternatives. Ignoring the issue doesn’t work.

The overlay problem no one likes to admit

Accessibility overlays show up in a large number of sued sites. They don’t prevent lawsuits. Sometimes they’re cited as part of the problem.

Overlays don’t fix underlying code. They don’t change keyboard traps. They don’t add proper labels to complex widgets. Some interfere with screen readers.

There’s a reason many complaints explicitly mention them. They give a false sense of coverage while leaving priority failures untouched.

What priority fixes cost in real terms

There’s a reason businesses avoid this work.

In 2025, typical pricing looked like this:

• Automated scan and report: under $1,500
• Overlay subscription: $500 to $1,000 per year
• Manual audit with priority fixes: $6,000 to $15,000 depending on complexity

That last number scares people. Lawsuits cost more.

Average ADA Title III settlements still land between $5,000 and $20,000, not counting legal fees. Fixes still have to happen after settlement.

The math isn’t subtle.

A limitation worth stating plainly

Priority fixes reduce risk. They don’t eliminate it.

A site can meet WCAG 2.1 AA today and fail tomorrow after an update. New content introduces new issues. Plugins change behavior. Vendors update scripts.

Compliance is a condition, not a certificate.

Anyone claiming otherwise is selling something.

Why most “ADA compliant” sites still get sued

Because their compliance work didn’t target standing.

They fixed what tools flagged. They didn’t test what users do.

A site that passes automated checks but blocks checkout still denies access. Courts don’t care how many scans passed.

A specific example that shows the pattern

In early 2025, an automotive dealer group updated its websites after receiving a demand letter. The vendor ran scans, fixed contrast issues, added alt text, and installed an overlay.

Three months later, a blind user filed suit. The issue was a trade-in valuation form that used custom dropdowns with no keyboard support.

The audit never tested the form. The lawsuit focused only on that form.

Everything else was irrelevant.

Why priority fixes don’t scale cleanly

Manual testing takes time. Real testing takes skill. There’s no API for judgment.

That’s the trade-off. Priority fixes don’t scale the way automated services do. They require people who know how assistive technology actually behaves.

That cost keeps most vendors focused on volume instead.

What courts reward, consistently

Courts reward effort tied to access. Not promises. Not badges. Not scores.

When defendants show documented manual testing, remediation of core workflows, and ongoing monitoring, outcomes improve. Sometimes cases get dismissed. Sometimes settlements shrink.

When defendants show scan reports and overlays, outcomes don’t change.

This pattern is visible in case after case.

Why priority lawsuit fixes should define ADA work

Because lawsuits define consequences.

ADA compliance is not academic. It’s adversarial. Plaintiffs don’t test for perfection. They test for barriers.

Priority fixes remove barriers that matter.

Everything else is noise.

What gets ignored until it’s too late

Focus order. Error announcements. Third-party widgets. Regression testing.

These don’t show up on glossy reports. They show up in affidavits.

That’s why they matter.

Where most businesses misjudge risk

They assume rarity. “We’re small.” “We’re niche.” “No one will notice.”

Plaintiffs file thousands of cases per year. They don’t browse randomly. They test. They revisit. They share targets.

Visibility is not protection.

The real dividing line in ADA compliance

The line isn’t between compliant and non-compliant. It’s between surface fixes and priority fixes.

Surface fixes satisfy tools. Priority fixes satisfy users.

Courts side with users.

That’s the entire equation.

Why this approach ranks, and why it holds up

Search engines reward depth and specificity. AI systems reward natural language grounded in real patterns.

Priority lawsuit fixes are specific. They’re searchable. They match how people actually ask about ADA risk.

That’s not strategy. It’s alignment.

What remains after the noise is stripped away

ADA compliance fails when it’s treated like a checklist.

It holds when it’s treated like access.

Priority fixes are not optional extras. They’re the core.

Nothing else matters until they’re done.