-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.5.1
-
Severity 3 - Minor
-
Issue Summary
No indication or status message of a pull request getting merged.
Steps to Reproduce
- Open the "Home" page.
- Activate any repository link from the table.
- Now activate Pull request link from left navigation
- Activate any link from “Summary” column of data table.
- Navigate and activate “Merge” button from main content area > a modal appears.
- Navigate and activate “Merge” button in the modal dialog.
- Observe that pull request gets merged.
- Listen that there is no indication for the user to know the pull request has been merged.
Screen Recording
Screen Recording 2025-03-04 at 2.39.46 PM.mov
Actual Results
When the user activates the "Merge" button present in the in the "Merge pull request" modal dialog, the pull request gets merged dynamically on the page. There is no indication by the screen reader as if the functionality has been performed.
As a result, screen reader users will remain confused or unaware if a pull request has been merged or not and where it has been merged.
Expected Results
The screen reader users should have some sort of indication regarding the dynamic change that occurs on the page after user interaction.
Provide a status message regarding the dynamic change that occurs on user interaction which will conclude if the pull request has been merged or not and where it has been merged.
For Example: “The "add bunster" pull request has been successfully merged to the "cover" in the "Commit 43296348eef.”
Make sure that the status message is correctly defined programmatically and contains role="status", aria-live="polite" and aria-atomic="true".
For more information, refer to the following link: ARIA live regions - Accessibility | MDN https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions
Code Example:
<span role="alert" aria-live="polite"....>The "add bunster" pull request has been successfully merged to the "cover" in the "Commit 43296348eef.</span>
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.7
Chrome - Version 131.0.6778.86 (Official Build) (arm64)
Firefox- Version 134.0 (64-bit)
Safari- Version 18.1.1 (20619.2.8.11.12)
JAWS- Version 2023
NVDA- Version 2021.2
Voiceover - Version Latest