/* ============================================================================
   COMPONENTS — the zh-* library.
   ----------------------------------------------------------------------------
   Implements the exact class contract that lib/page-templates/zh-sections.ts
   emits, so a page Autopilot writes into post_content is styled with no inline
   CSS at all. Extracted from that file, the contract is:

     zh-hero(--split) __left __right __text __eyebrow __line __cta
     zh-trust-bar __inner __item __label __val
     zh-intro(--split) __grid __text __body __media  zh-intro-extended(__text)
     zh-why __grid(--3) __card(--with-img) __card-img __card-body
     zh-process-steps  zh-process-step
     zh-reviews __intro __grid __card __stars __gbp
     zh-faq __list        + faq-item / faq-answer  (details/summary)
     zh-cta __inner __text __buttons
     zh-btn(--gold|--white|--outline-dark|--outline-light)
     zh-eyebrow(--light)  zh-wide
     zhx-crumb zhx-creds zhx-lead zhx-after zhx-cap zhx-rating zhx-subhead

   THE zhx-* RULES LIVE HERE DELIBERATELY.
   zh-sections.ts also ships them as an inline <style> inside post_content, and
   that stylesheet contains BLANK LINES. wpautop turns a blank line inside an
   inline <style> into </p><p> and the rule that follows is deleted — see
   reference_wpautop_kills_css_rules. Having them in the theme means the page
   renders correctly whether that inline block survives, is mangled, or is
   stripped before the push. Nothing depends on wpautop behaviour.

   FAQ: the markup is <details class="faq-item"> with a <div class="faq-answer">.
   That is a contract with the connector, which rebuilds the accordion from the
   approved Q&A by cloning the first item and swapping text. details needs no
   JS, so an answer can never be stuck at max-height:0 on a post_content page.
   ========================================================================= */

/* ---------------------------------------------------------------- layout -- */
.zh-wide { max-width: var(--wrap); margin-inline: auto; padding-inline: var(--gutter); }

/* ----------------------------------------------------------------- hero --- */
/* THE HERO IS BLACK WITH BLUE IN IT, not a blue panel.
   The first build ran a 170deg gradient from black into sky, so by the bottom
   third the whole band was saturated blue and the display type sat on it. The
   identity deck sets display type on BLACK (pages 2, 9, 13, 28) and uses the
   blues as light, not as a backdrop. So: a black surface, two soft blooms of
   navy and sky placed off the text, and a hairline of the brand gradient on
   the bottom edge where the section hands over to the next one. */
.zh-hero {
  position: relative;
  background: var(--bg-dark);
  color: #fff;
  padding: clamp(56px, 9vw, 112px) var(--gutter) clamp(48px, 7vw, 92px);
  overflow: hidden;
}
/* The blooms. Two radial gradients in ONE layer: a second element would be a
   second composite layer for no gain. */
.zh-hero::before {
  content: '';
  position: absolute;
  inset: 0;
  background:
    radial-gradient(70% 90% at 82% 8%,  rgba(26,79,173,.85), transparent 68%),
    radial-gradient(58% 80% at 104% 92%, rgba(59,110,255,.55), transparent 66%),
    radial-gradient(90% 70% at 0% 0%,   rgba(26,79,173,.30), transparent 72%);
  pointer-events: none;
}
/* A fine grid at 3.5% white, faded out towards the headline so it never
   competes with the type. It is texture, not pattern: at a glance it reads as
   surface. Costs no request and no image. A browser without mask-image gets
   the grid evenly, which is still correct. */
