/* meyerinternational-static — the only stylesheet written for this clone.
 *
 * Everything else under /assets/ is the original Salient theme CSS, copied
 * verbatim. This file exists to do one job: put back the behaviour the theme
 * used to get from JavaScript, using CSS only, without changing how anything
 * looks. Nothing here restyles the site.
 *
 * Sections:
 *   1. Screen-reader utility
 *   2. Heading-level compatibility
 *   3. Keyboard focus
 *   4. Primary nav dropdowns   (was: superfish .sfHover)
 *   5. Mobile off-canvas menu  (was: JS toggle -> now :target)
 *   6. Search overlay
 *   7. Request form
 */


/* ---------------------------------------------------------------- 1. sr-only
 * For headings that exist only so assistive tech has a document outline.
 * Must never affect layout. */
.mus-sr-only {
  position: absolute !important;
  width: 1px; height: 1px;
  padding: 0; margin: -1px;
  overflow: hidden;
  clip: rect(0 0 0 0);
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}


/* ------------------------------------------------- 2. Heading-level compat
 * Some pages had no <h1> at all; their visual title was an <h2>. Promoting
 * the tag alone would change the type, because this theme styles h1 as
 * Work Sans 60/74 and h2 as Cabin 26/40. These rules give the promoted
 * element exactly the h2 cascade it had before, at every breakpoint the
 * theme defines.
 *
 * Colour is deliberately NOT set here. These selectors are element+class, the
 * same weight as the `.light h1` rule that turns headings white inside a
 * dark-backgrounded section, and this file loads later -- so setting a colour
 * here won that tie and forced every brand hero headline to near-black on its
 * own dark hero. Left unset, a heading takes the dark default on an ordinary
 * section and white inside a .light one, which is what the untouched heading
 * did. */
h1.mus-h1-visual-h2 {
  font-family: Cabin, "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-size: 26px;
  line-height: 40px;
  font-weight: 700;
}
@media only screen and (max-width: 1300px) and (min-width: 1000px) {
  h1.mus-h1-visual-h2 { font-size: 22.1px; line-height: 34px; }
}
@media only screen and (max-width: 999px) and (min-width: 690px) {
  h1.mus-h1-visual-h2 { font-size: 20.8px; line-height: 32px; }
}
@media only screen and (max-width: 690px) {
  h1.mus-h1-visual-h2 { font-size: 19.5px; line-height: 30px; }
}


/* -------------------------------------------------------- 3. Keyboard focus
 * The theme suppressed focus rings in several places and relied on JS for the
 * rest, so keyboard users had almost nothing to follow.
 *
 * The ring is two-tone on purpose. This site puts text on white, on Meyer
 * blue and on near-black, and no single colour clears 3:1 against all three
 * (#005daa is 6.67:1 on white but only 2.97:1 on #000b14; #ff643a is the
 * reverse). A blue outline with a white inner ring means one of the two is
 * always visible, whatever it lands on. Both colours are already in the
 * palette -- nothing existing is recoloured. */
a:focus-visible,
button:focus-visible,
input:focus-visible,
select:focus-visible,
textarea:focus-visible,
summary:focus-visible,
[tabindex]:focus-visible {
  outline: 3px solid #005daa !important;
  outline-offset: 2px !important;
  box-shadow: 0 0 0 2px #ffffff !important;
}

/* The theme ships a skip link but parks it off-screen with no focus state. */
.nectar-skip-to-content {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 100000;
}
.nectar-skip-to-content:focus {
  left: 12px;
  top: 12px;
  width: auto;
  height: auto;
  padding: 12px 20px;
  background: #ffffff;
  color: #005daa;
  font-family: Cabin, "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-weight: 700;
  text-decoration: underline;
  box-shadow: 0 2px 12px rgba(0, 0, 0, 0.35);
}


/* ------------------------------------------------------ 4. Nav dropdowns
 * Superfish used to add .sfHover on mouseover. These mirror the theme's own
 * .sfHover rules onto :hover and :focus-within, so the dropdowns open for
 * both mouse and keyboard. Declarations are copied from style.css. */
#top nav > ul > li:hover > ul,
#top nav > ul > li:focus-within > ul,
#header-secondary-outer .sf-menu > li:hover > ul,
#header-secondary-outer .sf-menu > li:focus-within > ul,
.sf-menu > li:hover > ul,
.sf-menu > li:focus-within > ul {
  opacity: 1;
  pointer-events: auto;
  transform: none;
  -webkit-transform: none;
}

#top nav > ul > li:hover > ul > li,
#top nav > ul > li:focus-within > ul > li,
#header-secondary-outer .sf-menu > li:hover > ul > li,
#header-secondary-outer .sf-menu > li:focus-within > ul > li,
.sf-menu > li:hover > ul > li,
.sf-menu > li:focus-within > ul > li {
  opacity: 1;
  -webkit-transform: translate3d(0, 0, 0);
  transform: translate3d(0, 0, 0);
}

/* third level */
.sf-menu ul li:hover > ul,
.sf-menu ul li:focus-within > ul {
  -webkit-transform: translate3d(0, 0, 0);
  transform: translate3d(0, 0, 0);
  opacity: 1;
  pointer-events: auto;
}


/* ------------------------------------------- 5. Mobile off-canvas menu
 * The hamburger was already an anchor, so the panel opens with :target and
 * closes with a link back to #top. Every declaration below is one the theme
 * applied itself once its JS added .open / .menuopen; the selectors are
 * prefixed with `body` purely to outrank the theme's own rules, which carry
 * the same specificity and would otherwise win or tie unpredictably. */
body #slide-out-widget-area.slide-out-from-right-hover:target {
  -webkit-transform: translate3d(0, 0, 0);
  -ms-transform: translate3d(0, 0, 0);
  transform: translate3d(0, 0, 0);
}
body #slide-out-widget-area.slide-out-from-right-hover:target .inner,
body #slide-out-widget-area.slide-out-from-right-hover:target .bottom-meta-wrap {
  opacity: 1;
  -webkit-transform: translateX(0);
  transform: translateX(0);
}

/* The panel's markup contains .off-canvas-menu-container.mobile-only, which
 * the theme hides because its JS rebuilds the same links as .menuwrapper.
 * That rebuild never happens now, so the panel would slide open empty. */
body #slide-out-widget-area.slide-out-from-right-hover[data-dropdown-func="separate-dropdown-parent-link"] .off-canvas-menu-container.mobile-only,
body #slide-out-widget-area[class*="slide-out-from-right"] .off-canvas-menu-container.mobile-only {
  display: block;
}
body #slide-out-widget-area:target .off-canvas-menu-container .menu,
body #slide-out-widget-area:target .menuwrapper .menu {
  opacity: 1;
  pointer-events: auto;
  -webkit-transform: translateY(0);
  transform: translateY(0);
}
body #slide-out-widget-area:target .off-canvas-menu-container .menu li {
  opacity: 1;
}

/* Without JS the panel can't be walked one level at a time, so show the whole
 * tree at once rather than losing the brand links altogether. */
body.material #slide-out-widget-area[class*="slide-out-from-right"][data-dropdown-func]:target .off-canvas-menu-container li ul.sub-menu,
body #slide-out-widget-area[class*="slide-out-from-right"][data-dropdown-func]:target .menuwrapper li ul.sub-menu {
  display: block;
  max-height: none;
  padding-left: 20px;
  padding-top: 4px;
  padding-bottom: 4px;
  opacity: 1;
  overflow: visible;
}
body.material #slide-out-widget-area[class*="slide-out-from-right"][data-dropdown-func]:target .off-canvas-menu-container .menu li {
  display: block;
  opacity: 1;
}
body #slide-out-widget-area:target .ocm-dropdown-arrow {
  display: none;
}

/* Long menus must scroll rather than overflow the viewport. */
body #slide-out-widget-area .inner {
  max-height: 100vh;
  overflow-y: auto;
}

/* The close control is hidden for this skin because JS used to handle it. */
body[data-full-width-header="false"] #slide-out-widget-area.slide-out-from-right-hover:target .slide_out_area_close,
body #slide-out-widget-area:target .mus-ocm-close {
  display: block;
}


/* ---------------------------------------------------------- 6. Search
 * There is no search backend on the static site and no JS to open the
 * overlay, so it must not be reachable by keyboard — otherwise it is an
 * invisible tab stop.
 *
 * Three surfaces, all hidden for the same reason. #search-btn is the
 * magnifying glass in the header, which opened the overlay below it, and
 * .widget_search is the sidebar box on /news/ and /newsroom/. Left visible
 * they take a query and silently drop it: there is nothing to search, and
 * form-action 'none' in _headers blocks the submit anyway. Restore all three
 * together if a search backend ever lands. */
