-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.5.1
-
Severity 3 - Minor
-
Issue Summary
The content associated with the "Source branch" and "Branch actions" expandable buttons do not have an appropriate reading order.
Steps to Reproduce
- Open the home page and activate the "Project" link in the header.
- Activate “PROJ" project.
- Activate any repository link from the “name” column of the data table, which will direct you to the source page.
- Now activate the Commits link from the left navigation.
- Using screen reader, navigate with up/down arrow keys (Jaws/NVDA) and Control+Option+left/right arrow keys (VoiceOver).
- Navigate onto and activate "Source branch" and "Branch actions" buttons present in main content.
- Observe that the expanded content becomes available at the end of the page inaccurately.
Screenshot 1
Screenshot 2
Actual Results
When the "Source branch" and "Branch actions" buttons present in main content area are expanded, the expanded content of these buttons is available at the end of the page for screen reader users. This is because this content is not coded directly after the button in the DOM. It is instead coded at the end of the page. 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.
Make sure that the content that gets available on expanding the "Source branch" and "Branch actions" buttons is coded directly after the expandable button in the DOM. This will create an appropriate reading order for the users of assistive technologies. For instance, this will enable them to arrow down onto the expanded content when the buttons are expanded.
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: Sonoma 14.7
Chrome - Version 119.0.6045.105 (Official Build) (64-bit)
Firefox- Version 92.0 (64-bit)
Safari- Version 16.6 (18615.3.12.11.2)
JAWS- Version 2023
NVDA- Version 2021.2
Voiceover - Version Latest
