Issue Summary

On releases page, the popup which appears when user hover mouse over progressbar of the versions is not accessible for Keyboard & screen reader users.

Steps to Reproduce

1. Navigate to the Jira Dashboard page.
2. Navigate to the "Projects" menu in header section.
3. Activate any project link from the menu. For Example : "TestQA".
4. Activate the "Releases" link from the left navigation.
5. Navigate to the Progress bar of the versions in the main content.
6. Observe the popup which appears on mouse hover is not accessible with Keyboard & screen reader.

Actual Results

While navigating with Keyboard and screen reader, when user navigate to the versions progress bar element, the contents of versions popup don’t receive Keyboard focus & also screen reader doesn’t announce the contents.

Currently the popup is displayed only when user hover the mouse over the progress bar elements.

The popup container is missing required ARIA attributes such as role, name etc. Also the popup code is present at the end of the DOM incorrectly.

Expected Results

The versions popup should be accessible with keyboard & screen reader. 

Apply following fixes in the source code.

• Provide ARIA role="dialog" to the dialog container.
• Provide an aria-labelledby attribute to the dialog container and refer to the visual heading i.e. user name.
  For Example : "Versions : Version 1".

• Place the code of popup container right after the code of triggering elements such as Assignee or Reporter elements.

Following should be the Keyboard interaction.

• When progress bar button receive keyboard focus, the popup should be displayed.
• Pressing tab key the focus should go inside the contents of popup.
• Pressing ESC key should dismiss the popup & focus should set back to the triggering element.

Refer to the following link to read more about Non-modal dialog (popup) implementation as per Atlassian Accessibility Standards

https://hello.atlassian.net/wiki/spaces/A11Y/pages/1105796220/Non+Modal+Dialogs 

Screenshot

Workaround

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

Bug Ref: 739073