/* ============================================================================= AIToolsay — Dark-mode button contrast corrections ----------------------------------------------------------------------------- Loaded last in from layouts/public.blade.php, on every public page. ── WHY THIS FILE EXISTS ─────────────────────────────────────────────────── A DOM-wide contrast audit in dark mode (11 pages) found 24 distinct button classes whose label failed WCAG AA against their own fill. They were not 24 separate mistakes — they were two, repeated across every kit on the site: A. `#60A4F5` USED AS A FILL. That colour is --aits-blue-light: an INK token. Dark mode substitutes it for the brand blue so that *text and glyphs* stay legible on a dark card. Several kits then paint BUTTONS with it and put white text on top → **2.58:1**, and 1.67:1 where a lighter stop exists. This is the "button text is not visible in dark mode" report. B. `#3680ED` (brand blue) UNDER WHITE TEXT → **3.84:1**. Fails AA (4.5:1) by a little; legible but not compliant. Corrected here in DARK ONLY, because in light mode the same fill is the site's primary-button look on every page and changing it there is a design decision, not a bug fix. See the note at the end of this file. ── THE REPLACEMENT RAMP IS MEASURED ─────────────────────────────────────── White-on-fill contrast: #2E6FD0 4.88:1 · #2762C2 5.81:1 · #1B4E9E 7.98:1 so the worst point of the gradient clears AA for normal-size labels, and clears the 3:1 non-text minimum for white glyphs sitting on the same fill. Anything lighter than ~#2E6FD0 under white text fails — compute before changing. Brand blue #3680ED is fine for ink, borders and tints; it must never sit under white text. ── WHY !important ───────────────────────────────────────────────────────── These classes live in ~10 independent kits, several of which ship their CSS in an inline