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

select : Screen Reader is reading two times when user selects a value from combo-box #26480

Open
1 task done
SMuraliWipro opened this issue Jan 24, 2023 · 2 comments
Open
1 task done
Labels
Accessibility This issue is related to accessibility (a11y) area: material/select P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@SMuraliWipro
Copy link

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

This issue is seen in select component example. Screen reader is reading two times when user selects a values from combo-box.

Example link: [https://v11.material.angular.io/components/select/overview]

Reproduction

Steps to reproduce:

  1. Go to example link : [https://v11.material.angular.io/components/select/overview]
  2. Open NVDA screen reader and reach combo-box by hitting 'tab' key.
  3. Select a value from combo-box

Expected Behavior

Selected value should be understandable to screen reader users.

Actual Behavior

Selected values reading multiple times by screen reader.

Environment

  • Angular:
  • CDK/Material:
  • Browser(s):
  • Operating System (e.g. Windows, macOS, Ubuntu):
@SMuraliWipro SMuraliWipro added the needs triage This issue needs to be triaged by the team label Jan 24, 2023
@ArvindWip
Copy link

Hi Team,
Please provide us the solution for the issue. It would be helpful to get an answer sooner. Thanks.

Arvind

@zarend zarend added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent Accessibility This issue is related to accessibility (a11y) area: material/select and removed needs triage This issue needs to be triaged by the team labels Feb 9, 2023
@zarend
Copy link
Contributor

zarend commented Feb 13, 2023

Hello,

Thank you for reporting this issue. I wouldn’t expect this issue to block users from completing a workflow. For that reason, I’m updating the priority to P3. Please let us know if you have further concerns concerns and feel free to react with “👍” if you are impacted.

Best,
Zach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility This issue is related to accessibility (a11y) area: material/select P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
3 participants