-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.5.1
-
Severity 3 - Minor
-
Issue Summary
The "Merged" interactive element is inappropriately defined as a link instead of button.
Steps to Reproduce
- Open the homepage and activate the "Projects" link in the header.
- Select any project from the main content area.
- Select any of the repositories from the main content area.
- Now activate the "Branches" link from the side navigation.
- Navigate onto the mentioned instance and inspect the code.
- Observe that the interactive element has an interactive role.
- Observe that the role is inappropriate.
Screenshot
Actual Results
The "Merged" interactive element is programmatically determined as a link rather than button. This may particularly disadvantage users that interface with the accessibility properties of elements, such as screen reader users. That elements have inappropriate roles may confuse or mislead users.
Expected Results
Interactive elements must use an appropriate role.
In this scenario, since the element performs a function rather than opening a new page, it would be more semantically correct to refactor this link into a button. Use <button> native element which has an accessible role by default.
If this is not possible, you can use role=”button”, and tabindex=”0” attributes to ensure that the button receives keyboard focus and has an interactive role.
Code Snippet
<button>Merged</button>
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.1
Chrome - Version 119.0.6045.123 (Official Build) (64-bit)
Firefox- Version 93.0 (32-bit)
Safari- Version 17.3.1 (19617.2.4.11.12)
JAWS- Version 2023
NVDA- Version 2024.3
Voiceover - Version Latest
