Expander doesn't report Header to UI Automation

[jaigak]

Describe the bug

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:

1. Sample App w/ XAML
2. Go to Expander page
3. Focus expander control
4. 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.

Hello Jaiganeshkumaran, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[Kyaa-dost]

@Jaiganeshkumaran Thanks for highlighting the issue. Do you want to work on this issue and submit a PR?

[michael-hawker]

Is this a duplicate of #3502? @Jaiganeshkumaran which version were you using? Can you test out the fix from #3504?

[Kyaa-dost]

@Jaiganeshkumaran ⬆️

[Kyaa-dost]

@Jaiganeshkumaran please let us know if the fix from #3504 works for you?