Expander Header not read by screen reader if it's complex

[carlos-zamora]

Describe the bug

A screen reader is unable to read the header of an expander if the header was set to anything other than a TextBlock.

Steps to reproduce the bug

1. Create an Expander where the header is overridden as such:

<muxc:Expander>
    <muxc:Expander.Header>
        <StackPanel>
            <TextBlock>First text block!</TextBlock>
            <TextBlock>Additional text!</TextBlock>
        </StackPanel>
    </muxc:Expander.Header>
</muxc:Expander>

2. Use a screen reader to navigate to the expander

Expected behavior

The screen reader should read out the header content. Instead, it reads "group, collapsed"!

Screenshots

NuGet package version

WinUI 2 - Microsoft.UI.Xaml 2.8.2

Windows version

No response

Additional context

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!

Closed similar issues:

• Narrator cannot read the contents of the Expander header in scan mode (#5820), similarity score: 0.85

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[carlos-zamora]

Yes, this is similar to #5820. However, I don't think that screen reader users should be expected to enter scan mode to be able to get to the content. Is the expectation that the developer sets the AutomationProperty.Name on the Expander directly to define the desired behavior? I can honestly see an argument either way since the header can hold any content.