#search-outer,
#search-btn,
#sidebar .widget_search {
  display: none !important;
}


/* -------------------------------------------------------------- 7. Request form
 * Replaces the Formidable form on /request-form/. Styled to match the
 * surrounding page, not to introduce a new look. */
.mus-form {
  max-width: 760px;
  margin: 0 auto 40px;
  font-family: Cabin, "Helvetica Neue", Helvetica, Arial, sans-serif;
}
.mus-form fieldset {
  border: 0;
  padding: 0;
  margin: 0 0 28px;
}
.mus-form legend {
  font-family: Cabin, "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-size: 20px;
  font-weight: 700;
  color: #000b14;
  padding: 0;
  margin-bottom: 14px;
}
.mus-field {
  margin-bottom: 18px;
}
.mus-field > label,
.mus-field > .mus-label {
  display: block;
  font-weight: 700;
  color: #000b14;
  margin-bottom: 6px;
  font-size: 15px;
}
.mus-field input[type="text"],
.mus-field input[type="email"],
.mus-field input[type="tel"],
.mus-field select,
.mus-field textarea {
  width: 100%;
  padding: 11px 13px;
  border: 1px solid #6e7c87;   /* 4.29:1 on white — meets the 3:1 minimum for form borders */
  border-radius: 3px;
  background: #ffffff;
  color: #000b14;
  font-family: inherit;
  font-size: 15px;
  line-height: 1.4;
  box-sizing: border-box;
}
.mus-field textarea { min-height: 130px; resize: vertical; }
.mus-field input:focus,
.mus-field select:focus,
.mus-field textarea:focus { border-color: #005daa; }
.mus-choice { margin-bottom: 7px; font-size: 15px; color: #000b14; }
.mus-choice input { margin-right: 8px; }
.mus-required { color: #c0392b; }
.mus-hint { font-size: 14px; color: #000b14; opacity: 0.75; margin-top: 4px; }
.mus-submit {
  background: #005daa;
  color: #ffffff;
  border: 0;
  border-radius: 3px;
  padding: 14px 34px;
  font-family: inherit;
  font-size: 16px;
  font-weight: 700;
  cursor: pointer;
}
.mus-submit:hover { background: #00478a; }

/* Confirmation panel shown after submit. Hidden until the handler reveals it. */
.mus-dialog[hidden] { display: none; }
.mus-dialog {
  border: 2px solid #005daa;
  background: #ebf6ff;
  border-radius: 4px;
  padding: 26px 28px;
  margin: 0 auto 40px;
  max-width: 760px;
  font-family: Cabin, "Helvetica Neue", Helvetica, Arial, sans-serif;
  color: #000b14;
}
.mus-dialog h2 {
  margin: 0 0 10px;
  font-size: 22px;
  line-height: 1.3;
  color: #000b14;
}
.mus-dialog p { margin: 0 0 10px; font-size: 16px; line-height: 1.5; }
.mus-dialog a { color: #005daa; font-weight: 700; }


/* ------------------------------------- 8. Backgrounds the theme JS drew
 * Salient built these layers in JavaScript. The markup now carries the
 * background inline (see tools/import_pages.py); these rules give it the
 * geometry and the dark overlay the theme's own .bg-img rules provided. */
.nectar-fancy-box[data-style="parallax_hover"] .parallaxImg {
  position: relative;
}
.nectar-fancy-box[data-style="parallax_hover"] .parallaxImg-layer.mus-parallax-bg {
  position: absolute;
  top: 0; left: 0;
  width: 100%; height: 100%;
  background-size: cover;
  background-position: center;
  background-repeat: no-repeat;
  z-index: 0;
}
.nectar-fancy-box[data-style="parallax_hover"] .parallaxImg-layer.mus-parallax-bg::after {
  content: '';
  position: absolute;
  top: 0; left: 0;
  width: 100%; height: 100%;
  background-color: rgba(40, 40, 40, 1);
  opacity: 0.6;                       /* theme default for .bg-img:after */
  transition: opacity 0.45s cubic-bezier(0.25, 1, 0.2, 1);
}
.nectar-fancy-box[data-style="parallax_hover"] .parallaxImg-layer:not(.mus-parallax-bg) {
  position: relative;
  z-index: 2;
}
/* Per-box overlay strength, mirroring the theme's data-overlay-opacity rules. */
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0"]   .mus-parallax-bg::after { opacity: 0; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0.1"] .mus-parallax-bg::after { opacity: 0.1; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0.2"] .mus-parallax-bg::after { opacity: 0.2; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0.3"] .mus-parallax-bg::after { opacity: 0.3; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0.4"] .mus-parallax-bg::after { opacity: 0.4; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0.5"] .mus-parallax-bg::after { opacity: 0.5; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0.7"] .mus-parallax-bg::after { opacity: 0.7; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0.8"] .mus-parallax-bg::after { opacity: 0.8; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="0.9"] .mus-parallax-bg::after { opacity: 0.9; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity="1"]   .mus-parallax-bg::after { opacity: 1; }
/* Hover lightens the overlay, as it did before. */
.nectar-fancy-box[data-style="parallax_hover"]:hover .mus-parallax-bg::after { opacity: 0.2; }
.nectar-fancy-box[data-style="parallax_hover"][data-overlay-opacity-hover="0.1"]:hover .mus-parallax-bg::after { opacity: 0.1; }

/* ------------------------------------------------------------- 8b. Hero
 * The homepage hero, rebuilt as one component instead of two page-builder
 * rows (one desktop, one mobile) full of scaffolding that only worked with
 * the theme's JavaScript running.
 *
 * Values are the ones the original rendered at, so it looks the same:
 * 48px/1.2 title and 30px lede above 992px, 34px/1.2 and 20px below;
 * 18% vertical padding; and the same left-to-right scrim over the media. */
.hero {
  position: relative;
  width: 100vw;
  margin-left: calc(50% - 50vw);
  padding: 18% 0;
  overflow: hidden;
  color: #ffffff;
}

/* object-fit does what Salient measured the container in JavaScript to do. */
.hero__video {
  position: absolute;
  top: 0;
  left: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: center center;
  z-index: 0;
  border: 0;
  pointer-events: none;
}

.hero__scrim {
  position: absolute;
  top: 0;
  left: 0;
  width: 100%;
  height: 100%;
  z-index: 1;
  background: linear-gradient(90deg, #2d2d2d 0%, rgba(255, 255, 255, 0.001) 100%);
  opacity: 0.8;
}

.hero__inner {
  position: relative;
  z-index: 2;
  max-width: 1100px;
  margin: 0 auto;
  padding: 0 20px;
}

.hero__title {
  max-width: 66.66%;
  margin: 0 0 20px;
  /* The original marked this up as an <h2> purely so it picked up Cabin;
   * as a real <h1> it would inherit the theme's Work Sans. Same look, right
   * element. */
  font-family: Cabin, "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-weight: 700;
  font-size: 48px;
  line-height: 1.2;
  color: #ffffff;
}

.hero__lede {
  max-width: 66.66%;
  margin: 0;
  font-family: Cabin, "Helvetica Neue", Helvetica, Arial, sans-serif;
  padding-bottom: 1.2rem;
  font-size: 30px;
  line-height: 1.5;
  color: #ffffff;
}

/* Below the theme's 992px breakpoint the original swapped to a second row
 * with a still image instead of the video. Same swap, one component: the
 * video is dropped rather than downloaded and hidden. */
@media (max-width: 991px) {
  .hero {
    background-image: url(/assets/img/14326_ANO_AHC_10pc-Set_Glam_TIF.jpg);
    background-position: left top;
    background-size: cover;
    background-repeat: no-repeat;
  }
  .hero__video {
    display: none;
  }
  .hero__title {
    max-width: none;
    font-size: 34px;
  }
  .hero__lede {
    max-width: none;
    font-size: 20px;
  }
}

/* The clip autoplays and loops with no pause control, so anyone who has asked
 * for reduced motion gets the poster frame instead (WCAG 2.2.2). */
@media (prefers-reduced-motion: reduce) {
  .hero__video {
    display: none;
  }
  .hero {
    background-image: url(/assets/media/MUS-7089-website-clip_R2-1-poster.webp);
    background-position: center center;
    background-size: cover;
    background-repeat: no-repeat;
  }
}


/* ------------------------------------------------- 9. Map hotspots
 * "Our Global Presence" needs no JavaScript at all -- everything is already
 * in the markup and the theme's own CSS. Each marker carries its position as
 * inline top/left percentages, the tooltip text is real DOM, the pulse is a
 * CSS @keyframes, the plus icon is ::before/::after, and the theme already
 * opens the tooltip with `.nectar_hotspot:hover + .nttip`.
 *
 * One rule was hiding the lot: an entry animation that parks every marker at
 * opacity 0, 80px down, waiting for a class the JS added on scroll. Cancel it
 * and all 32 markers appear and work. */
.nectar_image_with_hotspots[data-animation="true"] .nectar_hotspot_wrap {
  opacity: 1;
  -webkit-transform: none;
  transform: none;
}

/* The tooltips only opened on :hover, which left keyboard users with no way
 * in. The markers are focusable now (see tools/import_pages.py), so open the
 * tooltip on focus too, and keep it above its neighbours while it is open. */
.nectar_image_with_hotspots .nectar_hotspot:focus + .nttip,
.nectar_image_with_hotspots .nectar_hotspot:focus-visible + .nttip,
.nectar_image_with_hotspots .nectar_hotspot_wrap:focus-within .nttip {
  opacity: 1;
}
.nectar_image_with_hotspots .nectar_hotspot_wrap:hover,
.nectar_image_with_hotspots .nectar_hotspot_wrap:focus-within {
  z-index: 950;
}
.nectar_image_with_hotspots .nectar_hotspot:focus + .nttip span,
.nectar_image_with_hotspots .nectar_hotspot:focus span {
  -webkit-transform: rotate(90deg);
  transform: rotate(90deg);
}


/* ------------------------------- 9a. Images inside animation wrappers
 * Salient wraps animated images as
 *   .img-with-aniamtion-wrap > .inner > .hover-wrap > .hover-wrap-inner > img
 * and parks the .hover-wrap at opacity 0 for its JS to fade in. The theme's
 * own no-JS fallback (html:not(.js)) covers `img.img-with-animation`,
 * `.col.has-animation` and `.wpb_column.has-animation` -- but NOT the
 * .hover-wrap, so the image inside it stayed invisible however visible the
 * <img> itself was. That hid 149 images across 21 pages, including the
 * Stanley Cheng portrait beside the homepage quote.
 *
 * Visible is the base state; the scroll reveals below animate from it. */
.img-with-aniamtion-wrap .hover-wrap,
.img-with-aniamtion-wrap[data-animation] .hover-wrap {
  opacity: 1;
  -webkit-transform: none;
  transform: none;
}


/* --------------------------------------- 9b. Scroll reveals, in CSS
 * Salient watched the scroll position in JavaScript and added a class when an
 * element came into view. Scroll-driven animations do the same thing natively
 * -- `animation-timeline: view()` runs an animation against the element's own
 * progress through the viewport, no observer and no script.
 *
 * Layered so it can only ever add motion, never hide anything:
 *
 *   - Everything is visible by default. These rules live inside
 *     @supports (animation-timeline: view()), so a browser without support
 *     (Safari and Firefox at the time of writing) shows the finished state
 *     and nothing is lost.
 *   - `prefers-reduced-motion: no-preference` means anyone who has asked for
 *     less movement keeps the static page.
 *   - Only above 1000px, which is where the theme itself allowed these
 *     animations; below that it forced them off with !important, and those
 *     rules are still in theme-settings.css.
 *
 * animation-fill-mode: both is what applies the "before" state, so an element
 * further down the page starts hidden and arrives as it scrolls in.
 */
@supports (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) and (min-width: 1000px) {

    @keyframes mus-fade-in        { from { opacity: 0; }
                                    to   { opacity: 1; } }
    @keyframes mus-fade-in-bottom { from { opacity: 0; transform: translateY(100px); }
                                    to   { opacity: 1; transform: none; } }
    @keyframes mus-fade-in-left   { from { opacity: 0; transform: translateX(-75px); }
                                    to   { opacity: 1; transform: none; } }
    @keyframes mus-fade-in-right  { from { opacity: 0; transform: translateX(75px); }
                                    to   { opacity: 1; transform: none; } }
    @keyframes mus-grow-in        { from { opacity: 0; transform: scale(0.75); }
                                    to   { opacity: 1; transform: none; } }

    img.img-with-animation[data-animation="fade-in"],
    .img-with-aniamtion-wrap[data-animation="fade-in"] .hover-wrap,
    .col.has-animation[data-animation="fade-in"],
    .wpb_column.has-animation[data-animation="fade-in"],
    .nectar-fancy-box.has-animation[data-animation="fade-in"],
    .wpb_animate_when_almost_visible.wpb_fadeInUp {
      animation: mus-fade-in 1s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 5% cover 22%;
    }

    img.img-with-animation[data-animation="fade-in-from-bottom"],
    .img-with-aniamtion-wrap[data-animation="fade-in-from-bottom"] .hover-wrap,
    .col.has-animation[data-animation="fade-in-from-bottom"],
    .wpb_column.has-animation[data-animation="fade-in-from-bottom"],
    .nectar-fancy-box.has-animation[data-animation="fade-in-from-bottom"],
    img.img-with-animation[data-animation="reveal-from-bottom"],
    .img-with-aniamtion-wrap[data-animation="reveal-from-bottom"] .hover-wrap,
    .col.has-animation[data-animation="reveal-from-bottom"],
    .wpb_column.has-animation[data-animation="reveal-from-bottom"] {
      animation: mus-fade-in-bottom 1s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 5% cover 25%;
    }

    img.img-with-animation[data-animation="fade-in-from-left"],
    .img-with-aniamtion-wrap[data-animation="fade-in-from-left"] .hover-wrap,
    .col.has-animation[data-animation="fade-in-from-left"],
    .wpb_column.has-animation[data-animation="fade-in-from-left"] {
      animation: mus-fade-in-left 1s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 5% cover 25%;
    }

    img.img-with-animation[data-animation="fade-in-from-right"],
    .img-with-aniamtion-wrap[data-animation="fade-in-from-right"] .hover-wrap,
    .col.has-animation[data-animation="fade-in-from-right"],
    .wpb_column.has-animation[data-animation="fade-in-from-right"] {
      animation: mus-fade-in-right 1s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 5% cover 25%;
    }

    img.img-with-animation[data-animation="grow-in"],
    .img-with-aniamtion-wrap[data-animation="grow-in"] .hover-wrap,
    .col.has-animation[data-animation="grow-in"],
    .wpb_column.has-animation[data-animation="grow-in"] {
      animation: mus-grow-in 0.9s cubic-bezier(0.15, 0.84, 0.35, 1.15) both;
      animation-timeline: view();
      animation-range: entry 5% cover 25%;
    }

    /* Map markers, staggered by their DOM order so they arrive in sequence
     * rather than all at once, the way the JS used to do it. */
    .nectar_image_with_hotspots[data-animation="true"] .nectar_hotspot_wrap {
      animation: mus-fade-in-bottom 0.8s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 12% cover 32%;
    }
  }
}


/* ------------------------------------------------ 10. Split headings
 * .nectar-split-heading is a text-animation element: the markup ships with
 * each line pre-hidden and Salient's JS slides or fades it in. With the JS
 * gone the heading is simply never revealed -- the words are in the HTML and
 * read fine to a screen reader, but nothing is on screen. This is what was
 * eating the homepage hero headline ("To nourish human connection by
 * inspiring joy for every chef") and three headings on /company/.
 *
 * Each rule below cancels one starting state the theme's JS was meant to
 * undo. Selectors mirror the theme's own so they win on source order. */

/* data-animation-type="default": every line sits 200% down inside an
 * overflow:hidden strip, so it is clipped out of view. */
.nectar-split-heading .heading-line > div {
  -webkit-transform: none;
  transform: none;
}

/* "line-reveal-by-space" and "letter-fade-reveal" start at opacity 0 and wait
 * for the JS to add .markup-generated once it has rebuilt the markup. */
.nectar-split-heading[data-animation-type="line-reveal-by-space"]:not(.markup-generated),
.nectar-split-heading[data-animation-type="letter-fade-reveal"]:not(.markup-generated) {
  opacity: 1;
}
.nectar-split-heading[data-animation-type="line-reveal-by-space"] span .inner {
  -webkit-transform: none;
  transform: none;
}
.nectar-split-heading[data-animation-type="letter-fade-reveal"] span span {
  -webkit-transform: none;
  transform: none;
  opacity: 1;
}
.nectar-split-heading[data-animation-type="twist-in"] {
  -webkit-transform: none;
  transform: none;
  opacity: 1;
}


/* --------------------------------------------------- 11. Background video
 * /brands/hestan/ has a full-bleed hero whose background is a silent, looping
 * YouTube film. It is an <iframe> rather than a <video> because the source is
 * hosted on YouTube; frame-src in _headers allows the player for exactly this,
 * and youtube-nocookie.com is used so nothing is set until playback.
 *
 * An iframe cannot be object-fit, and the player letterboxes itself to 16:9 if
 * it is simply stretched. So the frame keeps its aspect ratio and is grown past
 * whichever edge of the hero is the binding one, then centred -- the same
 * result object-fit: cover gives an image.
 *
 * It is inert to the reader: no controls, not focusable, hidden from assistive
 * technology, and pointer events pass through to the content above it. */
.mus-video-bg {
  position: absolute;
  top: 0;
  height: 100%;
  overflow: hidden;
  pointer-events: none;
}
/* The hero row is full-bleed while its content column is not, so the video has
 * to break out of the column to the viewport edges the same way the row's own
 * background layer does. */
.full-width-section > .mus-video-bg {
  left: 50%;
  width: 100vw;
  margin-left: -50vw;
}
.mus-video-bg__frame {
  position: absolute;
  top: 50%;
  left: 50%;
  transform: translate(-50%, -50%);
  /* Cover: never smaller than the hero on either axis, 16:9 throughout. */
  min-width: 100%;
  min-height: 100%;
  width: auto;
  height: auto;
  aspect-ratio: 16 / 9;
  border: 0;
  pointer-events: none;
}
/* Older engines without aspect-ratio fall back to viewport arithmetic, which
 * covers because the hero is full-width. */
@supports not (aspect-ratio: 16 / 9) {
  .mus-video-bg__frame {
    width: 100vw;
    height: 56.25vw;
    min-height: 100%;
    min-width: 177.78vh;
  }
}

/* It autoplays, loops, and runs well past five seconds with no way to pause it,
 * which is what WCAG 2.2.2 is about. There is no script to offer a pause
 * control, so anyone who has asked their system for reduced motion gets the
 * row's own overlay colour instead of a moving picture. */
@media (prefers-reduced-motion: reduce) {
  .mus-video-bg { display: none; }
}


/* ----------------------------------------------- 12. States driven by site.js
 * Everything here is additive. Without the script the page keeps the visible
 * state the rest of this stylesheet sets; these classes only add behaviour. */

/* Tabs, in CSS only. One radio per tab, labels in place of the old anchors,
 * and `:checked ~` doing the switching -- no script, and no #fragment in the
 * address bar or scroll jump when a tab is picked.
 *
 * The nth radio addresses the nth panel by position, so these rules work for
 * any tab set on any page rather than needing one rule per instance. Eight is
 * well past the largest here (three). */
.mus-tabs {
  position: relative;
}

/* Visually hidden but still focusable. `display: none` would drop the radios
 * out of the tab order and make the whole component unreachable by keyboard,
 * which is the usual flaw in this pattern. */
.mus-tab-input {
  position: absolute;
  width: 1px;
  height: 1px;
  opacity: 0;
  margin: 0;
  pointer-events: none;
}

.mus-tab-label {
  display: block;
  cursor: pointer;
}

/* Panels: hidden by default, the checked one shown. */
.mus-tabs .mus-tab-panels > .wpb_tab {
  display: none;
  position: static;
  left: auto;
  opacity: 1;
  visibility: visible;
  width: auto;
}
.mus-tabs > .mus-tab-input:nth-of-type(1):checked ~ .mus-tab-panels > .wpb_tab:nth-child(1),
.mus-tabs > .mus-tab-input:nth-of-type(2):checked ~ .mus-tab-panels > .wpb_tab:nth-child(2),
.mus-tabs > .mus-tab-input:nth-of-type(3):checked ~ .mus-tab-panels > .wpb_tab:nth-child(3),
.mus-tabs > .mus-tab-input:nth-of-type(4):checked ~ .mus-tab-panels > .wpb_tab:nth-child(4),
.mus-tabs > .mus-tab-input:nth-of-type(5):checked ~ .mus-tab-panels > .wpb_tab:nth-child(5),
.mus-tabs > .mus-tab-input:nth-of-type(6):checked ~ .mus-tab-panels > .wpb_tab:nth-child(6),
.mus-tabs > .mus-tab-input:nth-of-type(7):checked ~ .mus-tab-panels > .wpb_tab:nth-child(7),
.mus-tabs > .mus-tab-input:nth-of-type(8):checked ~ .mus-tab-panels > .wpb_tab:nth-child(8) {
  display: block;
  animation: mus-tab-in 0.35s ease both;
}
@keyframes mus-tab-in {
  from { opacity: 0; transform: translateY(4px); }
  to   { opacity: 1; transform: none; }
}
@media (prefers-reduced-motion: reduce) {
  .mus-tabs .mus-tab-panels > .wpb_tab { animation: none !important; }
}

/* The page shell for /news/ and /newsroom/: post column plus sidebar.
 *
 * The theme sizes the post column in fixed pixels -- 895px, then 660, 610, 420
 * and 320 at successive breakpoints -- and floats the sidebar beside it. Script
 * used to remeasure and reposition the masonry on every resize, so those fixed
 * numbers only ever had to be right at the breakpoints themselves. With the
 * script gone they are wrong everywhere in between: the post column stays at
 * its pixel width while the container shrinks, and the floated sidebar lands on
 * top of the cards.
 *
 * So the widths are percentages here and the two columns are a flex row, which
 * needs no measuring and cannot overlap at any width. Below 1000px they stack,
 * which is what the theme was reaching for. The selectors carry enough weight
 * to outrank the theme's own, which are plain class selectors under a
 * body[data-ext-responsive] prefix. */
body .container .row .post-area.span_9,
body[data-ext-responsive="true"] .container .row .post-area.masonry.span_9 {
  width: 68%;
  margin-right: 0;
  float: none;
}
body .container .row #sidebar.span_3 {
  width: 28%;
  margin-left: 4%;
  float: none;
}
@media only screen and (min-width: 1000px) {
  body .container .row:has(> .post-area) {
    display: flex;
    align-items: flex-start;
  }
}
/* Stacked below the point the theme gives up on two columns. */
@media only screen and (max-width: 999px) {
  body .container .row .post-area.span_9,
  body[data-ext-responsive="true"] .container .row .post-area.masonry.span_9,
  body .container .row #sidebar.span_3 {
    width: 100%;
    margin-left: 0;
    margin-right: 0;
    float: none;
  }
}

/* The cards themselves. Their masonry positions were written inline by script;
 * a grid places them with no measuring. Two columns beside the sidebar, one
 * when the page has stacked and the column is full width. */
.post-area.masonry .posts-container {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 30px;
  align-items: start;
}
.post-area.masonry .posts-container > article.masonry-blog-item {
  width: auto;
  margin: 0;
  position: relative;
  top: auto;
  left: auto;
}
/* The theme sizes a card image through `.post .content-inner
 * .post-featured-img img`, but .post-featured-img is a sibling of
 * .content-inner in this markup, not a descendant, so that rule never matched
 * and every image rendered at its natural width and spilled past the card. */
.post-area.masonry .posts-container > article.masonry-blog-item .post-featured-img img {
  display: block;
  width: 100%;
  height: auto;
  max-width: 100%;
}
@media only screen and (max-width: 690px) {
  .post-area.masonry .posts-container {
    grid-template-columns: minmax(0, 1fr);
    gap: 24px;
  }
}

/* The theme parks every card 450px below where it belongs and rotates it 24deg
 * in 3D, then relies on script to clear the transform once the page has loaded:
 *
 *   .posts-container[data-load-animation="perspective"] article .inner-wrap {
 *     transform: translateY(450px) rotateX(24deg) }
 *
 * With no script the transform is permanent, and a page of cards sits 450px
 * low, tilted away from the viewer -- which reads as a large empty gap under
 * the hero. The theme ships CSS-only resets for its "fade_in",
 * "fade_in_from_bottom" and "none" variants but not for "perspective", which
 * is the one this page asks for, so the reset is here instead.
 *
 * This is also the starting state the reveal below animates from, so it has to
 * be cleared rather than animated over -- otherwise the cards are invisible
 * wherever the reveal does not run. */
.posts-container[data-load-animation="perspective"] article .inner-wrap,
.posts-container[data-load-animation="perspective"] article .inner-wrap.animated {
  transform: none;
  -webkit-transform: none;
}

.posts-container article .inner-wrap.animated {
  opacity: 1;
}
/* Gated to 1000px like every other scroll-driven reveal in this file. Without
 * the gate the animation also ran on narrow viewports, where its timeline never
 * advanced and the cards stayed at the keyframe's opacity 0 -- a page of
 * invisible articles. The base rule above keeps them visible, so below this
 * width the failure mode is "no animation", never "no content". */
@supports (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) and (min-width: 1000px) {
    .posts-container article .inner-wrap.animated {
      animation: mus-fade-in-bottom 0.7s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 5% cover 24%;
    }
  }
}
.posts-container article .inner-wrap.mus-in {
  opacity: 1;
}

/* Reveal fallback for browsers without scroll-driven animations (Firefox at
 * the time of writing). site.js adds .mus-reveal, then .mus-in on entry. */
@supports not (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) and (min-width: 1000px) {
    .mus-reveal {
      opacity: 0;
      transform: translateY(40px);
      transition: opacity 0.8s cubic-bezier(0.25, 1, 0.5, 1),
                  transform 0.8s cubic-bezier(0.25, 1, 0.5, 1);
    }
    .mus-reveal.mus-in {
      opacity: 1;
      transform: none;
    }
  }
}

/* The mirror of .mus-h1-visual-h2: a heading demoted from h1 to h2 so the page
 * keeps a single h1, but which must still look exactly as it did. Values are
 * the theme's h1 cascade from theme-settings.css. */
h2.mus-h2-visual-h1 {
  font-family: "Work Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-size: 60px;
  line-height: 74px;
  font-weight: 700;
}
@media only screen and (max-width: 1300px) and (min-width: 1000px) {
  h2.mus-h2-visual-h1 { font-size: 45px; line-height: 55.5px; }
}
@media only screen and (max-width: 999px) and (min-width: 690px) {
  h2.mus-h2-visual-h1 { font-size: 42px; line-height: 51.8px; }
}
@media only screen and (max-width: 690px) {
  h2.mus-h2-visual-h1 { font-size: 39px; line-height: 48.1px; }
}


/* ------------------------------------------------- 13. Header on scroll
 * The body asks for this with data-hhun="1" ("hide header until needed").
 * Salient's JS wrote the transform inline, so there is nothing in the theme
 * CSS describing the hidden state; site.js only toggles the class below.
 * The transition is applied once the script is ready, so a page without
 * JavaScript never has a header that could slide anywhere. */
body.mus-header-scroll-ready #header-outer {
  transition: transform 0.35s cubic-bezier(0.4, 0, 0.2, 1);
  will-change: transform;
}
body.mus-header-scroll-ready.mus-header-hidden #header-outer {
  transform: translateY(-100%);
}
/* Keep it in place if a keyboard user tabs into it while it is away. */
body.mus-header-hidden #header-outer:focus-within {
  transform: none;
}
@media (prefers-reduced-motion: reduce) {
  body.mus-header-scroll-ready #header-outer {
    transition: none;
  }
}


