picture of google search

How to Make an Accesible Auto Suggest with vanilla Javascript

Rohan Faiyaz Khan
16 May 2020

What is an Auto Suggest? #

Autosuggest, also referred to semantically as a Combobox, is a web component we are all familiar with. It is comprised of an input where a user can type, and a dropdown menu with suggestions that the user can select. Depending on the use case, there may be some extra caveats. Some components will autofill the user's response based on the suggests, some will require that the user select something, some will fire a network request and so on.

A component such as this is pervasive in the modern web, search boxes, form inputs, and so many things utilize a variation of this component. It is a wonder that there isn't a standard HTML element to handle them.

The datalist way #

Well to be fair, there is one. The easiest way to go about making your own autosuggest would be to use HTML5's <datalist> element which is now widely supported across all browsers. The example from MDN shows how simple it is.

<label for="ice-cream-choice">Choose a flavor:</label>
<input list="ice-cream-flavors" id="ice-cream-choice" name="ice-cream-choice" />

<datalist id="ice-cream-flavors">
<option value="Chocolate"></option>
<option value="Coconut"></option>
<option value="Mint"></option>
<option value="Strawberry"></option>
<option value="Vanilla"></option>

However datalist comes with its own set of problems. The datalist behaviour isn't consistent across every browser and you are limited to a single line of text for displaying the options. Focus management is inconsistent and any sort of custom behaviour you want is going to cause more pain than you might expect. Feel free to try this out but the results might not be what you want.

If this is all you need then great. If not, let's look at a custom albeit harder way.

The combobox way #

So if <datalist> doesn't work you will have to devise your own solution using a combination of an input and a list that can be shown and hidden using CSS. Seems simple right? Well there is still a problem we need to consider and that is accessibility. When we use a <select> element the browser implements accessibility features out of the box, the user than scroll up and down using the arrow keys, and use keyboard controls to open and close the dropdown. Assistive software for users with disabilities know how to announce that the element has a dropdown, and whether or not the dropdown is open.

Using a simple <input type="text"> tag followed by a <ul> list will not give us these benefits out of the box, and so we need to code them in ourselves. The WAI-ARIA widget for an autosuggest is called a combobox and the official WAI-ARIA guidelines outline how to implement it while still maintaining accessiblity.

Note that you could perhaps use a library to implement this and that could work but a library might not have every feature you want or have features you don't want. Some of them are also not completely accessible. Even if you are using a library that you like, it is good to learn how it works on the inside.

Accessibility Requirements #

Using the official WAI-ARIA guidelines as reference, we can identify some features that our component needs to have to ensure it is accessible. Ignoring some optional cases or ones that are not applicable to our use case, we can list the requirements as follows.

1. Aria roles, states and properties #

2. Keyboard interaction #

Implementation #

Now that we have our requirements out of the way let us implement this. As I do with all my blog posts, I have implemented this in Codesandbox which you can view here if you are the type to dive straight into the code.

Markup and styles #

First of all let's set the markup. Of course the specifics of the markup will depend entirely on you as long as fulfill the accessibility requirements listed above. Here is my implementation. I am using a container div as my combobox container which contains an input that serves the role of textbox and an empty ul with a role of listbox. There is also a button containing an svg arrow for toggling the list.

<label for="autocomplete-input" id="autocomplete-label">
' Type a name of your favorite color

<!-- Combobox container -->


<!-- Arrow for toggling the dropdown -->
<button aria-label="toggle dropdown" class="autocomplete__dropdown-arrow">
<svg width="10" height="5" viewBox="0 0 10 5" fill-rule="evenodd">
<title>Open drop down</title>
<path d="M10 0L5 5 0 0z"></path>
<ul role="listbox" id="autocomplete-results" class="autocomplete__results">
<!-- This is where we will be inserting our list items -->

The children of the listbox which we will dynamically enter will look like this. The tabindex="0" enables this element to be focused.


<!-- content -->

Here are the styles that make this work. Notice that I use the visible class on the list and the expanded class on the dropdown as state indicators.

.autocomplete__container {
position: relative;
margin-top: '0.8rem';
width: 100%;
max-width: 350px;

.autocomplete__results.visible {
visibility: visible;

.autocomplete__input {
display: block;
width: 100%;
padding: 0.4rem 0rem 0.4rem 1rem;
border: 2px solid hsl(212, 10%, 80%);
border-radius: 5px;

.autocomplete__input:focus {
border-color: hsl(221, 61%, 40%);

.autocomplete__dropdown-arrow {
position: absolute;
right: 0;
top: 0;
background: transparent;
border: none;
cursor: pointer;
height: 100%;
transition: transform 0.2s linear;

.autocomplete__dropdown-arrow.expanded {
transform: rotate(-180deg);

.autocomplete__results {
visibility: hidden;
position: absolute;
top: 100%;
margin-top: 0;
width: 100%;
overflow-y: auto;
border: 1px solid #999;
padding: 0;
max-height: 200px;

.autocomplete__results > li {
list-style: none;
padding: 0.4rem 1rem;
cursor: pointer;

.autocomplete__results > li:hover {
background: hsl(212, 10%, 60%);

.autocomplete__results > li:focus {
background: hsl(212, 10%, 70%);

Toggling the listbox #

Getting started with the javascript, let's first handle opening and closing of the listbox. There are several triggers for this such as clicking on the input, focusing on the input and pressing the down arrow, and clicking the toggle dropdown arrow. There are also several triggers for closing, clicking outside the listbox, pressing the escape key while the input is focused and selecting an option in the listbox. It is best if we encapsulate the logic for opening and closing so we can reuse it.

// Extracting the relevant DOM nodes
const input = document.getElementById('autocomplete-input')
const resultsList = document.getElementById('autocomplete-results')
const dropdownArrow = document.querySelector('.autocomplete__dropdown-arrow')
const comboBox = document.querySelector('.autocomplete__container')

// Boolean used for signalling
let isDropDownOpen = false

// Signals which list item is focused, useful for updown keyboard navigation
let currentListItemFocused = -1

function openDropdown() {
isDropDownOpen = true
comboBox.setAttribute('aria-expanded', 'true')

function closeDropdown() {
isDropDownOpen = false
comboBox.setAttribute('aria-expanded', 'false')
input.setAttribute('aria-activedescendant', '')

Populating the list with data #

For the sake of this example I will be populating my list with static data. This can easily be modified to take in data from an API if you wish so.

const colors = [

// Take an input array of string values and insert them into the list
function setResults(results) {
if (Array.isArray(results) && results.length > 0) {
// Transform array of strings to a list of HTML ul elements
const innerListItems = results
(item, index) =>
`<li class="autocomplete-item"


resultsList.innerHTML = innerListItems

// Reset focus when list changes
currentListItemFocused = -1


Handling focusing and selecting a list item #

Focusing and selecting is a simple process but you do need to ensure the appropriate ARIA properties are set as per our requirements.

Note that for certain use cases you may want to disable the input on selection as well and add a button (or Backspace key) to clear it.

function focusListItem(listItemNode) {
const id = listItemNode.id
input.setAttribute('aria-activedescendant', id)

function selectValue(listItemNode) {
const value = listItemNode.innerText
input.value = value
listItemNode.setAttribute('aria-selected', 'true')

Adding click handlers #

We need click handlers for three things:

input.addEventListener("click", openDropdown);

dropdownArrow.addEventListener("click", event => {
if (!isDropDownOpen) {
} else {

document.addEventListener("click", () => {
const dropdownClicked = [

if (!dropdownClicked) {

resultsList.addEventListener("click", event => {
if ([...resultsList.childNodes].includes(event.target)) {

Adding keyboard controls #

Keyboard controls are a bit complicated as we need to make sure our list is completely navigable by keyboard and follows the conditions in the accessibility requirements.

One thing that might trip up people is scrolling. If you have a long list you will want to allow scrolling, but pressing up and down in a scrollable view will cause the view to scroll. As we want to use up and down arrow keys for navigation we need to prevent this with an event.preventDefault(). Then simply focusing each element as we navigate to it will cause said element to scroll into view.

function handleKeyboardEvents(event) {
const listItems = resultsList.childNodes
let itemToFocus = null

switch (event.key) {
case 'ArrowDown':
if (currentListItemFocused < listItems.length - 1) {
if (!isDropDownOpen) {
currentListItemFocused = currentListItemFocused + 1
itemToFocus = listItems.item(currentListItemFocused)
case 'ArrowUp':
if (currentListItemFocused > 0) {
currentListItemFocused = currentListItemFocused - 1
itemToFocus = listItems.item(currentListItemFocused)
case 'Home':
if (currentListItemFocused > 0) {
currentListItemFocused = 0
itemToFocus = listItems.item(currentListItemFocused)
case 'End':
if (currentListItemFocused < listItems.length - 1) {
currentListItemFocused = listItems.length - 1
itemToFocus = listItems.item(currentListItemFocused)
case 'Enter':
if (!isDropDownOpen) {
} else {
if (listItems[currentListItemFocused].innerText) {
case 'Escape':
if (isDropDownOpen) {
if (event.target !== input) {
// Check if list is focused and user presses an alphanumeric key, or left or right
if (/([a-zA-Z0-9_]|ArrowLeft|ArrowRight)/.test(event.key)) {
// Focus on the input instead

input.addEventListener('keydown', handleKeyboardEvents)
resultsList.addEventListener('keydown', handleKeyboardEvents)

Notice the default case which fulfills the last three conditions for keyboard controls in the accessibility requirements. If the user presses left, right or any printable key we need to return focus to the input field. We can use a simple regular expression to test for this and focus the input if needed. Simply focusing on the input will cause the characters to be printed on the input instead.

Deboucing input (optional) #

We have covered almost everything except filtering the list results when we type. Before we do this though I want to briefly cover debouncing which you will certainly want if you are either:

What a debouncer does is wait until your input has stopped changing for a set timeout before launching the callback, thus reducing unnecessary calls to it. If you don't need a debounce feel free to skip this.

let bounce = undefined
function debounce(callback) {
bounce = setTimeout(() => {
}, [500])

Filtering input #

Finally once all our bases have been covered we can write our filter function that gets called when the user types. This function will vary completely based on your requirements. I will demonstrate a very simple example using a very simple regular expression that checks if the word starts with the input string entered by the user.

function filter(value) {
if (value) {
const regexToFilterBy = new RegExp(`^${value}.*`, 'gi')
filteredResults = colors.filter((color) => regexToFilterBy.test(color))
} else {
filteredResults = [...colors]

input.addEventListener('input', (event) => {
const value = event.target.value

debounce(() => {
if (!isDropDownOpen) {

Conclusion #

With that our implementation should be off and working. You can test it in the aforementioned Codesandbox which you can view here before implementing yourself.

I should add however that while I have tried my best to adhere to the official WAI-ARIA guidelines, screen-readers widely vary in terms of what they announce to the user. As I am still new to learning about accessibility it is entirely possible that I have missed something. Please feel free to suggest improvements to this code either via a comment or a pull request to the repository.