Brain FroggyAccessibility
Brain Froggy is built so the breathing animation, the words, and the buttons stay usable when you change how you see, hear, or move.
Dyslexia-friendly font (in the app)
Inside the Brain Froggy app you can switch the on-screen text to OpenDyslexic under Settings → Personalization → Dyslexia-friendly font. The option is not offered when the app is in Arabic, Hindi, Japanese or Korean, because the font does not cover those scripts. From app version 1.0.2, text size follows your phone's text-size setting, and you can make it smaller or larger in the same Personalization section. This site (the one you're reading now) uses Montserrat for headings and Nunito for body text and doesn't currently offer a font toggle. The dyslexia-friendly option lives in the app, where the breath text matters most. IN PROGRESS: bringing the same font choice to this website. If a font here is hard to read for you, write to us via the contact form and tell us where.
Light and dark mode
This website has a light/dark toggle in the top navigation bar; your choice is remembered locally in your browser. The Brain Froggy app starts in light mode, and you can switch it to dark under Settings → Personalization → Dark Mode. TESTED on this site: the toggle on desktop and mobile Chromium, Firefox, and Safari; both modes meet WCAG 2.1 AA contrast on body text and primary buttons. IN PROGRESS: a handful of decorative gradients on the marketing pages that we want to push for slightly stronger contrast in dark mode.
High-contrast mode
High-contrast lives inside the Brain Froggy app, not on this website. In the app go to Settings → Personalization → High Contrast to swap to a palette tuned for low-vision use. On this website the calm, low-saturation palette is intentional, but it's verified against WCAG 2.1 AA for text and button contrast. If anything here trips that bar for you, tell us via the contact form. IN PROGRESS: a website-level high-contrast variant is on the list but not shipping in this version.
Keyboard navigation
TESTED on this site: Tab order moves through the top navigation bar, the page content, the contact form fields, and the footer in a predictable top-to-bottom, left-to-right sequence. Enter and Space activate buttons and links. Escape closes the mobile menu. Visible focus rings appear on every primary button, every link inside prose, and every form field. IN PROGRESS: a small number of decorative icon buttons in the language switcher are still being tuned for a stronger focus ring. If you reach a control here that you can't operate with the keyboard, write to us through the contact form and we'll fix it.
Screen reader support
TESTED on this site: VoiceOver on iOS Safari and macOS Safari reads the navigation, the hero (with a written fallback for the breathing animation), the App Store and Google Play buttons, the prose on every legal page, and the contact form end-to-end. TalkBack on Android Chrome is tested on the hero fallback, the store buttons, and the contact form. Every decorative glyph is marked aria-hidden so it does not clutter the reading order; every icon-only control has an aria-label. IN PROGRESS: reading order in the longer scroll narrative on the homepage is still being checked section by section against the visual order. In the app, from version 1.0.2: the breathing screen's tabs, session controls and daily quote carry screen-reader labels, icon-only buttons are labelled, and the onboarding and settings animations follow your phone's reduce-motion setting. IN PROGRESS: testing the app with VoiceOver and TalkBack on real phones. If something in the app can't be reached or is read out wrongly, please tell us through the contact form.
Contact us about accessibility
Accessibility reports are read by a person on our team. If something on this site or in the Brain Froggy app blocks you (a control you can't reach, text you can't read, a screen reader that loses its place, a focus ring that goes missing) write to us through /contact or directly at hello@wecodemobile.com. Tell us what you tried, what assistive technology you were using, and what you expected. We try to reply within a few working days and to ship a fix in the next release. We're a small team in Gdańsk and we treat accessibility reports as bugs, not feature requests.