-
Notifications
You must be signed in to change notification settings - Fork 24.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessibility in android- With talkback elements are not clickable while on a screen from stack navigator. #45482
Comments
|
@stutiv48 Repros are mandatory. Please provide a repro with project/video 👍 |
@cortinico I have added the repro along with video. Here the current screen page is Login_AND_REGISTRATION which is called through stack navigation. Through which only the first element is accessible but on calling it directly the it is working fine |
@stutiv48 the repro should be: If your bug is UI related: a Snack |
UPDATE : This issue solved by upgrading the react native version in the project 👍 |
Description
I'm using React Native with the Android platform. I'm using the Stack Navigator to navigate between screens. I've noticed that when I use the TalkBack accessibility service, the elements on the screen are not clickable.
I'm having an issue with accessibility in a screen that I call in the RootNavigator. When I call the screen directly, accessibility works fine. However, if I call the screen in stack navigation, only the first element of the screen is accessible, and the other elements are unclickable. I've tested this Voiceover it is working fine with stack navigation, and the issue only occurs with Talkback.
Steps to reproduce
React Native Version
0.71.8
Affected Platforms
Runtime - Android
Output of
npx react-native info
Stacktrace or Logs
Reproducer
##LoginAndRegiterScreen
In first video stack navigation is used to render the login screen while in second one it is directly called
Screenshots and Videos
Screen.Recording.2024-07-19.at.6.59.28.PM.mov
Screen.Recording.2024-07-19.at.7.00.53.PM.mov
The text was updated successfully, but these errors were encountered: