Issue Summary

The "Priority" field is not correctly associated with its corresponding visual label.

Steps to Reproduce

1. Open the Jira Cloud homepage.
2. Activate the "Create" button located in the header. A dialog appears.
3. Using a screen reader, navigate to the "Priority" field.
4. Note that the screen reader (NVDA/JAWS) announces the “Priority” field only as "Select field," without referencing its associated visual label.
5. Inspect the code of this field.
6. Observe that this field is not programmatically associated with its corresponding visual label.

Screenshot

Screen Recording

https://www.loom.com/share/e840a2d2e27540f793cf79835cc8d70a

Actual Results

The "Priority" field within the "Create Issue" dialog does not have an explicitly associated label. The aria-label attribute is incorrectly set to "Select field" on the input element, causing screen readers such as JAWS and NVDA to announce the field solely as "Select field" without associating it with its corresponding visual label.

As a result, screen reader users might not understand the purpose of this field.

Expected Results

The screen reader should announce the visual label for the form fields correctly. Use ‘for’ and ‘id’ attributes to associate labels with their respective form fields. 

Apply the following changes ->

• Remove the generic aria-label attribute currently assigned as "Select field" from the <input> element.
• Add an aria-labelledby attribute within the <input> element that references the 'id' of the corresponding <label> element.
• This approach ensures that screen readers accurately communicate the "Priority" field along with its corresponding visual label.

Code Snippet:

<label id="priority-field-label" for="priority-field" ...>Priority</label> 
(...)
<input aria-labelledby="priority-field-label" id="priority-field" role="combobox" ...>

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.5
Windows - 11 pro
Chrome - Version 148.0.7778.97 (Official Build) (arm64)
Safari - Version 26.5 (21624.2.5.11.4) 
JAWS - Version 2026
NVDA - Version 2024.4.2.35031
Voiceover - Version Latest