Accessibility
This is engineering guidance and nothing else. It cites no accessibility standard by criterion or level — the standards body’s site was unreachable from our research environment when these pages were written, and a citation we could not read is worse than none — and it makes no claim about the law anywhere. For obligations, store policy and health-data rules, see compliance. For building the app that runs on the wrist, see watch apps; for the algorithms behind a rep counter, AI motion.
When nobody is looking at the screen
The number changes four times a second and the user's eyes are on the road. Screen readers, live regions, and the trait that stops your rep counter shouting.
- VoiceOver and the numbers that change during a setApple's updatesFrequently trait tells VoiceOver to poll a timer or rep count instead of announcing it, which changes what the value has to say.UpdatedVerified August 22, 2026
- TalkBack and the Android workout screenSemantics, merged set rows and a polite live region for the rest timer: what Google's documentation says about TalkBack on an Android workout screen.UpdatedVerified August 22, 2026
- What to call an exercise, a set and a rep rangeWhy 3x10 at 60kg read literally is useless, and what an exercise, a set, a weight and a rep range should be called to a screen reader instead.UpdatedVerified August 22, 2026
- Making a health chart readable without the chartApple's audio graphs, the Android equivalent we could not verify, and the text summary plus data table that make an HRV or sleep trend readable.UpdatedVerified August 22, 2026
They can see it and still can't use it
Text that has to survive being doubled, targets that have to be hit with a shaking hand, and a screen that has to be readable in sunlight.
- Dynamic Type on a workout screen: what breaks at 200 percentApple asks for text enlargeable by at least 200 percent, 140 percent on watchOS. What that does to a timer, a rep count and a set table.UpdatedVerified August 22, 2026
- Touch targets when the hand is shakingApple's per-platform control sizes, Google's 48dp recommendation, and why pause and end workout should never sit next to each other.UpdatedVerified August 22, 2026
- Colour contrast when the screen is in sunlightGoogle's sp-based contrast thresholds, Apple's Increase Contrast guidance, and why heart-rate zones coloured by hue alone are the usual failure.UpdatedVerified August 22, 2026
- Reduce Motion in a coaching interfaceCut the confetti and the parallax, but a looping exercise demo teaches the movement. What to replace it with, and the Android gap we could not verify.UpdatedVerified August 22, 2026
- Gestures and hands-free control during a workoutApple says offer an onscreen way to achieve the same outcome as a gesture. That serves limited dexterity and anyone whose hands are on a barbell.UpdatedVerified August 22, 2026
The audio channel is already taken
Their music is playing and their headphones are in. What is left to tell somebody they finished a set, and what a class video owes a deaf viewer.
- Haptics when the audio channel is already busyMusic, a podcast and a coach are already using your audio channel. Apple says pair cues with matching haptics, and never let the tap be the only one.UpdatedVerified August 22, 2026
- Captions, subtitles and audio descriptions for workout videoApple defines four media alternatives. A demo video's information is visual, so audio description is the one fitness libraries skip and need most.UpdatedVerified August 22, 2026
Proving it
What a tool can catch, and the part only a person moving can.
Frequently asked questions
- Why does a fitness app need different accessibility work from a normal app?
- Because the conditions are different, not because the APIs are. A fitness product is used while the person is moving: eyes on the road or the floor, hands occupied or sweaty, phone on a bike mount or an armband, music already playing through the one audio channel your cues need, and a number on screen that changes several times a second. Each of those turns a standard control into an edge case. A rep counter is the clearest example — it is a label that updates constantly, which is a specific, documented problem with a specific, documented answer, and no general accessibility guide will ever mention it.
- Does this section tell me what the law requires?
- No, and that is deliberate. Every page here is engineering guidance sourced from Apple's and Google's own developer documentation. We do not cite accessibility standards by criterion or level, because the standards body's site was unreachable from our research environment when these pages were written, and a standards citation we could not read is worse than no citation. We also make no claims about legislation in any jurisdiction. Legal obligations, store policy and health-data rules live in the compliance section, and for anything binding you want a qualified professional, not a developer guide.
- Where should a team start if the app already shipped without any of this?
- Start with the screen somebody spends the workout on, not the settings screen. Turn on the screen reader and try to complete one set without looking: that single exercise surfaces unlabelled controls, a counter that either says nothing or will not stop talking, and buttons too small to hit while moving. Then run the platform's own tooling over the same screen — Apple's Accessibility Inspector audit, Android's Accessibility Scanner — because those catch the unlabelled and low-contrast elements faster than you can. What the tools cannot tell you is whether the flow works while somebody is actually exercising, which is why the testing page ends with people rather than tools.
Independent comparison, last reviewed August 22, 2026. Pricing, rate limits, and feature availability change often — confirm current details in each provider’s official documentation before you commit. Product and company names are trademarks of their respective owners; AIFitnessAPI is not affiliated with, endorsed by, or sponsored by any product listed here.