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 alert color to more appropriately communicate warnings vs watches #1074

Closed
sarahmhgov opened this issue Apr 17, 2024 · 12 comments
Closed
Assignees
Labels
Design Iteration Minor improvement based on feedback

Comments

@sarahmhgov
Copy link
Collaborator

sarahmhgov commented Apr 17, 2024

Description

Currently all WWA in the website are red. This has been called out by internal and external users as inconsistent with NWS practices and confusing.

Update

  • red: warning
  • orange: watch
  • yellow: advisory/statement/other and considering all hazard components (hourly table, banners)

Considerations

  • For implementation should we also include color updates in hazard on a map implementation?
  • do we need to inherit NWS hex colors for this implmentation or can we use USWDS?

Acceptance Criteria

  • Users are able to quickly know if a hazard is urgent or non-urgent using visual cues.

Note that the color based definitions are a secondary indicator and do not require an alternate color-blind safe supplement.

@sarahmhgov sarahmhgov added this to the MVP Milestone 3 milestone Apr 17, 2024
@colinmurphy01
Copy link
Collaborator

This feels ready for design.

Does this need to be scoped further?

@colinmurphy01 colinmurphy01 added the Iteration Minor improvement based on feedback label Apr 18, 2024
@colinmurphy01
Copy link
Collaborator

colinmurphy01 commented Apr 19, 2024

Product is aligned with moving forward with the simplified solution: red: warning / orange: watch / yellow: advisory/statement/other and considering all hazard components (hourly table, banners).

@shadkeene
Copy link
Collaborator

shadkeene commented Apr 29, 2024

@partly-igor @coreypieper Do we know if this aligns with latest thinking from the hazsimp team? Would be nice to be aligned with them on this. I know several months ago, they said there were many options supported since the survey results were pretty even across the board. Let me know if I can do something on this end to help.

@colinmurphy01
Copy link
Collaborator

Updated to also consider updating colors in the hazard on a map component.

@partly-igor
Copy link
Collaborator

Updated alert colors documentation

@colinmurphy01
Copy link
Collaborator

colinmurphy01 commented May 10, 2024

Can you confirm that next steps are:

  1. Share with HazSimp team, no red flags (elbow elbow) then
  2. Ready for eng

@partly-igor
Copy link
Collaborator

😆 yes that sounds right

@colinmurphy01
Copy link
Collaborator

@igorkorenfeld in order to get them approved can you provide links to the examples in context. I think that helps more.

@partly-igor
Copy link
Collaborator

Sure thing:

Mobile

Desktop

@colinmurphy01
Copy link
Collaborator

@shadkeene @coreypieper do either of you want to send the colors and preview environments over to the HazSimp team for review and objections. It may require some context, so a short meeting may be necessary.

@shadkeene
Copy link
Collaborator

Yes @colinmurphy01 @coreypieper , will do that today.

@shadkeene
Copy link
Collaborator

AFS supports the 3 color red/yellow/gray as prototype. Waiting to hear from another AFS person (will probably hear next week) but going to close this for now b/c we have communicated/coordinated this with AFS.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design Iteration Minor improvement based on feedback
Projects
Development

No branches or pull requests

5 participants