Accessibility
Built to work for everyone.
Last updated: July 17, 2026.
SplitEase is designed to work for everyone. Our mobile app supports the iOS and Android accessibility features listed below. If you find something we can improve, email hello@splitease.ai.
Screen readers (VoiceOver / TalkBack)
Every interactive element in the app is labeled, has a role (button, header, switch, tab, checkbox, radio), and announces state changes. Form fields expose their labels to screen readers, and error messages announce via a live region as they appear. Toast messages (success, error, warning) are spoken through the system announcement API. Screen titles are marked as headings so users can navigate by heading.
Voice Control
Every button carries a spoken name matching its visible label, so commands like "Tap Add Expense", "Tap Save", or "Tap Back" work throughout the app. Icon-only buttons carry explicit labels enforced at the code level.
Larger Text (Dynamic Type)
Text scales with the system Larger Text setting up to 1.3× the base size. We cap scaling to preserve layout integrity on data-dense screens (balances, split editors); if you need larger, please let us know.
Reduced Motion
The app watches the system Reduce Motion setting and disables spring animations, entrance transitions, and looping pulses when it's on. Final states remain intact — only the motion is skipped. This applies to the tab bar, onboarding, tutorial spotlights, and the voice recording pulse.
Sufficient Contrast
Body text meets WCAG AA (4.5:1) contrast against page backgrounds in both light and dark modes. Secondary text and UI elements meet 3:1. Interactive primary buttons use dark ink on the lime accent (well above 4.5:1).
Differentiate Without Color Alone
"You owe" and "You're owed" balances are shown with color and a directional icon and the literal words. Selection states use a checkmark plus color. No information depends on color alone.
Dark Mode
The app fully supports iOS/Android system dark mode, with a dedicated warm dark palette (not just inverted colors). Users can also force light, dark, or system-matched in Settings.
Touch Targets
Every tappable control has a minimum 44×44pt hit area, achieved through visible size or an extended press region. This meets Apple HIG and WCAG AA 2.5.5.
Haptic Feedback
Every interaction produces a matching haptic (light tap on buttons, selection change on toggles, success/warning/error notifications on outcomes). Users who prefer no haptics can disable them in Settings.
What we’re still working on
- Full end-to-end VoiceOver testing on every screen.
- Extended Dynamic Type support beyond the 1.3× cap on select screens.
- Captions and audio descriptions — we don't currently ship video content, but if we add tutorials this is planned.
Contact
Email hello@splitease.ai to report an issue, request a feature, or ask about our roadmap. We reply within 5 business days.
Accessibility Contact
Email: hello@splitease.ai