Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search results page #189

Open
timpaul opened this issue Feb 4, 2019 · 5 comments
Open

Search results page #189

timpaul opened this issue Feb 4, 2019 · 5 comments
Labels
pattern Goes in the 'Patterns' section of the Design System

Comments

@timpaul
Copy link
Contributor

timpaul commented Feb 4, 2019

What

How to display a list of search results

@devansXD
Copy link

devansXD commented Mar 21, 2019

It feels like this is potentially quite a large area and covers many different types of results, namely:

  • Information type and breakdown
  • Raw data presentation
  • Tabular or list based structure
  • Filter behaviour and positioning
  • Sort behaviour and positioning
  • Action a user can take eg: pick a thing/multiple things and do something else

@titlescreen
Copy link

I agree with @devansXD, the type of search results may well depend on

  • the type of search carried out
  • the number of expected results
  • information needed with those results to make a decision
  • are they using the basic or progressively enhanced version

As such, I can't comment on all the search result pages, and perhaps we could consider breaking this down into smaller more achievable items in the backlog then standardise them later?

Progressively enhanced version

In the two services, we made on the DfE claim project we were working primarily on a school search. The progressively enhanced version was a more simple decision as we used accessible auto-complete (https://github.com/alphagov/accessible-autocomplete) with a couple of tweaks to increase the contrast on the search options and pull in some additional information about the schools.

One of the user research participants (T15) had been using JAWS since 2002 and at the time of testing, they were on a Windows XP Machine. Generally speaking accessible autocomplete worked well for them.

Once they had started typing it was easy for them to select options from the dropdown

Possible issue, when changing the answer on this question as it remembered the response and they didn't know that the input was pre-filled

image

Non-javascript version

For the non-javascript search, we opted to return the search results as a list of radio buttons. This tested well for all users it just involved a bit of scrolling however, that seemed like preferable to a more dense list that was potentially harder to read.

image

Support issues related to our school search

Users got in touch with support when they:

  • were taken to an ineligible page as their school was not included in the pilot
  • they could not find the school because it had changed status (e.g. become an academy) and/or slightly changed its name

There was also an issue with apostrophes within the school name e.g. St Mary's or St Marys. Whilst it was possible to do something on the search results page to include both schools with and without apostrophes a more simple solution was to allow them to search via postcode.

@CharlotteDowns CharlotteDowns added the pattern Goes in the 'Patterns' section of the Design System label Oct 13, 2021
@laura-biscuits
Copy link

Is there a separate backlog item (that I can't find) for when a search has no results to return and telling a user what to try instead?

@domoscargin
Copy link

Hi @laura-biscuits, thanks to @adyhoran1 there is now: #264

@CharlotteDowns
Copy link

We've just added some guidance on how to 'share findings about your users' with us 📝. This will help us learn more about how your users understand search results within your service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pattern Goes in the 'Patterns' section of the Design System
Development

No branches or pull requests

6 participants