fix: allow pass-through of accessibilityRole on Chip #4327
Merged
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.
Motivation
The
Chip
component is frequently used for display purposes, and in these cases is often never clickable. However, theChip
element still announces as a button because it hasaccessibilityRole="button"
hardcoded.When the
Chip
element is not being used as a button, a more sensibleaccessibilityRole
should be able to be passed through. This PR keeps the default"button"
accessibilityRole
, but adds the ability to pass in a differentaccessibilityRole
if"button"
doesn't make sense.Related issue
n/a
Test plan
accessibilityRole='text'
as a prop to a Chip, and navigate to the Chip via screen reader. It should not announce as a button.accessibilityRole
prop, and navigate to the chip via screen reader; it should announce as a button.I have tested this locally, and it works as expected.