[Android][FactSets]: Mark textViews important for accessibility explicitly #7452
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.
Related Issue
Factset accessibility issue
Fixes #6752
Description
FactSets TextViews are wrapped under multiple ViewGroups, and further nesting, like having FactSets cards view under RecyclerViews is making Android accessibility services to skip factset data for talkBack (sometimes).
So marking these TextViews as important for accessibility explicitly
-- Newer API (for API26 and above) setScreenReaderFocusable() is used
-- Handled backward Compatibility also
Solution reference: Principles for improving app accessibility
Sample Card
Expense report example of Adaptive Cards Visualizer (sample app)
How Verified
Verified : Factset related Accessibility talkback and navigation for
Microsoft Reviewers: Open in CodeFlow