ARIA live regions or manual focus management for dynamic Algolia search results

Choosing an announcement strategy for live results

I'm building a user-facing search workflow with Algolia InstantSearch (assuming a recent v4 client), where results re-render on every keystroke. I need the experience to work for screen reader users, and I'm weighing two documented approaches: wrapping the hits container in an ARIA live region so updates are announced automatically, or leaving the region quiet and moving focus programmatically to a results summary after each search settles.

The constraint

With as-you-type search, a polite live region can flood assistive technology with announcements on every keystroke, while assertive announcements or aggressive focus shifts can yank users out of the search input mid-typing. Debouncing the query helps, but the core trade-off between announcement verbosity and focus stability remains.

Questions

Which pattern do teams typically pair with InstantSearch's hits widget: an aria-live wrapper with debounced updates, or a visually hidden status element that announces only the result count?

If focus is moved after a search, what is the accepted trigger so keyboard users typing in the search box are not interrupted?

Do query suggestions from the autocomplete experience need a separate opt-in or pause mechanism to satisfy accessibility expectations, or is standard combobox markup sufficient?