Issue Summary

The element appears and functions like a combobox but is missing required ARIA role(s) and/or attribute(s).

1. Element Name:

• Directory
• Status

2. Location of the element: Below the Group heading

3. The problem that it causes: These elements function as edit combo boxes but that do not implemented with appropriate role, state, & relevant aria properties to help non-sighted users read and access the widget easily.

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:
A combobox is a widget made up of the combination of two distinct elements: 1) a single-line textbox, and 2) an associated pop-up element for helping users set the value of the textbox.

Fix this issue by using ONE of the following techniques:
1. Use an HTML <select> element with <option> elements to create the drop-down menu.
2. Use the ARIA design pattern for a combobox. View the full ARIA design pattern for a combo including expected keyboard interactions and examples: https://www.w3.org/TR/wai-aria-practices-1.1/#combobox

REFERENCE:
W3C HTML5 Recommendation: https://www.w3.org/TR/html5/sec-forms.html#the-select-element
WAI-ARIA Authoring Practices: https://www.w3.org/TR/wai-aria-practices-1.1/#combobox

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: 360174