CommunityToolkit / CommunityToolkit/Windows

SettingsExpander sub controls have same accessible name and localized control type

Offen
#430 1 Kommentar 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
accessibility :accessibility: bug components::controls::settingscontrols
Vorherrschende Sprache
C#
Sterne
1.1k
Forks
166
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### Describe the bug

The SettingsExpander control have an accessibility issue on its internal controls. The accessible names on them are the same and they are stacked (one is child of the other). This creates a accessibility issue reported by the Accessibility Insights for Windows tool.

### Steps to reproduce

```text
Create a SettingsExpander control. Give it a Title and Description.
Run Accessibility Insights for Windows and inspect the control.
```

### Expected behavior

No accessibility issues found.

### Screenshots

Example 1:
![image](https://github.com/CommunityToolkit/Windows/assets/13912953/addb24ab-69b9-4785-bb37-c059f1a299bc)
![image](https://github.com/CommunityToolkit/Windows/assets/13912953/794dc25b-4828-44ad-8181-04ceee508d9b)
![image](https://github.com/CommunityToolkit/Windows/assets/13912953/2907eaed-5001-4c69-95c9-52865982db6b)
Example 2:
![image](https://github.com/CommunityToolkit/Windows/assets/13912953/89782bd6-212a-40fe-bedd-30415f48b246)
![image](https://github.com/CommunityToolkit/Windows/assets/13912953/9075c08f-fbb4-4e84-a7ef-b706fd11e0d7)
![image](https://github.com/CommunityToolkit/Windows/assets/13912953/0863b901-328d-4275-9cd0-88e1fc7bfaf8)

### Code Platform

- [ ] UWP
- [X] WinAppSDK / WinUI 3
- [ ] Web Assembly (WASM)
- [ ] Android
- [ ] iOS
- [ ] MacOS
- [ ] Linux / GTK

### 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)
- [ ] Windows 10 21H2 (Build 19044)
- [ ] Windows 10 22H2 (Build 19045)
- [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)
- [ ] Windows 10, version 2104 (Build 20348)
- [ ] Windows 11, version 22H2 (Build 22000)
- [ ] Other (specify)

### Other SDK version

_No response_

### Visual Studio Version

2022

### Visual Studio Build Number

_No response_

### Device form factor

Desktop

### Additional context

_No response_

### Help us help you

No, I'm unable to contribute a solution.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Beginne damit, die WinUI 3 SettingsExpander-Implementierung und ihre internen Steuerelemente zu lokalisieren, reproduziere dann das Problem mit einem Title und einer Description mithilfe von Accessibility Insights for Windows. Überprüfe, dass zugängliche Namen und lokalisierte Steuerelementtypen nicht mehr dupliziert oder falsch verschachtelt sind, und führe die Inspektion erneut aus, um zu bestätigen, dass kein Barrierefreiheitsproblem gemeldet wird.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
csharp
Bereich
accessibility, frontend
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
42/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.