Search Issue Basic : Action cannot be performed by Keyboard alone.

Issue Summary

Close label functions are not available using only the keyboard.

Element Name:
1. Resolution Date: 15/Dec/21
2. Label: All
and so on

Location of the element: Present in the navigation bar section.

Steps to Reproduce

1. Navigate to the Jira dashboard page.
2. Navigate to the "Issues" menu button in the header section & activate it.
3. Activate the “Search for issues ” link.
4. Navigate to the Search section and open the "More" dropdown button
5. Search for Label, Resolution date, etc. filter that needs to be applied.

Actual Results

In the search page, when the filters are selected from the "More " dropdown button, filters such as "Labels", "Resolution dates" etc appear in the form element for the filter. The close links to remove the filters are not accessible by keyboard and screen reader users. The Remove filter link is only accessible by mouse click.

A tab index of "-1" is given in the code to the link which does not allow to receive the keyboard and screen readers focus on the link.

<a href="#" class="remove-filter" title="Remove criterion" tabindex="-1"><span class="aui-icon aui-icon-small aui-iconfont-remove"></span></a>

This makes keyboard-only users difficult to access the close element for the labels in the Search for issues page.

Expected Results

Following are the expected keyboard interactions.

• The Interactive element "Remove filter" should be able to receive keyboard focus and screen reader should announce "remove filter for label", "remove filter for date", etc.
• The elements should get activated with enter key.
• The focus should go to the next  filter element.
• When user presses the "Remove filter" link , the screen reader should announce the change in the page happened.

Apply the following suggested fixes in the source code.

• Remove the tabindex="-1" attribute in the source code in order to receive focus on the element.

Screenshot

Screen Recording

Screen Recording 2022-03-09 at 3.03.20 PM.mov

Workaround

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

Bug Ref: 740111