Issue Summary

The content associated with the "branch actions" expandable button does not have an appropriate reading order.

Note: This issue also has been occurred on following pages:

• Commits
• Branches
• Create a brach 
• Repository details

Steps to Reproduce

1. Open the "source" page.
2. Navigate to the "branch actions" button and activate it.
3. Observe that the content becomes available at the end of the page inaccurately.

Screenshot 1

Screenshot 2

Screenshot 3

Screenshot 4

Actual Results

When the "branch actions" button is expanded, the expanded content of this button 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 button 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 behaviour. A workaround will be added here when available

Environment

MacBook Pro (14-inch, 2021)
macOs Ventura  13.4
Chrome - Version 114.0.5735.106 (Official Build) (arm64)
Firefox- Version 112.0. 1
Safari- Version 16.5 (18615.2.9.11.4)
JAWS- Version 2023
NVDA- Version 2023
Voiceover - Version Latest