Colour Watch's fastext label, not just its swatch
All checks were successful
Deploy / deploy (push) Successful in 22s

Swatch-only blue read as unfinished next to the other five fully-
coloured entries. The word now carries the colour like every other
key, same currentColor mechanism as the rest — accepting blue's
~2.4:1 contrast on black as a known, deliberate exception to the
4.5:1 bar everything else here clears.
This commit is contained in:
Barely Removable 2026-08-30 09:27:39 -07:00
parent 5dd49c505c
commit 9fba4f210e
3 changed files with 35 additions and 39 deletions

View file

@ -560,11 +560,10 @@ a.tt-row:focus-visible .tt-row-sub { color: var(--tt-black); }
.fastext .k-yellow { color: var(--voice); }
.fastext .k-cyan { color: var(--live); }
.fastext .k-magenta { color: var(--pending); }
/* Blue fails contrast as body text on black, so it marks the swatch
only — the button cap's colour, not the printed label — while the
row's own text stays legible ink. */
.fastext .k-blue::before { background: var(--field); }
.fastext .k-blue:hover, .fastext .k-blue:focus-visible { background: var(--field); }
/* Pure blue on black is ~2.4:1 contrast — well under the 4.5:1 every
other body text in this app clears — but the word carries the
colour like every other key here, at the visitor's request. */
.fastext .k-blue { color: var(--field); }
/* The one other legal way to get a distinct mark out of eight colours
without a ninth: an ordered dither, same mechanism as --dither-mid,
in place of a flat swatch. */