Scrum Softwre Development Wizard Modal 2 : Reading order of static content changes meaning for the tooltip content

Issue Summary

The screen reader's reading order of the content changes the intended meaning of the content for the Info icon tooltip content ("What's a project key?" link) in the Project management modal.

Location: Beside the Key form field

Steps to Reproduce

1. Select "Create project" from the projects menu
2. A list of options will be displayed
3. There select the "Project Management" option from the "Business" section
4. Then modal will be displayed, hit the "select" button
5. Then "Project management" modal will be displayed, navigate to the tooltip icon beside the Key input field and activate it and inspect the tooltip.

Actual Results

When user hits the "info icon " with the mouse, additional information will be displayed on the screen. 

• The focus does not go to the tooltip content or the icon with keyboard or screen reader.
• The code of the tooltip element container (class="aui-inline-dialog-contents contents") is placed at the end of the page in DOM order incorrectly.

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.

Expected Results

The reading and navigation order must be logical and intuitive. Fix this issue by ensuring that the order of the content in the DOM is logical.

• The tooltip icon should receive keyboard and screen reader focus and should stay active until the focus is removed.
• Place the code of the tooltip element container (class="aui-inline-dialog-contents contents") right after the code of (class="aui-icon aui-icon-help") link inside the DOM order. This makes sure that the visual order of the element matches the DOM order.

The visual order of the content can differ from the source code order, as long as the reading order for screen readers is still logical and meaningful.

Screenshot

Workaround

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

Bug Ref: 731846