-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Replace qualitative color palette in visualizations #13327
Comments
@snide I'm using this vis color palette on a stacked bar chart but, at least for a normal color viewer (for color blind seems work correctly), the contrast seems a bit too much high between green blue and red, especially between blue/red one, and it's quite eye disturbing. |
We have pretty strict guidelines on accessibility and contrast. It's difficult coming up with a set of ten colors that work against those requirements and that somewhat match our brand and that work on a dark background. Generally they tend to come out hot. |
I perfectly understand the difficulties there 👍 |
Feel free to adjust the order as you think works best. The blue should likely be first though. |
This issue has a closed PR associated with it. Is there anything left to do for this? (Not for addressing color blindness issues with visualizations more broadly, but specifically for replacing the old palette with the newer palette.) |
We are working on this right now - it's planned for 7.12 @stratoula do we need to keep this issue? I guess there's another one tracking this. |
As Joe said, we are working on it. We plan to migrate to the new palette for the xy axis and pie charts for 7.12 and eventually to the other charts. No need to keep this 🙂 |
This is an imperfect, but much better colorblind-safe palette that @Adrian-J and I like for chart usage.
Beyond these 10 colors, when more are needed we should either do one of two things:
The larger the palette becomes, the more impossible it becomes to scale against colorblindness. I'll leave it to you which system you think is best.
The text was updated successfully, but these errors were encountered: