#Steps to reproduce (assumes ChromeVox or similar)

1. [Tab] or [Shift+Tab] to the search box
2. Listen to the screen reader (it sounds fine)
3. Type in an entry
4. Hit [Enter]

Actual Result
Nothing happens, leaving a non-sighted user confused.

Expected Result
The screen reader would read something like:

There are 4 UI categories in your search. Please press tab to continue to the filtered results.

To indicate the number of results, along with the next action they should take.

Suggested Fixes
One solution that might work here is an "intent" pattern on the onchange event on search... something like the following borderline-pseudocode:

var notificationInterval;

document.querySelector('#search").onchange = function() {
  clearInterval(notificationInterval)
  notificationInterval = setInterval(function() {
    // code that would trigger the screen reader to read a certain aria-hidden element
  }, 500);
};

Category: #615: Elastic UI Chrome Accessibility
Relevant WCAG Criteria: 3.2.2 On Input