Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usability: Change color of map's filter buttons' 'hover' state. It looks too close to the 'selected' state, leading to some confusion #2267

Open
1 of 5 tasks
fancyham opened this issue Oct 29, 2024 · 2 comments · May be fixed by #2359
Assignees
Labels
Feature: Usability Issues that make it easy for visitors to find the information they need quickly and easily Missing: Size The effort estimate for this issue is missing P-Feature: Map Food seeker map view Role: Design UI/UX User interface / user experience design Role: Front-end Front End Developer

Comments

@fancyham
Copy link
Collaborator

fancyham commented Oct 29, 2024

Overview

When using a pointing device (mouse/trackpad) on the map screen, the new filter buttons at the top of the map are great, but an issue is that the 'hover' state looks a lot like the 'selected' state, leading to a bit of confusion or unexpected UI.

(video has sound)

Screen.Recording.2024-10-28.at.4.52.08.PM.mov

Consider: Should we have more differentiation between the hover state from the selected state, and if so, how?

What is the user trying to do?

  • Selecting and deselecting filters
  • Needs to know what filters are currently selected and which are not

How many people are / will be having this problem?
Anyone toggling filters

Videos and screenshots

Google's solution

Screen.Recording.2025-02-07.at.6.32.21.PM.mov

Our current solution, which has problems with hover states

Screen.Recording.2025-02-07.at.6.34.33.PM.mov

Discussion and possible Solution(s)

  • Perhaps selected state has much thicker outline?
  • Perhaps remove hover state tinting altogether?
  • If we have a hover color, it needs to work when selecting and de-selecting a filter.

What device is this happening on / what is the user’s context?

Resources/Instructions

  • How this problem is addressed elsewhere (possibly screenshots)?

How do other sites do it? Our filter buttons are based on Google Map's filter buttons — How do they do it? Would it make sense to copy their design patterns?

  • Things to think about?
  • How do others solve this?

Since this is CSS, you might try creating your own custom CSS locally to override the site's — that way you can try out different colors, styles, etc. without asking a dev to do it. Then pass the changes to the devs once design is done.

Action items

  • (optional) Confirm this is a problem. Ask a few people to try this out — is this actually an issue? What problems are they having?
  • (in progress) Design with alternate colors/design for the filter button unselected, hover, selected states
  • Devs build it
  • Test it
  • Release
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: FOLA: Project Board Oct 29, 2024
@fancyham fancyham added Feature: Usability Issues that make it easy for visitors to find the information they need quickly and easily Role: Front-end Front End Developer P-Feature: Map Food seeker map view labels Oct 29, 2024
@fancyham fancyham added Role: Design UI/UX User interface / user experience design and removed ready for product labels Nov 28, 2024
@fancyham fancyham moved this from New Issue Approval to Prioritized Backlog in P: FOLA: Project Board Nov 28, 2024
@fancyham fancyham changed the title Usability: The map's filter buttons' 'hover' state looks too close to the 'selected' state, leading to some confusion Usability: Change color of map's filter buttons' 'hover' state. It looks too close to the 'selected' state, leading to some confusion Nov 28, 2024
@whitneywind whitneywind self-assigned this Jan 28, 2025
@whitneywind whitneywind moved this from Prioritized Backlog to In Progress in P: FOLA: Project Board Jan 28, 2025
@whitneywind whitneywind moved this from In Progress to Prioritized Backlog in P: FOLA: Project Board Jan 28, 2025
@whitneywind
Copy link
Member

@fancyham Is this ready for dev now or should a designer work on it first?

@whitneywind whitneywind moved this from Prioritized Backlog to In Progress in P: FOLA: Project Board Jan 30, 2025
@fancyham
Copy link
Collaborator Author

fancyham commented Feb 8, 2025

Here are two videos (also added to the issue at top) showing Google and our solution. Would it be easy to copy Google's design pattern here? Perhaps it's already part of our Material Design library?

Google's solution, hover states work as expected:

Screen.Recording.2025-02-07.at.6.32.21.PM.mov

Our current solution, which has problems with hover states -- 1) can't see hover when trying to de-select. 2) Hovering makes it look selected when it's not:

Screen.Recording.2025-02-07.at.6.34.33.PM.mov

The proposed change would be:

  1. If this button is in its white "not selected" state, then hover state is a slightly darker grey, and (optionally, if it's part of Material Design) a bit darker/bigger dropshadow
  2. If button in its light blue "selected" state, then hover state is a slightly darker (more black, if using the HSB color scale), with (optionally, if it's part of Material Design) a bit darker/bigger dropshadow

What do you think?

@whitneywind whitneywind linked a pull request Feb 17, 2025 that will close this issue
@ExperimentsInHonesty ExperimentsInHonesty added the Missing: Size The effort estimate for this issue is missing label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Usability Issues that make it easy for visitors to find the information they need quickly and easily Missing: Size The effort estimate for this issue is missing P-Feature: Map Food seeker map view Role: Design UI/UX User interface / user experience design Role: Front-end Front End Developer
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

4 participants