Demo bug: expandable row table example is not keyboard or screen reader accessible
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
#### What is the expected behavior?
1. It must be possible to expand and collapse table rows in the example by using only a keyboard
2. Roles, states, and properties must be present so that users of screen reader software are aware that the rows can expand and collapse
#### What is the current behavior?
1. It is not possible to expand and collapse table rows in the example by using only a keyboard
2. Roles, states, and properties are not provided to convey the functionality to users of screen reader software
#### What are the steps to reproduce?
1. Using either of the following screen readers
- NVDA 2018.4.1 + Firefox 64
- VoiceOver for IOS (12.1.3) + Safari
2. Open the [table example page](https://material.angular.io/components/table/examples)
3. Use the screen reader to navigate to a table cell in the 'Table with expandable rows' example
4. Observe that the screen reader does not convey any semantics about the current expanded state, or that it is possible to interact with the row to expand the information
5. Press the 'enter' key or space bar and obverse that the row does not expand or collapse
#### Which versions of Angular, Material, OS, TypeScript, browsers are affected?
- Angular Material Example 7.2.2 located at https://material.angular.io/components/
- NVDA 2018.4.1 + FireFox 64
- VoiceOver for IOS (12.1.3) + Safari (12.1.3)
#### Is there anything else we should know?
Since rows and cells already have roles, it would be best to add a separate control to expand/collapse each row.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par la page d’exemple des tableaux Material et examinez l’exemple « Table with expandable rows », notamment la manière dont une ligne est actuellement activée. Vérifiez le résultat avec une saisie au clavier et les combinaisons NVDA/Firefox ou VoiceOver/Safari indiquées ; c’est terminé lorsque les lignes s’étendent et se réduisent au clavier et que les lecteurs d’écran annoncent les rôles, états et propriétés pertinents.
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é
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 45/100