Managing Releases : Drag and drop feature is not keyboard accessible.

Issue Summary

The drag and drop feature is not keyboard accessible.

Element: Reorder icons.

Location: Present in the main content area on the left of the Versions column.

Note: The Icon is used to drag the row of the table. The drag and drop feature is not accessible.

Steps to Reproduce

1. Navigate to the Jira dashboard page.
2. Navigate to the "Project" menu button in the header section & activate it.
3. Activate the "Kanban project" or any other available project.
4. In the left panel section of the "kanban project", Navigate to the "Releases" link and activate it.
5. Navigate to the "Releases" dashboard in the main content area, where "Versions", "Status", etc. features are present for the project release versions.

Actual Results

In the "Releases" dashboard section for the "Versions", "Status", etc. data, the Drag and Drop functionality (which is present on the left side, "Reorder versions" icon ) to move the data related to "Versions", "Status", etc., is not accessible for Keyboard alone and Screen reader users. The "Reorder versions" icon interactive element does not receive keyboard focus. Whereas this functionality is available with the mouse by Click + Hold on the "Reorder versions" icon and moving the data Up or Down. 

This makes it keyboard-only and screen reader users difficult to use this feature on the dashboard.

Expected Results

Following are the expected keyboard interactions.

• The "Reorder versions" element should receive Keyboard as well as Screen reader focus.
• The following could be a solution to implement this functionality 

1. Tab to move through the list of items
2. Space to select an item
3. Arrow keys to switch between the drop zone(s)
4. Enter to Drop

• An alternative element such as Up down arrow should be available to shift the table data up and down, and should announce when data is shifted with screen reader.

Screenshot

Screen Recording

JRASERVER-73396.mov

Workaround

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

Bug Ref: 736988