Possibly solve the issue with TalkBack order #47213
Open
+30
−21
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.
Solving issue #45096
Summary:
Change the order of setter in onInitializeAccessibilityNodeInfo and ensure the getTalkbackDescription return correct text for TalkBack
The order of TalkBack is not set correctly due to the way that we use setter in the method onInitializeAccessibilityNodeInfo. (It can be found in packages/react-native/ReactAndroid/src/main/java/react/ReactAccessibilityDelegate.java
The method goes from top to bottom and the setters was in order of:
setRole -> setTooltipText -> setLabeledBy -> setState -> addAction -> setCollectionItemInfo
->setRangeInfo
I also update the getTalkbackDescription to return the correct order of text for TalkBack by returning the talkbackSegments at once instead of keep checking twice