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
bug: a11y, talkback reads tab button twice when swiping to go to next/previous tab button #23332
Comments
Same problem with the ion-segment-button: |
We have the same problem with tabs being read/focues twiced when swiping left or irght through the page with talkback. I quickly tested with settings aria-hidden on the a tags inside the ion-tab-button and then the tab only got read/focused once. However, I'm not sure what other consequences that might occour by setting aria hidden on the link |
We encountered the same issue using ion-checkbox, when using TalkBack and linear navigation it reads the checkbox twice. The checkbox and its label are getting separate focus, so it reads it two times instead of reading it as a whole. |
Same problem here using ion-checkbox, ion-toggle and ion-segment |
Same issue here. Any solution ? |
Thanks for the issue. This has been resolved via #26576, and a fix will be available in an upcoming release of Ionic Framework. The same fix for segment will be resolved in #26575. The same issue for |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Bug Report
Ionic version:
[x] 5.x
Current behavior:
When going over a tab-button with screen-reader it will be red but if I tick left with one finger it keeps on the same item, reading again the label and identifing it as tab. Inspecting the item it's caused by an anchor element inside the component.
This happens only on Android Talkback.
Expected behavior:
As on iOS the screen reader should ignore the anchor inside the component.
Steps to reproduce:
Related code:
https://github.com/VittorioEuris/ionic-a11y-issues.git
Ionic info:
The text was updated successfully, but these errors were encountered: