Skip to content

bug(button-toggle): Accessibility breaks with matTooltip #28017

Open

Description

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

When adding the tooltip on a button toggle, the screen reader loses the group detection.

Reproduction

StackBlitz link: https://stackblitz.com/edit/dh5vz6?file=src%2Fexample%2Fbutton-toggle-overview-example.ts,src%2Fexample%2Fbutton-toggle-overview-example.html
Steps to reproduce:

  1. Use NVDA screen reader
  2. Navigate with the browse mode

Expected Behavior

The second button toggle should be detected as a whole. Like the first button toggle.

Actual Behavior

When navigating on the second button toggle, the screen reader doesn't mention all the other buttons at once.

Environment

  • Angular: 16
  • CDK/Material: 16
  • Browser(s): Edge
  • Operating System (e.g. Windows, macOS, Ubuntu): Windows 11
  • Screen reader: NVDA
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

AccessibilityThis issue is related to accessibility (a11y)P4A relatively minor issue that is not relevant to core functionsarea: material/button-togglearea: material/tooltipneeds: clarificationThe issue does not contain enough information for the team to determine if it is a real bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions