bug(mat-table): ChromeVox screen-reader highlights multiple table cells at a time
- Lenguaje dominante
- TypeScript
- Estrellas
- 25k
- Forks
- 6.8k
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 91
Descripción
### 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**
Guía de contribución
Línea de trabajo
Comienza con la reproducción vinculada de StackBlitz y los pasos de navegación por tablas de ChromeVox en ChromeOS para confirmar el comportamiento del resaltado. Sigue la accesibilidad y la gestión del foco de la tabla de Angular Material a partir de la demo reproducida; el trabajo estará terminado cuando ChromeVox resalte únicamente la celda enfocada mientras realiza la lectura y tanto la voz como el foco se mantengan correctos.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, typescript
- Área
- accessibility, frontend
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100