@webority/theme 0.98.0 → 0.99.0

package/README.md

@@ -31,34 +31,6 @@ load-bearing**:
 Importing part of the core chain is a bug: skipping `wui-aliases` leaves every
 `--color-*` reference unresolved.
 
-### The primary as text: `--wui-primary-ink`
-
-A brand primary is chosen as a fill. A light one fails WCAG AA as text: an orange such as `#E8501E`
-measures 3.75:1 on white. So the theme keeps two colours:
-
-- `--wui-primary` (`--color-primary`): fills, borders, focus rings, the selected-day disc.
-- `--wui-primary-ink` (`--color-primary-ink`): every link, tab label, page number, selected option,
-  avatar initial and primary-coloured icon. It is `$primary` darkened in 2% steps until it clears
-  4.5:1 on white, the page, the muted and elevated fills and the brand's own soft tint, so it equals
-  `$primary` when the primary already clears AA. Orange `#E8501E` gets `#BA4018` (5.48:1 on white).
-- `--wui-primary-text` (`--color-primary-text`): the label ON a solid primary fill, white when white
-- `--color-primary-hover-text`: the label colour on a pressed or hovered primary button (white in light mode, near-black in dark mode).
-  clears 4.5:1 on the primary, near-black otherwise.
-
-All three derive from `$primary` at compile time, so setting `$primary` (or `wui-brand-primary`) is
-enough. A product can set `$wui-primary-ink` / `$wui-primary-text` before the theme's variables, or
-`--wui-primary-ink` / `--wui-primary-text` at runtime. A brand layer that re-points `--wui-primary` at
-runtime must set `--wui-primary-ink` and `--wui-primary-text` beside it.
-
-Dark mode uses one colour, `--wui-dark-primary`, for primary text, rings, focus borders and the fill
-under its near-black label. It is `$primary` mixed with white in 2% steps until it clears 4.5:1 on
-every dark surface, on its own avatar tint, on the brand's soft tint and under that label, so
-`wui-brand-primary` carries the brand into dark mode (a royal blue `#2F50E4` lifts to about `#8FA1F0`). Never
-set it to the light brand fill: a runtime `--wui-dark-primary` must clear the same floors.
-
-`check-contrast` proves both derivations for an orange, an amber, a sky and a royal blue test brand
-and fails any theme rule that colours text with `--color-primary`.
-
 ### Country flags are opt-in
 
 The 245 `.wui-flag-*` rules are about 187 KB raw (38 KB Brotli) of inlined SVG, so
@@ -263,9 +235,9 @@ Anti-over-correction checklist. When thinning the package (e.g. marketing extrac
 
 ### Tokens & system (`scss/_variables`, `_tokens`, `_wui-aliases`)
 
-- Theme colors + `wui-brand-primary`; body/text/surface/border ramps (incl. AA tertiary)
+- Theme colors + `wui-brand-primary`; body/text/surface/border ramps
 - Radius ladder that differs from Bootstrap; spacer map extensions (6+)
-- Status ramps: fills **and** `-text` / danger-strong for AA
+- Status ramps: fills **and** `-text` / danger-strong
 - Control heights (`--wui-control-height*`: sm 32, md 36, lg 44; md is 44 on phone-width and touch screens) and one disabled opacity (`--wui-disabled-opacity`); flat in-page elevation; overlay shadows only
 - Z-index scale (`--wui-z-*`); dark-mode `--bs-*` / RGB bridges
 - Focus: no input glow (`$input-focus-box-shadow: none`); fields keep a soft brand border and also draw the shared keyboard ring
@@ -310,7 +282,6 @@ Keep shipping all of these; classify for **when to use**, not for removal:
 `corner-shape: squircle` is applied on many controls (buttons, fields, chips, menus, shell) as **progressive enhancement**:
 
 - Supporting browsers get slightly smoother corners; others keep plain `border-radius`.
-- Not a cross-browser design contract; not a WCAG requirement.
 - Missing squircle is **not** a bug.
 
 **Policy:** keep on shared control surfaces for consistent geometry; do **not** strip globally. Optional `.rounded-squircle` remains an opt-in utility. Products that want pure arcs only override locally — do not fork App*.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webority/theme",
-  "version": "0.98.0",
+  "version": "0.99.0",
   "description": "Webority shared design system — Bootstrap 5.3 SCSS overrides, --wui-* tokens, and shared component CSS. The single source of brand chrome for React portals and Razor sites.",
   "license": "SEE LICENSE IN LICENSE",
   "publishConfig": {

package/scss/_tokens.scss

@@ -61,8 +61,7 @@
     /// meaning: Resting fill of every input-like control, such as fields, selects and textareas.
     --wui-field-bg: #F9FBFC;
     // Resting and hover border of every input-like control: a soft edge a step darker than
-    // --wui-border-light, and the --wui-text-5 hover. They sit under WCAG 1.4.11's 3:1 by
-    // design choice; check-contrast reports them as FAIL without failing the gate.
+    // --wui-border-light, and the --wui-text-5 hover.
     /// meaning: Resting border of every input-like control.
     --wui-field-border: #DFE2EA;
     /// meaning: Hover border of every input-like control.

package/scss/wui/_media.scss

@@ -523,9 +523,6 @@
 }
 .attach-item-remove:hover {
     border-color: var(--color-danger);
-    // The glyph is graphical (icon-only button, 3:1) so the brand hue would technically pass
-    // at 3.36:1 — but "tint background ⇒ -text foreground" is worth keeping exceptionless, so
-    // check-contrast can enforce it by inspection instead of case-by-case judgement.
     color: var(--color-danger-text);
     background: var(--color-danger-soft);
 }