Repository navigation
[Android] TalkBack announces no state for unchecked checkbox and radio because stateDescription is never set #58739
Description
Description
On Android, a checkbox or radio built with role="checkbox" or role="radio" and aria-checked={false} is announced by TalkBack with its name and role but no state. For example: "Email me offers, tickbox". Once checked, TalkBack announces "Ticked" (en-GB wording for "checked"). A TalkBack user cannot tell an unchecked option from an element that has no state at all. The legacy accessibilityState={{ checked: false }} behaves the same.
The unchecked state does reach Android. A pressable radio with aria-checked={false} gets TalkBack's "double-tap to toggle" hint, which TalkBack only gives checkable nodes. The same radio without aria-checked gets "double-tap to activate". So ReactAccessibilityDelegate.setState is setting isCheckable = true and isChecked = false as intended.
What is missing is AccessibilityNodeInfo.stateDescription. Native CompoundButton (CheckBox, RadioButton, Switch) sets it on API 30 and later, and current TalkBack speaks the unchecked state from it. In the same screen, a native Switch that is off is announced as "off". ReactAccessibilityDelegate never calls setStateDescription, so TalkBack has nothing to speak for the unchecked case. I checked the source of 0.81.0, 0.86.3, 0.87.1 and main at commit d194d8b (29 September 2026). None of them set stateDescription.
TalkBack output on the device, one element per line. This was recorded on 0.86.3 in an app with the same props as the Snack. Element names are changed to match the Snack.
- Native
Switch, off: "Native switch, off". This is the control and works. role="checkbox",aria-checked={false}: "Email me offers, tickbox". No state.role="radio",aria-checked={false}: "Express, radio button". No state.accessibilityRole="radio",accessibilityState={{ checked: false }}: "Express, radio button". No state.role="radio"checked, then unchecked by double-tapping: "Ticked, Express, radio button", then "Express, radio button".role="radio"with noaria-checked: "Express, radio button". Identical to the unchecked radio.role="radio",aria-checked={false}, withonPress: "Probe J, radio button, double-tap to toggle".role="radio", no state, withonPress: "Probe K, radio button, double-tap to activate".
Expected: unchecked checkboxes and radios announce "not ticked" or "not checked", as native CheckBox and RadioButton do.
Related:
- [Android] Set AccessibilityNodeInfo.stateDescription so TalkBack stops reading "checked. on." on switches #58588 has the same root cause for switches: without
stateDescription, TalkBack reads "checked. on.". SettingstateDescriptionwhenevercheckedis set would fix both. - Talkback announces TouchableOpacity with accessibilityRole="radio" and accessibilityState "checked" in incorrect order #45096 shows TalkBack used to announce "not checked" for React Native radios, so this became audible when TalkBack started relying on
stateDescription.
App code cannot work around this. No JavaScript prop reaches stateDescription, and accessibilityValue.text only appends to contentDescription, which changes the accessible name.
Suggested fix: in ReactAccessibilityDelegate.setState, when checked is a boolean, also set info.stateDescription to a localised "checked" or "not checked" string. For role="switch" use "on" or "off", as #58588 proposes.
Steps to reproduce
- Open the Snack below on an Android device with TalkBack on.
- Swipe to the native switch. TalkBack says "Native switch, off".
- Swipe to "Email me offers". TalkBack says "Email me offers, tickbox", with no state.
- Swipe to the "Express" radio. TalkBack says "Express, radio button", with no state.
- Double-tap "Express", then swipe away and back. TalkBack now says "Ticked, Express, radio button", and "Standard" has no state.
- Swipe to Probe J and Probe K. J ends "double-tap to toggle" and K ends "double-tap to activate". This shows the unchecked state reached the node without being spoken.
React Native Version
0.86.3
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: Windows 11 10.0.26200
CPU: (14) x64 Intel(R) Core(TM) Ultra 7 155U
Memory: 17.80 GB / 31.52 GB
Binaries:
Node: 24.15.0
npm: 11.12.1
npmPackages:
react: 19.2.3
react-native: 0.86.3
Run in Expo Go on Expo SDK 57, which uses the New Architecture.
Device: Samsung Galaxy S25 Ultra, Android 16, TalkBack 17.
Stacktrace or Logs
No crash or error. This is an accessibility output bug. The TalkBack output for each element is under Description.
MANDATORY Reproducer
https://snack.expo.dev/@saleeem4rahman/talkback-unchecked-state-missing
Snack saved this on Expo SDK 54 (React Native 0.81). The TalkBack output above was recorded on 0.86.3 with the same props, and the Android accessibility delegate in 0.81 also sets setCheckable(true) without a state description.
Screenshots and Videos
None. The behaviour is audible, not visible.
Activity
BilalWalker commentedon Oct 12, 2026
Opened a fix in #59009:
ReactAccessibilityDelegate.setStatenow setsstateDescriptionwhenevercheckedis a boolean ("checked" / "not checked", and "on" / "off" for the switch role), so TalkBack announces the unchecked state.salrahman commentedon Oct 13, 2026
Thanks @BilalWalker, this matches what I traced. Two notes:
uimanager/res(for examplestate_on_descriptionis "sì" in values-it and "ein" in values-de), so the newstate_checked_descriptionandstate_unchecked_descriptionshould ideally be translated too. Otherwise non-English TalkBack users would hear an English word where TalkBack currently speaks their language.BilalWalker commentedon Oct 13, 2026
Thanks @salrahman, good catch on both. I looked at how those translations get in: every
values-*/strings.xmlchange comes from Meta's internal "Intl Scheduler" commits (last ran June 2023), not from PRs, which is whylink_description,rn_tab_descriptionandtimer_descriptionare English-only in every locale today. So any new string would stay English for a while regardless.To keep that from regressing the checked case, I narrowed #59009: the switch role uses the existing
state_on_description/state_off_description(translated in all 65 locales), and for checkbox/radio only the unchecked state gets the newstate_unchecked_description. A checked checkbox leavesstateDescriptionunset, so TalkBack keeps saying "Ticked" (or the device-language equivalent) exactly as now. Only the currently silent case gets a new, for now English-only, string.