Last updated: April 22, 2026
Ember is committed to making daily wellness challenges usable by everyone. We design with accessibility in mind and test against Apple's iOS accessibility guidelines and Google's Android accessibility guidelines.
We target WCAG 2.1 Level AA in the mobile app. If something doesn't work for you, please email accessibility@goember.app and we'll fix it.
| Feature | Support | Notes |
|---|---|---|
| VoiceOver (iOS) / TalkBack (Android) | Yes | Interactive elements are labeled; text and custom buttons are announced. |
| Voice Control | Yes | Navigation and primary actions have descriptive labels usable by voice commands. |
| Larger Text / Dynamic Type | Yes | Typography scales with the system text size setting. |
| Dark Interface | Yes | Full dark mode that follows the system appearance setting. |
| Differentiate Without Color Alone | Yes | Categories, difficulty, and status indicators always combine shape, icon, and text — not color alone. |
| Sufficient Contrast | Yes | Primary text and interactive elements meet WCAG 2.1 AA contrast ratios in both light and dark themes. |
| Reduced Motion | Yes | When your device has Reduce Motion enabled, decorative animations (fire effects, celebration transitions) are disabled or simplified. |
| Captions | Not applicable | Ember does not currently include audio or video content that carries spoken dialogue. |
| Audio Descriptions | Not applicable | Ember does not currently include narrated video content. |
Ember supports VoiceOver, Voice Control, Dynamic Type, Dark Mode, and Reduce Motion. The main "complete challenge" control uses a hold-to-confirm gesture for sighted users; VoiceOver users can activate it with a standard single-tap — no hold required.
Ember supports TalkBack, Select to Speak, Font Size, Dark Theme, and Remove Animations.
If you encounter something that doesn't work for you — a missing label, a control you can't reach, or anything else — please email accessibility@goember.app. Include your device model, OS version, and a short description of the issue. We aim to respond within 5 business days.
Accessibility is a process, not a checkbox. We routinely test new features with screen readers enabled and prioritize accessibility regressions like any other bug. This statement is reviewed and updated with each significant release.