-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Description
Action Performed:
Prerequisites:
- the user is signed in
- Using NVDA+Firefox, open the URL https://new.expensify.com/
- Navigate using the Tab key to the Workspaces section. and press the enter key to activate it.
- Tab to focus the More options icon button (three vertical dots).
- Observe the screen reader announcement.
Expected Result:
The control should be announced with a button role.
Actual Result:
The screen reader does not announce any actionable role when the control More options icon (three vertical dots). When focused, the screen reader announces only the label of the control as “More options”. Hence the screen reader users will not be aware that the control is actionable and can be activated.
HTML:
Area issue was found in:
Workspace
Failed WCAG checkpoints
WCAG 4.1.2 Name, Role, Value
https://www.w3.org/WAI/WCAG22/Understanding/name-role-value
User impact:
Providing role, state, and value information on all user interface components enables compatibility with assistive technology, such as screen readers, screen magnifiers, and speech recognition software, used by people with disabilities.
Suggested resolution:
Ensure that the interactive element has a semantic button role and a proper accessible name. Here, replace the role="presentation" to role="button" to announce the actionable role of a button. Alternatively, implement the control using native elements such as a button.
https://webaim.org/techniques/forms/controls#buttons
Environment(s)
Windows Windows 11 - Firefox
Screenshots/Videos
Bug6996754_1762788311479.SR-Workspace-The_button_of_more_options_has_no_button_role_announced.mp4
Version Number: NA
Reproducible in staging?: NA
Reproducible in production?: Yes
Email or phone of affected tester (no customers): NA
Logs: https://stackoverflow.com/c/expensify/questions/4856 NA
Notes/Photos/Videos: Any additional supporting documentation Yes
Expensify/Expensify Issue URL: https://platform.applause.com/company/12102/products/36605/community-issues/6996754
Issue reported by: NA
Slack conversation: NA