RESOURCES

A clearer starting point
for better access.

Understand the technical work, review important website experiences, and find guidance you can use with your team.

ADA LAWSUIT & DEMAND LETTER GUIDE

Understand the website
behind the claim.

Speak with qualified legal counsel about the legal matter. On the technical side, a structured review can establish what barriers are present and what remediation is needed.

  1. 01

    Assess

    Review your website, key journeys, project goals, and detectable accessibility barriers.

  2. 02

    Manual Testing

    Human experts test keyboard use, screen readers, and real interactions, then prioritize the findings.

  3. 03

    Code-Level Remediation

    Fix barriers in your website’s code, content, components, and behavior.

  4. 04

    Retest & Verify

    Repeat the affected journeys to confirm that the fixes work as intended.

  5. 05

    Documentation

    Record findings, completed fixes, test evidence, and remaining limitations.

Explore the full ADA lawsuit support process

Equal Access provides digital accessibility services, not legal advice.

ADA WEBSITE LAWSUIT STATISTICS

Read the data
with its context.

When reviewing lawsuit figures, check the reporting period, the courts included, and whether the source counts cases or unique defendants. Court filings do not capture every private demand letter.

UsableNet publishes a digital accessibility lawsuit tracker with monthly reporting and links to its research. Use the source's methodology and date when referencing its figures.

View UsableNet's lawsuit tracker ↗ (opens in a new tab)

External research from UsableNet. EqualAccess. does not publish or independently verify this dataset.

WEBSITE ACCESSIBILITY LAWS & COMPLIANCE GUIDE

Start with what people
need to do.

Start by identifying the requirements relevant to your organization, then agree on the technical standard, assessment scope, and evidence needed. Human-led testing turns that target into practical website improvements.

Understand the requirements

ADA, Title II, Section 508, and Section 504 address different contexts. Your legal or compliance team can confirm which obligations apply to your organization.

Explore the compliance topics

Define the technical target

Agree on the WCAG version, conformance level, and website scope. Include important pages, shared components, documents, and complete user journeys.

Understand WCAG evaluation

Test, improve, and keep evidence

Record the barrier, affected component, relevant criterion, and proposed correction. After a change, repeat the task and document what the retest found.

Further reading: W3C's introduction to web accessibility ↗ (opens in a new tab) and the official WCAG 2.2 standard ↗ (opens in a new tab).

ACCESSIBILITY CHECKLIST

Six useful checks
for a first review.

This is a starting point for discussion, not a complete accessibility audit or conformance assessment.

  • Keyboard navigation

    Can you reach and operate links, menus, forms, and dialogs without a mouse? Can you leave each component?

  • Focus visibility

    Is the current keyboard position visible, with a logical order through the page and after opening or closing a dialog?

  • Forms and errors

    Do fields have useful labels and instructions? Can users understand errors and find the fields that need attention?

  • Structure and alternatives

    Do headings communicate the content structure, and do meaningful images have text alternatives that fit their purpose?

  • Readable presentation

    Check text and controls for sufficient contrast. Enlarge content and review whether important information or controls become unavailable.

  • Complete user journeys

    Follow a critical task through every step, including confirmation, errors, and embedded or third-party components.

FREQUENTLY ASKED QUESTIONS

A little more clarity.

Is an automated scan enough?

No. A scan can identify many detectable technical issues, but it cannot evaluate every accessibility barrier. Manual and assistive-technology testing help review the interactions and context that automation cannot fully assess.

Can you work with our existing developers?

Yes. We can provide findings, recommended remediation, implementation support, and retesting, or perform code-level remediation directly within the agreed scope.

Which accessibility standard do you use?

Our website accessibility work is generally based on WCAG. The appropriate version and conformance target depend on the project requirements and are defined as part of the engagement.

What changes after remediation?

We retest affected components and user journeys and document the results. Ongoing review helps identify new barriers as the website changes.

What if we have received a lawsuit or demand letter?

Your legal counsel handles the legal response. We can investigate technical accessibility concerns, prioritize remediation, and document the work.

Read the ADA lawsuit support FAQs

INSIGHTS

Practical notes for
the next website update.

Test the journey, not just the page

A page can appear straightforward while an entire task still breaks. Include the transitions: opening a menu, moving into a dialog, submitting a form, correcting an error, and reaching a confirmation.

Document where the sequence fails, the input method used, and the expected result. That context helps developers reproduce the barrier and verify a correction.

Review shared components early

A navigation menu, form field, or product template may appear across many pages. Reviewing common components early can help organize remediation and reduce repeated implementation work.

After updating a shared component, retest representative pages and the journeys that use it. The same code can behave differently in different contexts.

Keep a useful record of each fix

Record the original barrier, affected page or component, remediation, and verification result. Include relevant testing conditions and any remaining limitations.

Clear records support future maintenance and make it easier for new team members to understand the accessibility decisions already made.

Opens in a new tab.