Issue Summary

On the Accessibility Assessment - Releases page, JAWS users cannot select an option using arrow keys that appears for the "All start dates" and "All release dates" custom input fields in the modal dialog (that becomes available on activating “Align dates” button) in the main content area.

Note: Similar issues are found in the following modal dialogs:

• In "Edit cross-project release" modal dialog for "Choose a project" custom input field.
• In "Add rinku to cross-project release" modal dialog for "Cross - project release" custom input field.

Steps to Reproduce

1. Navigate to the "Plans" dropdown and activate it.
2. Select any plan from the list.
3. Open the "Accessibility Assessment - Releases " page.
4. Navigate to the main content.
5. Navigate to the "More actions" buttons and activate any of these.
6. Navigate to the Align dates" button and activate it.
7. A modal dialog appears on the page
8. Navigate to the mentioned custom form fields.
9. Inspect the code.

Screen Recording 1

test - Advanced Roadmaps - InstEnv Jira - Google Chrome 2024-02-02 17-30-36.mp4

Screen Recording 2

test - Advanced Roadmaps - InstEnv Jira - Google Chrome 2024-02-02 17-39-02.mp4

Actual Results

As soon as user use arrow keys within the "All start dates" and "All release dates" custom input fields, a list of options appear visually. While trying to select an option using JAWS, the virtual cursor exits forms mode and none of the option could be selected. The focus is not managed appropriately such that using JAWS an option can be selected. Moreover, the options are not placed inline to the <input> elements. Instead, they are placed at the end of the page.

As well, the instructions “Use Up and Down to choose an option. Press enter to select the currently focused option. Press escape to exit the menu” are incomplete. The options in these input fields can be selected with Up, Down, Left, and Right arrow keys. However, the instructions do not talk about Left and Right arrow key navigation. As a result, the screen reader users cannot select any options that appears for the custom input fields.

Expected Results

Make sure that the combobox is programmatically defined by providing appropriate role and attributes, so that the screen reader users can interact with it effectively.

To achieve this, make the following changes:

• Provide role="combobox" for <input> element containing the mentioned form control in the DOM.
• Specify role="listbox" for <ul> element containing the combobox options, as well provide role="option" for <li> element containing each option.
• Specify the “aria-expanded” attribute and set the value as “false“ when it is in the collapse state. Make sure that the value should be updated on user interaction.
• The attributes "aria-autocomplete", "aria-haspopup", and "aria-controls" further define the exact behavior of the component. They are not strictly required for conformance. However, we strongly encourage you to use these attributes.
• Additionally, make sure the options available in combo boxes are also accessible for screen reader users. Use aria-activedescendant attribute on the <input> elements to determine the active option. This attribute uses the "id" of the active option.

For more information on implementing the combobox, Refer:

https://www.w3.org/WAI/ARIA/apg/patterns/combobox/

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-activedescendant

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available

Environment

MacBook Pro (16-inch, 2021)
macOs Monterey Version 12.3.1
Chrome - Version 101.0.4606.81 (Official Build) (64-bit)
Firefox- Version 93.0 (32-bit)
Safari- Version 15.3 (17612.4.9.1.5)
JAWS- Version 2022
NVDA- Version 2020.3
Voiceover - Version Latest