Action Performed:
- Using Chrome+JAWS, open URL: staging.new.expensify.com
- Navigate to Settings > Create new Workspace > Search for the created workspace > Details.
- Navigate to "back (<)", "Members", "Settings", "Invite", etc. controls using the screen reader.
- Observe the screen reader announcement.
Expected Result:
When a role is defined appropriately for the interactive element, the screen reader user will interact with the element effectively.
Actual Result:
Role is not defined for the "back (<)", "Members", "Settings", "Invite", etc. controls. This made it difficult for screen reader users to access the functionality associated with it. Additionally, the label is not defined for the mentioned interactive element in the source code of the page.
other occurrences:
Same issue repro on PR #8065, #8103, #8476, #8409, #9118, #9170, #8878, #9202
Same issue repro on PR #8760, #8873- Roles are not defined for send and next controls.
Workaround:
Yes
Area issue was found in:
Details
Failed WCAG checkpoints
4.1.2, 1.1.1
User impact:
Screen reader users will not be made aware that these elements are buttons.
Suggested resolution:
Ensure that all the page functionality is available for all users irrespective of the device being used.
Apply the following changes:
- Specify role="button" for the 'div' element containing the "back (<)", "Members", "Settings", "Invite", etc. controls.
- Provide aria-label value such as "back" for the 'div' element containing the "back (<)" control.
Platform:
- Web
- Desktop App
- Mobile Web
Version Number: 1.1.49-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Reference link: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role
Issue reported by: Sumit
Action Performed:
Expected Result:
When a role is defined appropriately for the interactive element, the screen reader user will interact with the element effectively.
Actual Result:
Role is not defined for the "back (<)", "Members", "Settings", "Invite", etc. controls. This made it difficult for screen reader users to access the functionality associated with it. Additionally, the label is not defined for the mentioned interactive element in the source code of the page.
other occurrences:
Workaround:
Yes
Area issue was found in:
Details
Failed WCAG checkpoints
4.1.2, 1.1.1
User impact:
Screen reader users will not be made aware that these elements are buttons.
Suggested resolution:
Ensure that all the page functionality is available for all users irrespective of the device being used.
Apply the following changes:
Platform:
Version Number: 1.1.49-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Reference link: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role
Issue reported by: Sumit