Issue Summary

On Active sprints page, the tooltip content which appears when mouse is hovered over 'Quick filters' text is Inaccessible for keyboard & screen reader users.

Tested URL

https://instenv-9109-pfsh.instenv.atl-test.space/secure/RapidBoard.jspa?rapidView=1&projectKey=TES

Issue Id: 740002

Steps to Reproduce

1. Navigate to any project in Jira.
2. Navigate to 'Active sprints' link from the left navigation.
3. Navigate to the 'Quick filters' text present inside main content.
4. Hover over the quick filter text to view the tooltip content.

Actual Results

When a user hovers the mouse over 'Quick filter' text a tooltip appears but while navigating with keyboard & screen reader, when user navigate to the 'Quick filter' text the tooltip content does not appear & not announced by screen readers.

This makes keyboard & screen reader users difficult to understand the tooltip content.

Expected Results

The tooltip content should be accessible with keyboard & screen reader. Apply the following fixes.

1. Mark the 'Quick filter' text inside native <button> element so that it receives keyboard focus.
2. When user navigate to the 'Quick filter' with keyboard tab key, the tooltip should be displayed & screen reader should announce it.
3. The tooltip should get closed with 'Esc' key.
4. Provide role="tooltip" to the tooltip element.
5. Associate the tooltip content with the button element via aria-describedby attribute which will help screen reader to announce.
6. The tooltip content should be hoverable, persistent & dismissible via keyboard.
7. The code of tooltip content should be present right after the triggering button element instead of at the end of page.

For more information refer to following 'Tooltip' component page.

https://hello.atlassian.net/wiki/spaces/A11Y/pages/1334491247/Tooltips#Developers

Screenshot

Screen recording

Screen Recording 2022-02-09 at 6.50.04 PM.mov

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.

Workaround

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