Issue Summary

The accessible name for the button "Bhanu-config-custom-field" is redundant.

Steps to Reproduce

1. Open the Jira Cloud Home page.
2. Select an existing Project from the side navigation or create a new Project.
3. Open any issue in the project or create a new issue.
4. Activate "Configure" from the bottom-right panel or the meatball menu, then select "Go to fields page."
5. Activate "Add field" button to add the Forge custom field to the issue screen.
6. Close the fields tab and return to the previous Jira tab.
7. Using screen reader (JAWS, NVDA, or VoiceOver), locate the custom edit buttons under Details on the right side.
8. Listen to the accessible name announced by the screen reader and note that it is verbose.
9. Inspect the button’s code and observe that the verbose accessible name is programmatically defined.

Screenshot

Actual Results

The "Bhanu-config-custom-field" button has a redundant accessible name. Its aria-label is set to "Edit Bhanu-config-custom-field, edit", which unnecessarily repeats the word “Edit” even though the control already represents an edit action.

This redundancy increases verbosity and may cause confusion for screen-reader users by presenting repetitive and unnecessary information.

Expected Results

Ensure that all interactive elements have a clear and appropriate accessible name.
In this scenario, remove the redundant "edit" at the end of the aria-label to make the accessible name concise and accurate.

Code Snippet:

<button aria-label="Edit Bhanu-config-custom-field" ...> </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 15.4.1
Windows - 11 pro
Chrome - Version 142.0.7444.60 (Official Build) (arm64)
Safari - Version 26.1 (20622.2.11.119.1)
JAWS - Version 2025
NVDA - Version 2024.4.2.35031
Voiceover - Version Latest