You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Navigate to Setting using Tab key and press Enter to select it.
Navigate to any workspace using Tab key and press using Enter to select it.
Navigate to More button using Tab key and press Enter to activate it.
Observe the behavior.
Expected Result:
All the interactive elements must be operable using screen reader. User should be able to accessible 'More' button by using Enter key.
Actual Result:
The 'More' button is not accessible using screen reader. When pressing the more button using screen reader different content appeared.
Other Occurrences:
Same issue also repro on PR #8581, #8906
PR #8730, #9220, #9193 -Call icon is not accessible using screen reader,
PR #7849, #8739 -Download button is not accessible using screen reader.
PR #9055 -Profile picture is not accessible using screen reader.
Workaround:
Yes
Area issue was found in:
Settings -> More
Failed WCAG checkpoints
4.1.1
User impact:
The Screen reader users are not able to use the 'More' button functionality as mouse/keyboard users.
Suggested resolution:
Make sure the more button performs the same action for both keyboard and screen reader users, and be sure the screen reader announces the correct name of the control.
Action Performed:
Expected Result:
All the interactive elements must be operable using screen reader. User should be able to accessible 'More' button by using Enter key.
Actual Result:
The 'More' button is not accessible using screen reader. When pressing the more button using screen reader different content appeared.
Other Occurrences:
Workaround:
Yes
Area issue was found in:
Settings -> More
Failed WCAG checkpoints
4.1.1
User impact:
The Screen reader users are not able to use the 'More' button functionality as mouse/keyboard users.
Suggested resolution:
Make sure the more button performs the same action for both keyboard and screen reader users, and be sure the screen reader announces the correct name of the control.
Refer to:
https://www.w3.org/TR/wai-aria-practices-1.1/examples/button/button.html
Platform:
Version Number: v1.1.49-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue reported by: Stuti
7990_More.button.is.not.accessible.using.screen.reader.mp4
The text was updated successfully, but these errors were encountered: