/*
 Theme Name:   Picostrap5 Life Transit Child
 Theme URI:    http://life-transit.local
 Description:  Guided Support "You're Not Alone" credibility site — warm, empathetic, supportive.
 Author:       Artificial Automation House
 Template:     picostrap5
 Version:      1.0.0
 Text Domain:  picostrap5-life-transit-child
*/

/* LiveCanvas header/footer wrapper resets */
#lc-header { margin: 0 !important; padding: 0 !important; }
#lc-footer { margin: 0 !important; }
body.lc-custom-header { padding-top: 0 !important; margin-top: 0 !important; }

/* ---------------------------------------------------------------------------
   The full site design lives in site-design.css, enqueued AFTER bundle.css
   (dep on 'picostrap-styles') so its component overrides (.btn-main, .navbar,
   .site-header) beat Bootstrap. style.css loads BEFORE bundle.css, so design
   rules must NOT go here — they'd be overridden by Bootstrap. Restored 2026-07-15
   from orphaned Customizer custom_css (theme switch left it keyed to the old theme).
   --------------------------------------------------------------------------- */


/* ── Forminator submit button — recolor with the palette ──────────────────
   Forminator ships its own button styling (stock blue #097BAA) which ignores
   the theme and matches no palette. Track --bs-primary so the submit button
   recolors with the customizer, exactly as probate-credibility already does. */
.forminator-ui.forminator-custom-form button.forminator-button-submit,
.forminator-ui .forminator-button.forminator-button-submit,
button.forminator-button-submit,
.forminator-button-submit { background-color: var(--bs-primary) !important; color: #fff !important; border-color: var(--bs-primary) !important; }
html body button.forminator-button-submit span,
html body .forminator-button.forminator-button-submit span { color: #fff !important; }


/* Gold .btn-warning CTAs — recolor with the palette accent, dark label (Bootstrap
   default) for WCAG-AA. Overrides the .text-white utility the markup forces on them. */
.btn-warning {
    --bs-btn-bg: var(--bs-warning) !important;
    --bs-btn-border-color: var(--bs-warning) !important;
    --bs-btn-hover-bg: color-mix(in srgb, var(--bs-warning) 88%, #000) !important;
    --bs-btn-hover-border-color: color-mix(in srgb, var(--bs-warning) 88%, #000) !important;
    --bs-btn-active-bg: color-mix(in srgb, var(--bs-warning) 82%, #000) !important;
    --bs-btn-active-border-color: color-mix(in srgb, var(--bs-warning) 82%, #000) !important;
}
html body .btn.btn-warning,
html body a.btn.btn-warning,
html body button.btn.btn-warning,
html body .btn.btn-warning span { color: #212529 !important; }

/* ==========================================================================
   Interaction-state AA (2026-09-16, gates/interaction-state-audit.cjs)

   Nav links and the brand hovered to the brand ACCENT while sitting on the dark
   navbar — 2.83:1 on the life-transit palette, 3.63:1 on the general one. Both
   fail AA and both are genuinely hard to read.

   Resting colours are untouched (a light slate on the bar, which passes); only
   :hover / :focus move, to white. That is the conventional affordance for a dark
   bar and it is what the divorce child theme already does for the same reason.
   The accent hover is kept everywhere else — this is scoped to the navbar.

   Declared here with `html body` specificity because these components are styled
   from a mu-plugin whose stylesheet the CSSOM would not expose, so the source
   rule could not be edited directly.
   ========================================================================== */
html body .navbar .nav-link:hover,
html body .navbar .nav-link:focus,
html body .navbar .nav-link:focus-visible,
html body .navbar .navbar-brand:hover,
html body .navbar .navbar-brand:focus,
html body .navbar .navbar-brand:focus-visible,
html body nav .nav-link:hover,
html body nav .nav-link:focus,
html body nav .navbar-brand:hover,
html body nav .navbar-brand:focus { color: #fff !important; }

/* Contact links in the dark top-bar and footer hovered to the mid teal accent —
   3.18:1 on #17282E (gates/interaction-state-audit.cjs, 2026-09-16). They are
   classless <a> inside .top-bar / .lt-footer, so a generic a:hover was reaching
   them. Lift the accent 20% toward white on those two dark surfaces only: 4.61:1,
   NOTE the accent is --bs-warning here, NOT --bs-primary: this theme's rendered
   warning is the teal #2e7f71 while its primary is a dark slate #26454f — the
   'source palettes lie' trap recorded in atl-theme-customizer-mechanism.md.
   still recognisably the teal rather than flattening to plain white. Resting
   colour (near-white) is untouched; hover/focus only.

   Applied to both copies of this theme even though only the life-transit build
   currently renders that top-bar — the copies have drifted, and keeping the rule
   in both stops the defect reappearing when content syncs. */
/* Buttons are excluded: they carry their OWN background, so recolouring their
   label to a link colour made a footer CTA worse (2.54:1). This rule is for bare
   text links on the dark surface only. */
/* Target the TEXT containers, not every link on the dark surface. A blanket
   `.lt-footer a` also hit a classless footer CTA that carries its own background
   (rgb(158,78,42) on the general build), recolouring its label to a link colour
   and taking it to 2.11:1 — worse than before. A `:not([class*="btn"])` guard is
   not enough because that CTA has no class at all. */
html body .top-bar .lt-topbar-item a:hover,
html body .top-bar .lt-topbar-item a:focus,
html body .top-bar .lt-topbar-item a:focus-visible,
html body .lt-footer .lt-footer-nap a:hover,
html body .lt-footer .lt-footer-nap a:focus,
html body .lt-footer .lt-footer-nap a:focus-visible,
html body .lt-footer .lt-footer-links a:hover,
html body .lt-footer .lt-footer-links a:focus,
html body .lt-footer .lt-footer-links a:focus-visible { color: color-mix(in srgb, var(--bs-warning) 80%, #fff) !important; }