Skip to content
AF
Accessibility

Accessibility

Accessibility in a fitness app is not the same problem as accessibility in a news site, because the person is moving. Their eyes are on the road, their hands are occupied, their music owns the audio channel your cues need, and the number they care about changes several times a second — Apple has a documented trait for exactly that element, and almost nobody building a rep counter has heard of it. These pages cover the moments where a fitness product specifically breaks: live metrics under a screen reader, text that has to survive doubling, targets hit with a shaking hand, contrast in sunlight, animation somebody has asked to stop, a heart-rate trend nobody can see, and a class video nobody can hear. Every claim comes from Apple’s or Google’s own documentation.

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.

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.

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.

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.

All 36 questions in Accessibility, answered

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.