Open Bug 1937803 Opened 2 months ago Updated 1 month ago

NVDA will read out Loud the Name of a Tab group twice as a Collapsed/Expanded button + Tab Group

Categories

(Firefox :: Tabbed Browser, enhancement, P3)

Desktop
Unspecified
enhancement
Points:
2

Tracking

()

Accessibility Severity s4
Tracking Status
firefox-esr128 --- disabled
firefox133 --- disabled
firefox134 --- disabled
firefox135 --- affected

People

(Reporter: rdoghi, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: access, Whiteboard: [fidefe-tabgrps-tabbrowser])

Found in

  • 135.0a1 (2024-12-17)

Affected versions

  • 135.0a1 (2024-12-17)

Preconditions
Set browser.tabs.groups.enabled true
Enable Screen Readers

Affected platforms

  • all

Steps to reproduce

  1. Have a "Shopping" Tab Group created.
  2. Use Ctrl+ Right /Left arrows in order to reach the Tab Group label.

Expected result

  • NVDA should read out loud Collapsed/Expanded Shopping Tab group

Actual result

  • NVDA will read out loud "Shopping button collapsed Shopping Tab group"

Regression range
Not a Regression.

Discussed it with Jamie yesterday and so far it seems that this behavior is the most realistically doable way we could implement it, without breaking ARIA specs or user interactions, or both. The duplication is also more-less justified, because the button label is presented on-screen and the same on-screen text serves as a group label, so both are being announced in accordance with WCAG 2.2 Success Criterion 2.5.3 Label in name. Marking is as access-S4 because we still want to look for a more delightful experience.

Accessibility Severity: --- → s4

The severity field is not set for this bug.
:niklas, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(nbaumgardner)
Blocks: 1928439
Severity: -- → S4
Points: --- → 2
Priority: -- → P3
Whiteboard: [fidefe-tabgrps-tabbrowser]
See Also: → 1943032

There is currently no way to make it not repeating without breaking HTML/ARIA specs (or both), because the issue is stemming from the screen reader focus entering the group (announcing its label #1) and then reading actual on-screen label text, because this is the first focusable element in the group (announcing the label #2). We cannot move the label outside of the group, because it’s a tab list which has it’s own set of limitations. And we cannot muzzle the group label announcement #1 because then, when navigating backwards to the group, the user won’t hear the label.

I'll move the bug to the Enhancement type, until there is a better path to handle it.

Type: defect → enhancement
Flags: needinfo?(nbaumgardner)
You need to log in before you can comment on or make changes to this bug.