Reports Burndown Chart : Action cannot be performed by Keyboard alone.

Issue Summary

Expand/ Collapse /Activate functionality is not possible for the following elements using the keyboard alone.

• Sample Sprint 1
• Story Points

Steps to Reproduce

1. In the Jira header, navigate to the Projects link and select an available project.
2. In the available project dashboard, navigate to the Reports link in the sidebar section.
3. In the available reports dashboard, Select the burndown charts.
4. Navigate to the dropdown comboboxes such as "sample sprint 1" and "Original estimate time" present in the Burndown charts dashboard. 

Screenshot

Screen Recording

Screen Recording 2022-07-06 at 7.09.02 PM.mov

Actual Results

While navigating with Keyboard & screen reader, in the "Burndown Chart" dashboard the combobox such as "Story points" and "Sample Sprint 1" present inside the main content doesn’t get activated with Keyboard enter/space keys. But currently, it gets activated with a mouse only. 

Also, the combobox input element doesn’t have an accessible label associated with it. 

Role="listbox" is provided to the <div> element incorrectly.

The code of the listbox popup is provided at the end of the page incorrectly.

Expected Results

Following are the expected keyboard interactions.

• The Combobox element should be activated via Keyboard enter/space keys and on pressing the "Escape" key it should collapse.
• Once the Combobox is expanded, the user should be able to navigate through the options with the "Up" and "Down" arrow keys.
• The screen reader should announce the options correctly.
• When the option is selected and the dropdown is collapsed the focus should remain on the dropdown element itself.
• Provide a visible or off-screen label such as "Choose report type" to the Combobox input element.
• Provide role="listbox" to <ul> element.
• The code of listbox popup should be present right after the code of Combobox input element in the source code.

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available.

Bug Ref: 728037