Feedback: "Read information about a menu item in interaction mode" (Navigation Menu Button, Test 15)

[RFischer-FS]

Description of Behavior

The announcement for the role "menu item" shouldn't be required. The keystrokes Insert+Tab and Inserst+Up should provide the same speech output you hear when landing on the item. Therefore announcing the role "menu item" should be optional.

Test Setup

• Test File: test-15-read-information-about-a-menu-item-interaction-jaws.collected.html
• AT: JAWS
• Browser: Chrome

[mcking65]

@RFischer-FS

I am curious about this.

For most elements, insert+tab helps the user understand what is focused. If I didn't understand or missed what was said when I Tab to something or open a widget, I can press insert+tab to hear all the information about the currently focused element. For example, if I am in a listbox or tree, pressing insert+tab tells me that I am in the listbox or tree and tells me the name of the listbox or tree. If I have focus in a menu, how can I find that out if it is not conveyed with insert+tab?

What do you think of making the insert+tab speaking of menu items more consistent with the speaking of other similar elements by announcing the name of the menu (if it has one), the role "menu", the name of the menu item, the state (if one is present), and and then position in set and set size? Then menu items would have support that is consistent with how JAWS supports other elements.

I note that insert+up and insert+tab differ meaningfully, and would probably differ in this case. So, they might need to have different assertions. Or, we would leave insert+up out of the test because the way we have designed these tests, all commands have to support the same assertions if they are in the same test.

[jscholes]

Update from meeting with Vispero on November 17, 2022:

When a JAWS user is inside a listbox, and presses JAWS+Tab, the software conveys the name and role of the listbox, name and position of the current item, total number of items, and instructions about how to move through the items (with default verbosity settings). It was agreed that were JAWS to treat menus in a similar way, this would be sufficient to imply the presence of a menu item, without explicitly stating the role.

Vispero will file an internal bug to this effect, and there is no need for updates to ARIA-AT tests at this time. This issue should remain open, and be imported into the new candidate review system within the ARIA-AT App, to create a record of the feedback and outcome. CC @s3ththompson