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 : Combo box label is not announced by the screen reader. #8553

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

Comments

@Stutikuls
Copy link

Stutikuls commented Apr 8, 2022

Action Performed:

  1. Using Chrome, open URL staging.new.expensify.com
  2. Navigate to Setting using Tab key and press Enter to select it.
  3. Navigate to preferences using Tab key and press using Enter to select it.
  4. Navigate to combo boxes using Ta key.
  5. Observe the screen reader announcement.

Expected Result:

Combo box label should be announced by the screen reader. It should read as "Priority mode Focus combo box collapsed"

Actual Result:

Combo box label is not announced by the screen reader. Screen reader is reading "focus combo box".

Note
Same issue repro on all pages where combo boxes are presented.

Other occurrences

Same issue repro on PR #8765

Workaround:

Yes

Area issue was found in:

Combo box

Failed WCAG checkpoints

1.3.1

User impact:

Screen reader user does not know the purpose of the combo box, if the label is not announced by the screen reader.

Suggested resolution:

Make sure screen reader announces the label of the combo box. (i.e. Priority mode)
Refer to:
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label

Platform:

  • Web
  • Desktop App

**Version Number:**v1.1.49-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
Notes/Photos/Videos: Any additional supporting documentation
Issue reported by: Stuti

7907_Label.priority.Mode.of.the.combo.box.not.read.by.screen.reader.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