Skip to Content
Platform.Ontology

Screen reader and assistive services flags

Tells whether TalkBack or VoiceOver, Switch Control and similar are running.

Gets silentlyLanguage and settingsAccessibilityAndroid and iPhoneWhen the app opensWhile you use it

In one line

Can tell whether TalkBack, VoiceOver or similar helpers are switched on

Tells whether TalkBack or VoiceOver, Switch Control and similar are running.

Discloses disability: a special-category fact. Apps need it to adapt, but it is a sensitive inference and Play restricts using the Accessibility API for it.

What it can and can't do

What the user does: Nothing. It happens when the app draws or when you turn a helper on

It can

  • Check if a screen reader is on
  • Check for Switch Control and similar services
  • List the enabled accessibility service IDs on Android
  • Adjust its screens for assistive technology

It cannot

  • See what the screen reader is saying
  • Turn the helper off
  • Show you a prompt; none is used for these checks

How it differs between platforms: Android also lists the IDs of enabled services. iPhone gives one yes or no per service.

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
First versionAndroid 4.0 (API 14)iOS 3.0
Permission or entitlementNot listednone
Protection levelnonenone
How access is grantednonenone
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyNone listedNone listed
APIAccessibilityManager.isEnabled(), isTouchExplorationEnabled(), getEnabledAccessibilityServiceList()One boolean per service
NotesIncludes list of enabled service IDsNone

Data you get

What comes back: Assistive flags
Shape: object
How often: On change

FieldTypeUnitRangePrecision
talkback_onbooleanNonetrue, false1 bit
enabled_serviceslistpackage id0 to 10exact

Technical limits

  • Android exposes the service package list; iOS exposes booleans

The story

What it is

An app can tell if a screen reader or other assistive tool is on.

For you

You turn on VoiceOver or TalkBack and your phone speaks what you touch. Apps may adapt their screens to work better with it. You never see the app notice, but it can learn you use assistive tech.

For makers

Makers need this to avoid broken screens for blind users and to skip tricky captchas. It also reveals a disability, which is a very sensitive fact. Google limits who may use the accessibility service for anything else.

Where you see it

TypeExampleApps
gamesA game adds audio cues and simpler menus when a screen reader is on.None named
bankingA bank app swaps a drag slider for buttons that a screen reader can use.None named
shoppingA shop gives product images spoken descriptions for people using VoiceOver.None named
socialA social app reads out alt text for photos as the person scrolls.Instagram
securityA sign up flow skips a visual captcha when it sees a screen reader.None named
analyticsA tracker records the flag, which would reveal a disability if used for profiling.None named

Risks

  • Discloses a disability
  • Misuse for profiling

Android and iPhone in short

  • Android: Android apps can see if TalkBack and other accessibility services are on, and Play restricts how they may use that API.
  • iPhone: iPhone apps can see if VoiceOver, Switch Control and similar tools are on with no prompt.

What the platform says

  • Apple: VoiceOver. Apple's screen reader describes what is on screen so blind and low vision people can use their iPhone.
  • Google: TalkBack. Android's screen reader speaks what is on screen and helps people who are blind or have low vision.

Good uses and abuse

Legitimate uses

  • Adapt UI
  • Skip captchas

Known abuse

  • Disability profiling

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits2Rough identifying entropy, when known

Same idea on the web

Sources

How well checked: Based on official documentation.

On this page