Many of the colors for node types (all can be seen at https://ameliorate.app/examples/ontology) are too dark to easily read the node type's text (or the node's text, if using the fill nodes with color options). They also vary in levels of saturation.
Solution you'd like
Using the new oklch color notation, it should be much easier to pick new colors for each node type such that:
they have consistent Lightness and Chroma (saturation)
the Lightness has sufficient contrast to easily read black text
Chroma can be increased to highlight the main two node types (problem & solution)
for #68, Lightness/Chroma can be adjusted to create dark-mode colors for the same hues
Alternatives you've considered
No response
Additional context
This blog post has a nice demo where you can adjust oklch and see if the color passes APCA/WCAG 2.1 on white/black text. It seems like 75 Lightness and 0.12 Chroma enable all Hue values to pass on black text, and 0.6 Lightness and 0.10 Chrome enable all Hue values to pass on white text (at least for AA).
Looks like stylelint is intended for actual CSS files, and I had troubles setting it up for a ts file. Could spend more effort but it's not a big deal.
Describe your issue
Many of the colors for node types (all can be seen at https://ameliorate.app/examples/ontology) are too dark to easily read the node type's text (or the node's text, if using the
fill nodes with color
options). They also vary in levels of saturation.Solution you'd like
Using the new oklch color notation, it should be much easier to pick new colors for each node type such that:
Alternatives you've considered
No response
Additional context
Technical ideas and questions