Issue Summary

The placeholder text has been incorrectly used as the accessible name for the Team combobox.

Steps to Reproduce

1. Open the Jira Cloud homepage.
2. Select any project from the side navigation and open an issue.
3. Within the issue view, locate the "Team" section present in the issue details.
4. Using a screen reader navigate to and activate the Team combobox.
5. Observe that the placeholder text is announced twice.
6. Inspect the code and note that the placeholder text has been incorrectly assigned as the accessible name

Screenshot

Actual Results

The placeholder text “Choose a team” in the Team combobox is currently used as the accessible name via the aria-labelledby attribute. Additionally, the same element is also referenced via aria-describedby, which results in screen readers announcing the placeholder text twice. The placeholder should function solely as supplementary hint text (via aria-describedby) rather than as the accessible name.

This redundancy increases verbosity and makes it difficult for screen reader users to understand the purpose of this combobox effectively.

Expected Results

Ensure that the accessible name for the form controls are appropriate and concise.

Apply the following changes - >

• Provide a unique and descriptive <label> element for the Team combobox.
• Associate the label explicitly with the combobox by providing a matching value to the for attribute of the <label> and the id attribute of the input field.
• If a visible label is not feasible, add an aria-label attribute with a descriptive name such as "Team" directly on the combobox input.
• In both cases, remove the current aria-labelledby reference to the placeholder element, and retain aria-describedby pointing to the placeholder so that "Choose a team" is announced only once as supplementary hint text.

Code Snippet:

<label id="team-label" for="...-input">Team</label>
<input id="...-input" role="combobox" aria-labelledby="team-label" aria-describedby="...-placeholder" /> 

Note: This code example is intended only as a general illustration of how to address the violation and should not be considered a complete or production-ready solution. If you have any questions, please attach this ticket to a #help-accessibility request.

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 26.3 (25D125)
Windows - 11 pro
Chrome - Version 145.0.7632.76 (Official Build) (arm64)
Safari - Version 26.2 (21623.1.14.11.9)
JAWS - Version 2025
NVDA - Version 2024.4.2.35031
Voiceover - Version Latest