For android, accessibility properties on and are ignored by screen reader

Bug report


In Android device when screen reader is turned “ON”, the accessibility properties on <Marker /> are ignored by screen reader and nothing is announced when user taps on a marker.
Also, the <Callout /> is not accessible. I am unable to tap and access <Callout /> descendants. Instead the focus automatically goes to parent <MapView />

Environment info

react-native info output:

    OS: macOS 10.15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
    Memory: 47.00 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
    Node: 10.20.1 - ~/projects/*/mobileapp/react-native/node_modules/.bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.3
      System Images: android-26 | Google APIs Intel x86 Atom, android-28 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom
    Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild

Library version: 0.60.6

Steps to reproduce

  { => (
      accessibilityLabel={`Some useful label`}
      <MyCustomMarkerView {...marker} />
     <Callout accessible>
        <MyCustomCalloutView {...marker} {...accessibleProps} />
   </Marker />
  1. Turn on screen reader (Talkback).
  2. Navigate to screen where <MapView /> is shown.
  3. Now, with talkback on, try to tap on custom <Marker /> shown and notice if screen reader announce it. Nothing is announced, accessibility props are ignored by screen reader.
  4. Double tap on <Marker />, it displays <Callout />, try to tap on it. Unable to tap on <Callout />, focus shift to parent <MapView /> component

Describe what you expected to happen:

  1. Screen reader should readout the accessibility labels passed.

1 possible answer(s) on “For android, accessibility properties on and are ignored by screen reader

  1. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.