/* @import url('http://example.com/example_style.css'); */

/***********************************************/

/* CSS @imports must be at the top of the file */

/* Add them above this section                 */

/***********************************************/

/*****************************************/

/* Start your style declarations here    */

/*****************************************/

/* ---------- Footer menu items ---------- */
  .main-header {
    padding: 10px 0px 10px 0px !important;
  }
footer.footer .pwr-adc-main .pwr-adc__col {
  padding-bottom: 0px !important;
}
.pwr-footer-advanced .pwr-adc-content__menu .hs-menu-wrapper li > a {

  opacity: 1 !important;

}

.pwr-adc-content--menu .pwr-adc-content__menu .hs-menu-wrapper.hs-menu-flow-vertical li a {

  font-size: 16px !important;

  font-weight: 400 !important;

  color: #ffffff !important;

  padding-top: 0 !important;

  padding-bottom: 0 !important;

  line-height: 1.25 !important;

}

/* The <li> is what actually sets the row height. The links above are already
   tight, but each list item inherits the body line-height of 30px (20px x 1.5),
   so every row stayed 30px tall no matter how small the link inside it was.
   Measured on staging: 30px per row before the fix. At 16px type and a 1.25
   line-height each row is 20px, plus the 6px margin below, so items sit
   26px apart. Adjust the gap with the margin rather than by loosening the
   line-height, so the two stay independent. */
.pwr-footer .pwr-adc-content__menu .hs-menu-wrapper.hs-menu-flow-vertical li,
.pwr-footer-advanced .pwr-adc-content__menu .hs-menu-wrapper.hs-menu-flow-vertical li {
  line-height: 1.25;
}
.pwr-footer .pwr-adc-content__menu .hs-menu-wrapper.hs-menu-flow-vertical li + li,
.pwr-footer-advanced .pwr-adc-content__menu .hs-menu-wrapper.hs-menu-flow-vertical li + li {
  margin-top: 6px;
}

/* ---------- HubSpot form ---------- */

.hs-form .hs-input {

  border-bottom-width: 1px !important;

  border-bottom-color: #ffffff !important;

}

.hs-form .hs-input::placeholder {

  color: #ffffff !important;

  opacity: 1;

}

.hs-form .hs-form-field {

  margin-bottom: 5px !important;

}

.hs-form .hs_submit {

  margin-top: 10px !important;

}

.hs-form input[type="submit"].hs-button {

  font-family: "Inter Tight", Arial !important;

  font-size: 15px !important;

  font-weight: 400 !important;

  line-height: 15px !important;

  letter-spacing: normal !important;

  text-transform: none !important;

  padding: 12px 24px !important;

  background: transparent !important;

  background-color: #000000 !important;

  color: #ffffff !important;

  border: 0.5px solid #ffffff !important;

  border-radius: 6px !important;

  text-decoration: none !important;

}

.hs-form input[type="submit"].hs-button:hover {

  background-color: #ffffff !important;

  color: #000000 !important;

}
.nc-inset p {
  font-size: 25px !important;
  line-height: 1em !important;
}

.nc-inset {
  font-size: 25px !important;
  line-height: 1em !important;
}
/* ── Accordion: Title ─────────────────────────────────────── */
.pwr-accordion__title,
.pwr--light .pwr-accordion__title,
.pwr--dark  .pwr-accordion__title {
  font-size: 16px !important;
  font-weight: 700 !important;
  line-height: 1.4 !important;
}

/* ── Accordion: Description body text ────────────────────── */
.pwr-accordion__desc,
.pwr-rich-text.pwr-accordion__desc,
.pwr-accordion__desc p,
.pwr-accordion__desc span,
.pwr-rich-text.pwr-accordion__desc p,
.pwr-rich-text.pwr-accordion__desc span,
.pwr-accordion.active .pwr-accordion__desc,
.pwr-accordion.active .pwr-accordion__desc p,
.pwr-accordion.active .pwr-accordion__desc span,
.pwr--light .pwr-accordion.active.pwr-accordion--text-only .pwr-accordion__desc,
.pwr--dark  .pwr-accordion.active.pwr-accordion--text-only .pwr-accordion__desc {
  font-size: 16px !important;
  line-height: 1.25 !important;
}
/* ── Request a Callback form only ── */
  .request-callback-form .hs-form label {
    display: none;
  }

  .request-callback-form .hs-form .hs-input::placeholder {
    color: #000000 !important;
  }

  .request-callback-form .hs-form .hs-input {
    border-bottom-color: #000000 !important;
  }

  .request-callback-form .hs-form .hs-form-field {
    margin-bottom: 20px !important;
  }
.request-callback-form .hs-form input[type="submit"],
.request-callback-form .hs-form button[type="submit"] {
  border: 1px solid #000000 !important;
}

.request-callback-form .hs-form input[type="submit"]:hover,
.request-callback-form .hs-form button[type="submit"]:hover {
  border: 1px solid #000000 !important;
  background-color: #ffffff !important;
  color: #000000 !important;
}
.request-callback-form .hs-form .hs-error-msgs label,
.request-callback-form .hs-form .hs-error-msg,
.request-callback-form .hs-form ul.hs-error-msgs li label {
  display: block !important;
  color: #ff0000 !important;
  font-size: 12px !important;
}

/* Global — show HubSpot form error labels on all forms */
.hs-form .hs-error-msgs label,
.hs-form .hs-error-msg,
.hs-form ul.hs-error-msgs li label {
    display: block !important;
    color: #ff0000 !important;
    font-size: 12px !important;
}
  /* These apply globally and don't need scoping */
  .pwr-sec-form {
    padding-left: 0 !important;
    padding-right: 0 !important;
  }

  .pwr-sec-form__intro-sec--vertical {
    margin-bottom: 20px !important;
  }

  @media (max-width: 767px) {
    .pwr-sec-form__form {
      padding: 0px;
    }
  }
/* ---------- Mega menu link arrows ---------- */

.pwr-adc-content__button.pwr-cta--link:not(.pwr-cta--link--back) .cta_button::before,

.pwr-adc-content__button.pwr-cta--link:not(.pwr-cta--link--back) .cta_button::after {

  display: none !important;

}

/* ---------- Mega menu link-back arrow style ---------- */

/* Default state: black text, font-weight 500 */
.pwr-adc-content__button.pwr-cta--link--back .cta_button {
  color: #000000 !important;
  font-weight: 500 !important;
}

/* Re-enable chevron only — .pwr-adc parent raises specificity
   above the display:none rule for .pwr-cta--link buttons */
.pwr-adc .pwr-adc-content__button.pwr-cta--link--back .cta_button::before {
  display: block !important;
}

/* Hide the line — chevron only */
.pwr-adc .pwr-adc-content__button.pwr-cta--link--back .cta_button::after {
  display: none !important;
}

/* Arrow chevron: always gold, faces right */
.pwr-adc .pwr-adc-content__button.pwr-cta--link--back .cta_button::before {
  color: #A28E5C !important;
  transform: translateY(-4px) rotate(45deg) !important;
}

/* Hover: text turns gold, chevron nudges right */
.pwr-adc-content__button.pwr-cta--link--back:hover .cta_button {
  color: #A28E5C !important;
}

.pwr-adc .pwr-adc-content__button.pwr-cta--link--back:hover .cta_button::before {
  color: #A28E5C !important;
  transform: translate(4px, -4px) rotate(45deg) !important;
}

/* ---------- Hamburger submenu arrow ---------- */

.pwr-menu_submenu-arrow {

  display: none !important;

}

.pwr-burger__menu .pwr-a11y-menu .pwr-menu_submenu-btn {

  background-color: transparent !important;

}

.pwr-burger__menu .pwr-a11y-menu .pwr-menu_submenu-arrow {

  display: block !important;

  /* Was #ffffff, which drew a white chevron on a white burger panel, so the
     accordion gave no sign it could be opened. Navy, same as the nav text. */
  color: #1F2759 !important;

  box-shadow: -2px 2px 0px 0px inset !important;

  width: 8px !important;

  height: 8px !important;

  transition: transform 0.18s ease !important;

  /* 135deg points the chevron down: tap to open. */
  transform: translateY(-5px) rotate(135deg) !important;

}

/* Open: flip the chevron up. The class is put on the li by child.js, which
   watches the sub-menu's inline display, because POWER marks the open state
   only with that inline style and nothing in the class list. */
.pwr-burger__menu .pwr-a11y-menu li.cg-submenu-open > .pwr-menu_submenu-btn .pwr-menu_submenu-arrow {

  transform: translateY(1px) rotate(-45deg) !important;

}

/* A thumb-sized target around the chevron. The whole row toggles as well, via
   child.js, but the chevron is what people aim at. */
.pwr-burger__menu li.hs-item-has-children > .pwr-menu_submenu-btn {

  width: 44px !important;

  height: 34px !important;

}

body .pwr--dark form.hs-form ul.inputs-list.hs-error-msgs,
body .pwr-form.pwr--dark form.hs-form ul.inputs-list.hs-error-msgs {
  color: var(--clr-form-error-dk);
  font-size: 14px !important;
}
#skip-to-content { display: none !important; }

.mm-btn .cta_button,
.mm-btn .cta_button:hover,
.mm-btn .cta_button:focus {
  border: none !important;
}

.eyebrow-h1 {
  font-size: 15px;
  font-weight: 500;
  text-transform: uppercase;
  line-height: 0.94em;
  letter-spacing: 2.5px;
  color: #000000;
  margin-bottom: 15px;
}
 /* Center the text + button group together */
.pwr-sec-cta--horizontal .pwr-sec-cta--content {
  justify-content: center !important;
  gap: 20px !important; /* reduced from 60px */
}

/* Stop the text wrapper from stretching to fill all space */
.pwr-sec-cta--horizontal .pwr-sec-cta__hor-text-wrapper {
  flex: 0 1 auto !important;
}
  @media (max-width: 991px) {
  /* Add 20px left/right padding inside the box */
  .pwr-sec-cta.pwr-sec--boxed-w-content-in {
    padding-left: 20px !important;
    padding-right: 20px !important;
  }

  /* Set gap between text and button to 20px */
  .pwr-sec-cta__cta-wrapper:has(.pwr-sec-cta__cta--right) {
    margin-top: 0px !important;
  }
}
/* ---------- Stats & section intro ---------- */



.section-intro {

  margin: 0 !important;

  line-height: 1em;

  font-size: clamp(32px, 8vw, 80px);

}

.section-intro b {

  margin: 0 !important;

  font-weight: 700;

  line-height: 1em;

}

@media (max-width: 1220px) {
  .pwr-sec--boxed-w-content-in {
    margin-left: 0 !important;
    margin-right: 0 !important;
  }

  .pwr-sec-cta:not(.pwr-sec--boxed-w-content-in) .pwr-sec-cta--content.page-center {
    margin-left: 0 !important;
    margin-right: 0 !important;
    max-width: 100% !important;
  }
}

@media (max-width: 1140px) {
  .pwr-sec-txt .page-center {
    margin-left: 0;
    margin-right: 0;
  }
}
/* ---------- Mobile (≤767px) ---------- */

@media (max-width: 767px) {

  #footer-legal-links {

    flex-direction: column !important;

    align-items: flex-start !important;

    gap: 10px !important;

  }

  #footer-legal-links li {

    margin: 0 !important;

  }

  #footer-legal-links li span {

    display: none !important;

  }

  /* REMOVED: this hid footer columns 2, 3 and 4 below 767px, which is every
     footer menu, leaving only the brand column on mobile. Carried over from an
     earlier build where the mobile footer was brand only. The menus are wanted
     on mobile now. */

}

/* ---------- Small mobile (≤575px) ---------- */

@media (max-width: 575px) {

  .page-center {

    margin-left: 0px !important;

    margin-right: 0px !important;

  }

  .pwr-sec--boxed-w-content-in,

  .pwr-sec--boxed-w-content-out,

  .pwr-sec--boxed-w-full {

    margin-left: 10px;

    margin-right: 10px;

  }

}



/** Menu quickfix Maka support **/


