Contact Accessibility Risk Snapshot

When To Use This Form

Ask a privacy question or request access, correction, or deletion.

Report an accessibility barrier on this site.

Ask about a submitted risk snapshot, resource request, buyer-tool summary, provider match, or referral follow-up.

Ask for a human review of whether your situation is better handled as a public-page snapshot, counsel-first lawsuit triage, quote brief, provider comparison, PDF inventory, procurement packet, or remediation roadmap.

What To Include

Include the page URL, your email, and a brief description of the request.

If the request is about a business website, include the website URL so we can connect it to the right snapshot.

If you already submitted a snapshot, use the same work email when possible. That makes it easier to match the request without asking you to repeat information.

If your request involves a lawsuit, demand letter, insurance claim, or counsel discussion, keep the message high level. Do not paste privileged attorney communications, full complaint text, private customer data, or docket records.

What Not To Send

Do not send passwords, payment information, bank details, medical information, patient data, private customer records, authentication tokens, confidential legal strategy, or personally sensitive information.

Do not send PACER-derived personal data, lists of sued businesses, docket downloads, case captions, or complaint attachments through this general contact form.

If a support conversation needs sensitive context later, the safer path is to first identify the type of issue, then decide what should be shared, with whom, and under what consent or legal-review process.

Best Starting Point By Situation

If you want an immediate public-page result, use the free snapshot first and then contact us with the same email if you need human follow-up.

If you received a lawsuit or demand letter, talk to counsel first, then use the lawsuit-response pages to organize technical questions, deadlines, public-page evidence, and remediation options.

If you are choosing a provider, use the provider scorecard or solution-fit assessment before asking for a referral. That produces a more specific handoff than a generic contact request.

If your issue involves PDFs, VPAT/ACR, procurement, healthcare forms, financial-services workflows, Shopify, WordPress, multi-location templates, or agency client portfolios, use the matching planner so the follow-up starts with useful context.

Response Expectations

Business, provider, snapshot, and technical follow-up requests are routed for human review first. Including a public website URL, the same work email used for a snapshot, or the relevant planner context usually makes the response more useful.

Privacy, accessibility-barrier, deletion, and formal rights requests are reviewed separately from business follow-up. The form is not an emergency channel and should not be used for urgent legal deadlines.

A response may ask for the public website URL, the page where the issue appears, the browser or assistive technology involved, whether the issue affects a public workflow, and whether partner sharing is authorized.

We do not provide legal advice. If the request involves a lawsuit, deadline, settlement, demand letter, insurance claim, or attorney strategy, the contact response should stay technical and counsel-first.

Referral And Partner Questions

You can ask whether a prior request was shared with a partner, whether accessiBe or another provider was considered, or whether referral compensation may apply.

Partner sharing is separate from ordinary contact follow-up. A contact message alone should not be treated as consent to send your details to a partner.

If you want provider options, say what outcome you need: audit, developer remediation, widget support, accessFlow-style workflow support, managed services, VPAT/ACR, PDF/file accessibility, user testing, monitoring, or litigation-support resources.