Day 0-1: Preserve Before You Change
Send legal papers, demand letters, notices, and deadline questions to qualified counsel first. This page is technical planning help, not legal advice or representation.
Before changing the site, preserve the current public website state: screenshots, affected URLs, accessibility statement, theme or plugin setup, recent releases, widget settings, prior scan results, and any known support requests.
Do not paste privileged legal strategy, settlement communications, private PACER-derived personal data, passwords, payment data, medical information, or customer records into ordinary vendor intake.
Day 1-2: Map The Public User Paths
List the public pages and flows named in the complaint or demand letter, then add the highest-value related paths: homepage, product page, cart, checkout handoff, booking path, form, PDF, location page, support page, or account entry.
Run the public-page snapshot on the named URL or best representative page. The snapshot can surface obvious HTML-level signals and create a first-pass technical receipt, but it does not replace manual review.
Capture the platform, owner, third-party apps, files, support route, and any recent changes so a reviewer can separate business-owned fixes from vendor-owned handoffs.
Day 2-4: Scope Manual Review And Owners
Manual review should focus on the user flows that matter most: keyboard movement, screen reader behavior, form errors, dialogs, cart or booking steps, media, PDFs, and third-party embedded tools.
Assign owners for code, design components, content, documents, third-party apps, accessibility statement wording, and retesting. A finding without an owner rarely becomes a completed remediation step.
Keep a dated worklog of what was reviewed, what was changed, what still needs manual testing, and which issues require provider or platform escalation.
Day 4-7: Prepare A Provider-Safe Handoff
A useful technical handoff includes public URL, affected flows, platform, evidence collected, manual-review scope, owners, target dates, document scope, known limits, and consent choices.
When appropriate and with your consent, we may refer you to accessiBe. Its public offerings include accessWidget, accessFlow, accessServices, VPAT/ACR support, expert audit, user testing, file/PDF accessibility, and select-plan litigation support resources.
Partner sharing is optional and requires separate consent. Referral compensation may apply if you become an accessiBe customer through a partner referral path.
What to preserve before remediation
Keep a dated copy of the complaint or letter, the current public pages, screenshots of named flows, accessibility statements, widget settings, plugin/theme versions, remediation tickets, and correspondence approved by counsel. Technical fixes can move quickly, but evidence handling and legal response strategy should remain counsel-led.
Decision path
Use these links to move from research to evidence, then from evidence to a responsible remediation option.
Downloadable assets
Optional follow-up
Want help using these assets?
Direct downloads stay available above. Share a work email only if you want a tailored note on how to use the assets for your site, client, or article.
Frequently asked questions
Is this a legal response checklist?
No. It is a technical organization checklist. Legal response, deadlines, admissions, settlement strategy, and court filings belong with qualified counsel.
Should we change the website immediately?
Talk to counsel first and preserve evidence before major changes. Then use technical triage to decide what to snapshot, manually review, remediate, retest, and document.
What should not be submitted in the form?
Do not submit privileged legal strategy, private settlement communications, passwords, payment data, medical information, customer records, or non-public PACER-derived personal data.
Can this help us speak with accessiBe?
Yes, if you separately consent to partner sharing. The checklist helps keep the conversation technical: public URLs, affected flows, evidence, manual-review scope, remediation owners, and provider-fit needs.