Legal

Accessibility commitments and support channels.

Our accessibility statement explains conformance intent, known limitations, and how users can report barriers for prompt remediation.

We publish accessibility commitments and support paths while keeping internal audit tooling and implementation-level remediation planning private.

Accessibility standards alignment targets
Known issues and improvement commitments
Clear support channel for accessibility feedback
Accessibility commitment statement
Conformance target references and policy links
Issue reporting and support contact pathway
Align legal copy with real product and billing behavior.
Confirm misuse and trust-report channels are active.
Review privacy statements for all live connectors.
Add update date and owner for each policy page.
Run a legal copy check before each major release.
Verify primary CTA route: /waitlist
Detail lane
What this page covers

Our accessibility statement explains conformance intent, known limitations, and how users can report barriers for prompt remediation.

Accessibility standards alignment targets
Known issues and improvement commitments
Clear support channel for accessibility feedback
Detail lane
Soft launch deliverables

These are the deliverables that should be complete before expanding invite volume.

Accessibility commitment statement
Conformance target references and policy links
Issue reporting and support contact pathway
Detail lane
Open kitchen boundary

We publish accessibility commitments and support paths while keeping internal audit tooling and implementation-level remediation planning private.

Keep terms consistent with pricing and product scope
Define escalation and support obligations
Maintain version history for policy updates
Common questions
What outcome should I expect from legal?

Our accessibility statement explains conformance intent, known limitations, and how users can report barriers for prompt remediation.

What is intentionally not disclosed publicly?

We publish accessibility commitments and support paths while keeping internal audit tooling and implementation-level remediation planning private.

Where should I go next?

Use "Contact support" first (/waitlist), then "Read privacy policy" (/privacy) for deeper context.