Details
-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
8.20.1, 9.1.0
-
8.2
-
Severity 2 - Major
-
Description
Issue Summary
The element Progressbar of the versions appears and functions like a tooltip but is missing the required ARIA role(s) and/or attribute(s) and has incorrect reading order.
Location of the element: Present in the "Progress" column
Additional details: When the mouse pointer is placed on the progress bar, additional information will be displayed.
Steps to Reproduce
- In the Jira dashboard, Navigate to the "Project " menu link in the header section.
- Select a "Scrum S/D" or any other project.
- Navigate to the "Releases" link available in the left panel of the main content area.
- In the "Releases" dashboard Navigate to the "Progress" section for different "Versions" in the main content area.
Actual Results
In the Releases section, for the progress bar on mouse hover, a tooltip is available showing information on the Version and issues, etc. This tooltip is not accessible by keyboard and screen reader users and has missing roles and states. Additionally, the DOM order of the issue is not correct. If the order of the code and the visual order of content differ in such a way that the meaning of the content is changed, screen reader users may not understand the content correctly and this will make the information inaccessible.
Expected Results
A tooltip is a popup that displays information related to an element. There are several common patterns for tooltips including tooltips that appear on mouse or keyboard focus of the tooltip trigger and tooltips that appear on activation of the tooltip trigger. Tooltips may contain only static text or they may contain functional elements.
Fix this issue by ensuring all of the following are true:
1. The tooltip trigger must be focusable and operable with a keyboard.
2. If the tooltip content contains functional elements - such as links, buttons or form fields - they must be focusable and operable with a keyboard.
3. The content of the tooltip must be readable with a screen reader.
4. The keyboard focus (Tab key) order and screen reader reading order must be logical. The simplest way to ensure this is to insert the tooltip content immediately after the tooltip trigger in the DOM.
Screenshot
Screen Recording
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.
Bug Ref: 739073
Attachments
Issue Links
- is duplicated by
-
JRASERVER-73389 Managing Releases : Accessibility issues with tooltips in Releases page
- Closed