.hs-menu-wrapper li a:hover: {color: #A28E5C !important}
.pwr-header.pwr-header--dark-dropdown .hs-menu-children-wrapper li:not(.active-branch) a, .pwr-header.pwr-header--dark-dropdown .hs-menu-children-wrapper li:not(.active-branch) a:after, .pwr-header.pwr-header--dark-dropdown .hs-menu-children-wrapper li:not(.hs-menu-depth-1):hover > a, .pwr-header.pwr-header--dark-dropdown .hs-menu-children-wrapper li:not(.hs-menu-depth-1):hover > a:after, .pwr-header.pwr-header--light-dropdown .hs-menu-children-wrapper li:not(.hs-menu-depth-1):hover > a, .pwr-header.pwr-header--light-dropdown .hs-menu-children-wrapper li:not(.hs-menu-depth-1):hover > a:after{color: #A28E5C !important}



/* ---------- Mega menu positioning fix ---------- */
/* Push the mega menu down to sit flush with the full header bottom (incl. padding) */
.pwr-header-advanced-mms {
  top: 100% !important;
}


/* ---------- Investment Management mega menu, removed 23 Oct 2026 ----------
   Two rules lived here, written for the Count Wealth menu's Focus series and
   Prosperity series columns:

     [data-target="2"] ... .pwr-adc__col:nth-child(3), :nth-child(4)
         { padding-right: 0 !important }
     the same two columns' .cta_button { margin-right: 0 !important }

   That menu no longer exists. In the Count Group mega menu data-target="2" is
   the Advisers panel, so the first rule was stripping 30px of right padding
   from its third column and nothing else: its cards measured 421 wide against
   391 everywhere else, which is why the highlight on Become an adviser ran
   wider than the rest. The second rule was already a no-op, every one of those
   margins computes to 0 on its own.

   Both removed rather than rescoped. Column padding for this menu is set in
   the mega menu block further down, under
   .pwr-header-advanced-mms .pwr-adc__col:nth-child(2) and :nth-child(3). */
.hpx-hero__btns .pwr-cta_button,
.hpx-hero__btns .hpx-hero__cta{ text-transform: none !important; }
/* ---------- Mega menu centering - always centered on visible viewport ---------- */
.pwr-header-advanced-mms {
  left: 50% !important;
  right: auto !important;
  transform: translateX(-50%) !important;
  width: 100vw !important;
}

/* ---------- Burger menu - sub-menus start closed ----------
   This block used to force every sub-menu open with display:block !important,
   which was needed back when the burger read the flat main nav. It also beat
   the inline display POWER writes when you tap a group, so the theme's own
   accordion could never close anything.

   The burger now reads Count Group Mobile Nav, which has a real tree, so the
   accordion is wanted. Plain display:none here, no !important, so POWER's
   slideToggle can write an inline display:block over it on tap and slide it
   shut again on the next tap. child.js collapses whatever POWER expanded at
   init, so every group starts closed on every page. */
.pwr-burger__menu .hs-menu-wrapper ul.hs-menu-children-wrapper {
    display: none;
}

/* ---------- Burger menu - row spacing ----------
   Tighter than the theme default, and tighter again on the children, so each
   group reads as a block rather than one long even list. */
.pwr-burger__menu .hs-menu-wrapper.hs-menu-flow-vertical li.hs-menu-depth-1 > a {
    padding-top: 6px;
    padding-bottom: 6px;
}

.pwr-burger__menu .hs-menu-wrapper ul.hs-menu-children-wrapper > li > a {
    padding-top: 2px;
    padding-bottom: 2px;
}

.pwr-burger__menu .hs-menu-wrapper ul.hs-menu-children-wrapper {
    padding-bottom: 8px;
}

/* ---------- Burger icon - white on transparent header (home page mobile only) ---------- */
.hs-content-name-home-count-wealth .pwr-header--transparent:not(.scroll) .pwr-burger__icon-open span,
.hs-content-name-home-count-wealth .pwr-header--transparent:not(.scroll) .pwr-burger__icon-open::after,
.hs-content-name-home-count-wealth .pwr-header--transparent:not(.scroll) .pwr-burger__icon-open::before {
    background-color: #fff !important;
}
  .mic-logo { width: 252px; height: auto; max-width: 100%; }
  @media (max-width: 600px) {
    .mic-logo { width: 160px; }
  }
/* ---------- Header - reduce horizontal padding to 20px on mobile ---------- */
@media (max-width: 575px) {
    .pwr-header .pwr--full-width {
          padding-left: 20px !important;
          padding-right: 20px !important;
  }
}

/* ---------- Nav menu - center in header ----------
   REMOVED. Superseded by the left-aligned nav further down this file. It only
   ever matched .pwr-header__menu--right, a modifier this header does not carry,
   so it was already dead, but it stated the opposite intent. */
/* ---------- FIX: Hero Parallax coded background vs KDNA module ---------- */
/* When a page contains BOTH "Hero - Parallax" (with its coded/KDNA background
   enabled) and a standalone "KDNA Animated Background" module, HubSpot loads
   kdna-background/module.css, which declares:

       .kdna-bg-module { position: relative; }

   The hero's gradient layer carries both classes (.hpx-hero__coded
   .kdna-bg-module) and hero-parallax styles it position:absolute; inset:0 so
   it fills the hero. Both selectors are a single class, so specificity ties
   and load order decides. kdna-background loads later and wins, the layer
   collapses to 0 height, its canvas never sizes past the 300x150 default,
   and the hero renders white.

   Two classes here beats one, so this holds regardless of load order. */

.hpx-hero__coded.kdna-bg-module {
  position: absolute !important;
  top: 0 !important;
  right: 0 !important;
  bottom: 0 !important;
  left: 0 !important;
}

/* ---------- Header height ----------
   The header has no height property. It is 105px of padding in two layers:

     10px  .pwr-header                            padding: 10px 0
     20px  .pwr--full-width.pwr-header--padding   padding: 20px 80px
     45px  .pwr-header-full                       logo + menu row, padding 0
     20px  .pwr-header--padding
     10px  .pwr-header
     -----
     105px

   Dropping the inner wrapper to 10/10 gives 85px total. Each 1px removed
   takes 2px off the header.

   Floor is the logo: it is 150x55 (Page Settings > Header Settings > Logo)
   sitting in a 45px row, hence .pwr-header-logo is absolutely positioned at
   top: 22.5px. At 85px the inner box is 65px, so the logo keeps 5px of
   clearance each side. Go much below this and shrink the logo first.

   Note .pwr-header__menu is position:absolute, so the 20px link padding set
   in the site-wide head HTML does NOT affect header height. Only these do. */

.pwr-header .pwr--full-width.pwr-header--padding {
  padding-top: 10px !important;
  padding-bottom: 10px !important;
}


/* ================================================================================
   COUNT GROUP BUTTON SYSTEM
   ================================================================================
   Three tiers, five core states, plus hover+focus, active+focus, loading and a
   visited reset.

   Every colour is Heritage Navy #1F2759 (Brand Guidelines 1.2 p15, Pantone
   2119C), which the guide calls the anchor of the palette. The states are not
   separate colours: each is Heritage Navy with a white or black overlay, at the
   alpha that reproduces the lightness step shown on the client's button sheet.
   Change --cg-btn-navy and the whole system follows.

     hover              white  5% over navy
     active             black 61% over navy
     secondary hover    navy  15% over white
     secondary active   navy  21% over white
     tertiary hover     white  9% over navy
     tertiary active    white 23% over navy
     tertiary disabled  white 37% over navy
     disabled fill      navy  54% over white

   The hexes the client's PNG appears to show (#1B2F4A and its ramp) are the
   same colours shifted by a colour profile conversion in the export, not a
   second navy. The values below are the guide's.

   Nothing here needs a markup change. The tier lists below map the existing
   POWER CTA classes, the HubSpot form submit button and our own module buttons
   onto the same tokens, so pages already published pick the new style up on
   upload. New markup can use .cg-btn + .cg-btn--primary / --secondary / --tertiary
   directly.

   Deliberately NOT mapped, because they are text links or structural elements
   rather than buttons:
     .pwr-cta--link, .pwr-cta--link--back   theme inline link CTAs
     .pwr-cta--custom-01..04, --cwc-custom  per-instance colours set in the editor
     .cwtbl__link                           linked table cell
     .cwteam-card__btn                      the whole team card, not a button
     .cgl-btn--link                         underlined reset link
     .cwib__link                            image-box arrow link
     .pwr-touch-btn                         carousel arrow control
   ================================================================================ */

:root{
  /* fills */
  --cg-btn-navy:          #1F2759;
  --cg-btn-navy-hover:    #2B3262;
  --cg-btn-navy-active:   #0C0F23;
  --cg-btn-disabled:      #868AA5;

  /* secondary, on light */
  --cg-btn-sec-hover:     #DEDFE7;
  --cg-btn-sec-active:    #D0D2DD;
  --cg-btn-sec-disabled:  #868AA5;

  /* tertiary, on the navy panel */
  --cg-btn-ter-hover:     #333A67;
  --cg-btn-ter-active:    #52587F;
  --cg-btn-ter-disabled:  #727796;

  --cg-btn-on-dark:       #FFFFFF;

  /* geometry and type. Full pill on every tier. */
  --cg-btn-radius:        999px;
  --cg-btn-pad-y:         14px;
  --cg-btn-pad-x:         24px;
  --cg-btn-min-h:         48px;

  /* small size, for Custom Size 02 and the theme's Small CTA option.
     14 + 14 + 18 + 2px border = 48. 11 + 11 + 16 + 2 = 40. */
  --cg-btn-pad-y-sm:      11px;
  --cg-btn-pad-x-sm:      20px;
  --cg-btn-min-h-sm:      40px;
  --cg-btn-size-sm:       14px;
  --cg-btn-lh-sm:         16px;
  --cg-btn-size:          15px;
  --cg-btn-weight:        600;
  --cg-btn-lh:            18px;

  /* focus ring: 2px, held 2px clear of the edge so it reads on a filled button */
  --cg-btn-ring-w:        2px;
  --cg-btn-ring-off:      2px;

  --cg-btn-ease:          .18s ease;
}

/* NOTE ON .cta_button
   The theme emits two class names for the same thing. Most CTAs render as
   .pwr-cta_button, but the mega menu's content button (pwr-adc-content__button)
   emits the unprefixed .cta_button, which then falls through to the theme's own
   .cta_button:not(.pwr-cta--hubspot-style){border-radius:var(--br-btn)} at 6px.
   Every selector below that names .pwr-cta_button therefore has a .cta_button
   twin. The wrapper class still scopes it, so the mega menu's pwr-cta--link
   items are untouched. */

/* ---------- shared shape and type ---------------------------------------- */

.cg-btn,
.pwr-cta--primary-solid .pwr-cta_button,
.pwr-cta--primary-solid .cta_button,
.pwr-cta--regular-solid .pwr-cta_button,
.pwr-cta--regular-solid .cta_button,
.pwr-cta--regular-solid-primary-background .pwr-cta_button,
.pwr-cta--regular-solid-primary-background .cta_button,
.pwr-cta--hubspot-style .pwr-cta_button,
.pwr-cta--hubspot-style .cta_button,
.pwr-cta--primary-border .pwr-cta_button,
.pwr-cta--primary-border .cta_button,
.pwr-cta--regular-border .pwr-cta_button,
.pwr-cta--regular-border .cta_button,
.hs-form input[type="submit"].hs-button,
.hs-form button[type="submit"].hs-button,
.request-callback-form .hs-form input[type="submit"],
.request-callback-form .hs-form button[type="submit"],
.csb .csb__cta,
.cwloc-card__cta > a,
.cgl-btn--primary,
.cgl-btn--ghost,
.hpx-hero__cta{
  display: inline-flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 8px !important;
  box-sizing: border-box !important;
  min-height: var(--cg-btn-min-h) !important;
  padding: var(--cg-btn-pad-y) var(--cg-btn-pad-x) !important;
  border-radius: var(--cg-btn-radius) !important;
  border: 1px solid transparent !important;
  font-family: "Inter Tight", Arial, sans-serif !important;
  font-size: var(--cg-btn-size) !important;
  font-weight: var(--cg-btn-weight) !important;
  line-height: var(--cg-btn-lh) !important;
  letter-spacing: normal !important;
  text-transform: none !important;
  text-decoration: none !important;
  text-align: center !important;
  cursor: pointer !important;
  appearance: none !important;
  transition: background-color var(--cg-btn-ease),
              color var(--cg-btn-ease),
              border-color var(--cg-btn-ease) !important;
}

/* POWER paints its hover fill with a ::before layer. It would sit over ours. */
.pwr-cta--primary-solid .pwr-cta_button::before,
.pwr-cta--primary-solid .cta_button::before,
.pwr-cta--regular-solid .pwr-cta_button::before,
.pwr-cta--regular-solid .cta_button::before,
.pwr-cta--regular-solid-primary-background .pwr-cta_button::before,
.pwr-cta--regular-solid-primary-background .cta_button::before,
.pwr-cta--hubspot-style .pwr-cta_button::before,
.pwr-cta--hubspot-style .cta_button::before,
.pwr-cta--primary-border .pwr-cta_button::before,
.pwr-cta--primary-border .cta_button::before,
.pwr-cta--regular-border .pwr-cta_button::before,
.pwr-cta--regular-border .cta_button::before{
  display: none !important;
}

/* ---------- primary ------------------------------------------------------ */

.cg-btn--primary,
.pwr-cta--primary-solid .pwr-cta_button,
.pwr-cta--primary-solid .cta_button,
.pwr-cta--regular-solid .pwr-cta_button,
.pwr-cta--regular-solid .cta_button,
.pwr-cta--regular-solid-primary-background .pwr-cta_button,
.pwr-cta--regular-solid-primary-background .cta_button,
.pwr-cta--hubspot-style .pwr-cta_button,
.pwr-cta--hubspot-style .cta_button,
.hs-form input[type="submit"].hs-button,
.hs-form button[type="submit"].hs-button,
.request-callback-form .hs-form input[type="submit"],
.request-callback-form .hs-form button[type="submit"],
.csb .csb__cta--solid,
.cgl-btn--primary{
  background-color: var(--cg-btn-navy) !important;
  border-color: var(--cg-btn-navy) !important;
  color: #FFFFFF !important;
}
.cg-btn--primary:hover,
.pwr-cta--primary-solid .pwr-cta_button:hover,
.pwr-cta--primary-solid .cta_button:hover,
.pwr-cta--regular-solid .pwr-cta_button:hover,
.pwr-cta--regular-solid .cta_button:hover,
.pwr-cta--regular-solid-primary-background .pwr-cta_button:hover,
.pwr-cta--regular-solid-primary-background .cta_button:hover,
.pwr-cta--hubspot-style .pwr-cta_button:hover,
.pwr-cta--hubspot-style .cta_button:hover,
.hs-form input[type="submit"].hs-button:hover,
.hs-form button[type="submit"].hs-button:hover,
.request-callback-form .hs-form input[type="submit"]:hover,
.request-callback-form .hs-form button[type="submit"]:hover,
.csb .csb__cta--solid:hover,
.cgl-btn--primary:hover{
  background-color: var(--cg-btn-navy-hover) !important;
  border-color: var(--cg-btn-navy-hover) !important;
  color: #FFFFFF !important;
}
.cg-btn--primary:active,
.pwr-cta--primary-solid .pwr-cta_button:active,
.pwr-cta--primary-solid .cta_button:active,
.pwr-cta--regular-solid .pwr-cta_button:active,
.pwr-cta--regular-solid .cta_button:active,
.pwr-cta--regular-solid-primary-background .pwr-cta_button:active,
.pwr-cta--regular-solid-primary-background .cta_button:active,
.pwr-cta--hubspot-style .pwr-cta_button:active,
.pwr-cta--hubspot-style .cta_button:active,
.hs-form input[type="submit"].hs-button:active,
.hs-form button[type="submit"].hs-button:active,
.csb .csb__cta--solid:active,
.cgl-btn--primary:active{
  background-color: var(--cg-btn-navy-active) !important;
  border-color: var(--cg-btn-navy-active) !important;
  color: #FFFFFF !important;
}

/* ---------- secondary ---------------------------------------------------- */

.cg-btn--secondary,
.pwr-cta--primary-border .pwr-cta_button,
.pwr-cta--primary-border .cta_button,
.pwr-cta--regular-border .pwr-cta_button,
.pwr-cta--regular-border .cta_button,
.csb .csb__cta--outline,
.cwloc-card__cta > a,
.cgl-btn--ghost{
  background-color: transparent !important;
  border-color: var(--cg-btn-navy) !important;
  color: var(--cg-btn-navy) !important;
}
.cg-btn--secondary:hover,
.pwr-cta--primary-border .pwr-cta_button:hover,
.pwr-cta--primary-border .cta_button:hover,
.pwr-cta--regular-border .pwr-cta_button:hover,
.pwr-cta--regular-border .cta_button:hover,
.csb .csb__cta--outline:hover,
.cwloc-card__cta > a:hover,
.cgl-btn--ghost:hover{
  background-color: var(--cg-btn-sec-hover) !important;
  border-color: var(--cg-btn-navy) !important;
  color: var(--cg-btn-navy) !important;
}
.cg-btn--secondary:active,
.pwr-cta--primary-border .pwr-cta_button:active,
.pwr-cta--primary-border .cta_button:active,
.pwr-cta--regular-border .pwr-cta_button:active,
.pwr-cta--regular-border .cta_button:active,
.csb .csb__cta--outline:active,
.cwloc-card__cta > a:active,
.cgl-btn--ghost:active{
  background-color: var(--cg-btn-sec-active) !important;
  border-color: var(--cg-btn-navy) !important;
  color: var(--cg-btn-navy) !important;
}

/* ---------- tertiary, for use on the navy panel --------------------------- */
/* One extra class over the secondary selectors, so these win on specificity. */

.cg-btn--tertiary,
.pwr--dark .pwr-cta--primary-border .pwr-cta_button,
.pwr--dark .pwr-cta--regular-border .pwr-cta_button,
.cgl--band-navy .cgl-btn--ghost,
.hpx-hero__cta{
  background-color: transparent !important;
  border-color: var(--cg-btn-on-dark) !important;
  color: var(--cg-btn-on-dark) !important;
}
.cg-btn--tertiary:hover,
.pwr--dark .pwr-cta--primary-border .pwr-cta_button:hover,
.pwr--dark .pwr-cta--regular-border .pwr-cta_button:hover,
.cgl--band-navy .cgl-btn--ghost:hover,
.hpx-hero__cta:hover{
  background-color: var(--cg-btn-ter-hover) !important;
  border-color: var(--cg-btn-on-dark) !important;
  color: var(--cg-btn-on-dark) !important;
}
.cg-btn--tertiary:active,
.pwr--dark .pwr-cta--primary-border .pwr-cta_button:active,
.pwr--dark .pwr-cta--regular-border .pwr-cta_button:active,
.cgl--band-navy .cgl-btn--ghost:active,
.hpx-hero__cta:active{
  background-color: var(--cg-btn-ter-active) !important;
  border-color: var(--cg-btn-on-dark) !important;
  color: var(--cg-btn-on-dark) !important;
}

/* ---------- focus, and the two combined states ----------------------------
   The ring is an outline, not a border, so it composes with hover and active
   for free: the fill changes underneath and the ring stays put. Never add
   outline:none to any of these selectors or both combined states are lost. */

.cg-btn:focus-visible,
.pwr-cta--primary-solid .pwr-cta_button:focus-visible,
.pwr-cta--primary-solid .cta_button:focus-visible,
.pwr-cta--regular-solid .pwr-cta_button:focus-visible,
.pwr-cta--regular-solid .cta_button:focus-visible,
.pwr-cta--regular-solid-primary-background .pwr-cta_button:focus-visible,
.pwr-cta--regular-solid-primary-background .cta_button:focus-visible,
.pwr-cta--hubspot-style .pwr-cta_button:focus-visible,
.pwr-cta--hubspot-style .cta_button:focus-visible,
.pwr-cta--primary-border .pwr-cta_button:focus-visible,
.pwr-cta--primary-border .cta_button:focus-visible,
.pwr-cta--regular-border .pwr-cta_button:focus-visible,
.pwr-cta--regular-border .cta_button:focus-visible,
.hs-form input[type="submit"].hs-button:focus-visible,
.hs-form button[type="submit"].hs-button:focus-visible,
.request-callback-form .hs-form input[type="submit"]:focus-visible,
.request-callback-form .hs-form button[type="submit"]:focus-visible,
.csb .csb__cta:focus-visible,
.cwloc-card__cta > a:focus-visible,
.cgl-btn--primary:focus-visible,
.cgl-btn--ghost:focus-visible{
  outline: var(--cg-btn-ring-w) solid var(--cg-btn-navy) !important;
  outline-offset: var(--cg-btn-ring-off) !important;
}

/* white ring wherever the button sits on navy */
.cg-btn--tertiary:focus-visible,
.pwr--dark .pwr-cta--primary-border .pwr-cta_button:focus-visible,
.pwr--dark .pwr-cta--regular-border .pwr-cta_button:focus-visible,
.cgl--band-navy .cgl-btn--ghost:focus-visible,
.hpx-hero__cta:focus-visible{
  outline-color: var(--cg-btn-on-dark) !important;
}

/* ---------- disabled ------------------------------------------------------ */

.cg-btn:disabled, .cg-btn[disabled], .cg-btn[aria-disabled="true"],
.pwr-cta--primary-solid .pwr-cta_button[aria-disabled="true"],
.pwr-cta--primary-solid .cta_button[aria-disabled="true"],
.pwr-cta--regular-solid .pwr-cta_button[aria-disabled="true"],
.pwr-cta--regular-solid .cta_button[aria-disabled="true"],
.hs-form input[type="submit"].hs-button:disabled,
.hs-form button[type="submit"].hs-button:disabled,
.csb .csb__cta[aria-disabled="true"],
.cgl-btn--primary[disabled]{
  background-color: var(--cg-btn-disabled) !important;
  border-color: var(--cg-btn-disabled) !important;
  color: #FFFFFF !important;
  cursor: default !important;
  pointer-events: none;
  opacity: 1 !important;
}
.cg-btn--secondary:disabled, .cg-btn--secondary[disabled],
.cg-btn--secondary[aria-disabled="true"],
.cwloc-card__cta > a[aria-disabled="true"],
.cgl-btn--ghost[disabled]{
  background-color: transparent !important;
  border-color: var(--cg-btn-sec-disabled) !important;
  color: var(--cg-btn-sec-disabled) !important;
}
.cg-btn--tertiary:disabled, .cg-btn--tertiary[disabled],
.cg-btn--tertiary[aria-disabled="true"],
.cgl--band-navy .cgl-btn--ghost[disabled],
.hpx-hero__cta[aria-disabled="true"]{
  background-color: transparent !important;
  border-color: var(--cg-btn-ter-disabled) !important;
  color: var(--cg-btn-ter-disabled) !important;
}

/* ---------- visited -------------------------------------------------------
   These render as anchors, so a browser or a parent sheet can recolour them
   after a click. Pinned back to the resting colour as a decision, not an
   oversight: a visited CTA looks identical to an unvisited one. */

.cg-btn:visited,
.pwr-cta--primary-solid .pwr-cta_button:visited,
.pwr-cta--primary-solid .cta_button:visited,
.pwr-cta--regular-solid .pwr-cta_button:visited,
.pwr-cta--regular-solid .cta_button:visited,
.pwr-cta--regular-solid-primary-background .pwr-cta_button:visited,
.pwr-cta--regular-solid-primary-background .cta_button:visited,
.pwr-cta--hubspot-style .pwr-cta_button:visited,
.pwr-cta--hubspot-style .cta_button:visited,
.csb .csb__cta--solid:visited,
.cgl-btn--primary:visited{ color: #FFFFFF !important; }

.cg-btn--secondary:visited,
.pwr-cta--primary-border .pwr-cta_button:visited,
.pwr-cta--primary-border .cta_button:visited,
.pwr-cta--regular-border .pwr-cta_button:visited,
.pwr-cta--regular-border .cta_button:visited,
.csb .csb__cta--outline:visited,
.cwloc-card__cta > a:visited{ color: var(--cg-btn-navy) !important; }

.cg-btn--tertiary:visited,
.pwr--dark .pwr-cta--primary-border .pwr-cta_button:visited,
.pwr--dark .pwr-cta--regular-border .pwr-cta_button:visited,
.hpx-hero__cta:visited{ color: var(--cg-btn-on-dark) !important; }

/* ---------- loading -------------------------------------------------------
   Driven by .is-loading, set by cgButtonLoading() in child.js. The button keeps
   its resting width so the layout does not jump, stays focusable so screen
   readers announce aria-busy, and is never also disabled. The spinner is a
   pseudo-element, so this works on <button> and <a> but not on
   <input type="submit"> — HubSpot form submits get the cursor and the width
   hold only. */

@keyframes cg-btn-spin{ to{ transform: rotate(360deg); } }

.cg-btn.is-loading,
.csb .csb__cta.is-loading,
.cgl-btn.is-loading,
.hpx-hero__cta.is-loading,
.pwr-cta_button.is-loading,
.cta_button.is-loading{
  cursor: progress !important;
  pointer-events: none;
}
.cg-btn.is-loading::after,
.csb .csb__cta.is-loading::after,
.cgl-btn.is-loading::after,
.hpx-hero__cta.is-loading::after,
.pwr-cta_button.is-loading::after,
.cta_button.is-loading::after{
  content: "";
  order: -1;
  flex: 0 0 auto;
  width: 1em;
  height: 1em;
  border: 2px solid currentColor;
  border-right-color: transparent;
  border-radius: 50%;
  animation: cg-btn-spin .6s linear infinite;
}
@media (prefers-reduced-motion: reduce){
  .cg-btn.is-loading::after,
  .csb .csb__cta.is-loading::after,
  .cgl-btn.is-loading::after,
  .hpx-hero__cta.is-loading::after,
  .pwr-cta_button.is-loading::after{ animation-duration: 2s; }
}

/* ---------- small screens ------------------------------------------------- */

@media (max-width: 575px){
  :root{
    --cg-btn-pad-x: 20px;
    --cg-btn-min-h: 46px;
  }
}

/* ---------- inverse tier, solid white on dark ------------------------------
   Not in the client's sheet. It exists because Count's dark panels (the notch
   card, the navy half of a two-column card, the hero) carry a solid white
   button rather than the outlined Tertiary. Pending confirmation, see the
   Custom Button 04 note below. */

.cg-btn--inverse{
  background-color: #FFFFFF !important;
  border-color: #FFFFFF !important;
  color: var(--cg-btn-navy) !important;
}
.cg-btn--inverse:hover{
  background-color: var(--cg-btn-sec-hover) !important;
  border-color: var(--cg-btn-sec-hover) !important;
  color: var(--cg-btn-navy) !important;
}
.cg-btn--inverse:active{
  background-color: var(--cg-btn-sec-active) !important;
  border-color: var(--cg-btn-sec-active) !important;
}
.cg-btn--inverse:focus-visible{ outline-color: var(--cg-btn-on-dark) !important; }
.cg-btn--inverse:visited{ color: var(--cg-btn-navy) !important; }
.cg-btn--inverse:disabled, .cg-btn--inverse[aria-disabled="true"]{
  background-color: var(--cg-btn-ter-disabled) !important;
  border-color: var(--cg-btn-ter-disabled) !important;
  color: var(--cg-btn-navy) !important;
}

/* ---------- Custom Button 01 to 04 -----------------------------------------
   These four are configured in Theme editor > Custom Styles, not here, because
   an editor needs to be able to see and change them. The panel only exposes a
   default and a hover, so this block adds the four things it cannot express
   (shape, type, focus, active, disabled) and leaves every colour to the panel.

   Assignment, matching the tiers above:
     Custom Button 01  Primary
     Custom Button 02  Secondary
     Custom Button 03  Tertiary, for dark sections
     Custom Button 04  Inverse, solid white on dark (the hero button)

   Height parity comes from min-height rather than a forced border, so a tier
   set to No Border still lines up with one that has a 1px border. */

.pwr-cta--custom-01 .pwr-cta_button,
.pwr-cta--custom-01 .cta_button,
.pwr-cta--custom-02 .pwr-cta_button,
.pwr-cta--custom-02 .cta_button,
.pwr-cta--custom-03 .pwr-cta_button,
.pwr-cta--custom-03 .cta_button,
.pwr-cta--custom-04 .pwr-cta_button,
.pwr-cta--custom-04 .cta_button{
  display: inline-flex !important;
  align-items: center !important;
  justify-content: center !important;
  gap: 8px !important;
  box-sizing: border-box !important;
  min-height: var(--cg-btn-min-h) !important;
  padding: var(--cg-btn-pad-y) var(--cg-btn-pad-x) !important;
  border-radius: var(--cg-btn-radius) !important;
  font-family: "Inter Tight", Arial, sans-serif !important;
  font-size: var(--cg-btn-size) !important;
  font-weight: var(--cg-btn-weight) !important;
  line-height: var(--cg-btn-lh) !important;
  letter-spacing: normal !important;
  text-transform: none !important;
  text-decoration: none !important;
}

/* focus ring, navy on light tiers and white on the two dark ones */
.pwr-cta--custom-01 .pwr-cta_button:focus-visible,
.pwr-cta--custom-01 .cta_button:focus-visible,
.pwr-cta--custom-02 .pwr-cta_button:focus-visible,
.pwr-cta--custom-02 .cta_button:focus-visible{
  outline: var(--cg-btn-ring-w) solid var(--cg-btn-navy) !important;
  outline-offset: var(--cg-btn-ring-off) !important;
}
.pwr-cta--custom-03 .pwr-cta_button:focus-visible,
.pwr-cta--custom-03 .cta_button:focus-visible,
.pwr-cta--custom-04 .pwr-cta_button:focus-visible,
.pwr-cta--custom-04 .cta_button:focus-visible{
  outline: var(--cg-btn-ring-w) solid var(--cg-btn-on-dark) !important;
  outline-offset: var(--cg-btn-ring-off) !important;
}

/* Pressed. A brightness step rather than a colour, so it works against
   whatever the panel is set to and does not need updating alongside it. */
.pwr-cta--custom-01 .pwr-cta_button:active,
.pwr-cta--custom-01 .cta_button:active,
.pwr-cta--custom-02 .pwr-cta_button:active,
.pwr-cta--custom-02 .cta_button:active,
.pwr-cta--custom-03 .pwr-cta_button:active,
.pwr-cta--custom-03 .cta_button:active,
.pwr-cta--custom-04 .pwr-cta_button:active,
.pwr-cta--custom-04 .cta_button:active{
  filter: brightness(.8) !important;
}

/* Disabled. The panel has no disabled state at all, so these are explicit. */
.pwr-cta--custom-01 .pwr-cta_button[aria-disabled="true"],
.pwr-cta--custom-01 .cta_button[aria-disabled="true"],
.pwr-cta--custom-04 .pwr-cta_button[aria-disabled="true"],
.pwr-cta--custom-04 .cta_button[aria-disabled="true"]{
  background: var(--cg-btn-disabled) !important;
  border-color: var(--cg-btn-disabled) !important;
  color: #FFFFFF !important;
  pointer-events: none; cursor: default !important;
}
.pwr-cta--custom-02 .pwr-cta_button[aria-disabled="true"],
.pwr-cta--custom-02 .cta_button[aria-disabled="true"]{
  background: transparent !important;
  border-color: var(--cg-btn-sec-disabled) !important;
  color: var(--cg-btn-sec-disabled) !important;
  pointer-events: none; cursor: default !important;
}
.pwr-cta--custom-03 .pwr-cta_button[aria-disabled="true"],
.pwr-cta--custom-03 .cta_button[aria-disabled="true"]{
  background: transparent !important;
  border-color: var(--cg-btn-ter-disabled) !important;
  color: var(--cg-btn-ter-disabled) !important;
  pointer-events: none; cursor: default !important;
}

/* ---------- small size -----------------------------------------------------
   Theme editor > Custom Styles > Custom Sizes drives padding, font size and
   line height for the POWER CTA variants. The system above pins the standard
   size, so this is what makes the small option in the style dropdown still do
   something. Custom Size 01 is the standard, Custom Size 02 is the small.

   Set the panel to match these numbers so the editor preview tells the truth:
     Custom Size 01   padding 14 / 24   font 15   line height 18
     Custom Size 02   padding 11 / 20   font 14   line height 16 */

.cg-btn--sm,
/* the stats bar buttons carry their own .csb__cta class, which the base rule
   above matches at (0,2,0). A bare .cg-btn--sm is (0,1,0), so with both rules
   !important the base one would win and the small size would silently do
   nothing. This selector raises it past that. */
.csb .csb__cta.cg-btn--sm,
.pwr-cta--small .pwr-cta_button,
.pwr-cta--small .cta_button,
.pwr-cta--custom-size-02 .pwr-cta_button,
.pwr-cta--custom-size-02 .cta_button,
.pwr-cta--custom-size-02.pwr-cta--custom-01 .pwr-cta_button,
.pwr-cta--custom-size-02.pwr-cta--custom-01 .cta_button,
.pwr-cta--custom-size-02.pwr-cta--custom-02 .pwr-cta_button,
.pwr-cta--custom-size-02.pwr-cta--custom-02 .cta_button,
.pwr-cta--custom-size-02.pwr-cta--custom-03 .pwr-cta_button,
.pwr-cta--custom-size-02.pwr-cta--custom-03 .cta_button,
.pwr-cta--custom-size-02.pwr-cta--custom-04 .pwr-cta_button,
.pwr-cta--custom-size-02.pwr-cta--custom-04 .cta_button{
  min-height: var(--cg-btn-min-h-sm) !important;
  padding: var(--cg-btn-pad-y-sm) var(--cg-btn-pad-x-sm) !important;
  font-size: var(--cg-btn-size-sm) !important;
  line-height: var(--cg-btn-lh-sm) !important;
}


/* ---------- Header side padding and left-aligned nav ---------- */

/* Header: 40px side padding from 576px up (the theme keeps 20px on mobile) */
@media (min-width: 576px) {
  .pwr-header .pwr--full-width.pwr-header--padding {
    padding-left: 40px !important;
    padding-right: 40px !important;
  }
}

/* Nav: left-aligned, 73px after the logo (the theme centres it with left:50%).
   !important because the theme's own rule is in a cross-origin stylesheet, so its
   specificity cannot be read and matched. Measured on staging: .pwr-header__menu
   is position:absolute against a containing block that starts at the padding
   edge, so `left` is offset from the logo's own left edge, and the 40px change
   above carries it across without altering the 73px gap.
   100px is the logo's rendered width. Change it if the logo is ever resized in
   Page Settings > Header Settings. */
.pwr-header .pwr--full-width .pwr-header__menu {
  left: calc(100px + 73px) !important; /* logo width + gap */
  transform: translateY(-50%) !important;
}


/* ---------- Inline font-weight tags ----------
   <sb>Why the profession</sb> chooses Count

   sb is not a real HTML element. Browsers render any unknown tag as a plain
   inline box, so it needs nothing but a weight. It survives because these
   heading fields are plain text printed with |safe, not rich text, so no
   sanitiser sees it.

   Use inside the heading text fields on image-boxes, count-stats-bar and
   sec-text, exactly like <b>. The class form is there for rich text fields,
   where the editor may strip an unknown tag.

   sb   semibold 600
   md   medium   500
   lt   light    300
   b / strong stay at 700, set per module. */

sb, .sb { font-weight: 600; }
md, .md { font-weight: 500; }
lt, .lt { font-weight: 300; }


/* ---------- Footer: divider between the columns and the legal sub area ----------
   The theme's own Border setting draws this on .pwr-adc-sub, which is
   pwr--full-width, so the rule runs edge to edge past the footer's padding.

   Measured on staging at 1965px: .pwr-adc-sub and its .pwr-adc__col both span
   L10 to R1949, but the column carries 30px side padding, so its content box is
   L40 to R1919. That is exactly where the footer columns' text starts above it.
   Drawing the border on the content box therefore lines it up with the columns
   at every breakpoint, with no widths hardcoded here.

   The first rule cancels the theme's version so this works whether the Border
   setting is None or Top. The theme's own border colour is white at 35%; this
   is solid white, set deliberately rather than inherited. */

.pwr-footer .pwr-adc-sub {
  border-top: 0 !important;
}

.pwr-footer .pwr-adc-sub .pwr-adc-content--text {
  border-top: 1px solid #ffffff;
  padding-top: 40px;
}

/* The sub area's own top padding sits above the rule. Zero it so the 40px below
   is the only gap, otherwise the line drifts down away from the columns. */
.pwr-footer .pwr-adc-sub.pwr--padding-b-0,
.pwr-footer .pwr-adc-sub {
  padding-top: 0 !important;
}


/* ---------- Stats bar tablet split: drop the map below ----------
   Pairs with "Tablet: heading beside stats" in the Count Stats Bar module.
   When that is on the module renders .csb--split and lays its heading and stats
   side by side, which needs the full row width, so the map column beside it has
   to move underneath.

   HubSpot stacks dnd columns at 767px by default, which is too late here.
   Scoped with :has() to .span6 specifically, and only in rows that actually
   contain a .csb--split, so no other two-column row on the site is touched. A
   looser selector would match every ancestor row-fluid as well.

   The 1199px must match the module's own media query. */

@media (max-width: 1199px) {
  .row-fluid > .span6:has(.csb--split),
  .row-fluid > .span6:has(.csb--split) ~ .span6,
  .row-fluid > .span6:has(+ .span6 .csb--split),
  .row-fluid > .span6:has(~ .span6 .csb--split) {
    width: 100% !important;
    margin-left: 0 !important;
    float: none !important;
  }
}


/* ---------- Footer: outer box inset ----------
   The black panel is .pwr-footer itself, and the theme gives it a horizontal
   margin that widens at smaller viewports. Measured at 889px wide: margin 40px
   each side, so the box sat 40px in from the page edge instead of 10px.

   This is the gap OUTSIDE the black box. The 30px of padding on each
   .pwr-adc__col is a separate thing and is left alone: it is the gutter between
   the footer menus. */

.pwr-footer {
  margin-left: 10px !important;
  margin-right: 10px !important;
}


/* ---------- Body paragraphs: 16px on mobile ----------
   Scoped to rich text rather than a bare `p`, because a blanket rule would also
   hit the stats footnote, the footer legal block, badges and card labels, all of
   which are deliberately smaller.

   Two exclusions:
     [style*="font-size"]  an editor set the size inline on that paragraph, so
                           leave it alone. This is what keeps the 12px footer
                           legal text at 12px.
     .csb__foot            the stats footnote sets 12.5px on the container and
                           has its paragraphs inherit it, so there is no inline
                           size for the rule above to catch.

   575px matches the phone breakpoint used everywhere else in this file and in
   the modules. Change it to 767px if mobile should include portrait tablets. */

@media (max-width: 575px) {
  .pwr-rich-text p:not([style*="font-size"]),
  .widget-type-rich_text p:not([style*="font-size"]),
  .hs_cos_wrapper_type_rich_text p:not([style*="font-size"]) {
    font-size: 16px !important;
  }

  /* Editors usually wrap a resized run in <span style="font-size:20px">, which
     sits INSIDE the paragraph, so the rule above sets the <p> and the span then
     overrides it on the child.

     Deliberately limited to paragraphs and their contents. An earlier version
     matched any inline-sized element and flattened headings and eyebrows too:
     an <h4 style="font-size:24px"> and a <div style="font-size:13px"> eyebrow
     both got forced to 16px. Headings and non-paragraph blocks keep whatever
     size they are given.

     The two :not()s keep this out of the footer legal block and the stats
     footnote, where the inline sizes on the paragraphs are deliberate. */
  .pwr-rich-text:not(.pwr-adc-content__text):not(.csb__foot) p[style*="font-size"],
  .pwr-rich-text:not(.pwr-adc-content__text):not(.csb__foot) p [style*="font-size"],
  .widget-type-rich_text p[style*="font-size"],
  .widget-type-rich_text p [style*="font-size"],
  .hs_cos_wrapper_type_rich_text p[style*="font-size"],
  .hs_cos_wrapper_type_rich_text p [style*="font-size"] {
    font-size: 16px !important;
  }

  .csb__foot p,
  .pwr-footer .pwr-adc-content__text p {
    font-size: inherit !important;
  }
}


/* ---------- Footer menus two-up on mobile ----------
   Below 767px the brand block takes the full width and the three menu columns
   sit two per row. Scoped to .pwr-adc-main__cols so the legal sub area below is
   untouched.

   The theme's 30px column padding is left in place so the menus stay in line
   with the logo and address above. That leaves roughly 117px of text width per
   column on a 375px screen, so the longer labels wrap. If that is too tight,
   the padding is the thing to reduce, not the alignment.

   Note this is the same 767px breakpoint the old hide rule used, so the menus
   appear two-up at exactly the width they used to disappear. */

@media (max-width: 767px) {
  .pwr-footer .pwr-adc-main__cols {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-start;
  }

  /* The theme's own 30px column padding is kept, so the menus line up with the
     logo and address above them exactly as they do on desktop. An earlier
     version zeroed it to win back width, which pushed the menus out of line
     with the rest of the footer. */
  .pwr-footer .pwr-adc-main__cols > .pwr-adc__col {
    float: none !important;
    margin-left: 0 !important;
    box-sizing: border-box;
  }

  /* brand block: logo, phone, Contact Us, address, socials */
  .pwr-footer .pwr-adc-main__cols > .pwr-adc__col:first-child {
    flex: 0 0 100%;
    width: 100% !important;
  }

  /* the three menu columns */
  .pwr-footer .pwr-adc-main__cols > .pwr-adc__col:nth-child(n + 2) {
    flex: 0 0 50%;
    width: 50% !important;
  }

  /* Pull Accountants up into the space left under Equity Partners.
     Row one is as tall as the taller of its two columns. Measured at a 390px
     viewport: Why Count + Equity Partners is 306px, Advisers + Investors is
     386px, so 80px of the row sits empty under the left column and Accountants
     starts below all of it.

     Pulling the full 80px puts Accountants hard against the bottom of Equity
     Partners, so the pull leaves a gap rather than closing it. Set by eye on
     device at -30px, which leaves 50px of clearance.

     This is a fixed number, not a calculation: CSS cannot measure the two
     columns against each other. It is right for the current menus and will need
     revisiting if links are added or removed, or if a label starts wrapping to
     a new line at some width. The structural fix is one menu per column, which
     removes the need for this entirely. */
  .pwr-footer .pwr-adc-main__cols > .pwr-adc__col:nth-child(4) {
    margin-top: -30px;
  }
}


/* ---------- ASX price bar above the header ----------
   Full-width navy strip, figure right aligned, with a brighter rule under it.
   Monospace so the price does not jitter horizontally when a digit changes.

   The [hidden] attribute is set in the markup and removed by child.js once a
   price arrives, so nothing reserves space if the request fails. display:none
   here beats the flex below, which would otherwise override [hidden].

   THE HEADER OFFSET BELOW IS THE LOAD-BEARING PART. .pwr-header is
   position:fixed, top:0, z-index:1000 with a white background and 85px of
   height, so it paints straight over this bar while the bar's height stays in
   the flow. The result is a taller gap at the top of the page with nothing
   visible in it, which is exactly what it looked like before this rule existed.

   Pushing the fixed header down by the bar's height only applies before the
   page scrolls. POWER adds .scroll once scrolling starts, at which point the
   bar has scrolled away and the header should sit flush at the top again.

   One token drives both the bar's height and the header offset so the two can
   never drift apart. 29px at every width: the bar is short enough that the
   mobile padding and type size are the only things worth changing. */

:root {
  --cg-ticker-h: 29px;
}

.cg-ticker[hidden] { display: none !important; }

.cg-ticker {
  display: flex;
  align-items: center;
  justify-content: flex-end;
  min-height: var(--cg-ticker-h);
  background: var(--cg-btn-navy, #1F2759);
  border-bottom: 2px solid #1E548D;
  box-sizing: border-box;
}

/* the inner is a flex box too, so the value is centred against the bar's content
   box rather than sitting on a text baseline. The 2px rule lives outside that
   content box under border-box sizing, so centring here reads as centred in the
   navy, not in the navy plus the rule. */
.cg-ticker__inner {
  display: flex;
  align-items: center;
  padding: 0 40px;
}

.cg-ticker__value {
  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
  font-size: 11px;
  font-weight: 500;
  letter-spacing: .06em;
  line-height: 1;
  color: #B9CBDF;
  white-space: nowrap;
}

/* sit the fixed header below the bar until the page scrolls */
.pwr-header.pwr-header-fixed:not(.scroll),
#pwr-header-fixed:not(.scroll) {
  top: var(--cg-ticker-h) !important;
}

/* if the price never arrived the bar stays hidden and takes no space, so the
   header has to go back to the top or it leaves a blank strip */
body:has(.cg-ticker[hidden]) .pwr-header.pwr-header-fixed:not(.scroll),
body:has(.cg-ticker[hidden]) #pwr-header-fixed:not(.scroll) {
  top: 0 !important;
}

@media (max-width: 767px) {
  .cg-ticker__inner { padding: 0 20px; }
}


/* ===========================================================================
   FAQ accordion toggle — Count About page
   The reference draws the open/close control as a 26 x 26 ring with a 12px
   bar, filled black. The POWER parent supplies its own glyph on
   .pwr-accordion__icon, so the content is neutralised and the ring is rebuilt
   from the element's own border plus two bars. Scoped to .cg-faq so no other
   accordion on the site is touched.
   ======================================================================== */
.cg-faq .pwr-accordion__icon{
  content:none !important;
  width:26px !important; height:26px !important;
  min-width:26px; min-height:26px;
  box-sizing:border-box !important;
  /* currentColor so the ring tracks the row's text colour. The module's
     own hover and active rules set the colour on .pwr-accordion__title and
     the icon inherits it, so the control can never fall out of step with
     the type again. */
  border:2px solid currentColor !important;
  border-radius:50% !important;
  background:none !important;
  font-size:0 !important;
  position:absolute;
  right:28px;
  top:50%;
  transform:translateY(-50%);
  transition:none;
}
.cg-faq .pwr-accordion__icon::before,
.cg-faq .pwr-accordion__icon::after{
  content:"" !important;
  position:absolute;
  left:50%; top:50%;
  background:currentColor !important;
  border:0 !important;
  transform:translate(-50%,-50%) !important;
  transition:opacity .2s ease;
}
/* horizontal bar: always on, so the control reads as a minus when open */
.cg-faq .pwr-accordion__icon::before{ width:12px; height:2px; }
/* vertical bar: hidden once the row is open */
.cg-faq .pwr-accordion__icon::after{ width:2px; height:12px; opacity:1; }
.cg-faq .pwr-accordion__icon.active::after,
.cg-faq .pwr-accordion__title.active .pwr-accordion__icon::after,
.cg-faq .active > .pwr-accordion__icon::after{ opacity:0; }

/* room for the ring at the end of the question row */
.cg-faq .pwr-accordion__title{ position:relative; padding-right:76px !important; }
@media (max-width:767px){
  .cg-faq .pwr-accordion__icon{ right:20px; }
  .cg-faq .pwr-accordion__title{ padding-right:62px !important; }
}


/* ===========================================================================
   Count About page — type the theme's own scale gets wrong
   Rich-text headings inside a module fall through to the POWER heading scale,
   which is not the scale in the reference design. These pin the two that came
   in wrong. Both values are read off the Framer layers, not measured.
   ======================================================================== */

/* Notch card text panel title: Framer reads 32px / 35px, Heritage Navy.
   Scoped to the notch card's text panel, so ordinary h3s are untouched. */
.nc-panel.nc-text h3{
  font-size:32px;
  line-height:35px;
  font-weight:400;
  margin:0 0 16px;
  color:#1F2759;
}
.nc-panel.nc-text h3 sb,
.nc-panel.nc-text h3 .sb{ font-weight:600; }

/* Panel body copy: Framer token "Body 3", 16px / 22px. Measured line pitch in
   the reference is 22.0px, which is that token exactly. */
.nc-panel.nc-text p{
  font-size:16px;
  line-height:22px;
  margin:0;
  color:#1F2759;
}
.nc-panel.nc-text p + p{ margin-top:16px; }

/* Body copy in the title-left / body-right section. sec-text has no body
   colour field, so without this the copy takes the theme's global text colour.
   Framer token "Light Grey" = #6C7178. */
.pwr-sec-txt--right .pwr-sec-txt__right,
.pwr-sec-txt--right .pwr-sec-txt__right p{ color:#6C7178; }


/* FAQ open and hover state. The theme paints the open row from its primary
   colour (navy) and flips the type to white; the reference keeps every row
   white with dark type and only the ring changes. Scoped to .cg-faq. */
.cg-faq .pwr-accordion.active .pwr-accordion__title,
.cg-faq .pwr-accordion.active .pwr-accordion__desc,
.cg-faq .pwr-accordion:hover .pwr-accordion__title,
.cg-faq .pwr-accordion:hover .pwr-accordion__desc{
  background-color:#FFFFFF !important;
}
.cg-faq .pwr-accordion.active .pwr-accordion__title,
.cg-faq .pwr-accordion:hover .pwr-accordion__title{ color:#141414 !important; }
.cg-faq .pwr-accordion.active .pwr-accordion__desc,
.cg-faq .pwr-accordion:hover .pwr-accordion__desc{ color:#5C6066 !important; }
.cg-faq .pwr-accordion.active .pwr-accordion__icon,
.cg-faq .pwr-accordion:hover .pwr-accordion__icon{ border-color:currentColor !important; }
.cg-faq .pwr-accordion.active .pwr-accordion__icon::before,
.cg-faq .pwr-accordion.active .pwr-accordion__icon::after,
.cg-faq .pwr-accordion:hover .pwr-accordion__icon::before,
.cg-faq .pwr-accordion:hover .pwr-accordion__icon::after{ background:currentColor !important; }

/* Heading to first row. Measured on the reference: the h2's line box sits 20px
   above the first card. The theme ships 60px, plus a description block. */
.cg-faq .pwr-sec__intro-sec{ margin-bottom:20px !important; }
.cg-faq .pwr-sec__desc{ margin-top:0 !important; }

/* ==========================================================================
   Leadership & Board page
   Reference: Framer /why-count/leadership, desktop frame.
   ========================================================================== */

/* Meet the Team — the reference leaves 24px between the heading and the tab
   row. The theme ships 60px below a section intro. */
.cg-team-head .pwr-sec__intro-sec{ margin-bottom: 0 !important; }
.cg-team{ margin-top: 24px; }

/* Governance callout — PWR Sec CTA, layout "horizontal".
   Structure the module renders:
     .cg-governance > .pwr-sec-cta--content.page-center
         > .pwr-sec-cta__hor-text-wrapper   (eyebrow + title)
         > .pwr-sec-cta__cta-wrapper        (one .pwr-cta div per button)
   The reference panel is the container width with the links beside the
   heading, so the box is pinned to 1140 and the button wrapper is made a row.
   The theme stacks the buttons and page-center re-centres the content inside
   the box, which is what pushed everything into the middle. */
.cg-governance{
  max-width: 1140px; margin-left: auto; margin-right: auto;
  /* Reference panel padding. pwr-sec--boxed-w-content-in ships 40. */
  padding-left: 72px !important; padding-right: 72px !important;
}
/* The theme centres this row and sizes the text wrapper flex:0 1 auto, which is
   what pushed the heading and the links into the middle of the panel. */
.cg-governance > .pwr-sec-cta--content.page-center{
  max-width: none; padding-left: 0; padding-right: 0; margin-left: 0; margin-right: 0;
  display: flex; align-items: center; justify-content: space-between !important; gap: 24px;
}
.cg-governance .pwr-sec-cta__hor-text-wrapper{
  flex: 1 1 auto !important; max-width: 583px; text-align: left !important;
  margin-left: 0 !important; margin-right: 0 !important;
}
.cg-governance .pwr-sec-cta__title,
.cg-governance .cg-eyebrow{ text-align: left !important; }
.cg-governance .pwr-sec-cta__cta-wrapper{
  /* The theme lays this wrapper out as a column, which is what was stacking
     the two links on top of each other. */
  flex: 0 0 auto; display: flex; flex-direction: row; flex-wrap: nowrap;
  align-items: center; justify-content: flex-end; gap: 12px; margin: 0;
  width: auto; max-width: none;
}
.cg-governance .pwr-sec-cta__cta-wrapper .pwr-cta_button,
.cg-governance .pwr-sec-cta__cta-wrapper .cta_button{ white-space: nowrap; }
.cg-governance .pwr-sec-cta__cta-wrapper > .pwr-cta{ margin: 0; }

.cg-governance .pwr-sec-cta__title{ color: #FFFFFF !important; font-size: 36px; line-height: 36px; margin: 0; }
.cg-governance .cg-eyebrow{
  display: block;
  font-size: 14px;
  line-height: 1.2;
  letter-spacing: 2px;
  font-weight: 600;
  text-transform: uppercase;
  margin-bottom: 18px;
}

/* Governance: white pill, navy label. child.css paints every solid variant
   navy, which disappears on the navy panel. */
.cg-governance .pwr-cta--primary-solid .pwr-cta_button,
.cg-governance .pwr-cta--primary-solid .cta_button{
  background-color: #FFFFFF !important;
  border-color: #FFFFFF !important;
  color: #1F2759 !important;
}
.cg-governance .pwr-cta--primary-solid .pwr-cta_button:hover,
.cg-governance .pwr-cta--primary-solid .cta_button:hover{
  background-color: #DDE5EE !important;
  border-color: #DDE5EE !important;
  color: #1F2759 !important;
}
/* Board Charter: outlined white. */
.cg-governance .pwr-cta--regular-border .pwr-cta_button,
.cg-governance .pwr-cta--regular-border .cta_button{
  background-color: transparent !important;
  border-color: #FFFFFF !important;
  color: #FFFFFF !important;
}
.cg-governance .pwr-cta--regular-border .pwr-cta_button:hover,
.cg-governance .pwr-cta--regular-border .cta_button:hover{
  background-color: rgba(255, 255, 255, 0.12) !important;
  border-color: #FFFFFF !important;
  color: #FFFFFF !important;
}

@media (max-width: 1199px){
  /* Same centring to undo below the desktop breakpoint: the theme keeps
     justify-content:center and its own text alignment on this row. */
  .cg-governance{ padding-left: 28px !important; padding-right: 28px !important; }
  .cg-governance > .pwr-sec-cta--content.page-center{
    display: block !important;
    text-align: left !important;
  }
  .cg-governance .pwr-sec-cta__title,
  .cg-governance .cg-eyebrow{ text-align: left !important; }
  .cg-governance .pwr-sec-cta__title{ font-size: 32px; line-height: 35px; }
  .cg-governance .pwr-sec-cta__hor-text-wrapper{
    max-width: none; margin-left: 0 !important; margin-right: 0 !important;
  }
  .cg-governance .pwr-sec-cta__cta-wrapper{
    /* The theme zeroes the top margin here, so this needs the same weight as
       the left/right overrides above. */
    margin-top: 28px !important; margin-left: 0 !important; margin-right: 0 !important;
    justify-content: flex-start !important; flex-wrap: wrap; flex-direction: row;
  }
}

/* ---------- Governance callout, phone ----------
   On a phone the two links are stacked and run the full width of the panel,
   as the mockup has them. Everything above keeps them in a row, which is what
   left them side by side and cramped at 320.

   The wrapper has to be widened as well as switched to a column. It is
   width:auto further up so it can hug the buttons on desktop, and a column of
   auto width shrinks to the widest button rather than filling the panel, so
   stacking alone produced two narrow buttons sitting left.

   Scope: .cg-governance only, which is the custom class on this panel. It is
   on four pages (Leadership, Governance, Annual reports, Media) and no other
   PWR Sec CTA picks it up, so the stock module is untouched everywhere else. */
@media (max-width: 575px){
  .cg-governance .pwr-sec-cta__cta-wrapper{
    flex-direction: column !important;
    align-items: stretch !important;
    width: 100% !important;
    max-width: none !important;
    gap: 12px !important;
  }
  .cg-governance .pwr-sec-cta__cta-wrapper > .pwr-cta{
    width: 100% !important;
    margin: 0 !important;
  }
  .cg-governance .pwr-sec-cta__cta-wrapper .pwr-cta_button,
  .cg-governance .pwr-sec-cta__cta-wrapper .cta_button{
    display: flex !important;
    width: 100% !important;
    justify-content: center !important;
  }
}

/* Ghost button for dark panels. .cg-btn--secondary is navy on transparent with
   !important, so it disappears on a navy background. */
.cg-btn--ghost-light{
  background-color: transparent !important;
  border-color: #FFFFFF !important;
  color: #FFFFFF !important;
}
.cg-btn--ghost-light:hover{
  background-color: rgba(255, 255, 255, 0.12) !important;
  border-color: #FFFFFF !important;
  color: #FFFFFF !important;
}
.cg-btn--ghost-light:active{
  background-color: rgba(255, 255, 255, 0.2) !important;
  border-color: #FFFFFF !important;
  color: #FFFFFF !important;
}
.cg-btn--ghost-light:visited{ color: #FFFFFF !important; }
.cg-btn--ghost-light:focus-visible{ outline-color: #FFFFFF !important; }

/* ==========================================================================
   Count form — underline fields on a pale panel.
   Reference: Framer /accountants/education-tech-services.
     panel  #F5F4F2, radius 16, padding 40
     label  13px / 500 / Heritage Navy, 8px above the rule
     field  no box, 1px bottom rule #DAD8D2, transparent, 16px
     submit navy pill, left aligned, trailing arrow

   Scope: any HubSpot form module inside a Count page template. The stock form
   module exposes no CSS class field in the page editor, so .cg-form alone never
   lands on a page; .widget-type-form is HubSpot's own wrapper for that module
   and is reliable. .cg-form stays as an opt-in hook for anywhere else.
   The site footer sits outside these wrappers and is left alone.
   ========================================================================== */
.cg-form,
[class*="body-container-wrapper--"] .widget-type-form{
  background: #F5F4F2;
  border-radius: 16px;
  padding: 40px;
}
.cg-form .hs-form-field,
[class*="body-container-wrapper--"] .widget-type-form .hs-form-field{ margin-bottom: 26px !important; }

.cg-form .hs-form-field > label,
.cg-form .hs-form-field > label span,
[class*="body-container-wrapper--"] .widget-type-form .hs-form-field > label,
[class*="body-container-wrapper--"] .widget-type-form .hs-form-field > label span{
  font-size: 13px;
  line-height: 1.3;
  font-weight: 500;
  color: #1F2759;
}
.cg-form .hs-form-field > label,
[class*="body-container-wrapper--"] .widget-type-form .hs-form-field > label{
  display: block;
  margin-bottom: 8px;
}

.cg-form :is(input[type="text"], input[type="email"], input[type="tel"], input[type="number"], input[type="url"], select, textarea),
[class*="body-container-wrapper--"] .widget-type-form :is(input[type="text"], input[type="email"], input[type="tel"], input[type="number"], input[type="url"], select, textarea){
  width: 100% !important;
  box-sizing: border-box;
  background: transparent;
  border: 0;
  border-bottom: 1px solid #DAD8D2;
  border-radius: 0;
  padding: 6px 0;
  font-size: 16px;
  line-height: 1.5;
  color: #141414;
  transition: border-color .2s ease;
}
.cg-form textarea,
[class*="body-container-wrapper--"] .widget-type-form textarea{ min-height: 90px; resize: vertical; }

.cg-form :is(input, select, textarea):focus,
[class*="body-container-wrapper--"] .widget-type-form :is(input, select, textarea):focus{
  outline: none;
  border-bottom-color: #1F2759;
  border-bottom-width: 2px;
  /* Keep the box height steady when the rule thickens. */
  padding-bottom: 5px;
}
/* Every field carries a visible label, so a placeholder would only repeat it.
   The attribute stays in the markup for assistive technology, painted out. */
.cg-form :is(input, textarea)::placeholder,
[class*="body-container-wrapper--"] .widget-type-form :is(input, textarea)::placeholder{
  color: transparent !important;
  opacity: 0 !important;
}

.cg-form .hs-input.invalid.error,
[class*="body-container-wrapper--"] .widget-type-form .hs-input.invalid.error{ border-bottom-color: #B3261E; }
.cg-form .hs-error-msgs label,
[class*="body-container-wrapper--"] .widget-type-form .hs-error-msgs label{ color: #B3261E; font-size: 13px; }

/* Submit: the navy pill, left aligned, with the trailing arrow the design uses. */
.cg-form .hs-submit,
[class*="body-container-wrapper--"] .widget-type-form .hs-submit{ margin-top: 8px; }
.cg-form .hs-submit .actions,
[class*="body-container-wrapper--"] .widget-type-form .hs-submit .actions{
  padding: 0;
  text-align: left;
  /* Shrink-wraps the button, which makes it the anchor for the arrow below. */
  display: inline-block;
  position: relative;
}

/* The form module writes the button's own colours inline behind an id selector
   carrying !important, including background-image: none. Nothing in this file
   can outrank that, so the arrow rides on the wrapper instead, where the module
   never reaches. Base64 rather than a raw svg so the CSS minifier cannot trip
   over the quotes and spaces inside the markup. */
.cg-form .hs-submit .actions::after,
[class*="body-container-wrapper--"] .widget-type-form .hs-submit .actions::after{
  content: "";
  position: absolute;
  top: 50%;
  right: 22px;
  width: 14px;
  height: 14px;
  margin-top: -7px;
  pointer-events: none;
  background-image: url("data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSIxNCIgaGVpZ2h0PSIxNCIgdmlld0JveD0iMCAwIDE0IDE0IiBmaWxsPSJub25lIj48cGF0aCBkPSJNMi41IDdoOU04IDMuNSAxMS41IDcgOCAxMC41IiBzdHJva2U9IiNmZmZmZmYiIHN0cm9rZS13aWR0aD0iMS42IiBzdHJva2UtbGluZWNhcD0icm91bmQiIHN0cm9rZS1saW5lam9pbj0icm91bmQiLz48L3N2Zz4=");
  background-repeat: no-repeat;
  background-position: center;
  background-size: 14px 14px;
}

/* POWER paints a button fill with two absolutely positioned layers on
   .hs_submit. Without the theme's own button variables they resolve to black at
   radius 0, which is the black rectangle framing the pill on the live page.
   The pill is painted on the input itself, so both layers are removed. */
.cg-form .hs_submit::before,
.cg-form .hs_submit::after,
[class*="body-container-wrapper--"] .widget-type-form .hs_submit::before,
[class*="body-container-wrapper--"] .widget-type-form .hs_submit::after{
  content: none !important;
  background: none !important;
}
.cg-form .hs_submit,
[class*="body-container-wrapper--"] .widget-type-form .hs_submit{
  background: transparent !important;
  border: 0 !important;
  border-radius: 999px;
}

.cg-form :is(.hs-button, input[type="submit"]),
[class*="body-container-wrapper--"] .widget-type-form :is(.hs-button, input[type="submit"]){
  display: inline-flex;
  align-items: center;
  gap: .55em;
  background-color: #1F2759 !important;
  border: 1px solid #1F2759 !important;
  color: #FFFFFF !important;
  border-radius: 999px !important;
  padding: 12px 24px !important;
  font-size: 15px;
  font-weight: 600;
  line-height: 1;
  width: auto !important;
  cursor: pointer;
  transition: background-color .2s ease, border-color .2s ease;
}
.cg-form :is(.hs-button, input[type="submit"]):hover,
[class*="body-container-wrapper--"] .widget-type-form :is(.hs-button, input[type="submit"]):hover{
  background-color: #182050 !important;
  border-color: #182050 !important;
}
/* Room on the right for the arrow drawn on the wrapper. */
.cg-form input[type="submit"],
[class*="body-container-wrapper--"] .widget-type-form input[type="submit"]{
  padding-right: 46px !important;
}

@media (max-width: 767px){
  .cg-form,
  [class*="body-container-wrapper--"] .widget-type-form{ padding: 24px; }
}

/* ==========================================================================
   Count — Governance page.
   The document library module carries no container of its own, the way the
   theme's own sections do, so the page sets the frame here: 1120 to match the
   hero panel above it, with the same 20px gutter the rest of the site uses.
   ========================================================================== */
.cg-doc-library{
  /* The dnd section already hands this module a 1140 wide centred container,
     the same one the hero's content wrapper sits in, so any padding here only
     pushes the library inside the hero's text edge. Carry no gutter at all on
     desktop and let the section's container do the work; below 1200 the
     container is wider than the content, so the gutter comes back. */
  max-width: 1140px;
  margin-left: auto;
  margin-right: auto;
  padding-left: 0;
  padding-right: 0;
}

@media (max-width: 1199px){
  .cg-doc-library{ padding-left: 20px; padding-right: 20px; }
}

/* The shared callout is 1140 elsewhere. On this page it lines up with the
   1120 hero instead, so the three panels share one edge. */
.body-container-wrapper--governance .cg-governance{
  max-width: 1120px;
}

@media (max-width: 809px){
  .cg-doc-library{ padding-left: 16px; padding-right: 16px; }
}

/* ==========================================================================
   Count — Whistleblower / Important information page.
   The policy module has no container of its own, the same as the document
   library, so the page frames it. The reference sets this block narrower than
   the hero above: 1040 against the hero's content width.
   ========================================================================== */
.cg-policy{
  /* Same trap as the document library: the dnd section already supplies a 1140
     centred container, so anything narrower here pushes the rail inside the
     hero's text edge. The block keeps the full width and the body column is
     capped on the module instead, which holds the reference's reading measure
     without moving the rail. */
  max-width: 1140px;
  margin-left: auto;
  margin-right: auto;
}

/* Only the phone needs a gutter here. Between 810 and 1199 the section's own
   container already holds the content off the edge, and adding to it insets
   the rail from the hero's text. */
@media (max-width: 809px){
  .cg-policy{ padding-left: 20px; padding-right: 20px; }
}

.body-container-wrapper--whistleblower .cg-governance,
.body-container-wrapper--board-charter .cg-governance,
.body-container-wrapper--complaints .cg-governance,
.body-container-wrapper--terms .cg-governance,
.body-container-wrapper--privacy .cg-governance{
  max-width: 1120px;
}

/* ---- Contact: office card grid ----------------------------------------
   The dnd row already supplies the 1140 centred container, so the module
   takes it whole. Capping again here is what inset the document library and
   the policy pages from the hero. */
.cg-offices { max-width: 1140px; margin-left: auto; margin-right: auto; }


/* ==========================================================================
   Count Group mega menu
   --------------------------------------------------------------------------
   Rebuilt 16 Oct 2026 from the Framer file "Count Group Homepage Redesign",
   component Project / Desktop - Primary. Values read from the Framer Style
   inspector, not measured off screenshots. The reference build is in
   Claude outputs/mega-menu/framer-mega-menu-spec.md.

   Design, desktop 1200:
     panel        1200 wide, height fit
     lead column  325 fixed, fill #DDE5EE at 30%, padding 32, vertical gap 12
       eyebrow    Inter Tight SemiBold 11, letter 2px, line 1.2em, #000
       heading    Inter Tight 22/28, mixed weight, #000, h-level 6
       copy       Inter Tight Medium 14/20, Slate Grey #5C6066
       button     pill, outlined, navy label, trailing arrow
     link grid    2 columns, gap 14, card padding 14, radius 9
       title      Inter Tight SemiBold 15/24, letter 0.2px, #000
       descriptor Inter Tight Medium 12.5/1.5em, letter 0.2px, Light Grey #6C7178
       one card per panel is highlighted: same fill as the lead column

   POWER gives four grid columns and no way to set their widths from the
   editor, so the track sizes are set here: lead, two link columns, and a
   zero width fourth that carries no wrappers. The HubSpot side puts one
   wrapper per card, each with custom_class cgmm-card, so the card is a real
   element rather than a run of loose contents.

   POWER's module stylesheet loads after child.css, so the contested
   declarations carry !important. Each one was verified by injection on the
   live page before being written here.
   ========================================================================== */

.pwr-header-advanced-mms {
    z-index: 100;
    /* POWER sizes this strip in 100vw and offsets it by -3px, which counts
       the scrollbar. Left at that, every margin set on the panel inside it
       lands 3px short: the panel measured 210 against a nav item at 213.
       Pinning it to the document puts the two back in step. */
    left: 0 !important;
    right: auto !important;
    width: 100% !important;
    transform: none !important;
}

/* ---------- Panel frame ----------
   The panels are set to page-center in the editor, so POWER sizes the panel
   box to the theme container and centres it. The 10px side padding and the
   half scrollbar nudge that used to live here were corrections for the old
   full width panel and are wrong now: they would push the panel off the
   container the rest of the page aligns to. */
.pwr-header-advanced-mms .pwr-adc-main {
    padding-left: 0 !important;
    padding-right: 0 !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
    max-width: none !important;
}

/* ---------- Panel geometry ----------
   The panel element itself carries POWER's page-center class, which gives it
   max-width 1140 and auto margins. That is the element to move: setting a
   margin on .pwr-adc-main inside it only stacks on top of the centring and
   pushed the panel to 473 instead of 213.

   Left edge sits on the first nav item. 213px is where .pwr-header__menu
   starts: the header's 40px inset plus the fixed width logo block. Measured
   identical at 1596 and 1665 wide, so it does not drift with the viewport
   above the burger breakpoint. Capped at the design's 1200 so the two link
   columns keep their proportions on a wide screen.

   The Framer panel is square with a 1px bottom rule in Line #DAD8D2. Count
   asked for the bottom corners rounded, so the rule is kept and the corners
   are added. overflow:hidden is what clips the lead column's tint into the
   rounded corner rather than letting it square off. */
.pwr-header-advanced-mms .pwr-header-advanced-mm {
    max-width: 1200px !important;
    margin-left: 213px !important;
    margin-right: auto !important;
    border-bottom-left-radius: 12px;
    border-bottom-right-radius: 12px;
    overflow: hidden;
}

/* The design's 1px bottom rule goes on the inner box, not the panel. A closed
   panel collapses to height 0 but still keeps its own border box, so a border
   here pushed every panel below it down by 1px: About Count sat flush,
   Advisers 1px low, and Foundation 5px low. That is the gap that appeared on
   some items and not others. */
.pwr-header-advanced-mms .pwr-adc-main {
    border-bottom: 1px solid #DAD8D2;
}

/* 213 + 1200 + the header's 40px right inset needs 1453. Below that the
   panel falls back to the header inset so it never runs off screen. */
@media (max-width: 1452px) {
    .pwr-header-advanced-mms .pwr-header-advanced-mm {
        margin-left: 40px !important;
        margin-right: 40px !important;
        max-width: none !important;
    }
}

.pwr-header-advanced-mms .pwr-adc-main__cols {
    display: grid !important;
    grid-template-columns: 325px minmax(0, 1fr) minmax(0, 1fr) 0 !important;
    gap: 0 !important;
    align-items: stretch !important;
    /* The panel is set to full width in the editor, so without this cap the
       two link tracks resolve against the viewport (1570 on a 1590 screen)
       and the design's proportions are lost. 1200 is the Framer frame. */
    /* POWER's default justify-items leaves each column at its content width,
       which measured 108 / 73 / 73 inside tracks of 325 / 437.5 / 437.5. */
    justify-items: stretch !important;
}

.pwr-header-advanced-mms .pwr-adc__col {
    padding: 0 !important;
    /* .pwr-adc__col--width-N carries a percentage width from POWER sized for
       the full width panel. It has to go or the column never fills its track. */
    width: auto !important;
    min-width: 0 !important;
}

/* ---------- Hover bridge ----------
   The nav item ends at 99px and the panel starts at 114px. Without these two
   invisible strips the pointer leaves both on the way down and the panel
   closes before it can be reached. */
.pwr-header__menu .hs-menu-wrapper > ul > li {
    position: relative;
}

.pwr-header__menu .hs-menu-wrapper > ul > li::after {
    content: '';
    position: absolute;
    left: 0;
    right: 0;
    top: 100%;
    height: 22px;
}

.pwr-header-advanced-mms .pwr-header-advanced-mm::before {
    content: '';
    position: absolute;
    left: 0;
    right: 0;
    top: -22px;
    height: 22px;
}

/* ---------- Lead column ---------- */
.pwr-header-advanced-mms .pwr-adc__col:first-child {
    background: rgba(221, 229, 238, 0.3);
    padding: 32px !important;
    display: flex !important;
    flex-direction: column !important;
    gap: 12px !important;
    align-content: flex-start !important;
}

/* Same trap as the cards: the eyebrow, heading, copy and button are children
   of .pwr-adc__content-wrappers, a grid carrying POWER's 28px gap, not of the
   column. The 12px set on the column was landing on nothing, and POWER's
   -4px block margins skewed it further: the gaps measured 20, 20 and 28
   against Framer's 12 throughout. */
.pwr-header-advanced-mms .pwr-adc__col:first-child .pwr-adc__content-wrappers {
    gap: 12px !important;
    row-gap: 12px !important;
}

.pwr-header-advanced-mms .cgmm-eyebrow,
.pwr-header-advanced-mms .cgmm-head,
.pwr-header-advanced-mms .cgmm-desc,
.pwr-header-advanced-mms .cgmm-cta {
    margin: 0 !important;
}

.pwr-header-advanced-mms .cgmm-eyebrow .pwr-adc-content__title {
    font-family: 'Inter Tight', sans-serif !important;
    font-size: 11px !important;
    line-height: 1.2 !important;
    font-weight: 600 !important;
    letter-spacing: 2px !important;
    text-transform: uppercase !important;
    color: #000000 !important;
    margin: 0 !important;
}

.pwr-header-advanced-mms .cgmm-head .pwr-adc-content__text p {
    font-family: 'Inter Tight', sans-serif !important;
    font-size: 22px !important;
    line-height: 28px !important;
    font-weight: 400 !important;
    letter-spacing: 0 !important;
    color: #000000 !important;
    text-wrap: balance;
    margin: 0 !important;
}

.pwr-header-advanced-mms .cgmm-head .pwr-adc-content__text strong {
    font-weight: 600 !important;
}

.pwr-header-advanced-mms .cgmm-desc .pwr-adc-content__text p {
    font-family: 'Inter Tight', sans-serif !important;
    font-size: 14px !important;
    line-height: 20px !important;
    font-weight: 500 !important;
    color: #5C6066 !important;
    text-wrap: balance;
    margin: 0 !important;
}

/* The lead CTA uses pwr-cta--custom-02, the theme's outlined pill, which is
   already navy on white and matches the design. custom-01 was wrong for it:
   that style paints a navy ::before across the whole button, which covered
   the label and rendered as a solid navy blob, and child.css gives custom-01
   a min-height meant for page CTAs, which forced it to 82px tall.

   Only the type scale and the trailing arrow are set here. Everything else
   comes from the theme's own button, so it stays in step with the site. */
.pwr-header-advanced-mms .cgmm-cta .pwr-adc-content__button a {
    font-family: 'Inter Tight', sans-serif !important;
    font-size: 14px !important;
    line-height: 20px !important;
    font-weight: 600 !important;
    letter-spacing: 0 !important;
    text-transform: none !important;
    white-space: nowrap !important;
    /* Read off the Framer button frame: fill #FFFFFF, radius 22,
       border 1px solid Heritage Navy, padding 15 / 21, gap 8.
       The fill has to be stated. The button sits inside the lead column's
       tinted block, so leaving it transparent showed the tint through and
       was the colour that read as wrong. */
    background: #FFFFFF !important;
    color: #1F2759 !important;
    border: 1px solid #1F2759 !important;
    /* Count asked for the mega menu button to match the rest of the site
       rather than the Framer frame. The site's standard button, measured on
       Find an accountant, Learn more, Enquire now and Partner with us, is
       40 tall: padding 11/20, 14px label on a 16px line, radius 999.
       Framer's own button was 46 tall with a 22px radius. The site wins. */
    border-radius: 999px !important;
    padding: 11px 20px !important;
    line-height: 16px !important;
    /* custom-02 carries min-height 48 for page CTAs, which held the button at
       48 even with the site's 11/20 padding. 11 + 16 + 11 + 2 = 40. */
    min-height: 0 !important;
    height: auto !important;
}

/* pwr-cta--custom-02 paints its fill with ::before, stacked above the label.
   It stays white on hover, which is why the navy never appeared and the text
   vanished: the overlay was covering both. The button's own background and
   border do the work instead. */
.pwr-header-advanced-mms .cgmm-cta .pwr-adc-content__button a::before {
    display: none !important;
    content: none !important;
}

.pwr-header-advanced-mms .cgmm-cta .pwr-adc-content__button a::after {
    content: '\2192';
    /* POWER's .cta_button::after is display:block, which dropped the arrow
       onto its own line and made the button two rows tall. */
    display: inline !important;
    position: static !important;
    inset: auto !important;
    width: auto !important;
    height: auto !important;
    margin-left: 8px;
    background: none !important;
    transform: none !important;
    /* POWER ships its arrow at opacity 0 and slides it in on hover. The
       design shows it at rest, so the reveal is switched off. */
    opacity: 1 !important;
}

/* Hover reverses the button: navy fill, white label and arrow. */
.pwr-header-advanced-mms .cgmm-cta .pwr-adc-content__button a:hover,
.pwr-header-advanced-mms .cgmm-cta .pwr-adc-content__button a:focus-visible {
    background: #1F2759 !important;
    color: #FFFFFF !important;
    border-color: #1F2759 !important;
}

.pwr-header-advanced-mms .cgmm-cta .pwr-adc-content__button a:hover::after,
.pwr-header-advanced-mms .cgmm-cta .pwr-adc-content__button a:focus-visible::after {
    color: #FFFFFF !important;
    opacity: 1 !important;
}

/* ---------- Link grid ----------
   Columns two and three are the grid. The cards sit flush to the lead column
   because the card's own 14px padding supplies the gutter the design shows. */
/* Framer's Client Destinations grid: 2 columns, gap 28 across and 6 down,
   padding 32 top and bottom, 30 left and right. POWER gives two separate
   columns rather than one grid, so the 28 is split 14 either side of the
   seam and the outer edges carry the 30. */
.pwr-header-advanced-mms .pwr-adc__col:nth-child(2),
.pwr-header-advanced-mms .pwr-adc__col:nth-child(3) {
    display: flex !important;
    flex-direction: column !important;
}

/* The cards are children of .pwr-adc__content-wrappers, not of the column.
   That element is a grid carrying POWER's own 28px gap, which is why setting
   6px on the column changed nothing. Framer's row gap is 6. */
.pwr-header-advanced-mms .pwr-adc__col:nth-child(2) .pwr-adc__content-wrappers,
.pwr-header-advanced-mms .pwr-adc__col:nth-child(3) .pwr-adc__content-wrappers {
    gap: 6px !important;
    row-gap: 6px !important;
}

.pwr-header-advanced-mms .pwr-adc__col:nth-child(2) {
    padding: 32px 14px 32px 30px !important;
}

.pwr-header-advanced-mms .pwr-adc__col:nth-child(3) {
    padding: 32px 30px 32px 14px !important;
}

/* Card box, measured against the Framer destination card: height 74, padding
   14, title 15/24, 3px to the descriptor, descriptor 12.5 at 1.5em.

   Two things were inflating it to 87. POWER leaves margins on the content
   blocks, and the title anchor is inline, so its line box added 4px of
   leading above the text. Zeroing the margins and taking the anchor out of
   inline flow brings the card back to 74 exactly. */
.pwr-header-advanced-mms .cgmm-card {
    position: relative;
    display: flex !important;
    flex-direction: column !important;
    gap: 3px !important;
    padding: 14px !important;
    /* POWER ships -4px vertical margins on the wrapper and the card to card
       gap measured 20 against Framer's row gap of 6. Zeroing the margin
       leaves the column's own 6px gap as the only spacing. */
    margin: 0 !important;
    border-radius: 9px;
    transition: background-color 0.18s ease;
}

.pwr-header-advanced-mms .cgmm-card > .pwr-adc-content {
    margin: 0 !important;
    padding: 0 !important;
}

.pwr-header-advanced-mms .cgmm-card .pwr-adc-content__button {
    line-height: 0 !important;
}

.pwr-header-advanced-mms .cgmm-card .pwr-adc-content__button a {
    display: block !important;
}

.pwr-header-advanced-mms .cgmm-card--hl {
    background: rgba(221, 229, 238, 0.3);
}

.pwr-header-advanced-mms .cgmm-card:hover {
    background: rgba(221, 229, 238, 0.55);
}

/* the whole card is the click target, not just the label */
/* POWER paints an arrow with this pseudo element at inset 50% -20px auto auto.
   It has to be fully reset or the overlay sits in the wrong place and only the
   label is clickable. */
.pwr-header-advanced-mms .cgmm-card .pwr-adc-content__button a::after {
    content: '' !important;
    position: absolute !important;
    inset: 0 !important;
    top: 0 !important;
    right: 0 !important;
    bottom: 0 !important;
    left: 0 !important;
    width: auto !important;
    height: auto !important;
    margin: 0 !important;
    background: none !important;
    transform: none !important;
    border-radius: 9px;
}

.pwr-header-advanced-mms .cgmm-card .pwr-adc-content__button .cta_button,
.pwr-header-advanced-mms .cgmm-card .pwr-adc-content__button a {
    font-family: 'Inter Tight', sans-serif !important;
    font-size: 15px !important;
    line-height: 24px !important;
    font-weight: 600 !important;
    letter-spacing: 0.2px !important;
    text-transform: none !important;
    color: #000000 !important;
    background: none !important;
    border: 0 !important;
    padding: 0 !important;
    margin: 0 !important;
    min-width: 0 !important;
}

.pwr-header-advanced-mms .cgmm-card .pwr-adc-content__text p {
    font-family: 'Inter Tight', sans-serif !important;
    font-size: 12.5px !important;
    line-height: 1.5 !important;
    font-weight: 500 !important;
    letter-spacing: 0.2px !important;
    color: #6C7178 !important;
    margin: 0 !important;
}

/* ---------- Tablet ---------- */
@media (max-width: 1199px) {
    .pwr-header-advanced-mms .pwr-adc-main__cols {
        grid-template-columns: 280px minmax(0, 1fr) minmax(0, 1fr) 0 !important;
    }
    .pwr-header-advanced-mms .pwr-adc__col:first-child {
        padding: 24px !important;
    }
    .pwr-header-advanced-mms .pwr-adc__col:nth-child(2),
    .pwr-header-advanced-mms .pwr-adc__col:nth-child(3) {
        padding: 24px 14px !important;
    }
}

/* ---------- Main nav wrapping on load ----------
   Stephen diagnosed this one. The sequence:
     1. Theme JS measures the menu ul and writes an inline width (615px).
     2. template_advanced-mm.min.js loads deferred and adds has-mega-menu to
        five of the six top level items.
     3. That class pulls in the theme's own rule, which takes those links from
        16px to 24px of right padding. 40px more in total, so Foundation no
        longer fits the locked width and drops to a second line.
     4. The theme measures again once loading finishes (655px) and the nav
        snaps back to one line. That snap is the glitch.
   Letting the ul size to its own content means the locked width never binds,
   so there is nothing to snap back from. */
.pwr-header__menu .hs-menu-wrapper > ul {
  width: max-content !important;
  white-space: nowrap;
}

/* ==========================================================================
   Bulleted lists — one marker everywhere
   --------------------------------------------------------------------------
   Count asked for a plain round bullet, the same in every context, taking the
   colour of the text beside it.

   POWER ships its own marker instead: it sets list-style:none on the li and
   draws a 22x2px rule at left:-42px in var(--clr-txt-bullet-lt). That applies
   in four contexts, and the selector list below is POWER's own, copied from
   template_pwr-defer.min.css so the override lands on exactly the same
   elements and nothing else:

     .hs_cos_wrapper_type_post_filter ul li
     .hs_cos_wrapper_type_post_listing ul li
     .hs_cos_wrapper_type_rich_text ul:not(.inputs-list):not([style*=list-style-type]) li
     .pwr-rich-text ul:not(.inputs-list):not([style*=list-style-type]) li

   .cmt__text is added because Count Media + Text renders its body outside
   .pwr-rich-text, so POWER never reached it. .pwr-sec-txt__desc and
   .cwib__desc both carry .pwr-rich-text, so they are already covered.

   :not(.inputs-list) is carried through from POWER. That class is the form
   checkbox and radio list. Bullets must never appear there.

   This switches the browser's own marker back on and turns POWER's rule off.
   A native ::marker takes its colour from the list item, which is what Count
   asked for, so the colour follows the surrounding text with no value of our
   own to keep in step. The ::marker rule at the end is belt and braces.

   padding-left is forced to 1.3em because several modules scope their own
   list padding with an ID selector, which beats any class rule. Without it
   the indent is 42px in some modules and 26px in others.
   ========================================================================== */
.hs_cos_wrapper_type_post_filter ul:not(.inputs-list),
.hs_cos_wrapper_type_post_listing ul:not(.inputs-list),
.hs_cos_wrapper_type_rich_text ul:not(.inputs-list):not([style*="list-style-type"]),
.pwr-rich-text ul:not(.inputs-list):not([style*="list-style-type"]),
.cmt__text ul:not(.inputs-list){
  list-style: disc outside !important;
  padding-left: 1.3em !important;
  margin-left: 0 !important;
}

.hs_cos_wrapper_type_post_filter ul:not(.inputs-list) > li,
.hs_cos_wrapper_type_post_listing ul:not(.inputs-list) > li,
.hs_cos_wrapper_type_rich_text ul:not(.inputs-list):not([style*="list-style-type"]) > li,
.pwr-rich-text ul:not(.inputs-list):not([style*="list-style-type"]) > li,
.cmt__text ul:not(.inputs-list) > li{
  list-style: disc outside !important;
  padding-left: 0 !important;
  margin-left: 0 !important;
}

.hs_cos_wrapper_type_post_filter ul:not(.inputs-list) > li::before,
.hs_cos_wrapper_type_post_listing ul:not(.inputs-list) > li::before,
.hs_cos_wrapper_type_rich_text ul:not(.inputs-list):not([style*="list-style-type"]) > li::before,
.pwr-rich-text ul:not(.inputs-list):not([style*="list-style-type"]) > li::before,
.cmt__text ul:not(.inputs-list) > li::before{
  content: none !important;
}

.pwr-rich-text ul > li::marker,
.cmt__text ul > li::marker{
  color: currentColor;
}

.cmt__text ul > li{
  margin-bottom: 8px;
}

/* ================================================================================
   Burger menu, Framer mobile nav design
   ================================================================================
   Built to Home / Mobile - Primary, node aoFciXR81, read from the Framer Style
   inspector. Values are recorded in
   Claude outputs/mega-menu/framer-mobile-nav-spec.md.

   The markup is POWER's, so this is all styling over the existing menu widget
   and bottom bar. Nothing here changes which items are in the menu.

   Rows        52 tall: 17 padding, 18px SemiBold label, 17 padding.
   Divider     1px #EAE8E3 under the row, and under an open panel.
   Panel       #DDE5EE at 30%, padding 6/18/14, items 14.5px on a 34px line,
               first item bold.
   Band        Heritage Navy #1F2759, 18 padding, 12 gap, eyebrow plus two
               pills.
   ================================================================================ */

/* The drawer's own inset. POWER insets the menu 28/30, which stops a row
   divider reaching the edge. Zero it and carry the inset on the rows
   themselves, so the dividers run full bleed the way the design draws them. */
.pwr-burger {
    padding: 0 !important;
}

.pwr-burger__menu {
    margin: 0 !important;
}

.pwr-burger__menu .hs-menu-wrapper.hs-menu-flow-vertical > ul {
    margin: 0 !important;
}

/* ---------- Group row ---------- */

.pwr-burger__menu .hs-menu-wrapper.hs-menu-flow-vertical li.hs-menu-depth-1 {
    position: relative;
}

.pwr-burger__menu .hs-menu-wrapper.hs-menu-flow-vertical li.hs-menu-depth-1 > a {
    display: block;
    padding: 17px 52px 17px 18px !important;
    font-size: 18px !important;
    font-weight: 600 !important;
    line-height: 18px !important;
    letter-spacing: 0 !important;
    color: #17191C !important;
    background: #FFFFFF;
    border-bottom: 1px solid #EAE8E3;
}

/* The chevron button is 44 x 34, so centre it against the 52 row rather than
   letting it sit wherever the theme's own offset put it. */
.pwr-burger__menu li.hs-item-has-children > .pwr-menu_submenu-btn {
    top: 12px !important;
}

/* Framer draws the chevron in Light Grey, not the navy this file set earlier
   when the arrow was invisible against white. */
.pwr-burger__menu .pwr-a11y-menu .pwr-menu_submenu-arrow {
    color: #6C7178 !important;
}

/* ---------- Open panel ---------- */

.pwr-burger__menu .hs-menu-wrapper ul.hs-menu-children-wrapper {
    background: rgba(221, 229, 238, 0.3);
    padding: 6px 18px 14px !important;
    margin: 0 !important;
    border-bottom: 1px solid #EAE8E3;
}

.pwr-burger__menu .hs-menu-wrapper ul.hs-menu-children-wrapper > li > a {
    display: block;
    padding: 0 !important;
    font-size: 14.5px !important;
    font-weight: 500 !important;
    line-height: 34px !important;
    letter-spacing: 0 !important;
    color: #3C4148 !important;
}

/* The Framer design sets the first child of a group bold, to mark it as the
   group's own landing page. In the built menu that reads as a subheading
   rather than a link, because it sits directly under the group row it is
   named after, so every child now carries the same weight.

   If Count wants that distinction back, a weight is the wrong tool for it:
   the row needs something that does not read as a heading, such as a chevron
   or a rule under it. */

/* ---------- Account band ---------- */

.pwr-burger-bottom-bar {
    display: flex !important;
    flex-wrap: wrap;
    align-items: center;
    gap: 12px;
    padding: 18px !important;
    background: #1F2759;
}

/* The design's eyebrow has no slot in POWER's markup, so it is drawn here.
   Static text, no link, which is all the design asks of it. */
.pwr-burger-bottom-bar::before {
    content: 'ALREADY WITH COUNT?';
    flex: 0 0 100%;
    font-family: 'Inter Tight', sans-serif;
    font-size: 10px;
    font-weight: 600;
    line-height: 1.2;
    letter-spacing: 1.4px;
    color: #FFFFFF;
}

/* The pair shares the row. Sized to content rather than forced equal, which is
   how the design draws them, and which keeps a long label on one line. If a
   pair of labels genuinely cannot fit, flex-wrap drops the second onto its own
   row rather than breaking a label across two lines. */
.pwr-burger-bottom-bar .pwr-burger-bottom-bar__item {
    flex: 1 1 auto;
    min-width: 0;
    margin: 0 !important;
    /* POWER puts 8px 0 8px 15px on these items, which held the first pill
       15px in from the band's own padding while the eyebrow and the closing
       line sat flush, and took the same 15px off the pair's width. */
    padding: 0 !important;
}

.pwr-burger-bottom-bar .pwr-burger-bottom-bar__item .pwr-cta_button {
    display: flex !important;
    align-items: center;
    justify-content: center;
    width: 100% !important;
    padding: 11px 16px !important;
    white-space: nowrap;
}

/* POWER paints both of these buttons with a ::before stacked above the label,
   so a background set on the anchor never shows. Kill the ::before and paint
   the anchor, same fix as the mega menu CTA. */
.pwr-burger-bottom-bar .pwr-burger-bottom-bar__item .pwr-cta_button::before {
    display: none !important;
    content: none !important;
}

/* First pill, outlined on navy. */
.pwr-burger-bottom-bar .pwr-cta--custom-02 .pwr-cta_button {
    background: transparent !important;
    color: #FFFFFF !important;
    border: 1px solid rgba(255, 255, 255, 0.45) !important;
}

.pwr-burger-bottom-bar .pwr-cta--custom-02 .pwr-cta_button:hover,
.pwr-burger-bottom-bar .pwr-cta--custom-02 .pwr-cta_button:focus-visible {
    background: rgba(255, 255, 255, 0.12) !important;
    border-color: #FFFFFF !important;
}

/* Second pill, white on navy. */
.pwr-burger-bottom-bar .pwr-cta--custom-01 .pwr-cta_button {
    background: #FFFFFF !important;
    color: #1F2759 !important;
    border: 1px solid #FFFFFF !important;
}

.pwr-burger-bottom-bar .pwr-cta--custom-01 .pwr-cta_button:hover,
.pwr-burger-bottom-bar .pwr-cta--custom-01 .pwr-cta_button:focus-visible {
    background: rgba(255, 255, 255, 0.88) !important;
    border-color: rgba(255, 255, 255, 0.88) !important;
}

/* The arrow POWER hides at rest and reveals on hover has nowhere to go inside
   a pill this size, and the design shows none, so it stays off. */
.pwr-burger-bottom-bar .pwr-burger-bottom-bar__item .pwr-cta_button::after {
    display: none !important;
    content: none !important;
}

/* The design's closing line, written by child.js because it carries links. */
.cg-burger-contact {
    flex: 0 0 100%;
    font-size: 14.5px;
    line-height: 20px;
    color: rgba(255, 255, 255, 0.72);
}

.cg-burger-contact a {
    color: inherit;
    text-decoration: none;
}

.cg-burger-contact a:hover,
.cg-burger-contact a:focus-visible {
    color: #FFFFFF;
    text-decoration: underline;
    text-underline-offset: 2px;
}