@import url('_tokens.css'); :root { --ms-accent-warm: #f6e9eb; /* The submit button while a page is in flight. A LIGHTER maroon, not `opacity`: opacity composites the whole control toward the page behind it, moving the white label with the fill and costing contrast on the one word a trainee on a slow connection is trying to read. Measured against #ffffff: idle #8e1f2d is 8.81:1, this is 6.00:1, and #b0616b - only slightly further - is 4.40:1 and FAILS AA. The margin is the point; do not nudge this lighter without re-measuring. */ --ms-primary-busy: #a34450; /* Deliberate blue-grey question ink (a confirmed reading-comfort decision, KEPT at s85). Distinct from the brand ink --ms-text-main (#221c19) — do not harmonise it away. Named here so the question text + number share one source instead of duplicating the colour literal per selector. */ --ms-question-ink: lab(35.5623% 1.74978 -15.4316); /* Status-pill ink. Both were darkened at s589 after measuring the RENDERED list page: each pill lays its text over a translucent wash of its own hue, so the real contrast is the token against the COMPOSITED wash, not against the surface. #64748b and #b45309 read fine token-to-token and failed WCAG AA in place (3.79:1 and 3.93:1 at the 0.12 wash over --ms-background). ops/lint/theme_a11y.py::status_pill_contrast_errors pins this; it checks both --ms-surface and --ms-background because the darker one fails first. */ --ms-status-upcoming: #55606f; --ms-status-closing-soon: #9c4507; --ms-radius-card-compact: 12px; --ms-shadow-gate: 0 6px 24px -4px rgba(24, 24, 27, 0.22); /* AA-compliant text shade of the accent-warning family. The shared --ms-accent-warning (#9a6a16) on --ms-accent-warning-soft is 4.31:1, under the 4.5:1 that 15px copy needs — and it shipped on both the validation toast a blocked trainee reads and the session-expiry panel. This clears at 5.20:1 on the same fill. NOT invented here: the facilitator portal reached the same finding first and pinned this exact value at ops/upload/static/upload.css:14-19, deliberately keeping it out of the byte-identical shared _tokens.css so the participant theme stayed untouched. Held theme-side for the same reason in reverse — promoting it to _tokens.css would mirror into the upload copy and cost a ?v= bump on four gate templates for a token neither the gate nor the portal consumes. Two scopes, one measured value; if a third consumer appears, promote it. Pinned by opaque_token_pair_contrast_errors in ops/lint/theme_a11y.py. */ --ms-accent-warning-strong: #8a5e12; /* The scrim over a sealed question page. Translucent so the blurred page reads as a page rather than as flat paint; see .is-ms-session-expired for why the blur alone is not the control. */ --ms-scrim: rgba(248, 244, 241, 0.72); --ms-shadow-soft: 0 2px 12px -2px rgba(24, 24, 27, 0.1); } body { font-family: "Manrope", "Segoe UI", sans-serif; color: var(--ms-text-body); background: var(--ms-background); } /* LimeSurvey core injects an inline