You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Expander doesn't report Header to UI Automation #3593
Expander control doesn't report the header property and because of this, I can't use it with Narrator.
Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:
Steps to Reproduce
Can this be reproduced in the Sample App? (Either in a sample as-is or with new XAML pasted in the editor.) If so, please provide custom XAML or steps to reproduce. If not, let us know why it can't be reproduced (e.g. more complex setup, environment, dependencies, etc...)
Navigate to the expander page and try to use the expander control with Narrator.
Steps to reproduce the behavior:
Sample App w/ XAML
Go to Expander page
Focus expander control
See error
Expected behavior
A clear and concise description of what you expected to happen.
Narrator reads expander header along with control details
Environment
NuGet Package(s):
Package Version(s):
Windows 10 Build Number:
Fall Creators Update (16299)
April 2018 Update (17134)
October 2018 Update (17763)
May 2019 Update (18362)
May 2020 Update (19041)
Insider Build (build number: )
App min and target version:
Fall Creators Update (16299)
April 2018 Update (17134)
October 2018 Update (17763)
May 2019 Update (18362)
May 2020 Update (19041)
Insider Build (xxxxx)
Device form factor:
Desktop
Xbox
Surface Hub
IoT
Visual Studio
2017 (version: )
2019 (version: )
2019 Preview (version: )
Additional context
Add any other context about the problem here.
It reads expander and details on expanded or not but not the header.
Activity
Kyaa-dost commentedon Dec 2, 2020
@Jaiganeshkumaran Thanks for highlighting the issue. Do you want to work on this issue and submit a PR?
michael-hawker commentedon Dec 3, 2020
Is this a duplicate of #3502? @Jaiganeshkumaran which version were you using? Can you test out the fix from #3504?
Kyaa-dost commentedon Apr 28, 2021
@Jaiganeshkumaran ⬆️
Kyaa-dost commentedon Jun 2, 2021
@Jaiganeshkumaran please let us know if the fix from #3504 works for you?