react / react/react-native

[Accessibility] [TalkBack] PanResponder callbacks do not fire when TouchableOpacity/Pressable is pressed and TalkBack is on

Open
#45,997 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

API: PanResponder Component: TouchableOpacity Issue: Author Provided Repro Newer Patch Available
Dominant language
C++
Stars
127k
Forks
25.3k
Avg merge
1d 23h
Merged PRs (30d)
4

Description

Description

On Android with TalkBack on, TouchableOpacity/Pressable components do not trigger PanResponder callbacks when pressed if the TouchableOpacity/Pressable has on onPress prop and its focusable prop is not false.

Steps to reproduce
  1. Create a PanResponder and apply its panHandlers to a View.
  2. Add a Pressable inside the View and give it an onPress prop.
  3. View the app in Android with TalkBack on.
  4. Double-tap to activate, observe the pan responder callbacks DO NOT fire.

Furthermore, double-tapping a non-TouchableOpacity/Pressable element such as a Text component will trigger PanResponder callbacks.

In the example repo I provided it should print "PanResponder Callback Triggered' but its only printing "ON PRESS TRIGGERED"

React Native Version

0.73.6

Affected Platforms

Runtime - Android

Output of npx react-native info
System:
  OS: macOS 14.5
  CPU: (11) arm64 Apple M3 Pro
  Memory: 84.00 MB / 18.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.18.0
    path: ~/.nvm/versions/node/v18.18.0/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 9.8.1
    path: ~/.nvm/versions/node/v18.18.0/bin/npm
  Watchman:
    version: 2024.04.22.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK:
    API Levels:
      - "29"
      - "30"
      - "31"
      - "32"
      - "33"
      - "33"
      - "34"
    Build Tools:
      - 29.0.2
      - 30.0.2
      - 30.0.3
      - 33.0.0
      - 33.0.1
      - 34.0.0
    System Images:
      - android-28 | Google ARM64-V8a Play ARM 64 v8a
      - android-29 | Google Play ARM 64 v8a
      - android-31 | Google APIs ARM 64 v8a
      - android-33 | Google APIs ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2022.1 AI-221.6008.13.2211.9514443
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /Library/Java/JavaVirtualMachines/jdk-17.0.10.jdk/Contents/Home/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.6
    wanted: 0.73.6
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
Stacktrace or Logs
No Stacktrace or log
Reproducer

https://github.com/Abhisflyingsoon/android-panresponder-accessibility

Screenshots and Videos

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked reproducer and reproduce the issue on Android with TalkBack enabled, using the PanResponder, Pressable, and TouchableOpacity cases described. Trace the interaction from TalkBack activation through the Pressable or TouchableOpacity and PanResponder callbacks. Done means the PanResponder callbacks fire in the reported case while the onPress callback continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, react-native
Domain
accessibility, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.