Visual indication of all the results in the list of the Facility Locator

[omahane]

User Story or Problem Statement

How might we better indicate when showing a set of results in the facility locator that the returned result list is longer than what is seen?

Acceptance Criteria

• [ ] Result list appears to be longer than what is currently shown, meaning that you can scroll to see more results.

Implementation steps

## Design principles Veteran-centered - [ ] `Single source of truth`: Increase reliability and consistency of content on VA.gov by providing a single source of truth. - [x] `Accessible, plain language`: Provide guardrails and guidelines to ensure content quality. - [ ] `Purposely structured content`: Ensure Content API can deliver content whose meaning matches its structure. - [ ] `Content lifecycle governance`: Produce tools, processes and policies to maintain content quality throughout its lifecycle. Editor-centered - [ ] `Purpose-driven`: Create an opportunity to involve the editor community in VA’s mission and content strategy goals. - [ ] `Efficient`: Remove distractions and create clear, straightforward paths to get the job done. - [ ] `Approachable`: Offer friendly guidance over authoritative instruction. - [ ] `Consistent`: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks. - [ ] `Empowering`: Provide clear information to help editors make decisions about their work. ### CMS Team Please check the team(s) that will do this work. - [ ] `Program` - [ ] `Platform CMS Team` - [ ] `Sitewide Crew` - [ ] `⭐️ Sitewide CMS` - [ ] `⭐️ Public Websites` - [x] `⭐️ Facilities` - [ ] `⭐️ User support`

[dsinla]

@omahane I see a scrollbar when I have more results than initially appear in the results area. I tested in both Chrome and Explorer at different magnifications (see screenshots).

I have a vague memory of coming across this before, where mac's sometimes won't display the scrollbar for some tools/controls? This page refers to a Mac system setting. Could that be the culprit?

[mmiddaugh]

Can we consider this during mobile map enhancement work?