-
Bug
-
Resolution: Fixed
-
Low
-
10.3.1
-
10.03
-
Severity 3 - Minor
-
Issue Summary
On the Viewing an issue page, the content associated with the "More", "Backlog", "Admin" and so on buttons do not have an appropriate reading order.
Steps to Reproduce
- Open the Jira page.
- Navigate to "Issues" dropdown and activate it.
- Select any issue from "Recent Issues" section.
- Observe that "Viewing an Issue" page has been appeared on the page
- Navigate to the main content.
- Using screen reader, navigate to the mentioned buttons and activate any of these.
- Observe that the content is getting updated at the end of the page for screen reader.
Screen Recording
Screenshot

Actual Results
When the "More", "Backlog", "Admin" and so on buttons are expanded, the expanded content of these buttons is available after the "Export" button for screen reader users. This is because this content is not coded directly after the buttons in the DOM. It is instead coded after the "Export" button. This inappropriate reading order might disorient the users of screen readers. That the content is available at the end might confuse or mislead them.
Expected Results
Content must have an appropriate reading order. Assistive technologies navigate content using the order in which elements appear in the DOM. Hence, make sure that the content is programmatically ordered in such a way that it provides an appropriate reading order to the users of assistive technologies.
Code Snippet
<a id="assign-issue" role="button" title="Assign this issue to someone" class="aui-button toolbar-trigger issueaction-<a href="#" id="opsbar-operations_more" aria-haspopup="true" role="button" class="aui-button aui-dropdown2-trigger" data-aui-alignment-container=".command-bar" resolved="" aria-controls="opsbar-operations_more_drop" aria-expanded="true">
<span class="dropdown-text">More</span>
</a>
<a role="menuitem" tabindex="-1" href="/secure/EditLabels!default.jspa?id=10200" class="">
<!-- content {"defaultContent":"","selector":null} -->
<span class="trigger-label">Labels</span>
<!-- /content -->
</a>
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Environment
MacBook Pro (16-inch, 2021)
macOs Monterey Version 12.3.1
Chrome - Version 131.0.6778.265 (Official Build) (64-bit)
Firefox- Version 134.0.1 (32-bit)
Safari- Version 18.1.1 (20619.2.8.11.12)
JAWS- Version 2023
NVDA- Version 2024.4.2
Voiceover - Version Latest
- is resolved by
-
A11Y-633 Loading...