Who This Page Is For
Use this page when a business owner, risk manager, operations leader, broker-facing coordinator, or counsel-approved contact needs to organize technical accessibility facts after a website accessibility lawsuit, demand letter, threatened claim, or NOS 446 matter.
This page does not evaluate coverage, interpret insurance policy language, provide legal advice, or decide whether notice should be given to a carrier or broker. Keep those questions with counsel and the appropriate insurance professional.
What To Preserve Before The Site Changes
Preserve the demand letter or complaint with counsel, current public URLs, page screenshots, accessibility statement, widget or overlay settings, theme and plugin versions, deployment history, prior scans or audits, support requests, remediation tickets, and any dated technical notes.
Do not submit policy numbers, claim numbers, privileged legal strategy, private insurance communications, passwords, customer records, medical information, or payment data through the public form.
Technical Packet For Risk Review
A useful packet separates legal documents, insurance or coverage communications, and technical remediation facts. The provider-facing version should usually include only the public URL, affected user flows, public-page snapshot, manual-review scope, remediation owners, retest plan, and known limitations.
Public-page snapshot output can identify common HTML-level signals. It cannot verify rendered JavaScript states, logged-in pages, checkout, screen reader output, keyboard traps, color contrast, documents, video captions, settlement posture, legal compliance, or insurance coverage.
Provider Conversation Scope
Provider categories may include public-page accessibility snapshot, expert audit, manual user-flow review, remediation workflow, monitoring, accessibility statement and evidence review, VPAT/ACR support, PDF/file accessibility, user testing, and litigation-support resources described by partner providers.
When appropriate and with consent, this site may refer a qualified request to accessiBe. accessiBe public offerings include accessWidget, accessFlow, accessServices, VPAT/ACR support, expert audit, user testing, file/PDF accessibility, and select-plan litigation support resources.
Claims To Keep Out Of The Packet
Do not describe a scan, widget, audit, provider, accessibility statement, or remediation ticket as a legal outcome, a coverage decision, a settlement strategy, or a replacement for counsel or an insurance professional.
Use careful technical language: preserve evidence, assess public-page signals, manually review named flows, remediate confirmed barriers, document fixes, monitor recurrence, and coordinate provider sharing only after consent.
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
Can this page tell me whether insurance covers a website accessibility lawsuit?
No. Coverage questions depend on policy language, facts, notice requirements, jurisdiction, and professional advice. This page helps organize the technical accessibility packet only.
Should I submit policy or claim numbers in the form?
No. Do not submit policy numbers, claim numbers, privileged communications, or private insurance documents. Use the form for public website URL, company, matter status, and consent-controlled technical follow-up.
What can be shared with an accessibility provider?
Usually the provider-safe packet should focus on public URL, alleged user flows, technical findings, manual-review scope, remediation owners, and retest needs. Ask counsel before sharing legal or insurance documents.
Will details be sent to accessiBe automatically?
No. Follow-up consent and partner-sharing consent are separate choices. Partner sharing happens only when the visitor separately consents.