issue 66: screen reader compatibility #112
Open
Conversation
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
ian-zyh
reviewed
Jun 5, 2025
Collaborator
ian-zyh
left a comment
ian-zyh
left a comment
There was a problem hiding this comment.
Everything works pretty well on android devices, I tested it on multiple devices. Just like you mentioned, I think we might need to test it on ios devices.
…lector into accessibility
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.
fixes issue #66
This adds React Native accessibility fields to multi-select dropdowns, single-select dropdowns, and their underlying selection list entries, allowing Android's native screen reader, talkback, to function.