CommunityToolkit / CommunityToolkit/Windows

Accessibility issues in segmented controls.

Abierto
#295 2 comentarios 0 reacciones 1 asignado Reclamado por @niels9001 Ver en GitHub
accessibility :accessibility: bug components::controls::segmented
Lenguaje dominante
C#
Estrellas
1.1k
Forks
166
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Describe the bug

Screen Readers don't announce important information when SegmentedControls are used. They are
1. Position in set
2. SizeOfSet
3. IsSelected

### Regression

_No response_

### Reproducible in sample app?

- [ ] This bug can be reproduced in the sample app.

### Steps to reproduce

```text
1. Clone the devhome repo at www.github.com/microsoft/devhome
2. Click on "Maching Configuration" in the nav bar
3. Click on "Clone Repositories"
4. Click on "Add Repositories"
5. Tab on the segmented control.

Keep in mind I added the PositionInSet and SizeOfSet automation properties. Without these the screen reader is incorrect.
```

### Expected behavior

When tabbing over the account tab, the screen reader should say "Account, 1 of 2" When tabbing over the URL tab the screen reader should say "URL, 1 of 2, selected"

### Screenshots

_No response_

### Windows Build Number

- [ ] Windows 10 1809 (Build 17763)
- [ ] Windows 10 1903 (Build 18362)
- [ ] Windows 10 1909 (Build 18363)
- [ ] Windows 10 2004 (Build 19041)
- [ ] Windows 10 20H2 (Build 19042)
- [ ] Windows 10 21H1 (Build 19043)
- [X] Windows 11 21H2 (Build 22000)
- [ ] Other (specify)

### Other Windows Build number

_No response_

### App minimum and target SDK version

- [ ] Windows 10, version 1809 (Build 17763)
- [ ] Windows 10, version 1903 (Build 18362)
- [ ] Windows 10, version 1909 (Build 18363)
- [ ] Windows 10, version 2004 (Build 19041)
- [ ] Other (specify)

### Other SDK version

_No response_

### Visual Studio Version

_No response_

### Visual Studio Build Number

_No response_

### Device form factor

_No response_

### Nuget packages

_No response_

### Additional context

_No response_

### Help us help you

No.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.