Reword accessible prop in accessiblity guide#4656
Merged
Merged
Conversation
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
cortinico
approved these changes
Jun 18, 2025
coado
pushed a commit
to coado/react-native-website
that referenced
this pull request
Jun 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current description of the accessible prop is misleading and confusing. The current wording implies that this prop mainly "groups its children into a single selectable component", which is a round-about way of saying it can receive focus, I think? I am not really sure what that means.
Regardless, the main point is not hammered home: This prop allows the View to be discoverable by screen readers (and other things).
The example is also a bit misleading, since Text is focusable by default on iOS. It is not wrong, but the example is better for a guide on label co-opting, not basic use of accessible.
Curious how, if at all, I should change this for previous versions.
NOTE: This is the same as #4653, with the requested changes. I had mucked up my fork and wanted to fix it.