/* --------------------------------- 14. Row background reveals and parallax
 * Two more things the theme's JavaScript drove.
 *
 * zoom-out-reveal is the serious one: the theme parks the whole background
 * wrapper at `transform: scale(0.7); opacity: 0` with its inner layer at
 * scale(1.75), and its script animated both to rest. Without that script the
 * section background is simply never drawn -- eight of them, on /, /about/,
 * /programs/, /work-with-us/, /sale/, /holiday-coupon/, /brands/anyday/ and
 * /brands/hestan/. Visible is the base state here; the animation is layered
 * on top only where the browser can drive it from scroll position. */
.row-bg-wrap[data-bg-animation="zoom-out-reveal"],
.column-image-bg-wrap[data-bg-animation="zoom-out-reveal"],
.wpb_column .column-bg-overlay-wrap[data-bg-animation="zoom-out-reveal"] {
  opacity: 1;
  -webkit-transform: none;
  transform: none;
}
.row-bg-wrap[data-bg-animation="zoom-out-reveal"] .inner-wrap,
.column-image-bg-wrap[data-bg-animation="zoom-out-reveal"] .inner-wrap {
  -webkit-transform: none;
  transform: none;
}
.row-bg-wrap[data-bg-animation="fade-in"] .inner-wrap.using-image,
.row-bg-wrap[data-bg-animation="fade-in"] .inner-wrap {
  opacity: 1;
}

@supports (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) and (min-width: 1000px) {

    @keyframes mus-zoom-out-reveal {
      from { opacity: 0; transform: scale(0.7); }
      to   { opacity: 1; transform: none; }
    }
    @keyframes mus-zoom-out-inner {
      from { transform: scale(1.75); }
      to   { transform: none; }
    }
    /* The background sits taller than its row (the theme adds 40-90px for
     * this), so sliding it against scroll position gives the parallax the
     * theme used to compute on every scroll event. */
    @keyframes mus-parallax {
      from { transform: translateY(-12%); }
      to   { transform: translateY(0); }
    }

    .row-bg-wrap[data-bg-animation="zoom-out-reveal"],
    .column-image-bg-wrap[data-bg-animation="zoom-out-reveal"] {
      animation: mus-zoom-out-reveal 1s cubic-bezier(0.12, 0.75, 0.4, 1) both;
      animation-timeline: view();
      animation-range: entry 0% cover 30%;
    }
    .row-bg-wrap[data-bg-animation="zoom-out-reveal"] .inner-wrap,
    .column-image-bg-wrap[data-bg-animation="zoom-out-reveal"] .inner-wrap {
      animation: mus-zoom-out-inner 1s cubic-bezier(0.12, 0.75, 0.4, 1) both;
      animation-timeline: view();
      animation-range: entry 0% cover 30%;
    }

    .parallax_section .row-bg[data-parallax-speed="fast"],
    .parallax_section .row-bg[data-parallax-speed="medium"],
    .parallax_section .row-bg[data-parallax-speed="slow"] {
      animation: mus-parallax linear both;
      animation-timeline: view();
      animation-range: cover 0% cover 100%;
    }
  }
}


