Open Issues : The element has missing or incorrect states or properties.

Issue Summary

The element has missing or incorrect states or properties that are necessary for screen reader users to interact with or understand the content conveyed by the element.

Element:

• My open issues
• reported by me ETC . . .

Location: In the Submenu of Switch filter.

Note: Applicable for all the links in the submenu.

Steps to Reproduce

1. Step 1

Actual Results

Actual results

Expected Results

Expected Results

Fix Information
RULE :
The name, role, value, states, and properties of user interface components MUST be programmatically determinable by assistive technologies.

HOW TO FIX:
Fix this issue by ensuring that all necessary ARIA states or properties are used per the ARIA Recommendation document and the ARIA Authoring Practices document (see References below).

Visually, there are two groups are present. Make sure to use role="menu" and role="menuitemradio" for both the group elements.

REFERENCE:
https://www.w3.org/TR/wai-aria-practices-1.1/examples/menubar/menubar-2/menubar-2.html

BACKGROUND:
Every user interface control must have a role along with any applicable states and properties so that screen reader users know how to interact with the control. Native HTML elements - such as <button>, <a>, <input>, <select> - already have a role, and their necessary states and properties - such as the checked/unchecked state of a checkbox - are automatically conveyed so nothing more needs to be done. If you create a custom version of a native HTML element or a custom control or widget that does not have a native HTML equivalent, you must add the relevant role(s) and any applicable states and properties using ARIA as well as expected keyboard interactions.

Screenshot

Screen Recording

screen recording

Workaround

workaround

Bug Ref: 731830