Discoverability for Facility Locator (mobile)

[mmiddaugh]

Issue Description

Mobile month research (conducted in August 2020) revealed that Veterans have a hard time finding Facility Locator in the top Nav menu, particularly on mobile. They tend to use global search to accomplish a service-oriented task (I need benefit assistance).

Current position in mobile experience


Two considerations: 1- How might we promote discoverability for Facility Locator? 2- How might we leverage global search to help more Veterans find Facility Locator and/or the detail pages they seek?

---

Tasks

• [ ] What work is necessary for this story to be completed?

Acceptance Criteria

• [ ] What will be created or happen as a result of this story?

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[davidmpickett]

@jilladams - this seems to be more about the homepage/ header as opposed to Facility Locator - review if relevant for Public Websites?

[jilladams]

Here too, I think this is a Facilities product management / strategy exercise to figure out where Facility Locator links / content should appear, and then partner with the PW team for changes to homepage/header. With my DaveC hat on, he's very protective of that real estate, and would want a clear Product case for the change request.