/* from: reusable-block-305088 */

/* ============================================================
   28 Offer landing — shared styles + registration form
   ------------------------------------------------------------
   This is a SYNCED PATTERN. Editing it changes every offer page
   at once. Per-page values (offer_id, Typeform, next step) live
   in the small "OFFER SETTINGS" block at the top of each page.
   Source of truth: 28bysamwood-website repo, wp/pattern-28-offer-form.html
   ============================================================ */

/* ---------- standalone page ----------
   The Rails pages these replace have no site chrome, so the header and the
   help bubble go: without that the page reads as the homepage with a form on it.

   The footer stays, on Jin's call (2026-08-22). It is the one piece of chrome
   worth keeping - it carries the disclaimer and the privacy and terms links -
   and template 2 keeps it too, so the two templates now agree.

   Every page on this site leaves a white band under the footer (/terms/ too).
   It is the whitespace text node after </footer>: it makes one empty line box
   of body's line-height, 26.4px, and body is white. Not the admin bar and not a
   browser extension - both were switched off and the band stayed. Removing the
   line box means touching the theme's typography, so paint the strip instead. */
/* The footer goes with them. 28 asked for it off this page on 2026-08-28, after we
   had already taken it off the checkout and the confirmation screen; it was kept
   here deliberately until then (Jin, 2026-08-22). */
#masthead,
.help-section,
#colophon { display: none !important; }

/* The theme's global footer.site-footer{border-top:20px solid rgb(234,120,95)}
   (specificity 0,1,1, atomic-blocks/style.css) paints an orange band above the
   footer. #colophon (1,0,0) outranks it. Template 2's pattern already carries
   this rule; template 1 never did, so the band showed on these pages only
   (measured live 2026-08-24: border-top-width 20px on page 305117). */
#colophon { border-top: 0; }

/* The card and FAQ column change at the Rails page's own breakpoint:
   1200px (.sign-up-box / .mobile-faq). */

/* ---------- form band: form left (7/12), FAQ right (5/12) ----------
   The Rails page puts the FAQ column beside the form, which is why its card
   sits left of centre rather than in the middle. Offers with no FAQ simply
   leave the right column out and the card keeps the same position. */
.sa28-formband {
  background: #FAFAFA;
  padding: 58px 0 35px;
  margin: 0;
}
.sa28-formrow {
  max-width: 1227px;
  margin: 0 auto;
  padding: 0 15px;
}
.sa28-col-form,
.sa28-col-faq { box-sizing: border-box; padding: 0 15px; }

@media (min-width: 1201px) {
  .sa28-formrow { display: flex; align-items: flex-start; }
  /* The theme wraps a Group block's children in .wp-block-group__inner-container,
     so the row has to keep working through one extra level of nesting. */
  .sa28-formrow > .wp-block-group__inner-container {
    flex: 1 1 100%;
    min-width: 0;
    display: flex;
    align-items: flex-start;
  }
  .sa28-col-form { flex: 0 0 58.333%; max-width: 58.333%; }
  .sa28-col-faq { flex: 0 0 41.667%; max-width: 41.667%; }
  /* once the quiz replaces the form it takes the whole row */
  .sa28-formrow.sa28-quiz-active .sa28-col-form { flex: 0 0 100%; max-width: 100%; }
  .sa28-formrow.sa28-quiz-active .sa28-col-faq { display: none; }
}

.sa28-card {
  background: #fff;
  border-radius: 20px;
  box-shadow: 0 4px 12px rgba(0, 0, 0, .25);
  padding: 32px 92px;
  font-family: 'Averta', sans-serif;
  color: #3C3C3B;
  box-sizing: border-box;
}
.sa28-label {
  display: block;
  font-size: 18px;
  font-weight: 600;
  line-height: 1.43;
  margin: 0 0 5px;
}
.sa28-input {
  display: block;
  width: 100%;
  box-sizing: border-box;
  font-family: 'Averta', sans-serif;
  font-size: 18px;
  line-height: 22px;
  color: #555;
  background: #fff;
  border: 1px solid #C4C8CA;
  border-radius: 10px;
  padding: 15px 18px;
  margin: 0 0 18px;
}
.sa28-input:focus { outline: 2px solid #FA9D7E; outline-offset: 1px; }
.sa28-input.is-invalid { border-color: #C62828; }

.sa28-terms {
  display: flex;
  align-items: flex-start;
  gap: 12px;
  font-size: 18px;
  line-height: 1.43;
  margin: 10px 0 0;
  cursor: pointer;
}
.sa28-terms input[type="checkbox"] {
  width: 24px;
  height: 24px;
  flex: 0 0 24px;
  margin: 0;
  accent-color: #FA9D7E;
}
.sa28-terms a { color: #FA9D7E; font-weight: 600; text-decoration: none; }
.sa28-terms a:hover { text-decoration: underline; }

.sa28-error {
  color: #C62828;
  font-weight: 700;
  font-size: 16px;
  margin: 6px 0 0;
}
.sa28-error:empty { display: none; }

/* An error message follows its own field's bottom margin, so it lands against the next
   field's label instead of the field it describes. Pull it back under its own field and
   put that gap after the message instead. Only above 1201px: below that the fields carry
   no bottom margin at all, so there the message only has to drop its own 6px top margin
   to sit against its field (Jin, 2026-08-28). An empty message is display:none, so none
   of this applies when there is no error. */
.sa28-card #sa28-first-name-error,
.sa28-card #sa28-email-error { margin-top: 0; }

@media (min-width: 1201px) {
  .sa28-card #sa28-first-name-error { margin: -22.28px 0 28.28px; }
  .sa28-card #sa28-email-error { margin: -21.21px 0 27.21px; }
}

.sa28-actions { text-align: center; padding: 28px 0 8px; }
.sa28-submit {
  font-family: 'Averta', sans-serif;
  font-size: 14px;
  font-weight: 700;
  letter-spacing: 2px;
  color: #fff;
  background: #FA9D7E;
  border: 0;
  border-radius: 56px;
  box-shadow: 0 4px 12px rgba(0, 0, 0, .25);
  padding: 14px 92px;
  cursor: pointer;
}
.sa28-submit:hover { filter: brightness(.95); }
.sa28-submit[disabled] { opacity: .6; cursor: default; }

.sa28-help { text-align: center; font-size: 16px; margin: 18px 0 0; }
.sa28-help a { color: #3C3C3B; }

/* ---------- Typeform step ---------- */
.sa28-quiz-mount { width: 100%; height: 100vh; height: max(520px, 100dvh); }

/* Personalise-or-skip screen. It reuses .sa28-card so it inherits the panel the form
   sits in, and .sa28-submit so the primary button is the same control the visitor
   just pressed. Skip is a link, not a button: it is the quieter of the two and the
   screen 28 supplied draws it that way. .sa28-card carries no display rule, so the
   hidden attribute alone holds this closed. */
.sa28-choice { text-align: center; }
.sa28-choice-title { margin: 0 0 12px; }
.sa28-choice-sub { margin: 0 0 24px; }
.sa28-choice-skip { margin: 16px 0 0; }
.sa28-choice-skip a { color: inherit; text-decoration: underline; }

/* Below 1200px the original drops the card entirely - no white panel, no
   shadow, the fields sit straight on the band (.sign-up-box gets
   background:none; box-shadow:none; padding:2px 32px). */
@media (max-width: 1200px) {
  .sa28-formband { padding: 32px 0 28px; }
  .sa28-formrow { padding: 0; }
  .sa28-col-form { padding: 0; }
  .sa28-card {
    background: none;
    box-shadow: none;
    border-radius: 0;
    padding: 2px 32px;
  }
  .sa28-terms { text-align: left; }
  .sa28-quiz-mount { height: 100vh; height: max(520px, 100dvh); }
}
@media (max-width: 500px) {
  .sa28-submit { padding: 4% 9%; }
  .sa28-help { font-size: 16px; }
}

/* ---------- FAQ column (desktop only, per Annie's brief) ----------
   The source markup calls this container "mobile-faq" but the page hides it
   below 1200px. Class names on that page are inverted throughout, so this
   follows the brief and the actual breakpoint rather than the name. */
.sa28-col-faq { display: none; }
@media (min-width: 1201px) {
  .sa28-col-faq {
    display: block;
    font-family: 'Averta', sans-serif;
    color: #3C3C3B;
  }
  .sa28-col-faq h2.sa28-faq-title {
    font-family: 'Averta', sans-serif;
    font-weight: 700;
    font-size: 24px;
    text-align: center;
    margin: 20px 0 25px;
  }
  .sa28-col-faq .c-accordion__item { border-bottom: 2px solid #E1E6EA; }
  .sa28-col-faq .c-accordion__title {
    font-family: 'Averta', sans-serif;
    font-size: 16px;
    font-weight: 700;
    line-height: 1.4;
    color: #3C3C3B;
    margin: 0;
    padding: 10px 34px 15px 15px;
    cursor: pointer;
    position: relative;
  }
  .sa28-col-faq .c-accordion__title::after {
    content: '';
    position: absolute;
    right: 12px;
    top: 18px;
    width: 9px;
    height: 9px;
    border-right: 2px solid #FA9D7E;
    border-bottom: 2px solid #FA9D7E;
    transform: rotate(45deg);
    transition: transform .2s;
  }
  .sa28-col-faq .is-open > .c-accordion__title::after { transform: rotate(-135deg); top: 22px; }
  .sa28-col-faq .c-accordion__content { padding: 0 15px 12px; }
  .sa28-col-faq .c-accordion__content p {
    font-size: 16px;
    line-height: 1.55;
    margin: 0 0 12px;
  }
  .sa28-col-faq .c-accordion__content a { color: #FA9D7E; font-weight: 600; }
}
/* ==========================================================================
   Fidelity pass 2026-08-23 — measured against app.28bysamwood.com/users/join
   and /offer/subscription at 1720 and 1440, both viewports matched.

   Everything here is desktop only (>=1201px). The original drops the card
   below 1200px and mobile is under a running A/B experiment, so nothing in
   this block may leak into the small breakpoints.

   These rules sit last on purpose: several of them override our own earlier
   declarations, and equal specificity is resolved by source order.
   ========================================================================== */
@media (min-width: 1201px) {

  /* --- Form card ------------------------------------------------------- */

  /* In the original the white box IS the column (.sign-up-box.col-lg-7, 698px
     at x = viewport/2 - 598). Our 15px column inset rendered the visible card
     698 -> 668 and the fields 514 -> 484. The column geometry was already
     right; only the inset was wrong, which is why column-level measurements
     kept reading as a match. */
  .sa28-col-form { padding: 0; }
  .sa28-card { margin-bottom: 15px; }

  /* The theme reaches these inputs with input[type="text"|"email"|...] (0,1,1)
     and button, input:not(input[type="radio"]) (0,1,2). Both outrank
     .sa28-input (0,1,0), so our font-size, padding, radius, colour and the
     margin that separates the two fields were all being discarded - the email
     label sat flush against the first-name field. Qualifying with the card
     class raises us to (0,2,1), which wins. Values are the original's. */
  .sa28-card input.sa28-input {
    height: 56px;
    font-size: 18px;
    line-height: 22px;
    padding: 15px 18px;
    margin: 0 0 28.28px;
    border-radius: 10px;
    border-color: #C4C8CA;
    color: #555;
  }

  /* The email field is not a copy of the first-name field in the original: it
     carries 20.5625px of padding on all four sides against the other's
     15px/18px, and a 25.7143px line-height against 22px. */
  .sa28-card input#sa28-email.sa28-input {
    padding: 20.5625px;
    line-height: 25.7143px;
    /* The gap below the email field is 27.21 on the original, not the 28.28
       the first field carries. Measured 2026-08-23. */
    margin-bottom: 27.21px;
  }

  /* 12.3px, not 5px: the original's label declares margin-bottom:5 but
     structural spacing puts 12.3px between the label box and the field.
     Matching the gap rather than the declaration is what makes label-top to
     label-top come out at the original's 123px. */
  .sa28-card .sa28-label { margin: 0 0 13.28px; line-height: 1.42857; }

  /* The original's card opens with an empty .form_title div (10.28px) and puts
     an 18px top margin on the first field wrapper - 28.28px of air above the
     first label that our markup has no element for. Measured 2026-08-23:
     original label sits 118.28px below the band top, ours sat at 90. */
  .sa28-card .sa28-form { padding-top: 28.28px; }

  /* 37.22, not 28: that is the gap the original leaves between the terms row
     and the button. */
  .sa28-card .sa28-actions { padding-top: 37.22px; }

  /* The help line is 18px on the original, not 16, and it sits 66.4px below the
     button rather than our 26. Its box is padded and rounded but transparent,
     so only the text position is visible - fit-content + auto margins land the
     text within 0.13px of the original at 1720. */
  .sa28-card .sa28-help {
    font-size: 18px;
    line-height: 25.7143px;
    padding: 8.46875px 0;
    border-radius: 5px;
    width: fit-content;
    margin: 58.4px auto 0;
  }
  /* The original's address is a coral underlined link; the base rule above
     paints it the body grey because the theme would otherwise colour it. */
  .sa28-card .sa28-help a { color: #FF7F50; text-decoration: underline; }


  .sa28-card .sa28-submit { padding: 9.67969px 92px; line-height: 20px; }

  /* The original indents the whole terms row 16px and hangs the checkbox out
     of it, putting the box at +16 and the text at +43. The theme also bolds
     label text to 600 where the original leaves it at 400. */
  .sa28-card .sa28-terms {
    padding-left: 16px;
    gap: 3px;
    font-weight: 400;
    /* 1.43 gives 25.74px; the original is 25.7143px = 18 x 1.42857. */
    line-height: 1.42857;
  }
  /* The original's checkbox sits 4px below the row top and 16.59px in from the
     card, and inherits the page font rather than the UA's Arial. Offsetting
     with position keeps our flex row 25.71px tall - a margin would make the
     28px-tall checkbox the tallest item and push the button down 2.27px. */
  .sa28-card .sa28-terms input[type="checkbox"] {
    position: relative;
    top: 4px;
    left: 0.59px;
    font: inherit;
    color: inherit;
  }
  /* The original centres the terms text inside a label that is padded 43px on
     the left; ours is a flex row, so the text has to fill the remaining track
     and centre inside it to land the two links where the original puts them
     (measured: within 0.05px at 1720). */
  .sa28-card .sa28-terms > span { flex: 1; text-align: center; }

  /* With no FAQ beside it the form is to sit centred (Jin, 2026-08-23). This
     is a deliberate departure from the original, which leaves it left-aligned
     whether or not the FAQ column is there. "No FAQ" covers both the column
     being deleted and it being left without any accordion item, because the
     editor can do either. Anchoring on .sa28-formrow keeps this to a single
     :has(): a :has() may not be nested inside another :has(), and one invalid
     selector drops the whole rule. */
  .sa28-formrow:not(:has(.c-accordion__title:not(:empty))) .sa28-col-form {
    margin-left: auto;
    margin-right: auto;
  }
  .sa28-col-faq:not(:has(.c-accordion__title:not(:empty))) { display: none; }

  /* --- FAQ column ------------------------------------------------------ */

  /* The theme gives h2 a 12px block padding and a 1.2 line-height, which made
     this heading 53px tall against the original's 26.39px. */
  .sa28-col-faq h2.sa28-faq-title {
    line-height: 1.1;
    padding: 0;
    margin: 20px 0 26.56px;
  }

  /* The original separates questions with an <hr> that is 3px tall, carries
     margin: 20px 0, and spans the full 498.75px column - i.e. outside the
     column's own 15px padding. Our border-bottom sat directly under the
     question with no breathing room, which is why our item pitch was 49px
     against the original's 101px at 1720. The negative margin reproduces the
     <hr>'s full-column width; the padding keeps the text where it was; the
     21px makes up the 1px the <hr> box carries beyond its 2px border. */
  .sa28-col-faq .c-accordion__item {
    margin: 0 -15px 21px;
    padding: 0 15px 20px;
  }

  /* 25.44 not 15: the original's question row is 58.28px tall at 1720 because
     its chevron is a block-level ::after that occupies 10.44px of flow. Ours
     is absolutely positioned and adds no height, so the row came out 47.84px.
     line-height 1.42857 matches the original's 22.8571px. */
  .sa28-col-faq .c-accordion__title {
    line-height: 1.42857;
    /* 26.5547 is the height the original's chevron ::after occupies in flow
       (display:block). The earlier 25.44 left every question row 1.12px short
       of the original's 59.41 - re-measured on a clean load 2026-08-23. */
    padding: 10px 34px 26.5547px 15px;
  }

  /* The original's chevron is a 20x10 rounded SVG filled #EA785F, sat at the
     right of a block ::after. Ours was a 9x9 CSS corner in #FA9D7E - wrong
     shape, wrong size, and a different coral. The same path is inlined here
     so no new asset is needed. */
  .sa28-col-faq .c-accordion__title::after {
    right: 7px;
    top: 26px;
    width: 20px;
    height: 10px;
    border: 0;
    transform: none;
    background: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='20' height='10' viewBox='0 0 20 10' fill='none'%3E%3Cpath d='M18.7084 2.04167L10.7084 9.70833C10.5 9.91667 10.25 10 10 10C9.75004 10 9.50004 9.91667 9.29171 9.70833L1.29171 2.04167C0.916709 1.66667 0.875043 1.04167 1.29171 0.625C1.66671 0.25 2.29171 0.25 2.70838 0.625L10 7.625L17.2917 0.625C17.7084 0.25 18.3334 0.25 18.7084 0.625C19.125 1.04167 19.0834 1.66667 18.7084 2.04167Z' fill='%23EA785F'/%3E%3C/svg%3E") no-repeat center / 20px 10px;
  }
  .sa28-col-faq .is-open > .c-accordion__title::after {
    transform: rotate(180deg);
    top: 26px;
  }
}

/* ---------- campaign post type ----------
   Campaigns are a post type, not Pages, and the theme's singular template prints
   breadcrumbs, the post title and a byline above the content where the Page
   template prints an empty heading. Measured 2026-08-24: /promos/banner-popup/
   carries all three, /304077-2/ (a plain Page) carries none. Everything else in
   the wrapper chain is identical, so this one rule is the whole difference. */
body.single-sa28_programs .entry-header { display: none; }

/* Atomic Blocks appends its Sharing block to the end of the content on a single
   post; a Page never gets one. Its own stylesheet is only enqueued for pages
   that really contain the block, so here it lands as three unstyled text links
   sitting on the footer band. Full inventory of the extra chrome a campaign
   single picks up, measured 2026-08-24: this and .entry-header, nothing else -
   no comments, no post navigation, no author box. */
body.single-sa28_programs .ab-block-sharing { display: none; }

/* wpautop wraps a stray comment or newline between top-level blocks in a bare
   <p>. The paragraph has no height but keeps its 21.15px bottom margin, and
   body is #3c3c3b here, so each one paints as a dark band. Measured on campaign
   305497: removing the two of them closed a 21px gap under the admin bar and
   took 42px off the document. The OFFER SETTINGS comment now lives inside the
   .sa28-config div so it cannot become one; this catches the rest. */
body.single-sa28_programs .entry-content > p:empty { display: none; }
/* The very first one is not :empty - it holds the newline that do_blocks left
   before the first block, so it needs its margins zeroed instead of hiding.
   Measured on campaign 305497: 21px gap -> 0. Zeroing rather than hiding keeps
   any real paragraph a marketer types there visible. */
body.single-sa28_programs .entry-content > p:first-child { margin-top: 0; margin-bottom: 0; }

/* The theme also hands a post-type single the blog layout: #page picks up
   .blog-container (max-width 680px, 75px of top padding) and #primary drops to
   width:70%. The offer Pages escape that through templates/template-builder.php,
   and a post type cannot select a page template. Measured on page 305117 at
   1720px: #page and #primary are both 100% wide with no padding, the hero spans
   1720 and the form row 1227. Reproduce it here instead of adding a theme file. */
body.single-sa28_programs #page,
body.single-sa28_programs #content,
body.single-sa28_programs #primary {
  /* .blog-container carries max-width:680px !important, so this needs the same
     weight - the pattern already does it for #masthead. */
  max-width: 100% !important;
  width: 100% !important;
  margin: 0;
  padding: 0;
}


/* The FAQ column carries eight fixed question/answer slots, one per pair of
   fields. A slot nobody filled in leaves the accordion item behind with an
   empty question, so hide it; when every question is empty the whole column
   goes and the form centres (the two rules in the 1200px block above).
   The pattern writes <h2>[acf ...]</h2> with no whitespace inside, or :empty
   would never match. */
.sa28-col-faq .c-accordion__item:has(.c-accordion__title:empty) { display: none; }



/* from: evvr-join-style */

/* evvr. rebrand of the join page (campaign copy 322744): colour and type only, no layout.
   Needs a Montserrat + Inter font <link> from the injected snippet (no @font-face here). */
body:not(#_):not(#_) {
  color: #111111;
  font-family: "Inter", sans-serif;
}


/* headings */
body:not(#_):not(#_) .sa28-col-faq h2.sa28-faq-title,
body:not(#_):not(#_) .sa28-choice-title {
  font-family: "Montserrat", sans-serif;
  font-weight: 800;
  color: #111111;
  letter-spacing: -0.02em;
}

/* form band and card */
body:not(#_):not(#_) .sa28-formband {
  background: #FBF6F3;
}
/* Padding input: Zero top and Zero bottom remove the band's own padding (58px 0 35px, and 32px 0 28px up to 1200px).
   Scoped to the band so no other section is touched; after the band's padding rules, with more weight than they have. */
body.single-sa28_programs:not(#_):not(#_):not(#_) .sa28-formband.programs-pad-zero-top {
  padding-top: 0;
}
body.single-sa28_programs:not(#_):not(#_):not(#_) .sa28-formband.programs-pad-zero-bottom {
  padding-bottom: 0;
}
body.single-sa28_programs:not(#_):not(#_):not(#_) .sa28-formband.programs-pad-zero-top-bottom {
  padding-top: 0;
  padding-bottom: 0;
}
body:not(#_):not(#_) .sa28-card {
  font-family: "Inter", sans-serif;
  color: #111111;
}
@media (min-width: 1201px) {
  body:not(#_):not(#_) .sa28-card {
    background: #FFFFFF;
    border: 1px solid #ECE3DD;
    box-shadow: 0 8px 24px rgba(35, 30, 52, 0.12);
  }
}
body:not(#_):not(#_) .sa28-label {
  font-family: "Inter", sans-serif;
  font-weight: 600;
  color: #111111;
}
body:not(#_):not(#_) .sa28-input {
  font-family: "Inter", sans-serif;
  color: #111111;
  background: #FFFFFF;
  border-color: #928880;
  border-radius: 8px;
}
body:not(#_):not(#_) .sa28-input::placeholder {
  color: #645D56;
  opacity: 1;
}
body:not(#_):not(#_) .sa28-input:focus {
  border-color: #5E30FF;
  outline: 3px solid #5E30FF;
  outline-offset: 2px;
}
body:not(#_):not(#_) .sa28-card input.sa28-input.is-invalid {
  border-color: #C700C7;
}
body:not(#_):not(#_) .sa28-error {
  color: #C700C7;
}
/* The pattern drops the 24px box 4px (top:4px) to sit on Averta's text line. With Inter the 18px/1.42857 line is 25.71px, so the
   box centre must sit at (25.71 - 24) / 2 = 0.86px from the row top to share the first text line's centre. */
body:not(#_):not(#_) .sa28-terms input[type="checkbox"] {
  accent-color: #5E30FF;
  top: 0.86px;
}
body:not(#_):not(#_) .sa28-help {
  color: #111111;
}

/* links: violet, plain underline where the page had one. The child theme sets
   a:hover{color:#ea785f !important;text-decoration:none !important}, so hover and focus need !important. */
body:not(#_):not(#_) .sa28-terms a,
body:not(#_):not(#_) .sa28-help a,
body:not(#_):not(#_) .sa28-choice-skip a,
body:not(#_):not(#_) .sa28-col-faq .c-accordion__content a {
  color: #5E30FF;
}
body:not(#_):not(#_) .sa28-help a,
body:not(#_):not(#_) .sa28-col-faq .c-accordion__content a {
  text-decoration: underline;
}
body:not(#_):not(#_) .sa28-terms a:hover,
body:not(#_):not(#_) .sa28-terms a:focus,
body:not(#_):not(#_) .sa28-help a:hover,
body:not(#_):not(#_) .sa28-help a:focus,
body:not(#_):not(#_) .sa28-col-faq .c-accordion__content a:hover,
body:not(#_):not(#_) .sa28-col-faq .c-accordion__content a:focus,
body:not(#_):not(#_) .sa28-choice-skip a:hover,
body:not(#_):not(#_) .sa28-choice-skip a:focus {
  color: #4A1FE6 !important;
  text-decoration: underline !important;
}
/* the theme paints link underlines as a coral box-shadow */
body:not(#_):not(#_) .sa28-card a,
body:not(#_):not(#_) .sa28-col-faq a {
  box-shadow: none;
}

/* buttons: violet pill, uppercase, letterspaced (same look as the home page) */
body:not(#_):not(#_) .sa28-submit {
  box-sizing: border-box;
  min-height: 48px;
  font-family: "Inter", sans-serif;
  font-weight: 500;
  letter-spacing: 0.11em;
  text-transform: uppercase;
  color: #FFFFFF;
  background: #5E30FF;
  border-radius: 999px;
  box-shadow: none;
}
body:not(#_):not(#_) .sa28-submit:hover {
  background: #4A1FE6;
  filter: none;
}
body:not(#_):not(#_) .sa28-submit:focus-visible {
  outline: 3px solid #5E30FF;
  outline-offset: 2px;
}

/* FAQ */
body:not(#_):not(#_) .sa28-col-faq {
  font-family: "Inter", sans-serif;
  color: #111111;
}
body:not(#_):not(#_) .sa28-col-faq .c-accordion__item {
  border-bottom-color: #ECE3DD;
}
body:not(#_):not(#_) .sa28-col-faq .c-accordion__title {
  font-family: "Inter", sans-serif;
  font-weight: 600;
  color: #111111;
}
body:not(#_):not(#_) .sa28-col-faq .c-accordion__content p {
  font-family: "Inter", sans-serif;
  color: #111111;
}
body:not(#_):not(#_) .sa28-col-faq .c-accordion__title::after {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='20' height='10' viewBox='0 0 20 10' fill='none'%3E%3Cpath d='M18.7084 2.04167L10.7084 9.70833C10.5 9.91667 10.25 10 10 10C9.75004 10 9.50004 9.91667 9.29171 9.70833L1.29171 2.04167C0.916709 1.66667 0.875043 1.04167 1.29171 0.625C1.66671 0.25 2.29171 0.25 2.70838 0.625L10 7.625L17.2917 0.625C17.7084 0.25 18.3334 0.25 18.7084 0.625C19.125 1.04167 19.0834 1.66667 18.7084 2.04167Z' fill='%235E30FF'/%3E%3C/svg%3E");
}
