fix: unify call quality accessibility descriptions [WPB-24422]#4725
Merged
fix: unify call quality accessibility descriptions [WPB-24422]#4725
Conversation
|
yamilmedina
approved these changes
Apr 14, 2026
ohassine
approved these changes
Apr 14, 2026
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
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.



https://wearezeta.atlassian.net/browse/WPB-24422
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764The PR Description
What's new in this PR?
Issues
Talkback reads some call quality dashboard button actions as "double tap to activate" and for others is more specific with "double tap to view details". We want all buttons to have unified description - the action is the same so the description also should be the same.
Solutions
Remove custom action names for click labels.
Add the button name as
contentDescriptionand move the part related to the state that changes tostateDescription- thanks to that state is read again when it changes, and the content is read only once after reading the state, but before "double tap to activate". So for the "view details" row with quality state, talkback reads it as: "network quality: good, view details, double tap to activate".Testing
How to Test
Join/start a call, open call details, enable talkback and let it read the content.
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.