Search - Advanced Search : Reading order of static content changes meaning

Issue Summary

The screen reader reading order of the content changes the intended meaning of the content.
Elements:
1) Search result from the editable combobox.

Location:
Search results from "contributor" and "In space" combobox.

Additional details:
The displayed search results are available for screen reader users at the end of the page after the footer.
whereas, they should be available just after the respected dropdowns.

Steps to Reproduce

1. Navigate to the confluence homepage.
2. Navigate to the Search image button inside the header section & activate it.
3. Navigate to the 'Advanced search' link inside the search modal & activate it.
4. Navigate to the OF TYPE section in the left sidebar.
5. Navigate and activate the "Custom" link and the form input field appears.

Actual Results

While navigating with the screen reader, when the user tries to navigate to the input field "Contributor" that triggers the elements, the focus does not move to the first interactive element, it directly shifts to the next input field i.e "In Space" which is incorrect. But visually the elements should receive the keyboard focus after that the input field "In Space" should receive the focus.

The code of quick "In Space" is placed before the code of list of elements incorrectly. This makes it keyboard-only users and screen reader users difficult to understand the correct focus order on the page.

Expected Results

When screen reader users navigate page content, they hear the content in the order of the code in the DOM.

• Provide it as an Editable Combobox.
• Provide aria-autocomplete="none in the <input>, Indicates that the suggestions in the combobox popup are not values that complete the current textbox input.
• Provide aria-controls, Identifies the element that serves as the popup.
•  Provide aria-expanded="true/false", Indicates that the popup element is ** displayed or not.
• Provide aria-activedescendant, When an option in the listbox is visually indicated as having keyboard focus, refers to that option,When navigation keys, such as Down Arrow, are pressed, the JavaScript changes the value. Enables assistive technologies to know which element the application regards as focused while DOM focus remains on the input element.

For more Reference: https://www.w3.org/WAI/ARIA/apg/example-index/combobox/combobox-autocomplete-none.html

Screenshot

Screen Recording

Screen Recording 2022-08-03 at 2.53.46 PM.mov

Workaround

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

Bug Ref: 724885