Issue Summary

The error messages for the "URL" and "Link text" input fields are inaccessible for the screen readers.

Element:

• You need to enter a web address
• You need to give your link a name

Location: Below the input fields of "Web Address and Label"

Steps to Reproduce

1. Open any issue in Jira.
2. In the Command bar, select the "More" button and activate it.
3. In the More dropdown, select the "Link" option.
4. A modal will appear to Link issues.
5. Select the "Web link" option from the left sidebar in the modal.
6. In the Web link section, try to enter invalid details in the "URL" and "Link text" input fields.

Actual Results

On the Jira issue link macro modal, for the Website link, when the user types some invalid input data or blank input and activates the link button, an error message such as "Invalid 'URL'. Make sure you include the full URL (e.g. http://www.google.com)." and "'Link Text' is required." is displayed under the "URL" and "Link text" input fields. But the following message is inaccessible to the screen reader users as well as not announced to the screen reader users. As a result, screen reader users were unaware of the occurrence of errors on the page.

Expected Results

Ensure the screen reader is able to access the error message when the user activates the "link" button and when the user enters any invalid input, the error message should be announced to the screen reader user.

Apply the following changes:

• Add the 'aria-describedby' attribute to the form input field. The value should match the “id” attribute of the error message.
• Set focus on the first field with error using the JavaScript .focus() method as soon as the form is submitted. 
• Add the role="alert" to the <div> element of the error message.
• Add the aria-invalid="false" value to the search input field element and should be aria-invalid="true" when any invalid input is entered in case of a requirement, along with adding the attribute aria-required="true".

Screenshot

Screen Recording

Screen Recording 2022-08-04 at 7.52.44 PM.mov

Workaround

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

Bug Ref: 724346