↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Colors, the Programming Way

The article argues that RGB is a poor model for choosing related colors, because it reflects display hardware more than how people perceive color. It suggests working in terms of hue, saturation, and lightness, then using geometry on the color wheel to build adjacent, complementary, triadic, and tetradic schemes.

It also recommends checking contrast with WCAG-style luminance calculations and testing schemes against several kinds of color blindness by applying matrices to each color channel. The same approach can be automated, but the author still recommends visual inspection and, in existing work, following a company’s branding guidelines.

Reading notes
#

  • RGB is useful for displays, but it makes relationships between colors hard to see.
  • Hue, saturation, and lightness give a more intuitive way to describe colors.
  • Adjacent, complementary, triadic, and tetradic schemes come from angles on the hue circle.
  • A closest named color can be found by comparing an input color against a list of named colors in HSL or HSV space.
  • Contrast can be calculated from luminance values and used to check whether colors are readable together.
  • Color schemes should also be tested against multiple kinds of color blindness.
  • The process can be automated, but the result still needs visual inspection.
  • For existing company work, branding guidelines should take priority over new color choices.