Accessibility

Summary

Talevara targets WCAG 2.2 AA and provides a support route for access barriers in reading, account, and creator workflows.

Steps

1. Try keyboard navigation with Tab and Shift+Tab, and activate a focused button or link with Enter or Space as appropriate.
2. Use browser zoom, high-contrast settings, a preferred typeface, or reduced-motion controls when they help you use the page.
3. If a task fails, note the page URL, device, browser, assistive technology if used, and the step where you became blocked.
4. Open Contact Support and select Accessibility; describe the barrier and the result you expected without including private credentials.

What to expect

• WCAG 2.2 AA is Talevara’s accessibility target; this statement is not a claim that every page or combination has been fully audited.
• Accessibility feedback helps identify barriers, but response time and resolution depend on the issue and its severity.
• For login problems unrelated to assistive access, use Account/Access Support; for immediate safety concerns, use Safety & Reporting.

Troubleshooting

• If keyboard focus disappears, tell Support which control had focus and what key you pressed next.
• If text overlaps at zoom, include the browser zoom percentage and screen width; avoid sending a screenshot containing private account information.
• If motion remains uncomfortable after enabling reduced motion, identify the animation and page so the team can reproduce it.