Experimental Design - Use my location

[briandeconinck]

What

Give a brief description of the component or pattern you want to propose.

Create a pattern for handling requests to access a user's browser location data.

There are a handful of instances on VA.gov where products use browser location data, eg. Find VA locations, but there's nothing in the design system around when that feature should be used or what the user interaction should look like. That's resulted in:

• Inconsistent placements for the "Use my location" button
• A button style that's inconsistent with any other buttons on VA.gov
• Underdeveloped content for the modal in the case where users have browser location turned off

Note: @laflannery on the Sitewide crew has started some design work around this as her team moves to Figma. Creating this mostly-blank ticket for visibility and tagging her to share her progress as she works on it!

Purpose

What problem does this component or pattern solve for the user?

Usage

Context or task: Explain the scenario or user tasks where this component is, or could be, used.

Behavior

Describe the key interactions for this component, calling out any specific considerations for mobile.

Examples

Include any examples you have of this component or pattern. These can be screenshots, links to a Sketch file, or links to staging or production.

Accessibility

Include any accessibility considerations.

Some initial thoughts on accessibility:

• The "Use my location" button should be visually recognizable as a button
• The button should come between the city/state/ZIP label and its input (matching Find VA Locations)
• I'm not exactly sure what should happen with keyboard focus when clicking the button -- if it should move to the input or stay on the button, and if success/failure to retrieve location information should matter for where it goes.

Guidance

What would you want to tell other teams about this component or pattern?

Research (optional)

Include any research you have already conducted, or plan to conduct, on this component or pattern.

Code (optional)

Include any existing code.

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 #platform-design-system.

During the meeting, the Design System Council Working Group will evaluate the request and make a decision.

If your request is approved, you can add your component or pattern to the system. If you have any questions on how to add your component or pattern to the system, please reach out to the Design System Team at #platform-design-system.

[caw310]

@briandeconinck this is on the agenda for the Feb 9 DSC meeting.

[laflannery]

@caw310 I'm not sure if this changes your agenda/plans at all but we don't have any solid new ideas for this yet. It is on our radar but we might not have anything to share until after the initial Facility Locator research which is planned for sometime probably Q2

[caw310]

@laflannery @briandeconinck we will hold off on discussing this in a DSC meeting.

[humancompanion-usds]

@laflannery - Has the Facility Locator research happened?

[laflannery]

@humancompanion-usds Unfortunately not, between other priorities and contract transition we had to put some other things ahead of this. @aklausmeier can probably speak a bit more specifically about a timeline though