Description
There appears to be a regression in the iOS accessibility activation behavior when enabling the React Native New Architecture.
With the Old Architecture, onAccessibilityAction with the activate action was sufficient to handle VoiceOver's standard double-tap gesture.
After enabling the New Architecture on iOS, the same implementation no longer reliably triggers onAccessibilityAction when the user performs the standard VoiceOver double-tap gesture.
Adding onAccessibilityTap makes the interaction work again.
Expected behavior
VoiceOver double-tap should trigger the activate accessibility action and invoke onAccessibilityAction.
<View
accessible={true}
accessibilityRole="switch"
accessibilityActions={[{name: 'activate'}]}
onAccessibilityAction={handleAccessibilityAction}
/>
Actual behavior
With the New Architecture enabled on iOS, VoiceOver can focus the element correctly, but performing the standard double-tap does not reliably invoke:
onAccessibilityAction
Adding:
onAccessibilityTap={handleAccessibilityAction}
causes the double-tap interaction to work.
Steps to reproduce
Steps to reproduce
- Create a new React Native project.
- Enable the New Architecture.
- Run the application on a physical iOS device.
- Enable VoiceOver.
- Focus the accessible switch.
- Perform the standard VoiceOver double-tap gesture.
- Observe whether onAccessibilityAction is invoked.
- Add onAccessibilityTap.
- Repeat the double-tap.
- Observe that the action is now triggered.
React Native Version
0.86.3
Affected Platforms
Runtime - iOS
Areas
Fabric - The New Renderer
Output of npx @react-native-community/cli info
System:
OS: Windows 11 10.0.26200
CPU: "(16) x64 AMD Ryzen 7 5800H with Radeon Graphics "
Memory: 862.17 MB / 5.86 GB
Binaries:
Node:
version: 24.15.0
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 1.22.19
path: C:\Users\Ola Abaza\AppData\Roaming\npm\yarn.CMD
npm:
version: 11.12.1
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-212.5712.43.2112.8815526
Visual Studio: Not Found
Languages:
Java: Not Found
Ruby: Not Found
npmPackages:
"@react-native-community/cli":
installed: 20.1.0
wanted: 20.1.0
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.86.3
wanted: 0.86.3
react-native-windows: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Stacktrace or Logs
MANDATORY Reproducer
https://github.com/OlaAbaza/rn-accessibility-reproducer
Screenshots and Videos
No response
Description
There appears to be a regression in the iOS accessibility activation behavior when enabling the React Native New Architecture.
With the Old Architecture, onAccessibilityAction with the activate action was sufficient to handle VoiceOver's standard double-tap gesture.
After enabling the New Architecture on iOS, the same implementation no longer reliably triggers onAccessibilityAction when the user performs the standard VoiceOver double-tap gesture.
Adding onAccessibilityTap makes the interaction work again.
Expected behavior
VoiceOver double-tap should trigger the activate accessibility action and invoke onAccessibilityAction.
<View
accessible={true}
accessibilityRole="switch"
accessibilityActions={[{name: 'activate'}]}
onAccessibilityAction={handleAccessibilityAction}
/>
Actual behavior
With the New Architecture enabled on iOS, VoiceOver can focus the element correctly, but performing the standard double-tap does not reliably invoke:
onAccessibilityAction
Adding:
onAccessibilityTap={handleAccessibilityAction}
causes the double-tap interaction to work.
Steps to reproduce
Steps to reproduce
React Native Version
0.86.3
Affected Platforms
Runtime - iOS
Areas
Fabric - The New Renderer
Output of
npx @react-native-community/cli infoStacktrace or Logs
MANDATORY Reproducer
https://github.com/OlaAbaza/rn-accessibility-reproducer
Screenshots and Videos
No response