The Tabs Widget cannot be activated using NVDA screen reader while navigating in brows mode

[bpmohith]

The Tabs Widget cannot be activated using NVDA screen reader while navigating in brows mode

Steps to Reproduce:

1. Open Tabs Widget Example on Chrome Browser.
2. Turn on NVDA screen reader.
3. Start navigating with the 'h' quick navigation key till the NVDA focus reaches the Example > Demo heading.
4. Start navigating with down arrow. When 'One' tab is active press down arrow till the NVDA focus moves to the 'Two' tab.
5. Press enter and space key and observe.

Description:
NVDA is a screen reader. Users with blindness use to operate computer. All UI elements are required to be operable with screen reader. In the current scenario a blind screen reader user cannot activate tabs when navigating with the NVDA brows mode.
The tabs are actionable only with the focus mode. This causes lots of issues to screen reader users and many will not know how to switch from brows to focus mode just to activate a tab.
The APG Tab Example works fine with NVDA brows mode.
NVDA screen reader can be downloaded from:
https://www.nvaccess.org/download/

[mgol]

Thanks for the report. I was able to confirm this on a Windows 11 VM with NVDA. VoiceOver on macOS doesn't have the issue.

This is something that I'd definitely want to fix.

[bpmohith]

@mgol
Thank you for taking this up. Adding few more details hope this will be of some help.

1. With JAWS screen reader on Chrome. If the user is in Forms mode off (Similar to NVDA brows mode) one needs to press enter or space twice to activate the jQuery UI tabs. Generally the tabs are expected to be activated with single press of enter / space key. The APG Example works as per the expected behavior.
2. The aria-expanded attribute is not required for a Tab component. Only aria-selected is sufficient to indicate the state of the tab. Currently both aria-selected and aria-expanded are provided. This causes increased listening overhead to the blind screen reader users.

Please suggest me if I have to make point of removing aria-expanded as a separate issue.