Actionsheet: Keyboard focus is not moving during navigation when JAWS is on

[pankajpandey01]

Describe the bug
When JAWS is on, Keyboard focus is not moving during navigation. JAWS focus is moving, but keyboard focus is stuck at first item. This issue occurs when Actionsheet role is changed to 'menu' as shown in below example.

  <ActionSheet
        horizontalAlign="Center"
        ref={popoverRef}
        **a11yConfig={{
          actionSheetMobileContent: {role: "menu"}
        }}**
        opener="actionSheetOpener"
        placementType="Right"
        verticalAlign="Center"
      >

Isolated Example
https://codesandbox.io/s/react-playground-forked-zrm65p

To Reproduce
Steps to reproduce the behavior:

1. Go to https://codesandbox.io/s/react-playground-forked-zrm65p
2. Enable JAWS
3. Use keyboard to open actionsheet and navigate using arrow key.

Expected behavior
Keyboard and JAWS focus should move together during navigation as it works without a11yConfig attribute.

Screenshots

UI5 Web Components for React Information
@ui5/webcomponents version: All
@ui5/webcomponents-react version: All
Operating System: Windows
Browser: All

Additional context
JAWS2022 is used for testing.

Stakeholder
Organization: {SuccessFactors}
Business impact: {a11y issue}

[Lukas742]

Hi @pankajpandey01

are you using the reading mode or the application mode (virtual cursor off) in JAWS?
In reading mode it's not expected that the internal navigation of the web-components works.

[pankajpandey01]

Hi @Lukas742
We are using browse/read mode. We have observed that with this mode enabled, keyboard focus works fine without "a11yConfig" attribute.

[Lukas742]

We're setting role="application" to the content of the ResponsivePopover. That's why it's working fine without the a11yConfig, because screen readers then use the application mode automatically. Since this is not how standard ui5 web components are handling this, we're going to remove it in our next major release (since it will be a breaking change).
So if you want to enforce the behavior, you have to set role="application" yourself - either on application level or component level.

[github-actions]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Inactive issues will be closed after 7 days. Thanks.

[github-actions]

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one.