Get help when somethingblocks your accessto Talvrin.
If an accessibility barrier is preventing you from using Talvrin, tell us what you were trying to do and what blocked you. You do not need to disclose a disability or medical information to ask for help.
Don't include passwords, one-time codes, recovery codes, API secrets, private keys, or unnecessary medical information. We will never ask you for them here.
What's blocking you?
Pick the closest match — this is for routing only, not a diagnosis. "Other" is always available.
Choose what's blocking you above, then Continue to see a tailored next step.
Report an accessibility barrier.
Reporting is never blocked behind a workaround or a sign-in step. Nothing here substitutes for an approved accessible authentication path.
- Passwords, one-time codes, recovery codes, API keys, or private keys.
- Medical records, a diagnosis, or disability documentation — never required.
- An attachment or screenshot — optional only. A text description is always enough to submit.
- Submitting does not guarantee a response time — no service-level commitment is published yet.
Choose what's blocking you above to open the report form — this keeps your report routed correctly from the start.
Account Support owns sign-in — not
this page.
Passwords, MFA, passkeys, SSO, recovery codes, and account state are owned by Account Support's approved identity systems, not by Accessibility Support copy. If a sign-in, verification, or recovery step is itself inaccessible, you don't need to complete it first.
You can report the barrier above, go to Account Support directly, or do both — your accessibility context travels with you either way. Never send a password or one-time code through either support path.
Go to Account Support →Accessibility Support frequently
asked questions.
Barriers that stop you using Talvrin — keyboard and focus, screen readers, zoom and reflow, color and contrast, motion, media, forms and time limits, authentication steps, and documents or downloads. Product defects and account access have their own routes under Related Support.
No. Tell us what you were trying to do and what blocked you. A diagnosis, medical records, or disability documentation are never required.
No. You can mention it if you think it will help us reproduce the barrier, but a plain description of what happened is enough.
Yes. Reporting is never blocked behind a sign-in step. If a sign-in, verification, or recovery step is itself inaccessible, you don't need to complete it first.
An accessibility statement or conformance artifact is not yet published for this build. We won't claim or imply conformance until an approved, current source exists.
No. Submitting a report doesn't guarantee a response time — no service-level commitment is published yet.






