bug(mat-table): ChromeVox screen-reader highlights multiple table cells at a time
- Vorherrschende Sprache
- TypeScript
- Sterne
- 25k
- Forks
- 6.8k
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 91
Beschreibung
### 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 navigating with screen reader controls only one table cell should be highlighted at a time, however multiple cells are highlighted.
### Reproduction
StackBlitz link: https://stackblitz-starters-fcezcx.stackblitz.io
Steps to reproduce:
1. Once the StackBlitz has loaded, click anywhere within the rendered demo.
2. Activate ChromeVox (CTRL + ALT + z)
3. Have ChromeVox select the table (Shift + Search + t), and you'll see that the first two table headers are highlighted together and the third is highlighted separately.
4. Now navigate around the table (CTRL + ALT + Search + [arrows]), and you'll see that multiple table cells are always highlighted
### Expected Behavior
When navigating around the table, only one table cell at a time should be highlighted by ChromeVox.
### Actual Behavior
Generally, the focused cell is highlighted together with the cell to its immediate right (if there is one). Also, all cells in the same row as the focused cell are highlighted separately.
**Note:** focusing and voicing are correct; it's only the highlighting that's wrong.
### Environment
- Angular: **17.0.8**
- CDK/Material: **17.0.4**
- Browser(s): **Chrome**
- Operating System: **ChromeOS**
Beitragsleitfaden
Rechercherichtung
Beginne mit der verlinkten StackBlitz-Reproduktion und den ChromeVox-Schritten zur Tabellennavigation in ChromeOS, um das Hervorhebungsverhalten zu bestätigen. Verfolge die Barrierefreiheit und Fokusbehandlung der Angular Material-Tabelle anhand der reproduzierten Demo; abgeschlossen ist die Aufgabe, wenn ChromeVox beim Vorlesen nur die fokussierte Zelle hervorhebt und Sprachausgabe und Fokus korrekt bleiben.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- accessibility, frontend
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100