@apliteni/apliteni-ui 0.9.1 → 0.11.1

package/src/tokens/tokens.css

@@ -105,8 +105,15 @@
   color-scheme: dark;
 
   --purple: #6a2dcc;
-  --purple-light: #9b5dff;
-  --purple-mid: #b479ff;
+  /* The ramp moves up one step so --accent is --purple-light again, which is
+     the shape light Nebula and light Ocean already ship and which dark Nebula
+     held until #157 lifted the accent onto the old --purple-mid. Left alone,
+     the two tokens would resolve to one colour and the ramp would carry a
+     duplicate step. #bd8cff is the value docs/adr/0006 reasons about and
+     rejects as the accent; it becomes the ramp's top step instead. Light
+     Nebula's ramp does not move. See issue #157. */
+  --purple-light: #b479ff;
+  --purple-mid: #bd8cff;
   --cyan: #20dcf5;
   --green: #98ff8f;
   /* Lighter than it looks like it should be, and deliberately so: --pink is read
@@ -135,8 +142,15 @@
   --dim: #c6c2d6;
   --muted: #948fa8;
 
-  --accent: #9b5dff;
-  --accent-strong: #7c3aed; /* button bg — white text clears WCAG AA (~6.5:1) */
+  /* Lifted from #9b5dff, which cleared the flat surfaces and failed on its own
+     wash over a card. This value was already in the ramp as --purple-mid, so no
+     new colour entered it; the ramp then moved up a step above so --accent is
+     --purple-light, which is how every other Nebula and Ocean cell is written.
+     --glow-purple and --ring follow it down the file. Held by
+     stories/accent-contrast.test.js. See issue #157.
+     why: docs/adr/0006-the-accent-is-measured-against-its-own-wash.md */
+  --accent: #b479ff;
+  --accent-strong: #7c3aed; /* button bg — white text clears WCAG AA at 5.70:1 */
   --accent-contrast: #ffffff;
   --ink: #e9e7f0;
 
@@ -157,7 +171,11 @@
   --danger-contrast: var(--signal-contrast);
 
   --glow-green: rgba(152, 255, 143, 0.16);
-  --glow-purple: rgba(155, 93, 255, 0.18);
+  /* Dropped from 0.18: the wash, not the surface beneath it, is what put --accent
+     under AA — it lifts the ground toward the ink faster than the ink lifts off
+     it. Re-tinted from the new --accent, which signal-contrast.test.js requires.
+     See issue #157. */
+  --glow-purple: rgba(180, 121, 255, 0.12);
   --glow-cyan: rgba(32, 220, 245, 0.14);
   --glow-pink: rgba(233, 124, 165, 0.16);
 
@@ -196,7 +214,12 @@
   /* Resting elevation for a card. Dark cards are borderless — the surface does
      the grouping on its own — so they cast nothing. */
   --shadow-card: none;
-  --ring: 0 0 0 3px rgba(155, 93, 255, 0.35);
+  /* The accent's own rgb at a fixed alpha, so it moves whenever --accent moves —
+     otherwise a token points at a colour the accent no longer is. At this alpha
+     the band sits under the 3:1 WCAG 1.4.11 asks of a focus indicator, before
+     this change and after it; nothing here closes that. See issue #157 and the
+     ADR's closing section. */
+  --ring: 0 0 0 3px rgba(180, 121, 255, 0.35);
 
   /* The ink a cast shadow is made of, and the specular white that reads as
      gloss on a raised surface. Effects mix these instead of writing rgba(). */
@@ -206,8 +229,12 @@
   /* Backdrop that dims the page behind an overlay (drawer, modal, composer). */
   --scrim: rgba(0, 0, 0, 0.58);
 
-  /* Accent gradient stops (hero headline, marketing) — overridden per sub-theme. */
-  --grad-from: var(--purple-light);
+  /* Accent gradient stops (hero headline, marketing) — overridden per sub-theme.
+     --grad-from is pinned to the literal rather than tracking --purple-light,
+     which #157 moved up a step: following it would lighten the hero gradient's
+     first stop, a visible change nobody asked for. Every --grad-from in
+     src/tokens/accents.css is already written as a literal for the same reason. */
+  --grad-from: #9b5dff;
   --grad-to: var(--cyan);
 }