Accessibility Assessment - Releases: Custom form controls not programmatically determined and operable for screen reader users

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.

Steps to Reproduce

1. Open the "Accessibility Assessment - Releases " page.
2. Navigate to the main content.
3. Navigate to the "More actions" buttons and activate any of these.
4. Navigate to the Align dates" button and activate it.
5. A modal dialog appears on the page
6. Navigate to the mentioned custom form fields.
7. 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

All interactive elements must be completely operable and compatible with all screen readers. In this scenario, Make sure that the options that appear on expanding the input fields are coded directly after the <input> elements in the DOM. As well, 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 using aria-activedescendant, you can refer: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-activedescendant#:~:text=The%20value%20of%20aria%2Dactivedescendant%20refers%20to%20an%20owned%20element,is%20controlled%20by%20the%20combobox. As well, modify the instructions in a manner such that they provide a complete information as to how to select the options properly. For instance, “Use Up and Down arrow keys to navigate to the options. Use Left and Right arrow keys to navigate to the selected options. Press enter to select the focused option. Press Escape to come out of the input field.

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.

Code Snippet

<label class="Field_Label-vqybw1-1 ghWQGY" id="startMethod-27eab882-da00-40cd-b17e-18c02dbfbb04-label" for="startMethod-27eab882-da00-40cd-b17e-18c02dbfbb04">All start dates<span class="Field_RequiredIndicator-vqybw1-2 hieiaz" aria-hidden="true">*</span></label>
<input class="" autocapitalize="none" autocomplete="off" autocorrect="off" id="react-select-14-input" spellcheck="false" tabindex="0" theme="[object Object]" type="text" aria-autocomplete="list" aria-expanded="false" aria-haspopup="true" aria-required="true" role="combobox" aria-labelledby="startMethod-27eab882-da00-40cd-b17e-18c02dbfbb04-label startMethod-27eab882-da00-40cd-b17e-18c02dbfbb04-helper startMethod-27eab882-da00-40cd-b17e-18c02dbfbb04-valid startMethod-27eab882-da00-40cd-b17e-18c02dbfbb04-error" value="" style="background: 0px center; border: 0px; font-size: inherit; opacity: 1; outline: 0px; padding: 0px; color: inherit; box-sizing: content-box; width: 100%;">

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