Skip to content
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

Several accessibilities roles are not working | Android #30807

Closed
nico22utn opened this issue Jan 28, 2021 · 5 comments
Closed

Several accessibilities roles are not working | Android #30807

nico22utn opened this issue Jan 28, 2021 · 5 comments
Labels
Accessibility Needs: Attention Issues where the author has responded to feedback. Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Resolution: Duplicate Resolution: Locked This issue was locked by the bot.

Comments

@nico22utn
Copy link

nico22utn commented Jan 28, 2021

Please provide all the information requested. Issues that do not follow this format are likely to stall.

Description

Currently, I've implemented the accessibilities feature for a RN app (0.63.4)
And I've noticed that several accessibilities roles are not working anymore.
It is happening only for Android.
I 've just tested for Samsung s10e and I was able to reproduce it.
Testing with samsung j6 is working as expected.

This PR could be related: https://github.com/facebook/react-native/pull/27496/files

React Native version:

0.63.4

Steps To Reproduce

Just Enable Talkback. You can follow this link(https://reactnative.dev/docs/accessibility) in order to enable the Talkback for the emulator
Read some element with the accessibiltyRole='header' or 'text' or 'keyboardkey'

Expected Results

The app should be able to read the different accessibilities roles.

@safaiyeh
Copy link
Contributor

Thank you @nico22utn for the issue & the investigation. Could you provide a repro and exact steps to test it with TalkBack so it is easier to investigate the issue. Once I can confirm it locally I'll tag the appropriate people.

PR ref: #27496

@safaiyeh safaiyeh added Accessibility Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Needs: Author Feedback and removed Needs: Triage 🔍 labels Jan 30, 2021
@github-actions
Copy link

⚠️ Missing Reproducible Example
ℹ️ It looks like your issue is missing a reproducible example. Please provide a Snack or a repository that demonstrates the issue you are reporting in a minimal, complete, and reproducible manner.

@nico22utn
Copy link
Author

Thank you @nico22utn for the issue & the investigation. Could you provide a repro and exact steps to test it with TalkBack so it is easier to investigate the issue. Once I can confirm it locally I'll tag the appropriate people.

PR ref: #27496

That happens in the Android devices. Just set in some view or text the following:
accessibilityRole="header" and that's it.
I think that It is not necessary a repo. Just tell me if you need more information.

@github-actions github-actions bot added Needs: Attention Issues where the author has responded to feedback. and removed Needs: Author Feedback labels Feb 1, 2021
@amarlette
Copy link

This issue will be resolved by #30839 as part of the Improved React Native Accessibility Project

@chrisglein
Copy link

Duplicate of #30839

@chrisglein chrisglein marked this as a duplicate of #30839 May 4, 2021
@facebook facebook locked as resolved and limited conversation to collaborators May 4, 2022
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label May 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility Needs: Attention Issues where the author has responded to feedback. Needs: Repro This issue could be improved with a clear list of steps to reproduce the issue. Resolution: Duplicate Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants