annepetersen
commented
5 days ago Hey Amy: let's talk with @jaclinec here to follow up on our meeting with Search.gov (originally discussed here). I also thought you had a few other action items before moving on this, and that that meeting provided answers to some of your questions here.
(This came up in open issues triage today, and it wasn't clear that the devs shouldn't take action yet, so this may have been mislabeled. I think you intend to do this in a future sprint, correct?)
Add guidance for users when implementing the search component. Ensure visitors' expectations are clear when: Searching a site (will they get external results?) Searching a sub-site or collection (how instructions need to differ; should form elements be unique?)
Site search vs. directory or other search. I’d like to know more about how many agencies have multiple searches on their page(s). vote.gov has a search that indexes the USA site, for example. How often does this happen? It could be considered a gray area for accessibility since there’s a change of context (site) if someone clicks a non-domain link. It’s at least confusing. We’d want to be clear about what results the person is getting. Guidance-be clear about search context Set up a meeting Search when they’re available to discuss linking across fed sites. If default is just subdomain you’re on, that’s expected by users
Is the default wider than the subdomain you’re on?