This repository has been archived by the owner on Jun 24, 2022. It is now read-only.
A11y focus issues #766
Merged
A11y focus issues #766
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #734 and #732
These issues relate to the navigation not handling the
useLayoutEffecthook when the screen changes focus. Fixes below allow for calling a function to manually focus on elements after the screen has received focus in certain scenarios where needed. Tested on Android with TalkBack.focusOnElementfunction to/src/shared/useAccessibilityAutoFocus.tsto allow focus on elements from anywhere in codeuseAccessibilityAutoFocusnow returns an array containing:[Manual focus ref , Auto focus ref]