The typeahead or combobox component is usually similar to a textbox where users can type ahead to select an option, or sometimes even type arbitrary text as a new item to add to the list.

It is a combination of a single line input field with a popup, typically a listbox. All of the digital accessibility requirements for form fields apply: a persistent label, visible focus state, perceivable control boundaries, and adequate text contrast.

Because this field is editable and is typically used for autocomplete behavior (to help the user find things more quickly), the aria-autocomplete attribute should be used.

There are a few forms of autocomplete that have historically been considered acceptable:

  1. no autocomplete: the suggested values that appear are the same, no matter what the user has typed in the textbox.

  2. list autocomplete with manual selection: the suggested values that appear contain values that complete or otherwise logically correspond with the characters that the user has typed into the textbox. However, the characters that the user has typed will be the value of the textbox unless the user manually selects a value displayed in the popup.

  3. list autocomplete with automatic selection: the suggested values that appear, contain values that complete (or otherwise logically correspond with) the characters that the user has typed into the textbox, and the first suggestion is automatically highlighted as selected. The automatically selected suggestion becomes the value of the textbox when the combobox loses focus, unless the user manually chooses a different suggestion.

  4. list with inline autocomplete: after the user types a certain number of characters, suggestions display inline after the input cursor in the textbox (known as a completion string). The suggested completion string should update as the user types additional characters.

However, it should be noted that in a recent user experience study conducted by Microsoft, they found that a number of people were confused by the filtering behavior when it was present. This was particularly notable when spelling mistakes were made that returned no results, and after an option was selected, when all other results would be filtered out. Because of this, the current recommendation is to avoid filtering unless there is a particular reason for it, such as a very large set of possible options. For more limited option sets, consider not filtering and only moving focus to the closest matching option. [source]

Part One: Considering Markup

<div class="form-group">
<label for="typeaheadInput-001" id="label-001" class="combobox-label">
Choice or Search Label Text
<div class="combobox-wrapper">
<div role="combobox" aria-expanded="false" aria-owns="listbox-001" aria-haspopup="listbox" id="combobox-001">
<input aria-autocomplete="list" aria-controls="listbox-001" id="typeaheadInput-001" type="text" />
<ul aria-labelledby="label-001" role="listbox" id="listbox-001" class="listbox hidden">
<li class="listbox-result" role="option" id="option-001">An option example</li>
<-- This will likely be a long list -->

Keyboard Interactions



arrow keys

cycle through the auto-suggestions and input field


close the listbox (if open)


select the currently focused auto-suggestion item and close the listbox


select the currently focused auto-suggestion, close the menu, and move focus to the next focusable element

The keyboard interactions are important here, because there is definitely the risk of introducing serious keyboard navigation flaws -- the focus could escape the listbox and continue down the page, or conversely, the focus could get trapped inside of the listbox and never allow the user to escape out of the list.

Conditions for Dropdown

The dropdown is hidden by default; as the conditions that should trigger it are specific to the application and use cases, consider possible methods but don't forget to remain consistent with other user experiences across the application.

Here are some possible display conditions:

  • It is displayed only if a certain number of characters are typed in the textbox and those characters match some portion of one of the suggested values.

  • It is displayed as soon as the textbox is focused, even if the textbox is empty.

  • It is displayed when the Down Arrow key is pressed or the show button is activated, possibly with a dependency on the content of the textbox.

  • It is displayed if the value of the textbox is altered in a way that creates one or more partial matches to a suggested value.

Part Two: Creating the Ember Component

Generate the component

ember generate component typeahead -gc

Three files will be created:

  • app/components/typeahead.js

  • app/components/typeahead.hbs

  • tests/integration/components/typeahead-test.js

A few styles will need to be added, but the method to do so will depend on the overall CSS approach for the application.

Add template code

In the typeahead.hbs file, the template code can be added:

<div class="form-group">
<label for={{this.inputId}}
<div class="combobox-wrapper">
<div role="combobox"
<input type="text"
<ul aria-labelledby={{this.labelId}}
class="listbox hidden">
{{#each this.listboxOptions as |option index| }}
<li class="listbox-result" role="option" id="{{this.listboxId}}-{{index}}">{{option}}</li>

//TODO abstract/add show/hide

Component JS

From the template code above, it is clear that there are multiple associations happening for accessibility reasons. Using the same approach as for other form components, unique IDs can be generated:

import Component from '@glimmer/component';
import { guidFor } from '@ember/object/internals';
export default class TypeaheadComponent extends Component {
inputId = 'typeaheadInput-' + guidFor(this);
comboboxId = 'combobox-' + guidFor(this);
listboxId = 'listbox-' + guidFor(this);
labelId = 'label-' + guidFor(this);
listboxOptions = [
// options here

//TODO add keyboard support

Using the Component

The component is now ready to be used in the page or form template file:

<Typeahead @typeaheadLabelText="Choice or Search Label Text" />

Part Three: Abstracting for Reuse

coming soon!


Feedback is welcome! Visit the GitHub repository for this project to raise an issue.