Accessibility
Last updated 20 August 2026
This page says what's actually true today, not what a generic accessibility statement usually says. Life OS has not been through a formal accessibility audit, and this is not a conformance claim. It's a plain account of what's been built in, and an open invitation to report what hasn't.
VoiceOver
Interactive controls across the app — buttons, rings, list rows, form fields — carry explicit VoiceOver labels rather than relying on Apple's automatic guesses, in a large majority of the app's screens. Some views also group or hide decorative elements specifically so VoiceOver reads the meaningful content in a sensible order rather than announcing every visual layer. That said, this hasn't been walked end to end with VoiceOver running as the only input method, so some screens may still have rough edges — see "Report a gap" below.
Reduce Motion
The system Reduce Motion setting is currently honored specifically in the Calendar space's own animations. Separately, Settings has its own in-app "Movement" switch that turns off Life OS's animated transitions app-wide — a manual override independent of the system setting, for anyone who wants animation off without changing it system-wide.
Text size
A number of text elements shrink to fit their layout rather than truncating or overflowing at larger sizes. Full support for every Dynamic Type accessibility size, on every screen, hasn't been systematically tested — if a screen clips or overlaps at a larger text size you use, that's a real, specific, fixable bug and reporting it is genuinely useful.
Colour and contrast
The app follows the system's light and dark appearance rather than forcing one, and the palette was chosen with legible contrast in mind. It has not been run through a formal contrast-ratio audit against WCAG thresholds, so this is a design intention stated honestly, not a compliance claim.
Report a gap
If VoiceOver, Switch Control, Voice Control, or a larger text size makes something in Life OS hard or impossible to use, email s0533495227@gmail.com with the screen and what happened. It's read by the person who wrote the app, and a real, specific report is the fastest way to get something fixed.