-
Notifications
You must be signed in to change notification settings - Fork 67
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
Experimental Design System Request: Typeahead #637
Comments
Thank you, @mgleo, this looks great. |
@mgleo Thanks for all the details in your request. Looks great. Please assign experimental design requests to me so I make sure it is brought to the Design System Council. Thanks! |
Thanks @GnatalieH and @caw310, let me know if you need anything else. |
@mgleo here is a link to user test findings that the team doing The Financial Status Report captured. They have multiple type-aheads in their list and loops, and the component tested poorly so they are going do another iteration that doesn't use list and loop. The 526 form add a condition type-ahead also has a similar usability issue:
Here is a link to the Slack conversation about the type-ahead. And, here is a link to the type-ahead audit I'm currently working on (Mural board). This doesn't require you to do anything, but I wanted to leave these links in a comment on this ticket. I think that the type-ahead is a pattern that works great for search, and I'm looking forward to documenting it. |
Here are the action items from DSC meeting on 2/4 where this item was discussed. No need to add this to experimental design since research was done and shows success. |
Hi @GnatalieH and @caw310, since this was approved for the Design System what are the next steps for the Search & Discovery team? Do you need anything more from us to get Typeahead up on design.va.gov? |
@mgleo , I don't think we need anything else as this time but Natalie may follow up once we start working on this. Thanks! |
@mgleo when I start working on the design for the type-ahead to help guide development of the web component, I'd like to leverage what I can from your mockups. Where can I find them in Sketch for Teams? Could you leave a link in this ticket? Thx. |
Sending you a Typeahead Sketch file via Slack (along with some Search UI mockups as well). |
Typeahead functionality is covered in https://design.va.gov/components/search-input |
Check the design system backlog and experimental design tab to see if your proposal has already been suggested.
What
Typeahead
Why
There are several products on VA.gov that utilize search.
According to Nielsen Norman Group:
"When your users select from search suggestions rather than typing in their own complete query, they benefit because they:
There are several VA.gov products that utilize search and could also utilize typeahead:
Not search related but typeahead has been utilized to assist users fill out forms:
05/25/2021 ToT Presentation:
06/01/2021 ToT Presentation:
06/15/2021 ToT Presentation:
06/29/2021 ToT Presentation:
Yes, it does not exist on the Design System.
Note: @GnatalieH recently opened #636: Document type-ahead as a Pattern on design.va.gov
Standardize type ahead search pattern department-of-veterans-affairs/va.gov-team#38264 opened Sept 2020
Anything else
Usability Research
Comparative Analysis
Accessibility updates:
Typeahead on Global Search highlights suggested characters
Next steps
You may present your work to the Design System Council at an upcoming meeting. If you do not or cannot attend the Design Council Meeting, you can opt to get an asynchronous approval.
Submit requests to join an upcoming Design System Council meeting in #vsp-design-system.
During the meeting, the Design System Council Working Group will evaluate the request and make a decision.
If your component request is approved, you can add your component to the experimental section on design.va.gov. If you havee any questions on how to add your component to the experimental section, please reach out to the Design System Team at #vsp-design-system
The text was updated successfully, but these errors were encountered: