Skip to content

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

Open
@bmayen

Description

@bmayen

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    AccessibilityThis issue is related to accessibility (a11y)P2The issue is important to a large percentage of users, with a workaroundarea: material/select

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions