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

Change "Back to Search" link to "< Back to Results" and change color #2189

Closed
fancyham opened this issue Aug 13, 2024 · 3 comments · Fixed by #2231
Closed

Change "Back to Search" link to "< Back to Results" and change color #2189

fancyham opened this issue Aug 13, 2024 · 3 comments · Fixed by #2231
Assignees
Labels
dev Code Development Feature: Usability Issues that make it easy for visitors to find the information they need quickly and easily good first issue Good for newcomers Missing: Milestone This issue is not part of any milestone Priority - Med Needs to be in the next release priority: SHOULD HAVE Ready for dev lead Issue ready for dev lead to review Role: Front-end Front End Developer

Comments

@fancyham
Copy link
Collaborator

Context

Currently, it's hard to see the "Back to Results"-type link on our organization detail screen.

This small design change should make this breadcrumb more prominent and help users have a better sense of their location on the site.

For reference, here's the current version

image

The light grey text makes it hard to understand that it's a breadcrumb. The low contrast also makes it hard to read for people with clouded vision (i.e. seniors)

Proposed change

image

Change the text a little (note that it's worded differently on Desktop for some reason):

  • Change text to read "< Back to Results" (this is more common terminology)
  • Change the color to be a darker/higher contrast color... dark gray rather than the current light gray.
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: FOLA: Project Board Aug 13, 2024
@fancyham fancyham added good first issue Good for newcomers Role: Front-end Front End Developer Feature: Usability Issues that make it easy for visitors to find the information they need quickly and easily Ready for dev lead Issue ready for dev lead to review Priority - Med Needs to be in the next release labels Aug 13, 2024
@fancyham fancyham moved this from New Issue Approval to Prioritized Backlog in P: FOLA: Project Board Aug 13, 2024
@fancyham
Copy link
Collaborator Author

This is from row 20 of the design team's usability issues spreadsheet

@prashantrai-30
Copy link

Hey @fancyham can you assign this issue to me,I have a potential solution for this.

@fancyham fancyham added the dev Code Development label Aug 16, 2024
@fancyham fancyham moved this from Prioritized Backlog to New Issue Approval in P: FOLA: Project Board Aug 16, 2024
@fancyham
Copy link
Collaborator Author

HI, @prashantrai-30, you must be a Hack for LA member and Food Oasis volunteer to work on these issues and I don't see you our our developer group -- check out hackforla.org to learn more, or contact your team lead please!

@sumit-sharma92 sumit-sharma92 added the Missing: Milestone This issue is not part of any milestone label Sep 26, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to ERs / Epic to make issues for in P: FOLA: Project Board Sep 27, 2024
@junjun107 junjun107 self-assigned this Sep 27, 2024
@github-project-automation github-project-automation bot moved this from ERs / Epic to make issues for to Done in P: FOLA: Project Board Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev Code Development Feature: Usability Issues that make it easy for visitors to find the information they need quickly and easily good first issue Good for newcomers Missing: Milestone This issue is not part of any milestone Priority - Med Needs to be in the next release priority: SHOULD HAVE Ready for dev lead Issue ready for dev lead to review Role: Front-end Front End Developer
Projects
Development

Successfully merging a pull request may close this issue.

5 participants