.zh-hero::after {
  content: '';
  position: absolute;
  inset: 0;
  background-image:
    linear-gradient(rgba(255,255,255,.035) 1px, transparent 1px),
    linear-gradient(90deg, rgba(255,255,255,.035) 1px, transparent 1px);
  background-size: 56px 56px;
  -webkit-mask-image: radial-gradient(70% 70% at 96% 2%, #000 5%, transparent 72%);
          mask-image: radial-gradient(70% 70% at 96% 2%, #000 5%, transparent 72%);
  pointer-events: none;
}
.zh-hero > * { position: relative; z-index: 1; }

.zh-hero__eyebrow,
.zh-eyebrow {
  display: inline-block;
  font-family: var(--sans);
  font-size: .72rem;
  font-weight: 600;
  letter-spacing: .12em;
  text-transform: uppercase;
  color: var(--sky);
  margin: 0 0 14px;
}
.zh-hero__eyebrow,
.zh-eyebrow--light { color: var(--sky-light); }

.zh-hero h1,
.zh-hero__text h1 {
  font-family: var(--heading);
  font-weight: 700;
  font-size: clamp(2rem, 5.2vw, 3.35rem);
  line-height: 1.06;
  letter-spacing: -.022em;
  margin: 0 0 18px;
  color: #fff;
  text-wrap: balance;
}
/* zh-hero__line does TWO jobs in the section library, and they need different
   rules. Inside the H1 it is an emphasised line of the headline. Inside the
   eyebrow it is the rule either side of the kicker, which is how the identity
   deck sets a label. A single display:block rule made the eyebrow render as
   an empty line, the text, and another empty line. */
.zh-hero h1 .zh-hero__line { display: block; color: var(--sky-light); }
.zh-hero__eyebrow .zh-hero__line {
  display: inline-block;
  width: 22px;
  height: 1px;
  margin: 0 10px;
  vertical-align: middle;
  background: var(--sky-light);
}

.zh-hero p,
.zh-hero__text p,
p.zh-hero__text {
  font-family: var(--sans);
  font-size: clamp(1.02rem, 1.6vw, 1.14rem);
  line-height: 1.68;
  color: rgba(255,255,255,.80);
  max-width: 48ch;
  margin: 0 0 30px;
}

.zh-hero__cta { display: flex; flex-wrap: wrap; gap: 12px; }

/* Flat hero: no media column.
   The identity deck sets display type on black with no photograph at all
   (pages 2, 9, 13, 28), so this is on brand rather than a compromise — and it
   means a page can ship before any photography exists, which for a site with
   an empty media library is the difference between live and blocked. */
.zh-hero--flat > .zh-hero__left { max-width: var(--wrap); margin-inline: auto; }

/* THE FLAT HERO IS ASYMMETRIC ON A WIDE SCREEN, and that is the point.
   Stacked in one column it was a headline, a paragraph, three credential
   figures wrapping into uneven columns, two buttons — and 600px of empty
   black to the right of all of it. The figures are the one piece of content
   that reads as well in a narrow column as in a wide one, so they move into a
   rail on the right and become a spec strip. The composition changes, no
   markup does, and the hero stops being a left-aligned stack. */
@media (min-width: 980px) {
  .zh-hero--flat > .zh-hero__left {
    display: grid;
    grid-template-columns: minmax(0, 1.1fr) minmax(290px, .9fr);
    column-gap: clamp(44px, 5vw, 88px);
    align-items: start;
  }
  /* The kicker runs the full width. It is eight trades long on the home page
     and the rule either side of it only reads as a rule on one line. */
  .zh-hero--flat .zh-hero__eyebrow { grid-column: 1 / -1; grid-row: 1; }
  .zh-hero--flat h1                { grid-column: 1; grid-row: 2; }
  .zh-hero--flat .zh-hero__text    { grid-column: 1; grid-row: 3; }
  .zh-hero--flat .zh-hero__cta     { grid-column: 1; grid-row: 4; }
  /* Spans the headline, the copy and the buttons, and stretches to their full
     height, so the three figures are spaced against the whole left column
     rather than bunched at the top of it. */
  .zh-hero--flat .zhx-creds {
    grid-column: 2;
    grid-row: 2 / span 3;
    align-self: stretch;
    align-content: space-between;
  }
}

/* A BLACK HERO NEEDS A LIGHT OUTLINE BUTTON.
   heroFlat emits .zh-btn--outline-dark, which is a black border and black
   text. That was already only just legible on the old blue gradient; on black
   the second call to action disappears completely. The variant is overridden
   inside the hero rather than changed at source, because on a white section
   it is correct as it is. */
.zh-hero .zh-btn--outline-dark {
  border-color: rgba(255,255,255,.52);
  color: #fff;
  background: transparent;
}
.zh-hero .zh-btn--outline-dark:hover { background: #fff; color: var(--dark); border-color: #fff; }

/* Split hero: copy left, media right. Stacks under 900px with the media first
   suppressed to keep the promise above the fold on a phone. */
.zh-hero--split .zh-hero__left,
.zh-hero--split .zh-hero__right { min-width: 0; }
.zh-hero--split {
  display: grid;
  gap: clamp(28px, 4vw, 56px);
  align-items: center;
}
@media (min-width: 900px) {
  .zh-hero--split { grid-template-columns: minmax(0, 1.05fr) minmax(0, .95fr); max-width: var(--wrap); margin-inline: auto; }
}
.zh-hero__right img {
  width: 100%;
  height: auto;
  border-radius: var(--radius-lg);
  box-shadow: var(--shadow-lg);
  display: block;
}

/* ------------------------------------------------------------ trust bar --- */
/* A spec strip, not a banner. It sits directly under the hero on black, so it
   has to read as the same object seen from closer: hairline dividers, no card,
   no tint. */
.zh-trust-bar {
  position: relative;
  background: var(--bg-dark-2);
  color: #fff;
}
/* The one place the brand gradient is used as a rule rather than a fill. It
   separates the hero from the strip without a grey line on black, which never
   looks like anything but a seam. */
.zh-trust-bar::before {
  content: '';
  position: absolute;
  inset: 0 0 auto 0;
  height: 2px;
  background: var(--grad-brand);
  opacity: .9;
}
.zh-trust-bar__inner {
  max-width: var(--wrap);
  margin-inline: auto;
  padding: 26px var(--gutter);
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 22px 0;
}
@media (min-width: 760px) {
  .zh-trust-bar__inner { grid-template-columns: repeat(4, minmax(0, 1fr)); }
}
.zh-trust-bar__item {
  text-align: center;
  padding-inline: 14px;
  border-left: 1px solid rgba(255,255,255,.12);
}
.zh-trust-bar__item:first-child { border-left: 0; }
@media (max-width: 759px) {
  /* Two per row: the third item starts a new row and must not carry a rule. */
  .zh-trust-bar__item:nth-child(odd) { border-left: 0; }
}
.zh-trust-bar__val {
  display: block;
  font-family: var(--heading);
  font-weight: 700;
  font-size: clamp(1.2rem, 2.2vw, 1.5rem);
  line-height: 1.15;
  letter-spacing: -.01em;
  color: #fff;
  text-wrap: balance;
}
/* CONTRAST. The old value was rgba(255,255,255,.62) over #0A0A0A, which
   measures 7.4:1 — it passes AA, and it still read as switched off, because
   11px of uppercase Sora at 500 against a black field has almost no mass.
   Fixed as a type problem rather than only a colour one: a size up, a weight
   up, and the alpha raised to .80 (≈12.3:1). text-wrap:balance stops
   "Honest window for search results" breaking 3/1. */
.zh-trust-bar__label {
  display: block;
  font-family: var(--sans);
  font-size: .745rem;
  font-weight: 600;
  letter-spacing: .085em;
  text-transform: uppercase;
  line-height: 1.45;
  color: rgba(255,255,255,.80);
  margin-top: 7px;
  text-wrap: balance;
}

/* ---------------------------------------------------------------- intro --- */
.zh-intro { padding: var(--section-y) var(--gutter); }
.zh-intro__grid {
  max-width: var(--wrap);
  margin-inline: auto;
  display: grid;
  gap: clamp(26px, 4vw, 54px);
  align-items: center;
}
@media (min-width: 900px) {
  /* 58/42 — the theme's own ratio. Long list content belongs in
     .zh-intro-extended below, not crammed into the 58% column, or the media
     column sits empty for hundreds of pixels. */
  .zh-intro--split .zh-intro__grid { grid-template-columns: 58% minmax(0, 1fr); }
  .zh-intro--split-reverse .zh-intro__grid { grid-template-columns: minmax(0, 1fr) 58%; }
  .zh-intro--split-reverse .zh-intro__text { order: 2; }
}
.zh-intro__text h2,
.zh-intro h2 {
  font-family: var(--heading);
  font-weight: 700;
  font-size: clamp(1.6rem, 3.2vw, 2.3rem);
  line-height: 1.14;
  letter-spacing: -.016em;
  color: var(--dark);
  margin: 0 0 16px;
  text-wrap: balance;
}
.zh-intro__body,
.zh-intro__text p { font-family: var(--sans); font-size: 1.0625rem; line-height: 1.8; color: var(--text); }
.zh-intro__body > :first-child { margin-top: 0; }
.zh-intro__body > :last-child { margin-bottom: 0; }
.zh-intro__media img {
  width: 100%;
  height: auto;
  display: block;
  border-radius: var(--radius);
  box-shadow: var(--shadow);
}

.zh-intro-extended { padding: var(--section-y) var(--gutter); }
.zh-intro-extended__text {
  /* The CONTAINER is page width so this section's left edge lines up with
     every .zh-wide section above and below it. The MEASURE is capped on the
     children: a 1,140px line of 17px type runs to about 150 characters, which
     is roughly twice what anyone reads comfortably. */
  max-width: var(--wrap);
  margin-inline: auto;
  font-family: var(--sans);
  font-size: 1.0625rem;
  line-height: 1.8;
  color: var(--text);
}
.zh-intro-extended__text > * {
  max-width: 72ch;
}

/* THE STATEMENT BLOCK: one heading, a few paragraphs, nothing else.
   On the home page that is the argument the whole site rests on, and it was
   rendering as 17px body copy under a 1.6rem heading in a 760px column with
   half the viewport empty beside it. Split in two, the heading becomes a
   statement at display size and the paragraphs answer it. The same section
   key is also used for long legal and service prose, which must NOT get this
   treatment, so the selector asks the DOM how many headings there are: one
   heading, first child, no sibling heading. A browser without :has() renders
   the single column it renders today. */
@media (min-width: 1000px) {
  .zh-intro-extended__text:has(> h2:first-child):not(:has(> h2 ~ h2)) {
    display: grid;
    grid-template-columns: minmax(0, .98fr) minmax(0, 1.02fr);
    column-gap: clamp(40px, 5vw, 88px);
    align-items: start;
  }
  .zh-intro-extended__text:has(> h2:first-child):not(:has(> h2 ~ h2)) > h2 {
    grid-column: 1;
    grid-row: 1;
    font-size: clamp(1.8rem, 3.3vw, 2.6rem);
    line-height: 1.1;
    letter-spacing: -.02em;
    max-width: 17ch;
  }
  .zh-intro-extended__text:has(> h2:first-child):not(:has(> h2 ~ h2)) > :not(h2) {
    grid-column: 2;
    max-width: 62ch;
  }
}

/* An anchor for every heading in a long document. A 72ch column of paragraphs
   with nothing but bold text to break it is what /privacy-policy/, /terms-of-
   service/ and every service page were. The tick is the brand gradient and the
   rule runs the measure, so a reader sees the structure before reading it. */
.zh-intro-extended__text h2 {
  position: relative;
  padding-top: 26px;
}
.zh-intro-extended__text h2::before {
  content: '';
  position: absolute;
  top: 0;
  left: 0;
  width: 34px;
  height: 3px;
  border-radius: 2px;
  background: var(--grad-brand);
}
.zh-intro-extended__text h2::after {
  content: '';
  position: absolute;
  top: 1px;
  left: 46px;
  right: 0;
  height: 1px;
  background: var(--border);
}

/* ------------------------------------------------- the section head rail --- */
/* EVERY SECTION ON THIS SITE WAS THE SAME SHAPE: kicker, heading, paragraph,
   grid, all flush left in a 760px column with the right half of the viewport
   empty. Nine of them in a row is what "it looks A.I. built" means — not any
   single block, the repetition.
   On a wide screen the kicker now moves into a rail on the left, under a rule,
   and the heading starts on an indent. The grids below still span the full
   container, so each section reads as an indented head over a full-bleed body
   rather than one more left-aligned stack. Nothing in the markup changes: the
   wrapper becomes a two-column grid and the children are placed by class. */
@media (min-width: 1060px) {
  .zh-why > .zh-wide,
  .zh-intro > .zh-wide,
  .zh-faq > .zh-wide,
  .zh-reviews > .zh-wide {
    display: grid;
    grid-template-columns: var(--rail) minmax(0, 1fr);
    column-gap: clamp(28px, 3.2vw, 54px);
    align-items: start;
  }
  /* Default: everything sits in the content column. */
  .zh-why > .zh-wide > *,
  .zh-intro > .zh-wide > *,
  .zh-faq > .zh-wide > *,
  .zh-reviews > .zh-wide > * { grid-column: 2; }

  .zh-why > .zh-wide > .zh-eyebrow,
  .zh-intro > .zh-wide > .zh-eyebrow,
  .zh-faq > .zh-wide > .zh-eyebrow,
  .zh-reviews > .zh-wide > .zh-eyebrow {
    grid-column: 1;
    grid-row: 1;
    margin: 0;
    padding-top: 16px;
    border-top: 2px solid var(--sky);
    text-align: left;
    text-wrap: balance;
  }
  .zh-why > .zh-wide > h2,
  .zh-intro > .zh-wide > h2,
  .zh-faq > .zh-wide > h2,
  .zh-reviews > .zh-wide > h2 { grid-row: 1; margin-top: -.14em; }

  /* The card and step grids take the whole container width. That difference
     between the indented head and the full-width body IS the composition. */
  .zh-why > .zh-wide > .zh-why__grid,
  .zh-intro > .zh-wide > .zh-process-steps,
  .zh-reviews > .zh-wide > .zh-reviews__grid { grid-column: 1 / -1; }
}

/* -------------------------------------------------------------- why/cards - */
/* The tinted band carries a wash of the brand blue in the corner the content
   does not use, and a hairline top and bottom. Flat #F7F9FC against flat #FFF,
   six times down a page, is the "generated" rhythm the owner called out. */
.zh-why {
  position: relative;
  padding: var(--section-y) var(--gutter);
  background: var(--bg-alt);
  border-top: 1px solid var(--border);
  border-bottom: 1px solid var(--border);
  overflow: hidden;
}
.zh-why::before {
  content: '';
  position: absolute;
  inset: -30% -20% auto auto;
  width: 46rem;
  aspect-ratio: 1;
  background: radial-gradient(circle, rgba(59,110,255,.10), transparent 62%);
  pointer-events: none;
}
.zh-why > * { position: relative; }
/* THESE THREE SELECTORS WERE DIRECT-CHILD AND MATCHED NOTHING.
   zh-sections.ts wraps a section's heading in <div class="zh-wide">, so
   `.zh-why > h2` never applied and the heading fell back to the browser's
   default h2. It looked like a design choice at a glance and it was a dead
   rule. Left-aligned on purpose: the eyebrow above it is left-aligned and the
   identity deck sets type on an edge, not on a centre line. */
.zh-why h2 {
  max-width: var(--wrap-text);
  margin: 0 0 10px;
  text-align: left;
  font-family: var(--heading);
  font-weight: 700;
  font-size: clamp(1.55rem, 3vw, 2.15rem);
  line-height: 1.16;
  letter-spacing: -.015em;
  color: var(--dark);
  text-wrap: balance;
}
.zh-why__grid {
  max-width: var(--wrap);
  margin: 36px auto 0;
  display: grid;
  gap: 18px;
  grid-template-columns: 1fr;
}
@media (min-width: 640px) { .zh-why__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (min-width: 1000px) {
  .zh-why__grid { grid-template-columns: repeat(4, minmax(0, 1fr)); }
  .zh-why__grid--3 { grid-template-columns: repeat(3, minmax(0, 1fr)); }
  /* FIVE CARDS IN A FOUR-COLUMN GRID IS FOUR AND AN ORPHAN.
     The case studies page has a five-card section and the default grid is
     four across, so the fifth sat alone on its own row and the four above it
     were 230px wide with eleven lines of text in each. CSS cannot count, but
     it can ask: a fifth child and no seventh means five or six cards, and
     both of those read as 3+2 and 3+3. No markup and no new modifier. */
  .zh-why__grid:not(.zh-why__grid--3):has(> :nth-child(5)):not(:has(> :nth-child(7))) {
    grid-template-columns: repeat(3, minmax(0, 1fr));
  }
  /* And the other end of the same problem: the hub pages pass --3 and then
     hand it two children, so two cards sat in two thirds of the row with a
     third of it empty. Two children, two columns. */
  .zh-why__grid:has(> :nth-child(2)):not(:has(> :nth-child(3))) {
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }
}
/* THE CARD.
   What was here was a white rectangle with a hairline and a shadow, which is
   the default every generated page ships. What it was missing was a reason
   for the eye to enter it and any sense of weight. It now has: a rule in the
   brand gradient above the heading that the eye lands on first and that grows
   under the cursor, a padding scale that is deliberate rather than even, and
   depth that deepens rather than appears. */
.zh-why__card {
  position: relative;
  isolation: isolate;
  background: #fff;
  border: 1px solid var(--border);
  border-radius: var(--radius-lg);
  padding: 30px 26px 28px;
  box-shadow: var(--shadow-card);
  /* Equal heights without flex gymnastics, and the CTA inside a card sits at
     the bottom rather than floating under short copy. */
  display: flex;
  flex-direction: column;
  transition: transform var(--dur-fast) var(--ease), border-color var(--dur-fast) var(--ease);
}
/* The hover shadow is PAINTED AT REST and faded in with opacity. Animating
   box-shadow itself re-rasterises the card on every frame; this is one
   composited layer changing alpha. */
.zh-why__card::before {
  content: '';
  position: absolute;
  inset: 0;
  z-index: -1;
  border-radius: inherit;
  box-shadow: var(--shadow-card-hover);
  opacity: 0;
  transition: opacity var(--dur-fast) var(--ease);
}
@media (hover: hover) {
  .zh-why__card:hover { transform: translateY(-4px); border-color: var(--sky-wash-edge); }
  .zh-why__card:hover::before { opacity: 1; }
  .zh-why__card:hover h3::before { transform: scaleX(1.9); }
}
.zh-why__card h3 {
  position: relative;
  padding-top: 20px;
  font-family: var(--heading);
  font-weight: 700;
  font-size: 1.12rem;
  line-height: 1.28;
  letter-spacing: -.012em;
  color: var(--dark);
  margin: 0 0 11px;
  text-wrap: balance;
}
.zh-why__card h3::before {
  content: '';
  position: absolute;
  top: 0;
  left: 0;
  width: 26px;
  height: 3px;
  border-radius: 2px;
  background: var(--grad-brand);
  transform-origin: left center;
  transition: transform var(--dur) var(--ease);
}
.zh-why__card p { font-family: var(--sans); font-size: .965rem; line-height: 1.74; color: var(--text); margin: 0; }
.zh-why__card--with-img { padding: 0; overflow: hidden; }
.zh-why__card-img { margin: 0; }
.zh-why__card-img img { width: 100%; height: 190px; object-fit: cover; display: block; }
.zh-why__card-body { padding: 26px 24px 24px; }
.zh-why__card-body > :last-child { margin-bottom: 0; }
.zh-why__card--with-img h3 { padding-top: 0; }
.zh-why__card--with-img h3::before { content: none; }

/* -------------------------------------------------- the card that links --- */
/* THE CARD IS A <div> AND THE LINK IS THE LABEL, STRETCHED.
   It used to be <a class="zh-why__card--link"> wrapping an <h3> and a <p>.
   Valid HTML5, and wpautop does not agree: it treats <a> as inline, so it
   rebalanced paragraphs around it and injected an orphan </p> immediately
   after the opening tag. The browser closed the anchor there and the heading,
   the body and the label became siblings in the grid — three cards rendered
   as six cells on the home page and on all three hub pages.
   wpautop cannot be turned off here (see functions.php), so the markup moved
   instead: no block element is inside an anchor any more. The whole card is
   still one tap target, via the stretched ::after below, and the accessible
   name of the link is now "See ads and local SEO" instead of the entire card
   read out as one link name. */
.zh-why__card--link { cursor: pointer; }
/* Scoped to the card on purpose. `.zhx-card-more` on its own loses to
   `.zh-why__card p` — same element, higher specificity — so the label kept the
   body colour, the body size, and margin:0 instead of margin-top:auto, which
   is why it sat under the copy rather than at the foot of the card. */
.zh-why__card .zhx-card-more {
  display: flex;
  align-items: center;
  gap: 9px;
  margin: 0;
  margin-top: auto;
  padding-top: 22px;
  font-family: var(--sans);
  font-size: .92rem;
  font-weight: 600;
  line-height: 1.3;
  color: var(--sky-ink);
}
.zh-why__card .zhx-card-more a {
  color: inherit;
  text-decoration: none;
  background-image: linear-gradient(currentColor, currentColor);
  background-size: 0% 1px;
  background-position: 0 100%;
  background-repeat: no-repeat;
  transition: background-size var(--dur) var(--ease);
}
/* The stretched hit area. inset:0 against the card, which is the nearest
   positioned ancestor. */
.zh-why__card .zhx-card-more a::after {
  content: '';
  position: absolute;
  inset: 0;
  border-radius: inherit;
}
/* The chevron is built from borders, like the FAQ one: no icon font, no glyph
   that depends on a fallback face having an arrow in it. */
.zh-why__card .zhx-card-more::after {
  content: '';
  flex: 0 0 auto;
  width: 7px;
  height: 7px;
  border-right: 2px solid currentColor;
  border-top: 2px solid currentColor;
  transform: rotate(45deg);
  transition: transform var(--dur-fast) var(--ease);
}
@media (hover: hover) {
  .zh-why__card--link:hover .zhx-card-more::after { transform: translateX(4px) rotate(45deg); }
  .zh-why__card--link:hover .zhx-card-more a { background-size: 100% 1px; }
}
/* KEYBOARD. The ring belongs on the card, because the card is what is
   highlighted. The inner ring on the label is left in place for a browser
   without :has(), which would otherwise show no focus indicator at all. */
.zh-why__card--link:has(.zhx-card-more a:focus-visible) {
  box-shadow: var(--ring);
  border-color: var(--sky);
}
@supports selector(:has(a)) {
  .zhx-card-more a:focus-visible { box-shadow: none; }
}

/* ----------------------------------------------------------------- steps -- */
.zh-process-steps {
  position: relative;
  max-width: var(--wrap);
  margin: 36px auto 0;
  display: grid;
  gap: 18px;
  grid-template-columns: 1fr;
  counter-reset: zhstep;
  list-style: none;
  padding: 0;
}
@media (min-width: 680px) { .zh-process-steps { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (min-width: 1000px) {
  .zh-process-steps { grid-template-columns: repeat(4, minmax(0, 1fr)); }
  /* ONE LINE BEHIND THE BADGES. The cards are opaque, so it shows only in the
     gaps between them — four dashes that say "in this order" without a single
     extra element. It is drawn before the cards in tree order, so they paint
     over it. */
  .zh-process-steps::before {
    content: '';
    position: absolute;
    left: 0;
    right: 0;
    top: 41px;
    height: 2px;
    border-radius: 2px;
    background: var(--sky-wash-edge);
  }
}
.zh-process-step {
  counter-increment: zhstep;
  background: #fff;
  border: 1px solid var(--border);
  border-radius: var(--radius-lg);
  padding: 72px 24px 26px;
  position: relative;
  box-shadow: var(--shadow-card);
}
/* A step's body text may arrive as a bare text node rather than a <p>: the
   section library escapes the step body, so it cannot carry a tag. Setting the
   type on the step itself makes both forms read identically. */
.zh-process-step { font-family: var(--sans); font-size: .94rem; line-height: 1.7; color: var(--text); }
.zh-process-step::before {
  content: counter(zhstep);
  position: absolute;
  top: 24px;
  left: 24px;
  width: 36px;
  height: 36px;
  display: grid;
  place-items: center;
  border-radius: 12px;
  background: var(--grad-brand);
  color: #fff;
  font-family: var(--heading);
  font-weight: 700;
  font-size: .98rem;
  line-height: 1;
  box-shadow: 0 8px 16px -8px rgba(26, 79, 173, .75);
}
.zh-process-step h3 {
  font-family: var(--heading);
  font-weight: 700;
  font-size: 1.06rem;
  line-height: 1.3;
  letter-spacing: -.012em;
  color: var(--dark);
  margin: 0 0 9px;
}
.zh-process-step p { font-family: var(--sans); font-size: .94rem; line-height: 1.7; color: var(--text); margin: 0; }

/* --------------------------------------------------------------- reviews -- */
.zh-reviews { padding: var(--section-y) var(--gutter); }
.zh-reviews h2 {
  max-width: var(--wrap-text);
  margin: 0 0 8px;
  text-align: left;
  font-family: var(--heading);
  font-weight: 700;
  font-size: clamp(1.55rem, 3vw, 2.15rem);
  line-height: 1.16;
  color: var(--dark);
}
.zh-reviews__intro {
  max-width: var(--wrap-text);
  margin: 0 auto;
  text-align: center;
  font-family: var(--sans);
  font-size: 1rem;
  line-height: 1.75;
  color: var(--muted);
}
.zh-reviews__grid {
  max-width: var(--wrap);
  margin: 32px auto 0;
  display: grid;
  gap: 20px;
  grid-template-columns: 1fr;
}
@media (min-width: 760px) { .zh-reviews__grid { grid-template-columns: repeat(3, minmax(0, 1fr)); } }
.zh-reviews__card {
  background: #fff;
  border: 1px solid var(--border);
  border-left: 3px solid var(--sky);
  border-radius: var(--radius);
  padding: 24px 22px;
  box-shadow: var(--shadow);
}
.zh-reviews__card p { font-family: var(--sans); font-size: .98rem; line-height: 1.75; color: var(--text); margin: 0 0 14px; }
.zh-reviews__card cite { font-family: var(--sans); font-size: .86rem; font-weight: 600; font-style: normal; color: var(--dark); }
.zh-reviews__stars { color: var(--star); letter-spacing: .1em; font-size: .95rem; margin-bottom: 10px; }
.zh-reviews__gbp { text-align: center; margin-top: 26px; font-family: var(--sans); font-size: .92rem; color: var(--muted); }
.zh-reviews__gbp a { color: var(--sky); font-weight: 600; }

/* ------------------------------------------------------------------- faq -- */
.zh-faq {
  padding: var(--section-y) var(--gutter);
  background: var(--bg-alt);
  border-top: 1px solid var(--border);
}
.zh-faq h2 {
  max-width: var(--wrap-text);
  margin: 0 0 26px;
  text-align: left;
  font-family: var(--heading);
  font-weight: 700;
  font-size: clamp(1.55rem, 3vw, 2.15rem);
  line-height: 1.16;
  color: var(--dark);
}
/* ONE PANEL WITH DIVIDERS, not five floating boxes.
   Five separate bordered rectangles with 12px between them read as five
   unrelated things; a FAQ is one list and should look like one. The markup
   contract is untouched — still <details class="faq-item"> with
   <div class="faq-answer"> — only the grouping is CSS. */
.zh-faq__list {
  max-width: 860px;
  margin: 0;
  background: #fff;
  border: 1px solid var(--border);
  border-radius: var(--radius-lg);
  box-shadow: var(--shadow-card);
  overflow: hidden;
}

.faq-item {
  background: transparent;
  border: 0;
  border-top: 1px solid var(--border);
  border-radius: 0;
  margin: 0;
  transition: background-color var(--dur-fast) var(--ease);
}
.faq-item:first-child { border-top: 0; }
.faq-item[open] { background: var(--sky-wash); }
.faq-item > summary {
  display: flex;
  justify-content: space-between;
  align-items: center;
  gap: 16px;
  cursor: pointer;
  padding: 20px 24px;
  font-family: var(--heading);
  font-weight: 700;
  font-size: 1.02rem;
  line-height: 1.4;
  letter-spacing: -.01em;
  color: var(--dark);
  list-style: none;
}
.faq-item > summary::-webkit-details-marker { display: none; }
/* THE QUESTION IS AN <h3> INSIDE THE <summary>, and nothing was styling it.
   It kept the browser's defaults — 1.17em and a 1em margin top and bottom —
   so every row was about 40px taller than it reads, and the answer appeared
   to float away from its question. The h3 is there for the outline and for
   the FAQPage schema; visually it is the summary. */
.faq-item > summary h3 {
  margin: 0;
  font: inherit;
  color: inherit;
  letter-spacing: inherit;
}
/* The chevron is CSS, so no icon font and no JS. It rotates rather than
   swapping a glyph, so open and closed are the same object. */
.faq-item > summary::after {
  content: '';
  flex: 0 0 auto;
  width: 9px;
  height: 9px;
  border-right: 2px solid var(--sky);
  border-bottom: 2px solid var(--sky);
  transform: translateY(-3px) rotate(45deg);
  transition: transform var(--dur) var(--ease);
}
.faq-item[open] > summary::after { transform: translateY(2px) rotate(-135deg); }
.faq-item > summary:hover { background: rgba(59, 110, 255, .05); }
.faq-answer {
  padding: 0 24px 20px;
  font-family: var(--sans);
  font-size: 1rem;
  line-height: 1.8;
  color: var(--text);
}
/* <details> cannot transition its own height without script. The answer gets
   a short fade-up instead, so opening reads as a movement rather than a jump.
   Opacity and transform only, and the reduced-motion guard in style.css
   collapses the duration to nothing. */
.faq-item[open] .faq-answer { animation: zh-fade-up .3s var(--ease) both; }
.faq-answer > :first-child { margin-top: 0; }
.faq-answer > :last-child { margin-bottom: 0; }

/* ------------------------------------------------------------------- cta -- */
/* Same surface rule as the hero: black with blue in it, and the brand
   gradient as a rule on the edge rather than as the fill. The 135deg
   black-to-navy wash put the buttons on mid-blue, where the white one lost
   most of its contrast against the background. */
.zh-cta {
  position: relative;
  background: var(--bg-dark);
  color: #fff;
  padding: clamp(52px, 7.5vw, 92px) var(--gutter);
  overflow: hidden;
}
.zh-cta::before {
  content: '';
  position: absolute;
  inset: 0;
  background:
    radial-gradient(60% 110% at 88% 100%, rgba(26,79,173,.80), transparent 66%),
    radial-gradient(48% 90% at 10% 0%,   rgba(59,110,255,.26), transparent 70%);
  pointer-events: none;
}
.zh-cta::after {
  content: '';
  position: absolute;
  inset: 0 0 auto 0;
  height: 2px;
  background: var(--grad-brand);
}
.zh-cta > * { position: relative; z-index: 1; }
/* THE CTA MARKUP HAS NO __text WRAPPER.
   zh-sections.ts emits <p class="zh-cta__text"> as a SIBLING of the h2, not a
   container for it. Against a two-column grid that put the eyebrow, the
   heading, the paragraph and the buttons in four separate cells, and against
   `.zh-cta__text h2` it left the heading with no colour at all, so a black
   heading rendered on a near-black gradient. One column, and both shapes of
   the heading selector. */
.zh-cta__inner {
  max-width: var(--wrap);
  margin-inline: auto;
  display: block;
}
.zh-cta__inner > h2,
.zh-cta__text h2 {
  font-family: var(--heading);
  font-weight: 700;
  font-size: clamp(1.6rem, 3.2vw, 2.35rem);
  line-height: 1.1;
  letter-spacing: -.02em;
  color: #fff;
  margin: 0 0 14px;
  text-wrap: balance;
}
p.zh-cta__text,
.zh-cta__text p { font-family: var(--sans); font-size: 1.02rem; line-height: 1.72; color: rgba(255,255,255,.80); margin: 0 0 26px; max-width: 56ch; }
.zh-cta__buttons { display: flex; flex-wrap: wrap; gap: 12px; }

/* The closing band is the one section that repeats on all eighteen pages, so
   it is the one most able to make the site feel templated. On a wide screen
   the ask goes left and the action goes right, against the gradient rule, and
   the band stops being a fourth left-aligned stack in a row. */
@media (min-width: 980px) {
  .zh-cta__inner {
    display: grid;
    grid-template-columns: minmax(0, 1fr) minmax(0, .82fr);
    column-gap: clamp(40px, 5vw, 84px);
    align-items: center;
  }
  .zh-cta__inner > .zh-eyebrow   { grid-column: 1; grid-row: 1; margin-bottom: 12px; }
  .zh-cta__inner > h2            { grid-column: 1; grid-row: 2; }
  .zh-cta__inner > .zh-cta__text { grid-column: 1; grid-row: 3; margin-bottom: 0; }
  .zh-cta__inner > .zh-cta__buttons {
    grid-column: 2;
    grid-row: 1 / span 3;
    justify-content: flex-end;
    align-self: center;
  }
}

/* --------------------------------------------------------------- buttons -- */
.zh-btn {
  position: relative;
  isolation: isolate;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 8px;
  /* 48px min target: a thumb on a phone, and it is the number people tap. */
  min-height: 50px;
  padding: 14px 26px;
  border: 2px solid transparent;
  border-radius: 999px;
  font-family: var(--sans);
  font-size: .96rem;
  font-weight: 600;
  line-height: 1;
  letter-spacing: .005em;
  text-decoration: none;
  cursor: pointer;
  transition: background-color var(--dur-fast) var(--ease), color var(--dur-fast) var(--ease),
              border-color var(--dur-fast) var(--ease), transform var(--dur-fast) var(--ease);
}
@media (hover: hover) { .zh-btn:hover { transform: translateY(-2px); } }
.zh-btn:active { transform: translateY(0); }
.zh-btn:focus-visible { outline: none; box-shadow: var(--ring); }

/* The primary button carries the deck's gradient UNDER the flat sky fill and
   crossfades to it. Two states of one brand asset, and the transition is a
   pseudo-element's opacity rather than a repainted background. */
.zh-btn--gold { background: var(--sky); color: #fff; box-shadow: 0 10px 22px -12px rgba(59, 110, 255, .95); }
.zh-btn--gold::before {
  content: '';
  position: absolute;
  inset: 0;
  z-index: -1;
  border-radius: inherit;
  background: var(--grad-brand);
  opacity: 0;
  transition: opacity var(--dur-fast) var(--ease);
}
.zh-btn--gold:hover { background: var(--sky); color: #fff; }
.zh-btn--gold:hover::before { opacity: 1; }
.zh-btn--white { background: #fff; color: var(--dark); }
.zh-btn--white:hover { background: var(--sky-wash); color: var(--dark); }
.zh-btn--outline-dark { border-color: var(--dark); color: var(--dark); background: transparent; }
.zh-btn--outline-dark:hover { background: var(--dark); color: #fff; }
.zh-btn--outline-light { border-color: rgba(255,255,255,.7); color: #fff; background: transparent; }
.zh-btn--outline-light:hover { background: #fff; color: var(--dark); }

/* ------------------------------------------- zhx-*: the page-level patch --- */
/* Also shipped inline by zh-sections.ts. Duplicated here on purpose; see the
   wpautop note at the top of this file. */
.zhx-crumb {
  max-width: var(--wrap);
  margin-inline: auto;
  padding: 14px var(--gutter);
  font-family: var(--sans);
  font-size: .8rem;
  color: var(--muted);
}
.zhx-crumb a { color: var(--gold); text-decoration: none; }
.zhx-crumb a:hover { text-decoration: underline; }
.zhx-crumb span { margin: 0 7px; color: var(--border); }
.zhx-crumb span[aria-current] { margin-left: 0; color: var(--muted); }
/* wpautop appends a <br /> after the last crumb, which pushed the page's
   first section down by a line for no reason anyone could see. */
.zhx-crumb br { display: none; }

/* THE HERO CREDENTIAL STRIP.
   It was flex with `flex: 1 1 210px`, so three labels of very different
   lengths produced three columns of very different widths and the dividers
   landed at random. It is a grid now: equal tracks, even dividers, and at
   980px and up the hero turns it on its side into a rail (see .zh-hero--flat
   above) where each figure gets a full line. */
.zhx-creds {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(190px, 1fr));
  gap: 18px 0;
  list-style: none;
  margin: 4px 0 32px;
  padding: 0;
  max-width: 780px;
}
.zhx-creds li { padding: 2px 24px; text-align: left; border-left: 1px solid rgba(255,255,255,.22); }
.zhx-creds li:first-child { border-left: 0; padding-left: 0; }
@media (max-width: 639px) {
  .zhx-creds { grid-template-columns: 1fr; gap: 14px; }
  .zhx-creds li { padding-left: 0; border-left: 0; }
}
.zhx-creds strong {
  display: block;
  font-family: var(--heading);
  font-weight: 700;
  font-size: 1.12rem;
  color: #fff;
  line-height: 1.22;
  letter-spacing: -.012em;
}
.zhx-creds span {
  display: block;
  margin-top: 5px;
  font-family: var(--sans);
  font-size: .695rem;
  font-weight: 500;
  letter-spacing: .085em;
  line-height: 1.5;
  text-transform: uppercase;
  color: rgba(255,255,255,.66);
}

/* The rail form. One figure per line, read down rather than across, which is
   what the hero grid above puts in the second column. */
@media (min-width: 980px) {
  .zh-hero--flat .zhx-creds {
    grid-template-columns: 1fr;
    gap: 0;
    margin: 6px 0 0;
    max-width: none;
    border-left: 1px solid rgba(255,255,255,.20);
  }
  .zh-hero--flat .zhx-creds li {
    padding: 18px 0 18px 26px;
    border-left: 0;
    border-top: 1px solid rgba(255,255,255,.12);
  }
  .zh-hero--flat .zhx-creds li:first-child { padding: 0 0 18px 26px; border-top: 0; }
  .zh-hero--flat .zhx-creds li:last-child { padding-bottom: 0; }
  .zh-hero--flat .zhx-creds strong { font-size: 1.38rem; }
}

.zhx-lead { max-width: 72ch; margin: 0 0 8px; font-size: 1rem; color: var(--text); line-height: 1.85; font-family: var(--sans); text-align: left; }
.zhx-after { max-width: 72ch; margin: 26px 0 0; text-align: left; font-family: var(--sans); font-size: 1rem; line-height: 1.8; color: var(--text); }
.zhx-cap { display: block; margin-top: 8px; font-family: var(--sans); font-size: .8rem; color: var(--muted); text-align: center; }
.zhx-rating { font-family: var(--sans); font-size: .9rem; color: var(--muted); }
.zhx-subhead { font-family: var(--heading); font-weight: 600; font-size: 1.02rem; color: var(--dark); margin: 20px 0 8px; }

/* ------------------------------------------------- content safety nets ---- */
/* post_content pages are written by Autopilot, so the theme has to be forgiving
   about an element arriving without a class. */
/* Headings and paragraphs inside the long-prose block.
   Without these they fall through to the browser defaults, which size an h2
   from 1em of the CONTAINER rather than from the page's type scale and give it
   almost no space above. Two headings on the contact page got away with it.
   The privacy and terms pages carry a dozen each, and there it reads as an
   unstyled document pasted inside a designed site.

   `.zh-intro__body ul` USED TO BE THE FIRST SELECTOR IN THIS LIST, which gave
   every list inside a split body a 1.65rem heading size, a 1.25 line height
   and 40px of margin above it. It was meant to be in the padding rule further
   down, where it now is. No page on this site renders a split, which is why
   nobody saw it. */
.zh-intro-extended__text h2 {
  font-size: clamp(1.45rem, 2.6vw, 1.8rem);
  line-height: 1.22;
  letter-spacing: -.016em;
  margin: 52px 0 12px;
}
.zh-intro-extended__text > h2:first-child { margin-top: 0; }
.zh-intro-extended__text h3 {
  font-size: 1.1rem;
  line-height: 1.35;
  margin: 28px 0 6px;
}
.zh-intro-extended__text p { margin: 0 0 17px; }

.zh-intro__body ul,
.zh-intro-extended__text ul,
.zhx-after ul,
.faq-answer ul { padding-left: 1.15em; margin: 0 0 16px; }
.zh-intro__body li,
.zh-intro-extended__text li,
.zhx-after li,
.faq-answer li { margin-bottom: 8px; }
.zh-intro__body a,
.zh-intro-extended__text a,
.zhx-after a,
.faq-answer a { color: var(--sky-ink); text-decoration: underline; text-underline-offset: 2px; }

/* A bulleted list in a long prose block is the one piece of structure those
   pages have, and it was the browser's default disc. A brand marker on a
   baseline-aligned indent is the cheapest thing on this page that says the
   document was designed. */
.zh-intro-extended__text > ul,
.zhx-after > ul {
  list-style: none;
  padding-left: 0;
}
.zh-intro-extended__text > ul > li,
.zhx-after > ul > li {
  position: relative;
  padding-left: 26px;
}
.zh-intro-extended__text > ul > li::before,
.zhx-after > ul > li::before {
  content: '';
  position: absolute;
  left: 2px;
  top: .72em;
  width: 7px;
  height: 7px;
  border-radius: 50%;
  background: var(--sky);
}
/* An empty paragraph is what wpautop leaves behind around a block element. */
.entry-content p:empty { display: none; }

/* ============================================================================
   MOTION. Minimum, and present.
   ----------------------------------------------------------------------------
   Three things move on this site and nothing else does:
     1. the hero arrives, once, on load (CSS only — no script can fail and
        leave it invisible);
     2. cards, steps, the FAQ panel and section headings fade up as they come
        into view (IntersectionObserver, inlined by functions.php);
     3. hover and focus states, which are handled on the components above.

   RULES EVERY ONE OF THEM OBEYS:
     - transform and opacity only. Nothing animates box-shadow, width, height,
       top/left or any property that triggers layout.
     - nothing reserves or releases space, so no effect can shift the page.
     - the pre-hidden state applies ONLY under html.zh-js, which the inline
       script adds after checking for IntersectionObserver AND for
       prefers-reduced-motion. With no script, a failed script, or reduced
       motion requested, every element is simply visible. A crawler that does
       not run script sees the finished page.
   ========================================================================= */
@keyframes zh-fade-up {
  from { opacity: 0; transform: translate3d(0, 10px, 0); }
  to   { opacity: 1; transform: none; }
}

/* The hero entrance. Four elements, 70ms apart, 'both' so the end state is
   the resting state. */
.zh-hero__eyebrow,
.zh-hero h1,
.zh-hero .zh-hero__text,
.zh-hero .zhx-creds,
.zh-hero__cta { animation: zh-fade-up .62s var(--ease) both; }
.zh-hero h1              { animation-delay: .06s; }
.zh-hero .zh-hero__text  { animation-delay: .12s; }
.zh-hero .zhx-creds      { animation-delay: .18s; }
.zh-hero__cta            { animation-delay: .24s; }

/* The scroll reveal. The selector list here is the contract with the script
   in functions.php: change one and change the other. */
html.zh-js .zh-why__card,
html.zh-js .zh-process-step,
html.zh-js .zh-faq__list,
html.zh-js .zh-reviews__card,
html.zh-js .zh-trust-bar__item,
html.zh-js .zh-why > .zh-wide > h2,
html.zh-js .zh-intro > .zh-wide > h2,
html.zh-js .zh-faq > .zh-wide > h2,
html.zh-js .zh-intro-extended__text > h2 {
  opacity: 0;
  transform: translate3d(0, 14px, 0);
  transition: opacity var(--dur) var(--ease), transform var(--dur) var(--ease);
}
/* Every revealed state repeats its own hiding selector plus .is-in. A single
   `html.zh-js .is-in` rule looks like it should work and does not: the hiding
   selectors that name a descendant heading score higher than one class, so the
   heading would be added to, told it was visible, and stay at opacity 0. */
html.zh-js .zh-why__card.is-in,
html.zh-js .zh-process-step.is-in,
html.zh-js .zh-faq__list.is-in,
html.zh-js .zh-reviews__card.is-in,
html.zh-js .zh-trust-bar__item.is-in,
html.zh-js .zh-why > .zh-wide > h2.is-in,
html.zh-js .zh-intro > .zh-wide > h2.is-in,
html.zh-js .zh-faq > .zh-wide > h2.is-in,
html.zh-js .zh-intro-extended__text > h2.is-in { opacity: 1; transform: none; }

/* A grid reveals as a grid, not as one block: 60ms between cards is enough to
   read as a sequence and short enough that the last one is not late. */
html.zh-js .zh-why__card:nth-child(2),
html.zh-js .zh-process-step:nth-child(2) { transition-delay: .06s; }
html.zh-js .zh-why__card:nth-child(3),
html.zh-js .zh-process-step:nth-child(3) { transition-delay: .12s; }
html.zh-js .zh-why__card:nth-child(4),
html.zh-js .zh-process-step:nth-child(4) { transition-delay: .18s; }
html.zh-js .zh-why__card:nth-child(n+5)  { transition-delay: .24s; }
html.zh-js .zh-trust-bar__item:nth-child(2) { transition-delay: .05s; }
html.zh-js .zh-trust-bar__item:nth-child(3) { transition-delay: .10s; }
html.zh-js .zh-trust-bar__item:nth-child(4) { transition-delay: .15s; }

/* The belt to style.css's braces. Both are deliberate: style.css collapses
   every duration globally, and this removes the starting offsets outright, so
   a reader who asks for no motion gets a page that was never offset. */
@media (prefers-reduced-motion: reduce) {
  html.zh-js .zh-why__card,
  html.zh-js .zh-process-step,
  html.zh-js .zh-faq__list,
  html.zh-js .zh-reviews__card,
  html.zh-js .zh-trust-bar__item,
  html.zh-js .zh-why > .zh-wide > h2,
  html.zh-js .zh-intro > .zh-wide > h2,
  html.zh-js .zh-faq > .zh-wide > h2,
  html.zh-js .zh-intro-extended__text > h2,
  .zh-hero__eyebrow,
  .zh-hero h1,
  .zh-hero .zh-hero__text,
  .zh-hero .zhx-creds,
  .zh-hero__cta {
    opacity: 1;
    transform: none;
    animation: none;
  }
}
