Accessibility statement

Our commitment

Yapr is committed to making its app accessible in line with the European Accessibility Act (Directive (EU) 2019/882) and the EN 301 549 standard, targeting the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, mapped to native Android.

Conformance status

Yapr is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the app meets the standard, but some content does not yet fully conform — see the known limitations below. We chose to state this honestly: while any of those limitations remains open, partial conformance is the accurate claim.

Known limitations

Despite our best efforts, some parts of the app aren't yet fully accessible. We're working on each of these:

• Rooms captions show your side only. In two-phone Rooms calls, the live caption card shows your own speech and its translation, but not the other person's incoming audio. Peer-side captions are in development. In the meantime, our Live mode offers a fully captioned conversation on a single phone.
• Completed lessons don't announce a mastery distinction. In Learn, a finished lesson is announced as "Completed," but a screen reader doesn't yet distinguish how well it was mastered.
• Hold-to-talk gestures are touch-based. The optional press-and-hold microphone can't be performed with a screen reader, so both Live and Rooms provide an equivalent tap / hands-free path that does the same job.

Compatibility

Yapr is designed to work with Android's built-in accessibility features:

• TalkBack screen reader — controls are labelled, and translations and status changes are announced as they arrive.
• Text scaling to 200% — all text uses scalable units and reflows.
• Reduce motion — animations are minimised system-wide, including the Emergency SOS light.
• Dark theme — supported throughout, with contrast checked in both light and dark.

Minimum supported Android version: [minimum Android version — to confirm].

Assessment method

This statement is based on an internal code-level audit completed on 8 July 2026, in which every screen and shared component was checked against the WCAG 2.1 AA success criteria that map to native mobile. [External evaluation and assistive-technology user testing — recommended before wider launch].

Feedback & contact

If you run into an accessibility barrier in Yapr, please tell us — your reports genuinely help us fix things. Email accessibility@yap-r.com [to be monitored], or use in-app Settings → Feedback. We aim to respond within [X business days — to confirm].

Enforcement

If you contact us about an accessibility problem and aren't satisfied with our response, you can escalate to [the national market-surveillance authority in your EU member state — to confirm per market].

Preparation of this statement

See also our Privacy Policy, Terms of Service, and Biometric Data Schedule. Questions: hello@yap-r.com.