Accessibility

1. What we strive for

We do not claim full conformance with any specific standard (such as WCAG 2.1) across every screen or workflow until we have completed a formal audit. In the meantime, we focus on practical improvements, including:

• Keyboard use and focus: Interactive controls should be reachable with the keyboard where we provide them, with visible focus indicators that match our design system.
• Structure and labels: We aim for clear headings and descriptive labels on core flows so assistive technologies can navigate the experience more predictably.
• Contrast and readability: We aim for readable text and sufficient contrast on primary UI where we control styling.

2. Audio-first listening

The heart of Sozo Play is audio storytelling. Playback controls are designed to be discoverable and operable alongside the listening experience.

Where we provide them for a given story or episode, you may also open a transcript to read along with playback. Transcripts are not guaranteed for every title; if something is missing or hard to use, please tell us using the contact information below.

3. Third-party experiences

Some parts of the Service are provided by partners and may follow their own interfaces and accessibility practices—for example:

• Stripe for checkout and billing. See Stripe's accessibility information: stripe.com/accessibility.
• Google when Google sign-in is enabled for a deployment. See Google's accessibility commitments and product documentation for the sign-in experience you use.

4. Limitations and ongoing work

New features may take time to reach the same level of polish as established flows. If you run into a barrier—keyboard traps, missing labels, confusing focus order, or anything else—we want to hear about it so we can prioritize a fix.