GIBCT Search and Filters - Usability Test Prep - Accessibility Feedback

[1Copenut]

Feedback framework

• ❗️ Must for if the feedback must be applied
• ⚠️ Should if the feedback is best practice
• ✔️ Consider for suggestions/enhancements

Must

• Ensure the new search results are communicated clearly to screen readers. We haven't had the chance to see what the shape of the data is; will this return multiple facets or a single co-mingled list that matches on the keyword or string? A search for "California" may return a number of results like the state of California, universities, colleges, schools with California in the title, etc.

Should

• Make sure clicking a search result doesn't fire the form submit from the first page. This goes out and around the Search for schools button and feels like it breaks the expected workflow.
• Add a "Search" or "Go" button to the updated filters on the search results page. If this is not possible, I'd encourage a short paragraph describing that changes made to the filter inputs will trigger a new search. This falls under the recommendation of WCAG 2 SC 3.2.2 On Input
• Observe and record qualitative and quantitative usability of the updated search. I am looking forward to seeing the expanded search criteria, and how they will be presented to users. It was mentioned results are coming back sub-two seconds, which is a great metric. I'm interested to hear how users feel about the expanded result set.

Consider

• Consider a dry run test of the non-code prototypes (InVision) with screen magnifiers like Windows Zoom.
• Consider a dry run test of the mobile Zoom experience
• Adding an OKR for measuring high, low, average, media, and standard deviation around time to return data from the API.
• Any API caching strategies or ways to speed up results? Any common lookup requests?

Definition of Done

• Team has responded with answers to the Must and Should questions. These can be 2-3 sentence summaries, links to prototypes / live code, whatever the team feels are the best ways to respond.
• Team schedules any dry runs with accessibility specialist if needed. If no dry runs are needed, this point can be disregarded.

[amyknox]

Thanks for this input Trevor. As you saw Friday, we've incorporated some of your feedback and are still working on the search button & Search Results page updates.