Issue Summary

On the "Pull Request" page, the "Author", "Targeted branch" and so buttons inappropriately use the input field role.

Steps to Reproduce

1. Navigate to the above mentioned page.
2. Navigate to the "Author", "Targeted branch" and so on input fields.
3. Inspect its code and functionality.
4. Observe that the functionality of the input field is unclear for Keyboard only and Screen reader users.
5. Note that the buttons use <input> elements inappropriately.

Screen Recording

Screen Recording 2023-09-25 at 5.03.56 PM.mov

Actual Results

When Keyboard only and Screen reader users navigate to the "Author", "Targeted branch" and so on input fields and try to activate it, they are not able to do so as the input field does. As a result, it may confuse or mislead the screen reader and keyboard only users. Additionally, the state is not defined for the mentioned instances. 

Expected Results

Every functionality that is available for Mouse users, must be available for Keyboard only and assistive technology users as well. In this scenario, we would recommend you to refactor this <input> element into a button and activating the button can then trigger the "Comment" popup.

Make sure that the focus moves onto the editable comboboxes when the "Author", "Targeted branch" and so on buttons button are activated.

Provide the "aria-expanded" attribute in the source code of the mentioned instances. 

Workaround

Currently, there is no known workaround for this behaviour.

MacBook Pro (16-inch, 2019)
macOS 13.4.1 (c) (22F770820d)
Chrome - Version 115.0.5790.170 (Official Build) (x86_64)
Firefox- Version 114.0 (64-bit)
Safari- Version 16.5.2 (18615.2.9.11.10)
JAWS- Version 2023.2306.28
NVDA- Version 2022.2.2
Voiceover - Version Latest