---
title: "Search Autocomplete UX: Fast, Clean, Keyboard-Ready · Rubric"
description: Show suggestions after two or three characters with no lag, remove duplicates and make the list work from the keyboard.
url: https://rubric.design/ux/search.autocomplete-suggestions
format: agent view of this page
updated: 2026-11-16
---

[UX guides](https://rubric.design/ux/) / [Site search](https://rubric.design/ux/topic/search) / Autocomplete suggests as the user types, fast, clean and keyboard-operable

# Autocomplete suggests as the user types, fast, clean and keyboard-operable

Usually high · How serious this usually is when it goes wrong. Not a score.

## The guideline

Show suggestions after two or three typed characters, with no visible lag or flicker as the user keeps typing. Deduplicate and filter suggestions so nothing redundant or clearly irrelevant appears, and visually distinguish raw query completions from suggestions that point at a specific product, title or category. Tolerate near misspellings rather than returning an empty popup for a one-character typo. Implement the control as an accessible combobox, not a plain text input with a floating list glued on: arrow-key navigation highlights an option and can copy it into the field, Enter accepts the highlighted option, Escape closes the popup without altering typed text, and the relationship between the input and its suggestions is exposed with aria-autocomplete and aria-activedescendant (or equivalent) so screen reader users get the same capability sighted users do.

## Common failures

- The site's search field does not display keyword query suggestions while the user types, forcing shoppers to formulate complete queries from memory and increasing the risk of zero-result or poorly framed searches.

## Where it applies

### Pages

- Search

### Disciplines

- Conversion
- Accessibility

### Devices

- Desktop web
- Mobile web
- Mobile app

## Why it matters, how to fix it, and the research behind it

Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first.

[Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents)

## Related guides

- [Labels are programmatically associated with their fields](https://rubric.design/ux/accessibility.form-label-association) · Usually critical · Associate every input's visible label with its control using a native \<label for>/id pair, or aria-labelledby when a native label element is not possible.
- [Video and audio content ships with captions and a transcript](https://rubric.design/ux/accessibility.video-captions-transcripts) · Usually critical · Provide synchronized closed captions for every prerecorded video that has a soundtrack, including speaker identification and non-speech sounds that carry…
- [Pages have a descriptive title and a logical heading hierarchy](https://rubric.design/ux/accessibility.heading-structure) · Usually high · Give every page a unique \<title> that identifies its specific content, with the page-specific part first (WCAG 2.2 SC 2.4.2).
- [Pointer targets meet a minimum size or spacing](https://rubric.design/ux/accessibility.pointer-target-size) · Usually high · Make every pointer target at least 24 by 24 CSS pixels — the WCAG 2.2 Level AA floor — and design to 44 by 44 wherever the control carries weight, which is…
- [Password composition rules are shown before submission, not after](https://rubric.design/ux/auth.password-requirements-visible) · Usually high · If the password field enforces composition rules, state them next to the field before the first submit attempt — as static hint text or a live checklist that…
