-
Notifications
You must be signed in to change notification settings - Fork 65
[DATA VIZ] colors #405
Comments
Hey @amycesal can you send us the Hex codes when you are ready/get a chance so we can test them out in the wild? A list of hex codes would be fine (doesn't need to be put in the formatted document). Thanks! Very excited to try them out! |
HEX: #00A35B HEX: #0C568C HEX: #DFE6DD HEX: #E2BFCB |
I created a file for Tableau to use these color palettes. Do they have a specific order they should go in? Right now they are in whatever order was listed. |
Requesting an update on this from @amycesal and @designlanguage. Thanks! – The Eye 55 Grooming Crew |
After talking with @ajbush about Consumer credit trends charts some issues we have using the illustration color scheme are:
|
Maybe let's table map colors for now. And work within our current color palette and see where that gets us. @nataliafitzgerald @ajbush @designlanguage @ekellett what issues do you see with this? |
@amycesal Also, for the cool family did you try using brand green for the emphasis color? If yes did you run into issues with it? |
I think those options are looking good @amycesal! My eye can discern the different levels of color but I've been searching with no luck for color contrast requirements for data viz in general and specifically line graphs. For Consumer Credit Trends we eventually tried to meet WCAG 2.0 contrast levels for normal type this is what led us to explore varied line thicknesses to keep the contrast high. Some of the current tints you are using wouldn't pass those seemingly aggressive guidelines. I know we'll need to use direct labeling whenever possible and be smart about how we apply the colors but I'm still wondering what rules you've seen around contrast for data viz @amycesal? |
Black and white viewSo, you generally want all of the lights to have the same color density/weight and all of the darks to have the same color density/weight to not give emphasis for one thing over another unintentionally. This is where pattens, different strokes, and direct labeling come into play, so that you don't use only color to identify the bar/line/wedge. However, we don't want well sighted users to confuse the blues, and think they might be the same thing or related if they are not. brand green@nataliafitzgerald As far as using the mid-dark instead of the brand green, I was looking to have all of the "dark" colors have the same density. and also be 508 compliant to have white text on them. Which is why I chose the mid-dark over the true brand. other guidelines@ajbush it's hard, because there aren't a ton of guidelines for color for data viz. there's a lot of theme generators like http://colorbrewer2.org/ and https://www.vis4.net/blog/posts/avoid-equidistant-hsv-colors/ but they mainly focus on contrast/brightness/density between the colors themselves and not contrast with the background. So I think my questions are:
|
First pass at these. NONE of the hex codes/actual numbers are correct.
I think I'm mostly worried about sequential colors at the moment. Since they are mostly used for maps, it probably doesn't make sense to use a blue OR a green. Thoughts?
@designlanguage is going to check for 508-ness and alignment to current colors.
@marteki @ekellett @bfongdata @piccocesar want to kick the tires and let me know what fails?
The text was updated successfully, but these errors were encountered: