Autocomplete (Formally known as Typeahead) UI/UX Standards
Prototypes
Mockups:
https://www.figma.com/file/k6jd9O6y1amgF83JhobcLx/PLP-Autocomplete?node-id=302%3A5236
Desktop Prototype:
Mobile Prototype:
Name | Attributes | Functionality | Notes | |
---|---|---|---|---|
1 | Search Field | |||
2 | Text Field |
|
|
|
3 | Search Button |
|
| |
4 | Recommendations | |||
5 | ||||
6 | Requirements | |||
7 | Section Order | The Business (Merchandising) will need to be able to control the order that the different autocomplete recommendation sections show up in, through Endeca/XM. | ||
8 | Quantity per Section | The number of recommendations that show up in each section should be based on a relevancy ranking based on the query that the user has entered. Because the autocomplete widget should expand to fit its options (and never use a scrollbar to limit their size), the number of options should be limited so they don’t overflow the user’s viewport. (see guideline #404) | ||
9 | Max Quantity | Desktop:
Mobile:
| ||
10 | Navigation | User can use the up and down arrow keys on the keyboard to navigate through the recommendation list. The focused item will use the hover styles, and the query in the text field will update to match the focused element. Allowing the user to navigate and select the autocomplete suggestions with their keyboard is essential (see guideline #369) If the user hovers over a recommendation item with their mouse, the item will appear in the hover state, but no change is made to the query until the user clicks on a recommendation item. When the user presses "enter", whatever query is populated in the text field will be submitted. | ||
11 | Recommendation Types: | |||
12 | Search History | Icon: Clock Icon | Shows upon Text Field focus.13 | Give the users the ability to remove an item from their search history
|
13 | Removal Success Message | Label: "Removed from search history" Link: "Undo" | Message shows for up to 7 seconds. If the user pushes "Undo" while the message is shown, the item will be returned to the list. | |
14 | Suggestions | Title: "Suggestions" Icon: Search Icon | Provide “Suggested Search Queries” for users, instead of just categories or results (products). Search Query Suggestions should provide the following benefits to the user:
Suggested search queries requires 2 parts to make it useful:
| |
15 | Dimensions | Title: "Categories" or "Brands" respectively Label:
Number of Results: Show the number of results for each item in parenthesis to give the user context into how the results are ordered. | This is the only thing that shows in the current Autocomplete. Items are ordered by number of results within each one. | |
16 | Results | Title: "Products" Product Image: {product-image} Line 1: Will show {web-display name} or {product-code} depending on the search query and which one we're confident they're searching for. Line 2:
| If the web display name is too long to show, only show the most relevant section with ellipsis' on the beginning and end when necessary. |
Glossary
Autocomplete -
(n.) Sometimes referred to as "Typeahead", Autocomplete is the component on ferguson.com that drops down and shows recommendations as the user is typing in the main search field on the site.
Dimension -
(n.) Any product attribute returned as a recommendation by the Autocomplete algorithm. Currently only "category" or "brand" are returned.
Query -
(n.) The string that is entered into search field.
Recommendation -
(n.) An item that is returned by the Autocomplete algorithm as being relevant to what the user is typing. Could be 1 of 4 types: Search History, Suggestion, Dimension, or Result.
Result -
(n.) Any specific product (SKU) returned as a recommendation by the Autocomplete algorithm, that takes the user directly to a product page.
Search History -
(n.) Any query that the user has entered that didn't result in a 404 or "no results" page.
Suggestion -
(n.) Curated search query offered to the user as a possible search that would cause the site to return relevant results to what they're looking for.