Issue Summary

The form field in the Automation section has missing instructions for required form fields and missing explicit association.

Steps to Reproduce

1. Select the "Administration" icon from top navigation.
2. Navigate to the Manage Apps -> expand "Automation for Jira" drop down -> "Get started" button.
3. Select the "Automate a sample project" button.
4.  Select the "Automate" button.
5.  Select "Create rule" from the top right corner.
6.  Select the "Skip tour" link. Note that you only have to select this link first time.
7.  Select trigger "Issue commented" from the menu.
8. Save the "Issue commented" trigger
9. Select "New condition" Component.
10. Select "Issue fields condition" field.

Screenshot

Actual Results

In the Automation section, the dropdown input field such as "Field", "Condition", and (Value and Field in the tab) do not have label explicitly associated with it. The 'for' and 'id' association is missing between the label and the form control.

Additionally, the form fields have missing instructions for the required form fields. The form label is marked with a '*', but a aria-hidden="true" is provided to the character, which hides it from the screen reader users.

Labels are specified for form controls to help users understand what information needs to be inputted. However, labels need to be explicitly associated with their respective form controls for assistive technologies to identify the label accurately and convey the information to the users, and the required field should be provided with instructions.

Expected Results

Instructions are expected to be provided for fields marked with asterisks. In this instance, a text description such as "Required fields are marked with an asterisk *" is expected to be provided for the fields marked with asterisks within the page.

Remove the aria-hidden="true" for the '*' character.

Use the “for” attribute of the label element and the “id” attribute of the form control to explicitly associate labels with their respective form controls. 

This makes the clicking area wider for users without affecting the presentation of the page. This association needs to be done programmatically through the code to ensure that assistive technologies can identify the association.   

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available