Backlog : Search results are not programmatically defined

Issue Summary

On the “Backlog” page, the search results are not programmatically communicated to the users of a screen reader.

Steps to Reproduce

1. Navigate onto the above mentioned page.
2. Type any character in the "Search for issues" input field.
3. Observe that the content below gets dynamically updated.
4. Observe that this dynamic update is not communicated to the users of screen readers.

Actual Results

When the any character is typed in the "Search for issues", the content below gets dynamically updated. This update is not communicated to the users of a screen reader. This behaviour might confuse or mislead them.

Expected Result

Make sure that search results are programmatically determined. To achieve this, use a polite live region, such as role=“status”, and aria-atomic to make sure that the entire text node is always announced. If this is not possible due to any constrains, then use hidden instructions, notifying users about the dynamic update in advance. Make sure that this instruction is programmatically associated with the form field with aria-describedby. Make sure that the id values match appropriately.

Screen Recording

Screen Recording 2023-05-18 at 10.57.51 AM.mov

Code snippet

<span role="status" aria-atomic="true">10 results found</span>
<span role="status" aria-atomic="true">No results found</span>
<label for="i1">Search for issues</label>
<input type="text" id="i1" aria-describedby="hintText" ...>
<span id="hintText" class="hiddenText">The table below will get updated as you change the values.</span>

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 Monterey Version 12.4
Chrome - Version 103.0.5060.134 (Official Build) (arm64)
Firefox- Version 93.0 (32-bit)
Safari- Version 15.5 (17613.2.7.1.8)
JAWS- Version 2022
NVDA- Version 2020.3
Voiceover - Version Latest