In short
Talevara targets WCAG 2.2 Level AA. The Step 29 engineering pass now covers keyboard/focus behavior, dialog semantics, forms, Reader interactions, Creator Studio, Admin and responsive accessibility foundations. Formal conformance is still not claimed until the documented manual assistive-technology matrix is completed.
1. Commitment
Talevara aims to make reading, discovery, publishing, account management, and community features usable by people with disabilities and compatible with common assistive technologies.
2. Target standard
Target: WCAG 2.2 Level AA for the Talevara web experience, together with applicable accessibility requirements in the markets where the service operates.
3. Current status
Conformance status: Talevara targets WCAG 2.2 Level AA and maintains ongoing accessibility review. Talevara must not claim full or partial WCAG conformance until keyboard, screen-reader, zoom/reflow, forced-color and reduced-motion testing is documented against the release candidate.
4. Measures in this foundation
The platform includes semantic landmarks and skip navigation, visible keyboard focus, accessible dialog naming and focus return, keyboard-operable tabs and menus, Reader drawer focus containment, accessible progress indicators, labelled forms, reduced-motion handling, forced-color safeguards, touch-target floors, annotation keyboard support and accessibility regression validation across all checked-in HTML pages.
5. Known limitations
The remaining known limitation is verification rather than an intentionally inaccessible feature: Talevara has not yet completed the release-candidate manual assistive-technology matrix. Complex Creator Map workflows, Reader annotations/choices/comments, authentication errors, billing/access messaging and Admin/moderation dialogs must be exercised with real screen readers and high-zoom/reflow configurations as part of release operations.
6. Feedback and support
Users can submit an accessibility support case through the support request flow. Support and legal-notice routing is available through the linked support forms.
7. Assessment
Step 29 includes automated structural regression checks, but automated checks are not a conformance audit. As part of release operations, Talevara must record tested browser/assistive-technology combinations, assessment date, discovered issues and remediation status. The required matrix is tracked internally for release sign-off.
Questions about this policy?
Use the accessibility support case form. Support and legal notices can be submitted through the linked support routes.