Accessibility at Roamly Flow
Last updated: 21 July 2026. Accessibility work at Roamly Flow is ongoing — this statement describes where we are today and how to reach us.
Our commitment
We want Roamly Flow to be usable by everyone, including people who rely on assistive technologies such as screen readers, screen magnifiers, keyboard-only navigation, and voice control. Accessibility is part of how we build and review the product, not an afterthought.
The standard we aim for
We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We test with a combination of automated tooling (axe-core in our test suite) and manual review, including keyboard-only and screen-reader checks.
We do not yet claim full WCAG 2.2 AA conformance. Some areas are still undergoing manual assistive-technology testing, and some depend on third-party services we integrate but do not control (see below).
What we've done
- Keyboard-accessible navigation, timer, tasks, and dialogs, with a "Skip to content" link and visible keyboard focus indicators across all themes.
- Dialogs that trap focus, restore it on close, and close with the Escape key.
- A reduce-motion setting and support for your system's "reduce motion" preference.
- A color-blind-friendly mode that switches timer and status colors to a blue/orange palette.
- Labeled form fields and error messages, and accessible names on icon-only controls.
- Automated accessibility checks that run on every code change to catch regressions.
Known limitations
We're being honest about what still needs work:
- Full screen-reader passes (VoiceOver and NVDA) across every workflow are still in progress.
- Analytics charts are being supplemented with text/table alternatives.
- Embedded Spotify and Apple Music players, Stripe's hosted checkout, and Supabase-hosted auth screens are provided by third parties; their internal accessibility is outside our direct control, though we choose accessible entry points and offer alternatives where we can.
- Content inside documents you upload (for example, scanned image-only PDFs) may not have an accessible text alternative if the original document doesn't.
Report an accessibility barrier
If something is hard or impossible to use, please tell us — your reports directly shape what we fix next.
You can reach us using the "Contact support / send feedback" option in the in-app Help & Legal menu, or by email at support@roamlyflow.com.
To help us reproduce and fix the issue quickly, please include, where you can:
- The page or feature (a link or description)
- Your device and operating system
- Your browser and version
- Any assistive technology you were using (e.g. VoiceOver, NVDA, JAWS, Dragon)
- What you expected to happen, and what happened instead
We aim to acknowledge accessibility reports within 5 business days and will keep you updated on our plan to address them. Reports that block an essential task are prioritized.