[Bug]: In browse mode, screen reader not announcing the selected/not selected state for the legends. about fluentui

[behowell]

Hi @gilenzi, please provide a minimal repro that includes source code (e.g. using codepen or stackblitz).

[gilenzi]

Hi @behowell, I added image, because that is screen reader issue related to "Legends" component. So I don't know which code to include. Here are repro steps:

1. Open URL in the Edge browser.
   2.  Storybook M365 SCC Components page opens.
2. Navigate to left panel and activate 'Card Content' under components.
3. Activate 'DualreportcardContent' tab > Default.
4. Activate 'Open canvas in in tab'.
5. The new page will be opened in the new tab.
6. Now, navigate to the graph legends in browse mode and observe the issue.

[behowell]

I'm not an expert on charting, so I've assigned this to the charting team to take a further look.

However, as far as I can tell, it is setting aria-selected="true" correctly when a single legend item is selected. And Narrator does read "selected" for those items.

I noticed that when there is no selection, all legend items appear selected, but they all have aria-selected="false". Is that the case you're referring to?

[AtishayMsft]

@gilenzi Could you share a video of the issue.
I am seeing that selected and not selected state is announcing on selection/deselection of legends.
And the not selected legend states are announced on keyboard navigation.

[smhigley]

I can't say for sure without more info on the screen reader used and the browser (guessing NVDA because of "browse mode"?), but this is almost certainly the specific NVDA/JAWS behavior of not announcing "selected" when you navigate to selected listbox options. This stems from historical Windows desktop choices around selected state following focus, and is not a bug.

You should hear the selected state when you toggle selection, and you should hear "not selected" announced when you move onto options that are not selected (assuming this is NVDA; this behavior varies by screen reader, since it is a screen reader UX choice).