-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Making links independently focusable by Talkback #33215
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
0e06e4b
Make links independently focusable by Talkback (#31757)
blavalla f5d053c
Remove .gitattributes causing error add_cacheinfo
fabOnReact 95a1357
Merge branch 'main' into independent-links
fabOnReact b8b0ea3
Merge branch 'main' into independent-links-rebased
fabOnReact c56ee8b
update EditText and Slider AccessDelegates
fabOnReact af0eecf
remove comment
fabOnReact 561266f
analysis-bot no-alert: Unexpected alert.
fabOnReact 0576405
Merge branch 'main' into independent-links-rebased
fabOnReact 485cf61
Merge branch 'main' into independent-links-rebased
fabOnReact File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you verify that this is still necessary? At the time this was written, if this didn't happen focus would move to the last link in the paragraph on the first swipe, and then the next swipe would start navigating through the links from the bottom to the top. I'm not sure if this is still necessary or not, as it seemed like it may have been an unintentional side effect of the way we create these ClickableSpans, and that code may have changed since then.
A video showing a focus on a paragraph and then a swipe through the links both with this code and without it should be enough.
This may also be impacting the order that the links appear in the "Links" menu, although their order there isn't as important, as it's out of the context of the text itself. Ideally these would still match though and the first link in the text would be first in the list as well as the first swipe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @blavalla Yes. It is still necessary.
I run a test of the functionality on the main branch and the PR branch.
I remain available for improvements. Thanks
I included below the test cases and updated the summary of the Pull Request.
TalkBack focus moves through links IN THE CORRECT ORDER from top to bottom (PR Branch with link.id)
Testing with the link.id in AccessibilityLink (discussion)
Expected Result:
Swiping move TalkBack focus in this order:
This is a test of inline links in React Native. Here's another link. Here is a link that spans multiple lines because the text is so long. This sentence has no links in it. links available
test
,inline links
,another link
,link that spans multiple lines...
)Links are displayed in the above order in the TalkBack menu
Actual Results:
RESULT 1 (SUCCESS) - Swiping moves TalkBack focus in the correct order
This is a test of inline links in React Native. Here's another link. Here is a link that spans multiple lines because the text is so long. This sentence has no links in it. links available
2022-03-07.09-11-19.mp4
RESULT 2 (FAIL) - Links are NOT displayed in the correct order in the TalkBack menu
2022-03-07.09-13-23.mp4
TalkBack focus does NOT move through links in the correct order from top to bottom (PR Branch without link.id)
Testing without the link.id in AccessibilityLink (discussion)
Expected Result:
Swiping move TalkBack focus in this order:
This is a test of inline links in React Native. Here's another link. Here is a link that spans multiple lines because the text is so long. This sentence has no links in it. links available
test
,inline links
,another link
,link that spans multiple lines...
)Links are displayed in the above order in the TalkBack menu
Actual Results:
RESULT 1 (FAIL) - Swiping moves TalkBack focus in this wrong order
This is a test of inline links in React Native. Here's another link. Here is a link that spans multiple lines because the text is so long. This sentence has no links in it. links available
link that spans multiple lines because the text is too long
.2022-03-07.08-07-55.mp4
RESULT 2 (FAIL) - Links are NOT displayed in the correct order in the TalkBack menu
2022-03-07.08-17-20.mp4