When creating a new bug, the search for components/products is very accessible to blind screen reader users. You hear when suggestions are available, and when selecting an entry using the arrow keys, you also get speech feedback. Please apply the same to the CC: and other fields where autocomplete is used when creating or modifying a bug.

How do we do that? What's the magical HTML attribute?

(In reply to Frédéric Buclin from comment #1) > How do we do that? What's the magical HTML attribute? 1. The edit field(s) get: a) aria-autocomplete="true" to indicate that there is an auto-complete mechanism at work. This is independent from the autocomplete attribute and is purely semantic for screen readers, so doesn't change browser behavior. b) aria-expanded="false" if no results are currently showing, and aria-expanded="true" once results are showing. c) aria-controls=idref to the listbox (see below) that contains the actual results. 2. The ul of autocomplete results gets: a) role="listbox". b) an ID (if it doesn't already have one) that aria-controls from above points at. 3. The individual entry li elements get: a) role="option". b) tabindex="-1" to make them focusable with the keyboard, but not include them in the tabbing order. c) aria-selected="true" if the current element is the selected one, otherwise aria-selected="false". All elements that are currently in the list must have an aria-selected value, but only one of them must be "true" at any given time. 4. Once there are elements showing, aria-expanded on the textbox gets a value of "true". 5. Once the user presses downarrow to go into the list, the first item should receive keyboard focus by setting resultElement.focus on it. Every subsequent press of up or down arrow will move the cursor up and down through the elements. 6. If the user presses Enter or tab to accept the autocomplete, the field gets filled, and keyboard focus is returned to the text field. 7. If the user presses Escape, focus is returned to the text field without accepting the chosen entry.

I’ll create an accessible autocomplete widget to replace the Devbridge Autocomplete jQuery plug-in we are currently using. https://github.com/devbridge/jQuery-Autocomplete The best practices and examples can be found at: https://w3c.github.io/aria-practices/#combobox