Issue Summary

On the "Create pull request" page, the content associated with the "Diff view settings expandable button does not have an appropriate reading order.

Steps to Reproduce

1. Navigate onto the above mentioned page.
2. Navigate onto the mentioned button with a screen reader and activate it.
3. Arrow down onto the expandable content from the button.
4. Note that the content associated with it is available at the main content area.

Screenshot

Actual Results

When the "Diff view settings" 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 buttons is coded directly after the expandable buttons 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.

Code Snippet

<div>
<button aria-expanded="true">Diff view settings</button>
...
</div>

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.4
Chrome - Version 103.0.5060.134 (Official Build) (arm64)
Firefox- Version 93.0 (32-bit)
Safari- Version 15.5 (17613.2.7.1.8)
JAWS- Version 2023
NVDA- Version 2023.3
Voiceover - Version Latest