Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[med] : Many pages: Chrome + Jaws: Name & Role is not defined for Back (<) control. #8522

Closed
Stutikuls opened this issue Apr 7, 2022 · 1 comment

Comments

@Stutikuls
Copy link

Stutikuls commented Apr 7, 2022

Action Performed:

  1. Using Chrome + Jaws, open URL staging.new.expensify.com
  2. Navigate to any chat window using Tab key and press Enter to select it.
  3. Resize the page.
  4. Navigate to Back(<) button using Tab key.
  5. Observe the screen reader announcement.

Expected Result:

Name & Role should define for the Back (<) control. Screen reader should read like "Back button".

Actual Result:

Name & Role is not defined for Back (<) control. Screen reader is reading "unlabeled".

Note-

  1. On Android screen reader is 'Silent'
  2. On MAC screen reader is 'group'

Other occurrences

Same issue repro on PR #8795, #8969

Workaround:

Yes

Area issue was found in:

All pages

Failed WCAG checkpoints

4.1.2

User impact:

Name & Role are the fundamental attribute for accessibility. If the role & name are not announced, then Screen reader user will have difficulty understanding the purpose of the button.

Suggested resolution:

Make sure that screen reader announces the correct name of the button.

Refer to: https://knowbility.org/blog/2021/whats-in-a-name

Platform:

  • Web
  • Android
  • Desktop App
  • Mobile Web

**Version Number: ** v1.1.49-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
Issue reported by: Stuti

7801_Name.role.is.not.defined.for.the.back.control.mp4
@melvin-bot
Copy link

melvin-bot bot commented Jun 24, 2022

@Stutikuls, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant