Repositories: Inaccurate reading order

Issue Summary

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

Steps to Reproduce

1. Open the "Repositories" page.
2. Using screen reader, navigate to the "Type" button present in main content area and activate it.
3. Observe that the content becomes available is at the end of the page.

Screenshot

Actual Results

When the "Type" button is expanded, the associated 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 "Type" 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 button is 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.3
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