Updated October 16, 2026.
A website accessibility complaint needs a clear response. So does a visitor who tells you they can’t complete a booking or read an important document. I want you to know which questions belong with your attorney and which tasks belong with your website team.
This page explains how to organize accessibility work. It doesn’t assess your legal liability, predict a settlement, or promise protection from a lawsuit.
Key Takeaways
- Get qualified legal advice for a demand letter, complaint, or court deadline.
- Ask the website team to investigate specific barriers and affected tasks.
- An accessibility widget doesn’t provide legal immunity.
- Document changes and retest the complete visitor experience.
- Keep accessibility work active after the first round of fixes.
Written by Dotty Scott
Founder of Premium Websites, Inc.
Empowering small businesses to go from Invisible to Invincible.
Table of Contents
- What to Do When a Complaint Arrives
- Does the Same Rule Apply to Every Website?
- What Should the Technical Review Cover?
- What Should You Ask the Website Team to Deliver?
- Organize the Response
- Can a Widget Prevent an ADA Lawsuit?
- How Do You Know a Fix Works?
- Keep the Work From Being Undone
- Get the Right Help
- Common Questions
What to Do When a Complaint Arrives
Keep the communication and record when you received it. Bring a demand letter or lawsuit to a qualified attorney promptly so counsel can assess the response and any deadlines. Don’t assume a general article can determine how a claim applies to you.
Tell your website team which pages, documents, or tasks are involved. Coordinate technical investigation and record handling with counsel, rather than making broad claims about what the complaint proves.
Does the Same Rule Apply to Every Website?
No. DOJ’s Title III overview explains the framework for covered businesses open to the public. Its web guidance describes its position on accessibility of their online goods and services. Applicability to a particular organization needs legal assessment.
The Title II government web rule is separate. Don’t assume its compliance dates apply to a private business. My ADA website overview explains that distinction and links to current official guidance.
What Should the Technical Review Cover?
Begin with the reported task. Can someone navigate to a service, understand the information, complete the form, and receive a meaningful confirmation? Include the booking tool, checkout, documents, or other outside service used in that task.
Ask the evaluator to identify the applicable technical criteria and the scope of the review. WCAG provides testable accessibility criteria, but a partial scan isn’t an evaluation of every page or every interaction.
What Should You Ask the Website Team to Deliver?
I would ask for a written work list with examples of the problem, where it occurs, what will change, and how the result will be checked. That gives you something concrete to discuss with the people supporting your business.
A vague statement that the site was made compliant doesn’t explain the work. Ask which templates, forms, documents, and third-party services were included and which remain outside the agreed scope.
Organize the Response
Keep legal interpretation and technical remediation connected, while assigning each to the appropriate professional.
| Need | Who should lead | Useful output |
|---|---|---|
| Claim and deadlines | Qualified attorney | Advice specific to the claim and organization |
| Barrier investigation | Accessibility evaluator and website team | Reproducible findings and defined scope |
| Remediation | Responsible developer or content owner | Documented corrections |
| Verification | Qualified evaluator, with user testing where possible | Task-based retest results |
| Ongoing care | Business and website team | Publishing checks and feedback process |
Can a Widget Prevent an ADA Lawsuit?
I wouldn’t make that promise. A display tool may offer preferences some visitors find helpful, but its presence doesn’t establish that the underlying website is accessible.
W3C’s evaluation-tool guidance explains why human judgment is necessary. In its accessiBe enforcement matter, the FTC challenged claims about automated WCAG compliance. Evaluate the specific work and evidence rather than a guarantee attached to a subscription.
How Do You Know a Fix Works?
Retest the reported task after the change. Use manual checks and appropriate assistive-technology testing alongside automated tools. Where possible, involve people with disabilities in evaluation.
Document what was tested and the outcome. If the issue comes from a shared header, form component, or page template, check other places that use it. A local fix can leave the same barrier elsewhere.
Keep the Work From Being Undone
New images, forms, videos, PDFs, and software updates can change the experience. Give the person maintaining your site an accessibility checklist and a way to escalate questions.
Keep a visible contact method for accessibility feedback and respond to reports. An accessibility statement should describe your actual process and limitations, rather than claiming perfection.
Get the Right Help
If you’ve received a legal demand, contact counsel. For website work, schedule a Discovery Call so we can discuss the reported barriers and the evaluation or development support you need.
My role is to help you understand the technical work and plan practical improvements. Legal advice and a legal conclusion about your obligations belong with a qualified attorney.
Common Questions
Is there a typical settlement amount I should budget for?
This page doesn’t offer a settlement estimate. Ask counsel about the actual claim and circumstances.
Does installing an accessibility tool make me lawsuit-proof?
No. Don’t treat a tool, badge, or automated report as a guarantee of legal protection.
Should I wait for a complaint before reviewing accessibility?
I recommend reviewing important visitor tasks as part of normal website care. Removing barriers helps people use your business.
