Accessibility
Accessibility statement.
We want every parent to be able to use emoGlow, including parents who use a screen reader, navigate by keyboard, magnify text, prefer reduced motion, or see color differently.
The standard
This website is built and tested against the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. Every page is checked with automated tooling (axe) at phone and desktop sizes on each release, and walked by keyboard and with a screen reader before launch.
Specifically, the site provides:
- A “skip to content” link as the first focusable element on every page.
- Visible focus on every link and control, and no content hidden under the sticky header when you tab to it.
- Touch targets of at least 48 × 48 pixels on every control.
- Text that scales to 200 % and beyond without loss of content; no text in images.
- Color contrast of at least 4.5:1 for text and 3:1 for controls in both the light and dark themes.
- Respect for your “reduce motion” setting: animations stop and the background video shows a still image.
- A pause control on any moving content that lasts longer than five seconds.
- Captions or a text alternative for any video with speech (our current background video has none).
- Right-to-left layout for Arabic, and language attributes on every page so assistive technology reads it correctly.
The app
The emoGlow app targets the same standard. It supports Dynamic Type up to the largest accessibility sizes, VoiceOver and TalkBack, and includes optional Atkinson Hyperlegible and OpenDyslexic typefaces. Voice conversations with Bloom are available for parents who prefer to talk rather than type or read.
Known limitations
- Store badges are supplied by Apple and Google as images; their text is provided through accessible labels.
- The site’s PDF-free; if you need any content in another format, ask and we will provide it.
Tell us
If anything on this site or in the app is hard to use, email support@emoglow.ai with “Accessibility” in the subject line. A person reads every message, and we treat accessibility reports as bugs, not requests.