Toolkit Settings Expander Fails Axe Scan

[karkarl]

Describe the bug

SettingsExpander is used in WinUI3 Gallery, and the element does not pass the accessibility insights scan.

I believe the fix is from Toolkit side to bind appropriate AutomationProperties.Name to its elements.

Steps to reproduce

- Install WinUI 3 Gallery from Store
- Navigate to Design Guidance -> Icons
- Run Accessibility Insights for Windows Scan on the page
- Observe failed checks

Expected behavior

Axe tests should be passing.

Screenshots

No response

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)
• [ ] 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

No response

Visual Studio Build Number

No response

Device form factor

No response

Additional context

No response

Help us help you

Yes, but only if others can assist.

[michael-hawker]

@karkarl was talking to @niels9001, by default the automation name is set based on the Header which looks like you don't have here. For now, you should be able to set yourself on the control?