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.

Sign up for GitHub

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

Jump to bottom

bug(select): Non-native Selects do not announce state properly with screen readers #30362

Open
1 task
bmayen opened this issue Jan 21, 2025 · 0 comments
Open
1 task

bug(select): Non-native Selects do not announce state properly with screen readers #30362

bmayen opened this issue Jan 21, 2025 · 0 comments
Labels
Accessibility This issue is related to accessibility (a11y) area: material/select P2 The issue is important to a large percentage of users, with a workaround

Comments

@bmayen
Copy link

bmayen commented Jan 21, 2025

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

Reported by our accessibility team:
"When the selects are activated the state is not communicated. In JAWS neither state is communicated, in NVDA only the collapsed state is communicated."

Reproduction

StackBlitz link:
Steps to reproduce:
1.
2.

Expected Behavior

Should announce different states on state changes

Actual Behavior

In JAWS neither state is communicated, in NVDA only the collapsed state is communicated

Environment

  • Angular: 18.x
  • CDK/Material: 18.x
  • Browser(s): Chromium
  • Operating System (e.g. Windows, macOS, Ubuntu): Windows/OSX
@bmayen bmayen added the needs triage This issue needs to be triaged by the team label Jan 21, 2025
@wagnermaciel wagnermaciel added P2 The issue is important to a large percentage of users, with a workaround 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 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Accessibility This issue is related to accessibility (a11y) area: material/select P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bmayen @wagnermaciel