Issue Summary

On backlog page, the "Versions" & "Epics" buttons present inside main content are not accessible with keyboard alone.

Issue id: 734659

Steps to Reproduce

1. Navigate to the Jira homepage.
2. Navigate to any project. For Example : Test-QA
3. Navigate to the Backlog page.
4. Navigate to the "Versions" & "Epics" buttons present inside main content.

Actual Results

• The "Versions" & "Epics" elements don’t receive keyboard focus & does not get activated via keyboard alone.
• The "Versions" & "Epics" elements are marked in <ul> & <li> element unnecessarily.
• The current state of "Versions" & "Epics" elements i.e expanded/collapsed is not announced by screen reader.
• The tooltip text which appears on mouse hover is not accessible for keyboard users.

Expected Results

• The "Versions" & "Epics" elements should receive keyboard focus & should get activated via keyboard enter/space keys.
• The focus should go inside the panel element when user activates versions/epics panel.
• Mark the "Versions" & "Epics" elements inside HTML native <button> element & remove the <ul> & <li> elements.
• Provide aria-expanded="false" to the button elements & toggle the value between true/false as per user interaction.
• The tooltip text should appear when the button element receives keyboard focus & screen reader should also announce the text.
• Provide role="tooltip" to the element & associate the tooltip element with button via aria-describedby attribute.

BACKGROUND

Some people cannot use a mouse due to vision or motor disabilities. Content that can be operated with a mouse must also be made operable with a keyboard. When content is operable through a keyboard, it becomes operable by a variety of assistive technologies such as speech input software, sip-and-puff software, on-screen keyboards, scanning software, and alternate keyboards.

Screenshot

Workaround

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