pressable + disable + accessibility bug

This issue has been tracked since 2022-09-16.

Description

I use the 'Pressable' component which in some cases can become 'disabled', without the enabled TalkBack function on android everything is fine, but as soon as this function is enabled, the 'Pressable' element is always available, no matter if it is 'disabled' or not

Version

0.64.0

Output of npx react-native info

System:
OS: Windows 10 10.0.22000
CPU: (8) x64 Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz
Memory: 1.20 GB / 7.88 GB
Binaries:
Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.18 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.6.0 - ~\AppData\Roaming\npm\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Not Found
Visual Studio: Not Found
Languages:
Java: 11.0.16 - /c/Program Files/OpenJDK/openjdk-11.0.16_8/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.0 => 0.64.0
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found

Steps to reproduce

The Pressable component has disabled=true property, then you need to enable the TalkBack function on the android device and try to interact with your Pressable component using it

Snack, code example, screenshot, or link to a repository

<Pressable
accessibilityLabel='example'
disabled={true}

More Details About Repo
Owner Name facebook
Repo Name react-native
Full Name facebook/react-native
Language JavaScript
Created Date 2015-01-09
Updated Date 2022-10-03
Star Count 105144
Watcher Count 3666
Fork Count 22469
Issue Count 2232

YOU MAY BE INTERESTED

Issue Title Created Date Updated Date