/* ------------------------------------------ 15. Fancy-box hover (grid tiles)
 * The brand tiles are data-style="parallax_hover": a 3D card that tilts
 * toward the cursor, with the photo pushing back and the logo lifting
 * forward. The theme built the layer stack in JavaScript and tracked the
 * pointer on every move; site.js now sets two custom properties for the tilt
 * and everything else is CSS.
 *
 * Hover-only, and only where a pointer can actually hover -- a touch device
 * would otherwise get stuck in the hovered state after a tap. */
@media (hover: hover) and (pointer: fine) {
  .nectar-fancy-box[data-style="parallax_hover"] .parallaxImg {
    -webkit-perspective: 1000px;
    perspective: 1000px;
  }
  .nectar-fancy-box[data-style="parallax_hover"] .parallaxImg,
  .nectar-fancy-box[data-style="parallax_hover"] .parallaxImg-layer {
    -webkit-transform-style: preserve-3d;
    transform-style: preserve-3d;
    transition: transform 0.4s cubic-bezier(0.2, 0.8, 0.25, 1);
  }

  /* the tilt itself — --mus-rx/--mus-ry come from site.js */
  .nectar-fancy-box[data-style="parallax_hover"].mus-tilt .parallaxImg {
    transform: rotateX(var(--mus-rx, 0deg)) rotateY(var(--mus-ry, 0deg));
  }

  /* photo pushes back and zooms; logo lifts toward the viewer */
  .nectar-fancy-box[data-style="parallax_hover"] .parallaxImg-layer.mus-parallax-bg {
    transition: transform 0.45s cubic-bezier(0.2, 0.8, 0.25, 1);
  }
  .nectar-fancy-box[data-style="parallax_hover"]:hover .parallaxImg-layer.mus-parallax-bg {
    transform: scale(1.08) translateZ(-30px);
  }
  .nectar-fancy-box[data-style="parallax_hover"]:hover .parallaxImg-layer:not(.mus-parallax-bg) {
    transform: translateZ(48px);
  }

  /* The drop shadow. The theme injected a .parallaxImg-shadow element in
   * JavaScript, so there is nothing in the markup to style -- it is drawn on
   * the tile itself instead, and lifts with the card on hover. */
  .nectar-fancy-box[data-style="parallax_hover"] .parallaxImg {
    box-shadow: 0 2px 6px rgba(0, 0, 0, 0.10);
    transition: transform 0.4s cubic-bezier(0.2, 0.8, 0.25, 1),
                box-shadow 0.4s cubic-bezier(0.2, 0.8, 0.25, 1);
  }
  .nectar-fancy-box[data-style="parallax_hover"]:hover .parallaxImg {
    box-shadow: 0 28px 55px rgba(0, 0, 0, 0.32),
                0 10px 20px rgba(0, 0, 0, 0.16);
  }
}

