-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
[a11y][iOS] Nested accessibility items not accessible #27147
Comments
I may be asking the wrong question but why would you nest |
@CoryWritesCode this is how we’ve been creating text all in one line where different parts of the text needs different styling. For example, if one part of a sentence needs a hyperlink. Wrapping with a View even with flexWrap “wrap” has some visual issues, unless maybe we create a separate child Text component for every word. So there is a sort of a clunky workaround, however it seems like native iOS and Flutter have a nicer way of handling nested accessibility, that would be nice to have in React Native as well. |
I can see that @cihan-m. Makes sense as RN doesn't have a |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Hello,
This is basically a repeat of #24515. It seems like that issue is locked though, so creating a new one.
React Native version: 0.61.2
Steps To Reproduce
Describe what you expected to happen:
Voiceover user should be able to access the entirety of the text, and the hyperlink (so both the parent Text component and nested Text components). There were two strategies proposed by @sahrens in #24515, can we open that issue back up to continue that discussion?
The text was updated successfully, but these errors were encountered: