Recovery for every mind, every eye, every voice.

Who Renovyn is built for

We build for the people other recovery apps leave out. The populations Renovyn serves, dyslexic, ADHD, blind and partially sighted users, are over-represented inside addiction. If the front door is locked, we've failed before we've started.

What Inclusive Recovery does

• Voice-first onboarding. If a screen reader is active, the app speaks every question aloud and accepts spoken answers. Tap or text answers always work too.
• Adaptive modes. Dyslexia Mode, ADHD Mode, and Low Vision Mode change typography, spacing, contrast, motion, and shortcuts. Modes stack, you can have all three on at once.
• Listen on every screen. Tap the speaker icon to hear the page read aloud. Pre-rendered audio for the static parts of the app; on-demand TTS elsewhere.
• Quick check-in. A three-tap path, mood, craving, save, for the days when a full check-in is too much.
• Crisis hotkey. Volume up + volume down held for a second opens a single-page audio response: call your sponsor, listen to a craving audio, or open a UK helpline.

Standards we work to

The Renovyn mobile app is built against WCAG 2.2 Level AA, with AAA targeted on the high-stakes paths, onboarding, daily check-in, sponsor messaging, and crisis routing. We run an automated component audit on every pull request that touches the app. It reports rather than blocks today, because the app carries a backlog of findings we are working through, and we do not yet run automated colour-contrast checks in continuous integration. The marketing site and web dashboard are not covered by that audit at all.

Tell us when we get it wrong

We will. When you find a barrier, email accessibility@renovyn.io with as much detail as you can. Triaged within five working days and prioritised against open release work.

Known limitations

• The web dashboard is partially accessible, the mobile app ships first, with web parity tracked separately.
• Atypical-speech support (cerebral palsy, Korsakoff, post-stroke, ALS) requires partner SDK integration; in flight.
• Captioning of all narrated audio is a content workstream; new tracks ship with captions, the back catalogue is being captioned.
• Our automated component audit still reports a substantial backlog in the mobile app, most of it controls with no screen-reader label. We are working through it, and until we have, the audit reports rather than blocks a release. If something is unusable for you today, please write to us and we will prioritise it.