Issue Bug New Orphaned

#108480Navigation workspace tables causes excessive and hierarchically incorrect screenreader output

Anonymous 12/12/25, 16:16 updated 12/12/25, 16:16

Description

Description

The workspaces table contains a global head-section (-Element), and multiple sub section with header cells (-elements) that span all columns.

Using the NVDA screenreader paired with Google Chrome, all of the header cells are announced for every cell upon navigation. The attached screenshot demonstrates the announcement for the single cell with content “Testredaktuer” [sic]. The problem grows exponentially with the number of children.

Note: The many slashes are part of the output with default punctuation verbosity, resulting in the rather lengthy word “Schrägstrich” in German.

Reproduction steps

  1. Use the NVDA screenreader and Google Chrome.
  2. Select “Einfacher Freigabeprozess” from the Workspace menu in the top bar (this label remains German when I change the user interface language to English).
  3. Select “Workspaces” from the module side bar.
  4. In the page tree, select a node with multiple nested children.
  5. Navigate the table in the main area; for every header or content cell, all header cells in the table are announced.

Impact

Due to the excessive auditory announcements, the functionality is extremely hard to understand and use with the affected environment. Besides the verbosity, the relational structure is wrong. To make matters worse, it is not even possible to interrupt the redundant information, because the content comes last.

Target group

Screenreader users

Severity

high

Frequency

common

Definition of Done

Only relevant header cells are announced during table navigation for any selected cell.

Recommended solution

Unfortunately, this looks like a hard problem to solve without a major overhaul of the UX.

The general recommendation for this problem area is to split complex tables with multiple sections and header cells into multiple simple tables. Problems in this case would be:

  • The complexity of the multi-selection checkbox increases.
  • The visual presentation is cluttered for sighted users by repeating the section. (That might be a solvable problem by visually hiding them, but would require extensive testing with browser/screenreader pairings to ensure it doesn’t introduce new problems.)

Note: It is not sufficient to add explicit relations with headers/id-Attributes. This works fine in Firefox paired with NVDA, but not in Google Chrome. Please refer to chromium bug report in the next section. I verified this long standing bug hasn’t been solved at the time of writing with NVDA 2025.3.2 and Chrome 143.

References / WCAG 2.2 Reference

In terms of the WCAG, the current table structure is not accessibility supported and success criterion 1.3.1 (9.1.3.1 in the EN 301 549) is not satisfied.

Existing issues in the NVDA and Google Chrome trackers:

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Navigation workspace tables causes excessive and hierarchically incorrect screenreader output Resolves: #108480 Releases: main