@media (prefers-reduced-motion: reduce) {
  .nectar-fancy-box[data-style="parallax_hover"] .parallaxImg,
  .nectar-fancy-box[data-style="parallax_hover"] .parallaxImg-layer {
    transition: none;
    transform: none !important;
  }
}


/* ------------------------------ 16. Tab labels inherit the tab-anchor styling
 * The tabs are radio + label now, so every `.tabbed ... a` rule the theme
 * shipped stops matching and the tab titles lose their type, padding and
 * colour. These are those same rules, generated from the theme CSS with the
 * anchor swapped for .mus-tab-label, so the tabs look exactly as they did. */
.tabbed >ul li .mus-tab-label { display:block; color:#888; position:relative; background-color:rgba(0,0,0,0.045); padding:8px 15px; transition:all 0.3s cubic-bezier(0.12,0.75,0.4,1); -webkit-transition:all 0.3s cubic-bezier(0.12,0.75,0.4,1); border-left:0px; border-right:1px solid rgba(0,0,0,0.06) }
.tabbed >ul li .mus-tab-label svg { fill: #888; }
.tabbed > ul li .mus-tab-label:hover { background-color:rgba(0,0,0,0.035) }
.tabbed > ul li:last-child .mus-tab-label { border-color:transparent }
.light .tabbed >ul li:last-child .mus-tab-label, .light .tabbed >ul li .mus-tab-label { border-color:rgba(0,0,0,0.2) }
.light .tabbed >ul li .mus-tab-label { background-color:rgba(0,0,0,0.15) }
.tabbed[data-style="minimal"] >ul li:not(.cta-button) .mus-tab-label, .tabbed[data-style="minimal_alt"] >ul li:not(.cta-button) .mus-tab-label { background-color:transparent; border-right:none; position:relative; color:inherit; z-index:10; padding:18px 17px; line-height:32px; margin-bottom:-1px; overflow-y:hidden; transition:all 0.3s cubic-bezier(0.12,0.75,0.4,1); -webkit-transition:all 0.3s cubic-bezier(0.12,0.75,0.4,1) }
.tabbed[data-style="minimal"] >ul li:not(.cta-button) .mus-tab-label svg, .tabbed[data-style="minimal_alt"] >ul li:not(.cta-button) .mus-tab-label svg { fill: currentColor; }
.tabbed[data-style="minimal"] >ul li .mus-tab-label:hover { opacity:0.7 }
.tabbed[data-style*="minimal"] >ul li .mus-tab-label:after { height:4px; width:100%; content:' '; background-color:#000; display:block; position:absolute; bottom:-4px; left:0; z-index:10; transition:transform 0.3s cubic-bezier(0.12,0.75,0.4,1); -webkit-transition:-webkit-transform 0.3s cubic-bezier(0.12,0.75,0.4,1) }
.tabbed[data-style*="vertical"] .wpb_tabs_nav li .mus-tab-label { border-right:none }
.tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label { background-color: rgba(0,0,0,0.04); }
.tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label:hover { background-color: rgba(0,0,0,0.025); }
.tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label { display: -webkit-box; display: -webkit-flex; display: -ms-flexbox; display: flex; align-items: center; }
.tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label { border-radius: 6px; padding: 25px 20px; overflow: hidden; }
.tabbed[data-style="minimal_alt"] >ul li:not(.cta-button) .mus-tab-label { padding:2px 0px!important }
.tabbed[data-style*="material"][data-color-scheme="extra-color-gradient-1"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="material"][data-color-scheme="extra-color-gradient-2"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="default"][data-color-scheme="extra-color-gradient-1"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="default"][data-color-scheme="extra-color-gradient-2"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="vertical"][data-color-scheme="extra-color-gradient-1"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="vertical"][data-color-scheme="extra-color-gradient-2"] .wpb_tabs_nav li .mus-tab-label:before { background-color: #000; display: block; left: 0; width: 100%; position: absolute; content: ''; height: 1px; opacity: 0.25; visibility: visible; }
.tabbed[data-style*="material"][data-color-scheme="extra-color-gradient-1"] .wpb_tabs_nav li .mus-tab-label, .tabbed[data-style*="material"][data-color-scheme="extra-color-gradient-2"] .wpb_tabs_nav li .mus-tab-label { background-color: transparent; }
.tabbed[data-style*="material"][data-color-scheme="extra-color-gradient-1"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="material"][data-color-scheme="extra-color-gradient-2"] .wpb_tabs_nav li .mus-tab-label:before { height: 100%; top: 0; opacity: 0; transition: all 0.3s cubic-bezier(0.12,0.75,0.4,1); -webkit-transition: all 0.3s cubic-bezier(0.12,0.75,0.4,1); z-index: -1; border-radius: 5px 5px 0 0px; }
.tabbed[data-style*="default"][data-color-scheme="extra-color-gradient-1"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="default"][data-color-scheme="extra-color-gradient-2"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="vertical"][data-color-scheme="extra-color-gradient-1"] .wpb_tabs_nav li .mus-tab-label:before, .tabbed[data-style*="vertical"][data-color-scheme="extra-color-gradient-2"] .wpb_tabs_nav li .mus-tab-label:before { height: 100%; top: 0; opacity: 0; transition: all 0.3s cubic-bezier(0.12,0.75,0.4,1); -webkit-transition: all 0.3s cubic-bezier(0.12,0.75,0.4,1); z-index: -1; }
.tabbed[data-style*="material"] .wpb_tabs_nav li .mus-tab-label:not(.active-tab):hover, body .tabbed[data-style*="material"][data-color-scheme] .wpb_tabs_nav li .mus-tab-label:not(.active-tab):hover { color: #000; }
.tabbed[data-style*="material"] .wpb_tabs_nav li .mus-tab-label:not(.active-tab):hover svg { fill: #000; }
.tabbed[data-style*="material"] .wpb_tabs_nav li .mus-tab-label:after { transition: all 0.3s cubic-bezier(0.12,0.75,0.4,1); opacity: 0.3; display: block; content: ''; width: 92%; height: 92%; top: 4%; left: 4%; z-index: -2; position: absolute; }
.span_12.light .tabbed[data-style*="material"] >ul li .mus-tab-label:not(.active-tab) { color: rgba(255,255,255,0.7); }
.span_12.light .tabbed[data-style*="material"] >ul li .mus-tab-label:hover { color: rgba(255,255,255,1); }
.tabbed[data-style="minimal_flexible"] .wpb_tabs_nav > li .mus-tab-label { background-color: transparent; text-align: center; color: inherit; border: none; font-size: 1.2em; padding: 25px 30px; }
.tabbed[data-style="minimal_flexible"] .wpb_tabs_nav > li .mus-tab-label:not(.active-tab):hover { opacity: 0.6; }
.tabbed[data-style="minimal_flexible"] .wpb_tabs_nav > li .mus-tab-label.active-tab:hover { background-color: transparent; }
.tabbed[data-style="minimal_flexible"] .wpb_tabs_nav > li .mus-tab-label:not(.active-tab):after { background: none; }
.tabbed[data-style="minimal_flexible"] .wpb_tabs_nav > li .mus-tab-label:after { -webkit-transform: scaleY(0); transform: scaleY(0); -webkit-transform-origin: bottom; transform-origin: bottom; height: 4px; bottom: 0; -webkit-transition: transform .4s ease; transition: transform .4s ease; }
.tabbed[data-style="minimal_flexible"] .wpb_tabs_nav > li .mus-tab-label.active-tab:after { -webkit-transform: scaleY(1); transform: scaleY(1); }
.tabbed[data-style="minimal_flexible"] .wpb_tabs_nav > li .mus-tab-label:before { position: absolute; display: block; content: ''; bottom: -4px; left: 0; width: 100%; height: 4px; opacity: 0; transition: opacity .4s ease; box-shadow: 0px 8px 24px rgba(0,0,0,0.15); }
.tabbed[data-style="minimal_flexible"] .wpb_tabs_nav > li .mus-tab-label.active-tab:before { opacity: 0.3; }
#ajax-content-wrap [data-stored-style="vs"] .tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label:before { display: block; position: absolute; left: 3px; top: 0; content: ''; background-color: rgba(0,0,0,0.1); width: 1px; height: 100%; }
.light #ajax-content-wrap [data-stored-style="vs"] .tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label:before { background-color: rgba(255,255,255,0.2); }
[data-stored-style="vs"] .tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label { background-color: transparent!important; padding: 0 0 0 40px; margin-bottom: 35px; }
[data-stored-style="vs"] .tabbed[data-style="vertical_modern"] .wpb_tabs_nav li:last-child .mus-tab-label { margin-bottom: 0; }
[data-stored-style="vs"] .tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label:before { display: none; }
[data-stored-style="vs"] .tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label:before { opacity: 0; background-color: #000; transition: opacity 0.3s ease; }
[data-stored-style="vs"] .tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label.active-tab:before { opacity: 1 }
.tabbed[data-style="material"] .wpb_tabs_nav li .mus-tab-label { transition: all 0.3s cubic-bezier(0.12,0.75,0.4,1); padding-top: 13px; padding-bottom: 13px; border: none; border-radius: 5px 5px 0 0px; }
.tabbed[data-style="material"] >ul li .mus-tab-label:not(.active-tab) { background-color: transparent; }
.tabbed[data-spacing="side-15px"]:not([data-style="vertical"]) .wpb_tabs_nav li .mus-tab-label { padding-left: 17px; padding-right: 17px; }
.tabbed[data-spacing="side-20px"]:not([data-style="vertical"]) .wpb_tabs_nav li .mus-tab-label { padding-left: 20px; padding-right: 20px; }
.tabbed[data-spacing="side-25px"]:not([data-style="vertical"]) .wpb_tabs_nav li .mus-tab-label { padding-left: 25px; padding-right: 25px; }
.tabbed[data-spacing="side-30px"]:not([data-style="vertical"]) .wpb_tabs_nav li .mus-tab-label { padding-left: 30px; padding-right: 30px; }
.tabbed[data-spacing="side-35px"]:not([data-style="vertical"]) .wpb_tabs_nav li .mus-tab-label { padding-left: 35px; padding-right: 35px; }
.tabbed[data-spacing="side-40px"]:not([data-style="vertical"]) .wpb_tabs_nav li .mus-tab-label { padding-left:40px; padding-right:40px; }
.tabbed[data-spacing="side-45px"]:not([data-style="vertical"]) .wpb_tabs_nav li .mus-tab-label { padding-left:45px; padding-right:45px; }
@media only screen and (max-width: 999px) {
  .tabbed[data-style="vertical_modern"] .wpb_tabs_nav li .mus-tab-label { padding: 15px 20px; }
}
@media only screen and (min-width:1000px) {
  body .tabbed[data-style="minimal_alt"] >ul li .mus-tab-label:after { display:none }
}
@media only screen and (max-width : 690px) {
  .tabbed[data-style*="minimal"] > ul li:not(.cta-button) .mus-tab-label { padding: 20px 15px 5px 15px; }
  .tabbed > ul li .mus-tab-label { border-right: 0px!important; }
  .tabbed[data-style="material"] .wpb_tabs_nav li .mus-tab-label { display: block; text-align: center; }
  .tabbed[data-style="material"] ul li .mus-tab-label, .tabbed[data-style*="material"][data-color-scheme="extra-color-gradient-1"] ul li .mus-tab-label:before, .tabbed[data-style*="material"][data-color-scheme="extra-color-gradient-2"] ul li .mus-tab-label:before { border-radius: 5px; }
}


/* ---- Tab selected/focus states, last so they win --------------------
 * The generated block above mirrors the theme's base tab-anchor styling,
 * including the dimmed colour of an unselected tab. These come after it so
 * the selected tab is actually the bright one. */
.mus-tabs > .mus-tab-input:nth-of-type(1):checked ~ .wpb_tabs_nav > li:nth-child(1) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(2):checked ~ .wpb_tabs_nav > li:nth-child(2) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(3):checked ~ .wpb_tabs_nav > li:nth-child(3) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(4):checked ~ .wpb_tabs_nav > li:nth-child(4) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(5):checked ~ .wpb_tabs_nav > li:nth-child(5) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(6):checked ~ .wpb_tabs_nav > li:nth-child(6) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(7):checked ~ .wpb_tabs_nav > li:nth-child(7) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(8):checked ~ .wpb_tabs_nav > li:nth-child(8) > .mus-tab-label {
  opacity: 1;
}
.mus-tabs[data-style*="minimal"] > .mus-tab-input:nth-of-type(1):checked ~ .wpb_tabs_nav > li:nth-child(1) > .mus-tab-label:after,
.mus-tabs[data-style*="minimal"] > .mus-tab-input:nth-of-type(2):checked ~ .wpb_tabs_nav > li:nth-child(2) > .mus-tab-label:after,
.mus-tabs[data-style*="minimal"] > .mus-tab-input:nth-of-type(3):checked ~ .wpb_tabs_nav > li:nth-child(3) > .mus-tab-label:after,
.mus-tabs[data-style*="minimal"] > .mus-tab-input:nth-of-type(4):checked ~ .wpb_tabs_nav > li:nth-child(4) > .mus-tab-label:after,
.mus-tabs[data-style*="minimal"] > .mus-tab-input:nth-of-type(5):checked ~ .wpb_tabs_nav > li:nth-child(5) > .mus-tab-label:after,
.mus-tabs[data-style*="minimal"] > .mus-tab-input:nth-of-type(6):checked ~ .wpb_tabs_nav > li:nth-child(6) > .mus-tab-label:after {
  transform: scaleX(1);
  opacity: 1;
}

/* Keyboard focus lands on the radio, which is invisible, so the ring is drawn
 * on its label instead. */
.mus-tabs > .mus-tab-input:nth-of-type(1):focus-visible ~ .wpb_tabs_nav > li:nth-child(1) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(2):focus-visible ~ .wpb_tabs_nav > li:nth-child(2) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(3):focus-visible ~ .wpb_tabs_nav > li:nth-child(3) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(4):focus-visible ~ .wpb_tabs_nav > li:nth-child(4) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(5):focus-visible ~ .wpb_tabs_nav > li:nth-child(5) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(6):focus-visible ~ .wpb_tabs_nav > li:nth-child(6) > .mus-tab-label {
  outline: 3px solid #005daa;
  outline-offset: 2px;
  box-shadow: 0 0 0 2px #ffffff;
}


/* Tab label colour. The theme's "minimal" style sets `color: inherit` on the
 * tab anchor, which picked up white inside a .light column and the dark body
 * colour elsewhere. A <label> does not inherit the same way the anchor did,
 * so the two contexts are stated here: /about/ and /work-with-us/ sit in a
 * .light column over blue, /company/ sits on white. */
.mus-tabs .wpb_tabs_nav li .mus-tab-label {
  color: inherit;
  opacity: 0.6;
  transition: opacity 0.3s ease, color 0.3s ease;
}
.light .mus-tabs .wpb_tabs_nav li .mus-tab-label {
  color: #ffffff;
}
.mus-tabs .wpb_tabs_nav li .mus-tab-label:hover {
  opacity: 0.85;
}
.mus-tabs > .mus-tab-input:nth-of-type(1):checked ~ .wpb_tabs_nav > li:nth-child(1) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(2):checked ~ .wpb_tabs_nav > li:nth-child(2) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(3):checked ~ .wpb_tabs_nav > li:nth-child(3) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(4):checked ~ .wpb_tabs_nav > li:nth-child(4) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(5):checked ~ .wpb_tabs_nav > li:nth-child(5) > .mus-tab-label,
.mus-tabs > .mus-tab-input:nth-of-type(6):checked ~ .wpb_tabs_nav > li:nth-child(6) > .mus-tab-label {
  opacity: 1;
}

/* The tab title sits in a <span> inside the label. With the original anchor
 * the span inherited the anchor's colour; on its own it picks up the theme's
 * accent (#005daa), which on the blue panels is blue-on-blue and unreadable. */
.mus-tabs .wpb_tabs_nav li .mus-tab-label span,
.mus-tabs .wpb_tabs_nav li .mus-tab-label * {
  color: inherit;
}

/* theme-settings.css shipped a bare `label span { color: #005daa }` among a
 * 17-selector list -- styling for the WordPress forms that were removed with
 * the rest of the plugins. Nothing in the theme uses a label any more, so the
 * only things it still hit were the tab titles (blue on blue) and the request
 * form's required asterisks (blue instead of red). The selector is deleted
 * from theme-settings.css; this stays as a guard in case that CSS is ever
 * re-copied from the original site. */
.mus-tabs .wpb_tabs_nav li .mus-tab-label span {
  color: inherit;
}
.mus-form label .mus-required {
  color: #c0392b;
}

/* ------------------------------------------------ 17. Map tooltip sizing
 * .nttip sits inside a 30x30 .nectar_hotspot_wrap and is position:relative,
 * so it shrinks to the wrapper. The theme only ever set `max-width: 250px`,
 * which constrains nothing without a width -- Salient's JS supplied that.
 * Result without it: a 30px column of text one word per line.
 *
 * 250px matches the theme's own figure, and its `width: 250px!important`
 * for always-visible tooltips. The full-screen mobile treatment below 690px
 * uses !important and still wins. */
.nectar_image_with_hotspots .nectar_hotspot_wrap .nttip {
  width: 250px;
  max-width: 250px;
  box-sizing: border-box;
}
/* The country sits on its own line above the address. */
.nectar_image_with_hotspots .nectar_hotspot_wrap .nttip strong {
  display: block;
  margin-bottom: 4px;
  color: #000b14;
}

/* ------------------------------------------- 18. Milestones and dividers
 * Two more elements parked in a pre-animation state waiting for a class the
 * theme's JS added on scroll:
 *
 *   .nectar-milestone:not(.animated-in) { opacity: 0 }   -- hides the figure
 *       AND its label, so "11 / factories", "30+ / countries" and
 *       "17 / brands in our portfolio" were all missing under their headings.
 *   .divider-small-border[data-animate="yes"] { visibility: hidden }
 *       -- the short rule between the heading and the figure.
 *
 * Visible is the base state; the reveal is layered on where the browser can
 * drive it from scroll position. */
.nectar-milestone:not(.animated-in) {
  opacity: 1;
}
.divider-small-border[data-animate="yes"] {
  visibility: visible;
}

@supports (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) and (min-width: 1000px) {
    @keyframes mus-milestone-in {
      from { opacity: 0; transform: translateY(20px); }
      to   { opacity: 1; transform: none; }
    }
    /* the divider draws itself out from its transform-origin, as it did */
    @keyframes mus-divider-in {
      from { transform: scaleX(0); }
      to   { transform: scaleX(1); }
    }
    .nectar-milestone:not(.animated-in) {
      animation: mus-milestone-in 0.7s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 8% cover 26%;
    }
    .divider-small-border[data-animate="yes"] {
      animation: mus-divider-in 0.8s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 8% cover 26%;
    }
  }
}

/* --------------------------------- 19. Counting up, and the +, without JS
 * @property registers --mus-n as an integer, which makes it animatable; a
 * CSS counter then renders it. That is the whole count-up, no script.
 *
 * The real figure stays in the markup as the element's text. It is what a
 * screen reader reads and what shows anywhere this technique is unavailable,
 * so the page can never end up stating a number that is not true -- the
 * failure mode is "no animation", never "wrong number".
 *
 * Gated on animation-timeline support, which is a subset of the browsers that
 * have @property, so the two always arrive together. */
@property --mus-n {
  syntax: "<integer>";
  initial-value: 0;
  inherits: false;
}

/* The symbol beside the figure ("30+"). The theme's JS appended it from
 * data-symbol; it is real text in the markup now (see prepare_milestones),
 * so it just needs to sit inline at the same size as the number. attr() was
 * not an option -- data-symbol is on the milestone, and attr() only reads the
 * attribute of the element its pseudo-element belongs to. */
.nectar-milestone .number .mus-symbol {
  display: inline-block;
  font-size: inherit;
  line-height: inherit;
  font-weight: inherit;
  color: inherit;
  vertical-align: baseline;
}

@supports (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) and (min-width: 1000px) {
    .mus-count {
      counter-reset: mus-n var(--mus-n);
      animation: mus-count-up 1.6s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 8% cover 26%;
    }
    /* The literal figure stays in flow but out of sight, so it reserves the
     * final width and the surrounding layout never moves. The counter is
     * drawn over it, centred, so the number stays put as the digit count
     * changes -- an earlier version pinned it to left: 0, which made it jump
     * sideways on every tick, and another took the digits out of flow
     * entirely, which collapsed the height and overlapped the label. */
    .mus-count {
      position: relative;
      display: inline-block;
    }
    .mus-count > .mus-count-text {
      visibility: hidden;
    }
    .mus-count::after {
      content: counter(mus-n);
      position: absolute;
      left: 0;
      right: 0;
      top: 0;
      text-align: center;
      visibility: visible;
    }
    @keyframes mus-count-up {
      from { --mus-n: 0; }
      to   { --mus-n: var(--mus-to); }
    }
  }
}

/* ------------------------------------------- 18. Milestones and dividers
 * Two more elements parked in a pre-animation state waiting for a class the
 * theme's JS added on scroll:
 *
 *   .nectar-milestone:not(.animated-in) { opacity: 0 }   -- hides the figure
 *       AND its label, so "11 / factories", "30+ / countries" and
 *       "17 / brands in our portfolio" were all missing under their headings.
 *   .divider-small-border[data-animate="yes"] { visibility: hidden }
 *       -- the short rule between the heading and the figure.
 *
 * Visible is the base state; the reveal is layered on where the browser can
 * drive it from scroll position. */
.nectar-milestone:not(.animated-in) {
  opacity: 1;
}
.divider-small-border[data-animate="yes"] {
  visibility: visible;
}

@supports (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) and (min-width: 1000px) {
    @keyframes mus-milestone-in {
      from { opacity: 0; transform: translateY(20px); }
      to   { opacity: 1; transform: none; }
    }
    /* the divider draws itself out from its transform-origin, as it did */
    @keyframes mus-divider-in {
      from { transform: scaleX(0); }
      to   { transform: scaleX(1); }
    }
    .nectar-milestone:not(.animated-in) {
      animation: mus-milestone-in 0.7s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 8% cover 26%;
    }
    .divider-small-border[data-animate="yes"] {
      animation: mus-divider-in 0.8s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 8% cover 26%;
    }
  }
}

/* --------------------------------- 19. Counting up, and the +, without JS
 * @property registers --mus-n as an integer, which makes it animatable; a
 * CSS counter then renders it. That is the whole count-up, no script.
 *
 * The real figure stays in the markup as the element's text. It is what a
 * screen reader reads and what shows anywhere this technique is unavailable,
 * so the page can never end up stating a number that is not true -- the
 * failure mode is "no animation", never "wrong number".
 *
 * Gated on animation-timeline support, which is a subset of the browsers that
 * have @property, so the two always arrive together. */
@property --mus-n {
  syntax: "<integer>";
  initial-value: 0;
  inherits: false;
}

/* The symbol beside the figure ("30+"). The theme's JS appended it from
 * data-symbol; it is real text in the markup now (see prepare_milestones),
 * so it just needs to sit inline at the same size as the number. attr() was
 * not an option -- data-symbol is on the milestone, and attr() only reads the
 * attribute of the element its pseudo-element belongs to. */
.nectar-milestone .number .mus-symbol {
  display: inline-block;
  font-size: inherit;
  line-height: inherit;
  font-weight: inherit;
  color: inherit;
  vertical-align: baseline;
}

@supports (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) and (min-width: 1000px) {
    .mus-count {
      position: relative;
      counter-reset: mus-n var(--mus-n);
      /* hides the literal digits while keeping their width reserved, so the
       * layout does not jump as the counter ticks up */
      visibility: hidden;
      animation: mus-count-up 1.6s cubic-bezier(0.25, 1, 0.5, 1) both;
      animation-timeline: view();
      animation-range: entry 8% cover 26%;
    }
    .mus-count::after {
      visibility: visible;
      position: absolute;
      left: 0;
      top: 0;
      content: counter(mus-n);
    }
    @keyframes mus-count-up {
      from { --mus-n: 0; }
      to   { --mus-n: var(--mus-to); }
    }
  }
}

/* ------------------------------------------------ 20. Carousel rails

   Salient's carousels are flickity, and flickity is JavaScript. The theme
   already handles nearly all of the no-script case itself, keyed on
   `:not(.flickity-enabled)`: the viewport gets `height: auto`, the slider
   `display: flex` and `position: relative`, each cell `flex: 0 0 auto`, and the
   three-column carousels `width: 31.9%`.

   The one thing it does not do is make the overflow reachable. A 15-tile rail is
   5,955px of cells in a 1,245px box, so twelve of them paint outside their
   container and are clipped by an ancestor -- present, unreachable, and no
   scrollbar to say so. That is the whole defect, and this is the whole fix.

   No affordance CSS needed: 31.9% x 3 leaves 4.3% of the box spare, so a sliver
   of the next tile already shows.

   Extends the theme's own `:not(.flickity-enabled)` hook rather than inventing
   one. `:not(.masonry)` is carrying specificity -- the theme's viewport rule is
   three classes, and site.css loads after carousel.css. */

.nectar-flickity:not(.flickity-enabled):not(.masonry) .flickity-viewport {
  overflow-x: auto;
  overflow-y: hidden;
}