Skip to content

Instantly share code, notes, and snippets.

@hannalaakso
Last active July 10, 2018 16:52
Show Gist options
  • Save hannalaakso/d758b0a45f90da89b6123e390c713462 to your computer and use it in GitHub Desktop.
Save hannalaakso/d758b0a45f90da89b6123e390c713462 to your computer and use it in GitHub Desktop.
Suggestions for future "accessible-autocomplete" work

Findings from a phone call with Ed Horsford on 10th July 2018:

  1. govuk-country-and-territory-autocomplete should remain its own repo as much of the logic is specific to country data (more specific notes made about the workings of that repo).

  2. We should make it easy for depts to consume accessible-autocomplete while adding their own data / logic to it.

  3. We should add the following (in this order of priority?) to accessible-autocomplete:

  • Sorting (what would be an example of this?)
  • Synonyms (for instance on typing "gb", render "United Kingdom (GB)")
  • Typos (replace mistyped word with correct word)
  • Weighting (biased results)
  1. Possibly controversial: There is enough evidence to recommend doing the above without doing further user research on user requirements.

  2. There is some prototype code written for sorting and weighting results in govuk-country-and-territory-autocomplete. It should be rewritten but could be useful for initial investigation.

  3. This is a useful resource: https://baymard.com/blog/autocomplete-design

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment