bug(mat-table): ChromeVox screen-reader highlights multiple table cells at a time
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
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 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**
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par la reproduction StackBlitz liée et les étapes de navigation dans les tableaux de ChromeVox dans ChromeOS afin de confirmer le comportement de la mise en surbrillance. Suivez l’accessibilité et la gestion du focus du tableau Angular Material à partir de la démo reproduite ; le travail est terminé lorsque ChromeVox ne met en surbrillance que la cellule ayant le focus pendant la lecture vocale, et que la vocalisation et le focus restent corrects.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- accessibility, frontend
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100