/* =============================================================================
   WANDA MM2H - FAQ page styling
   Pages: 37 (EN) / 549 (SC) / 551 (TC)   Built 2026-08-06

   Brings the FAQ in line with the finished hub pages
   (/categories/ /benefits/ /mm2h-requirements/ /fees/).

   THE RULE THIS FILE EXISTS TO KEEP
   ---------------------------------
   Every FAQ item stays a NATIVE DIVI TOGGLE MODULE. The client adds, edits,
   reorders and deletes questions in the Divi builder exactly as before; this
   stylesheet never touches page content and applies automatically to any new
   toggle. Delete this file and the page reverts - nothing else to undo.

   WHY THE SELECTORS LOOK HEAVY
   ----------------------------
   Divi writes per-module CSS for every toggle, and the open-title rule
   `.et_pb_toggle_0.et_pb_toggle.et_pb_toggle_open h5.et_pb_toggle_title`
   carries `!important` at specificity (0,4,1). Rules here are prefixed
   `html body.wanda-faq` so they land at (0,4,2)+ and win. Do not "tidy" the
   prefix away - the page silently reverts to black 15px toggles if you do.
   The zh site rule `body.mm2h-large-text :not(.sc-footer) p|span|li` (0,2,2)
   is added by JS at runtime and is out-specified the same way.

   Body classes are added by wanda-faq-style.php: .wanda-faq on all three,
   .wanda-faq-zh on 549/551.
   ============================================================================= */

html body.wanda-faq {
  --wf-brand:      #0A558A;
  --wf-brand-deep: #0A3E63;
  --wf-navy:       #062A44;
  --wf-gold:       #BCAC75;
  --wf-ink:        #313131;
  --wf-body:       #4A4A4A;
  --wf-muted:      #6E6E6E;
  --wf-line:       #E1EAF2;
  --wf-fill:       #F7F9FC;
  --wf-fill-icon:  #EBF3FA;
  --wf-maxw:       1180px;
}

/* =============================================================================
   1. HERO  - first section, brand overlay recipe from the styleguide
   Sections are addressed structurally (first / last child) rather than by
   .et_pb_section_N so the rules survive a section being added or removed.
   ============================================================================= */

/* The photo sits on .et-pb-parallax-background and the overlay on a sibling
   .et_parallax_gradient carrying an INLINE background-image - hence !important. */
html body.wanda-faq .et_builder_inner_content > .et_pb_section:first-child .et_parallax_gradient {
  background-image:
    radial-gradient(120% 92% at 92% 8%, rgba(130,192,199,.26) 0%, rgba(130,192,199,0) 58%),
    linear-gradient(105deg, rgba(10,85,138,.93) 0%, rgba(12,78,128,.90) 55%, rgba(10,62,99,.93) 100%) !important;
}

html body.wanda-faq .et_builder_inner_content > .et_pb_section:first-child .et_pb_text_inner h1 {
  letter-spacing: -.5px !important;
  text-shadow: none !important;          /* finished pages carry no text shadow */
  margin: 0 0 18px !important;
  padding: 0 !important;
}

html body.wanda-faq .et_builder_inner_content > .et_pb_section:first-child .et_pb_text_inner p {
  font-size: 16px !important;
  line-height: 1.75 !important;
  color: #FFFFFF !important;
  opacity: .92;
  max-width: 620px;
  margin: 0 !important;
  padding: 0 !important;
}

/* =============================================================================
   2. TOPIC INDEX  - the code module, rewritten to classes (see build_faq.py)
   ============================================================================= */

html body.wanda-faq .faq-index {
  max-width: var(--wf-maxw);
  margin: 0 auto 8px;
}

html body.wanda-faq .faq-index-eyebrow {
  font-size: 12px !important;
  font-weight: 700 !important;
  letter-spacing: 2.5px;
  text-transform: uppercase;
  color: var(--wf-gold) !important;
  text-align: center;
  margin: 0 0 10px !important;
  padding: 0 !important;
}

html body.wanda-faq h2.faq-index-title {
  font-size: 23px !important;
  font-weight: 800 !important;
  color: var(--wf-brand) !important;
  text-transform: none !important;
  letter-spacing: -.3px !important;
  line-height: 1.25 !important;
  text-align: center !important;
  margin: 0 0 30px !important;
  padding: 0 !important;
}

/* The ul-reset must be written at ID strength too: Divi's list stack includes
   `#left-area ul` (1,0,1). This page is full-width so #left-area is absent,
   but the rule is kept per the styleguide recipe so the grid cannot regress
   if the layout ever gains a sidebar. */
html body.wanda-faq ul.faq-index-grid,
#left-area ul.faq-index-grid,
.entry-content ul.faq-index-grid {
  list-style: none !important;
  margin: 0 !important;
  padding: 0 !important;
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(212px, 1fr));
  gap: 14px;
}

html body.wanda-faq ul.faq-index-grid > li,
#left-area ul.faq-index-grid > li,
.entry-content ul.faq-index-grid > li {
  list-style: none !important;
  display: block !important;
  margin: 0 !important;
  padding: 0 !important;
}
html body.wanda-faq ul.faq-index-grid > li::marker { content: none; }

html body.wanda-faq .faq-index-card {
  display: flex;
  flex-direction: column;
  height: 100%;
  min-height: 128px;
  background: #FFFFFF;
  border: 1px solid var(--wf-line);
  border-radius: 12px;
  padding: 18px 18px 16px;
  text-decoration: none !important;
  transition: border-color .22s ease, box-shadow .22s ease, transform .22s ease;
}

html body.wanda-faq .faq-index-card:hover {
  border-color: #9DB9CE;
  box-shadow: 0 10px 26px rgba(10,62,99,.10);
  transform: translateY(-2px);
}

html body.wanda-faq .faq-index-card .fi-n {
  display: block;
  font-size: 12px !important;
  font-weight: 700;
  letter-spacing: 1.5px;
  color: var(--wf-gold) !important;
  margin-bottom: 8px;
}

html body.wanda-faq .faq-index-card .fi-t {
  display: block;
  flex-grow: 1;
  font-size: 15.5px !important;
  font-weight: 700 !important;
  line-height: 1.4 !important;
  color: var(--wf-brand) !important;
  margin-bottom: 14px;
}

html body.wanda-faq .faq-index-card .fi-go {
  display: block;
  font-size: 13px !important;
  font-weight: 600 !important;
  color: var(--wf-gold) !important;
}

html body.wanda-faq .faq-index-card .fi-go .arr {
  display: inline-block;
  margin-left: 5px;
  transition: transform .22s ease;
}
html body.wanda-faq .faq-index-card:hover .fi-go .arr { transform: translateX(4px); }

/* Deep-link landings: a visitor arriving on /faq/#faq-deposit (a search result,
   a shared link) lands with the category heading tucked under the fixed
   #main-header, which measures 80px wide but wraps to 127px somewhere in the
   981-1100px band (styleguide DIVI GOTCHA 2 - it is not predictable by width,
   so the reserve is sized for the taller case; an over-reserve only shows a
   little extra whitespace). Below 981px the header is position:absolute and
   scrolls away, so almost no reserve is needed. */
html body.wanda-faq [id^="faq-"] { scroll-margin-top: 100px; }

@media (max-width: 1100px) and (min-width: 981px) {
  html body.wanda-faq [id^="faq-"] { scroll-margin-top: 147px; }
}
@media (max-width: 980px) {
  html body.wanda-faq [id^="faq-"] { scroll-margin-top: 20px; }
}

/* =============================================================================
   3. CATEGORY HEADINGS  - the 10 text modules above each toggle group
   Scoped to the non-parallax (content) section so the hero H1 and the CTA H2,
   which both live in parallax sections, are never caught by these rules.
   ============================================================================= */

html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner h6 {
  font-size: 12px !important;
  font-weight: 700 !important;
  letter-spacing: 2.5px !important;
  text-transform: uppercase !important;
  color: var(--wf-gold) !important;
  margin: 0 0 9px !important;
  padding: 0 !important;
}

html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner h2 {
  font-size: 23px !important;
  font-weight: 800 !important;
  color: var(--wf-brand) !important;
  text-transform: none !important;   /* house standard is Title Case, not caps */
  letter-spacing: -.3px !important;
  line-height: 1.25 !important;
  margin: 0 0 10px !important;
  padding: 0 !important;
}

html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner p {
  font-size: 15px !important;
  line-height: 1.7 !important;
  color: var(--wf-body) !important;
  max-width: 720px;
  margin: 0 auto !important;
  padding: 0 !important;
}

/* Breathing room between one category block and the next.
   ⚠ DIRECT CHILD ONLY. The SC page wraps its groups in an extra row+column
   (10 nested rows; EN and TC have none), so a plain `.et_pb_row` rule applied
   twice there and opened a 94px gap against 52px on the other two languages -
   the exact cross-language inconsistency this restyle exists to remove.
   Nested rows are explicitly zeroed so the spacing cannot compound. */
html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) > .et_pb_row {
  padding-top: 46px !important;
  padding-bottom: 6px !important;
}
html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) > .et_pb_row:first-of-type {
  padding-top: 0 !important;
}
html body.wanda-faq .et_pb_column .et_pb_row {
  padding-top: 0 !important;
  padding-bottom: 0 !important;
  margin-top: 0 !important;
  margin-bottom: 0 !important;
}

/* ⚠ The three language pages were BUILT DIFFERENTLY by the team: the SC content
   section is display:flex with row-gap:60px, EN and TC are display:block. Left
   alone, SC spaces its category groups 60px further apart than the others. The
   gap is zeroed so the 46px row padding above is the SINGLE source of spacing in
   every language (no-op on the block-layout pages). */
html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) {
  row-gap: 0 !important;
}

/* =============================================================================
   4. THE TOGGLES  - the heart of the restyle
   Divi default: white card, 9px radius, 30px gap, black 15px title, grey +/-.
   Target: hairline-separated rows, brand-blue question, chevron caret -
   the same row language as the /mm2h-requirements/ accordion.
   ============================================================================= */

html body.wanda-faq .et_pb_toggle.et_pb_module {
  background-color: transparent !important;
  border: 0 !important;
  border-bottom: 1px solid var(--wf-line) !important;
  border-radius: 0 !important;
  box-shadow: none !important;
  margin: 0 !important;
  padding: 0 !important;
  overflow: visible !important;
  transition: background-color .22s ease;
}

/* The first row of each group closes the top of the list.
   NOT :first-of-type - the category heading is a div sibling too, so the first
   toggle is never the first div. The adjacent-sibling selector is exact. */
html body.wanda-faq .et_pb_text + .et_pb_toggle.et_pb_module {
  border-top: 1px solid var(--wf-line) !important;
}

/* ---- question row ---- */
html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_title {
  position: relative;
  font-size: 15.5px !important;
  font-weight: 700 !important;
  line-height: 1.55 !important;
  color: var(--wf-brand) !important;
  padding: 17px 48px 17px 0 !important;
  margin: 0 !important;
  cursor: pointer;
  transition: color .2s ease;
}

/* open state - Divi forces #000 with !important at (0,4,1); this is (0,5,2) */
html body.wanda-faq .et_pb_toggle.et_pb_toggle_open.et_pb_module .et_pb_toggle_title {
  color: var(--wf-brand-deep) !important;
  padding-bottom: 6px !important;
}

html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_title:hover {
  color: var(--wf-brand-deep) !important;
}

/* ---- caret ----
   Reuses the site's own chevron glyph '\33' (already used by the mobile menu)
   instead of Divi's grey +/-, and rotates it on open. Divi sets content and
   font-family with !important at (0,3,1); these rules are (0,4,3). */
html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_title:before,
html body.wanda-faq .et_pb_toggle.et_pb_toggle_close.et_pb_module .et_pb_toggle_title:before,
html body.wanda-faq .et_pb_toggle.et_pb_toggle_open.et_pb_module .et_pb_toggle_title:before {
  font-family: "ETmodules" !important;
  content: '\33' !important;
  font-weight: 400 !important;
  font-size: 17px !important;
  line-height: 1 !important;
  color: var(--wf-brand) !important;
  position: absolute !important;
  right: 2px !important;
  left: auto !important;
  /* centre on the row rather than a hardcoded offset, so the caret stays
     aligned at every breakpoint, in both languages, on one- and two-line
     questions alike. The rotation must carry the translate with it. */
  top: 50% !important;
  margin: 0 !important;
  transform: translateY(-50%) rotate(0deg);
  transform-origin: 50% 50%;
  transition: transform .3s ease, color .2s ease;
}

html body.wanda-faq .et_pb_toggle.et_pb_toggle_open.et_pb_module .et_pb_toggle_title:before {
  transform: translateY(-50%) rotate(180deg);
  color: var(--wf-brand-deep) !important;
}

html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_title:hover:before {
  color: var(--wf-brand-deep) !important;
}

/* ---- answer ----
   padding-top must be !important: the site Custom CSS carries a bare
   `.et_pb_toggle_content { padding-top:5px!important }`. */
html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_content {
  padding: 0 48px 22px 0 !important;
  margin: 0 !important;
}

html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_content p {
  font-size: 14px !important;
  line-height: 1.75 !important;
  color: var(--wf-body) !important;
  font-weight: 400 !important;
  margin: 0 0 12px !important;
  padding: 0 !important;              /* Divi ships p { padding-bottom:1em } */
}
html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_content p:last-child {
  margin-bottom: 0 !important;
}

/* pasted answers carry inline font-weight:300 on spans - normalise */
html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_content span {
  font-weight: 400 !important;
  font-size: inherit !important;
  color: inherit !important;
}
html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_content strong,
html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_content strong span {
  font-weight: 700 !important;
  color: var(--wf-ink) !important;
}

/* answer lists - written at ID strength per the styleguide list recipe */
html body.wanda-faq .et_pb_toggle_content ul,
#left-area .et_pb_toggle_content ul,
.entry-content .et_pb_toggle_content ul {
  list-style: disc !important;
  margin: 0 0 12px !important;
  padding: 0 0 0 1.15em !important;
}
html body.wanda-faq .et_pb_toggle_content ul li,
#left-area .et_pb_toggle_content ul li,
.entry-content .et_pb_toggle_content ul li {
  font-size: 14px !important;
  line-height: 1.75 !important;
  color: var(--wf-body) !important;
  font-weight: 400 !important;
  margin: 0 0 5px !important;
  padding: 0 !important;
}

/* =============================================================================
   5. CTA BAND  - last section. Centred, type pinned to the cross-page standard
   (H2 28px / 800 / uppercase / -.5px, lead 16px EN / 18px zh).
   ============================================================================= */

html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_parallax_gradient {
  background-image:
    linear-gradient(180deg, rgba(6,42,68,.72) 0%, rgba(6,42,68,.86) 100%) !important;
}

html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_text {
  max-width: 760px !important;
  margin-left: auto !important;
  margin-right: auto !important;
}

html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner {
  text-align: center !important;
}

/* h2 AND h3: the CTA heading is being moved to H3 per the styleguide SEO rule
   (CTA banners mark up as H3 site-wide); both are covered so the rule holds
   before and after the content pass. */
html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner h2,
html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner h3 {
  font-size: 28px !important;
  font-weight: 800 !important;
  text-transform: uppercase !important;
  letter-spacing: -.5px !important;
  line-height: 1.2 !important;
  text-align: center !important;
  color: #FFFFFF !important;
  margin: 0 0 14px !important;
  padding: 0 !important;
}

html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner p {
  font-size: 16px !important;
  line-height: 1.75 !important;
  color: #FFFFFF !important;
  text-align: center !important;
  margin: 0 !important;
  padding: 0 !important;
}

/* ---- CTA buttons: restyle the Divi button module to the house .btn-primary /
   .btn-ghost spec (Lee flagged the drift 2026-08-07: one button only, flatter
   pill, lighter type, and Divi's arrow-icon hover instead of the house lift).
   Divi's per-module rules live at `body #page-container .et_pb_section
   .et_pb_button_0` (0,1,3)+!important and pin padding at the wrapper level
   (0,2,0)+!important - everything here out-specifies both. ---- */

/* the column centres; each wrapper becomes inline so two buttons sit side by side */
html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_column {
  text-align: center !important;
}
html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_button_module_wrapper {
  display: inline-block !important;
  vertical-align: middle !important;
  text-align: center !important;
  margin: 30px 7px 0 !important;
}

/* primary (first button) = house .btn-primary: white pill, brand-blue 13px/700 */
html body.wanda-faq #page-container .et_builder_inner_content > .et_pb_section:last-child .et_pb_button {
  background-color: #FFFFFF !important;
  color: var(--wf-brand) !important;
  font-size: 13px !important;
  font-weight: 700 !important;
  letter-spacing: 1px !important;
  text-transform: uppercase !important;
  border: 0 !important;
  border-radius: 999px !important;
  padding: 14px 32px !important;
  transition: transform .22s ease, box-shadow .22s ease, background-color .22s ease !important;
}

/* kill Divi's hover arrow icon - the house buttons carry no icon */
html body.wanda-faq #page-container .et_builder_inner_content > .et_pb_section:last-child .et_pb_button:after,
html body.wanda-faq #page-container .et_builder_inner_content > .et_pb_section:last-child .et_pb_button:hover:after {
  content: none !important;
  display: none !important;
}

/* house hover = lift + soft shadow (btn-primary:hover on every hub page) */
html body.wanda-faq #page-container .et_builder_inner_content > .et_pb_section:last-child .et_pb_button:hover {
  background-color: #FFFFFF !important;
  color: var(--wf-brand) !important;
  transform: translateY(-2px);
  box-shadow: 0 10px 24px rgba(0,0,0,.18);
  padding: 14px 32px !important;
}

/* ghost (second button) = house .btn-ghost: transparent, white text, white outline */
html body.wanda-faq #page-container .et_builder_inner_content > .et_pb_section:last-child
  .et_pb_button_module_wrapper + .et_pb_button_module_wrapper .et_pb_button {
  background-color: transparent !important;
  color: #FFFFFF !important;
  border: 1px solid rgba(255,255,255,.45) !important;
  padding: 13px 28px !important;
}
html body.wanda-faq #page-container .et_builder_inner_content > .et_pb_section:last-child
  .et_pb_button_module_wrapper + .et_pb_button_module_wrapper .et_pb_button:hover {
  background-color: rgba(255,255,255,.12) !important;
  color: #FFFFFF !important;
  transform: none;
  box-shadow: none;
  padding: 13px 28px !important;
}

/* =============================================================================
   6. CHINESE  - SC 549 / TC 551
   Sizes read off the /sc/mm2h-requirements/ accordion, the direct zh reference:
   section h2 28px/700, row title 16px/700, body 16px/1.85, eyebrow 16px.
   These out-specify the runtime `body.mm2h-large-text ... {18px}` rule (0,2,2).
   ============================================================================= */

html body.wanda-faq-zh .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner h6 {
  font-size: 16px !important;
  letter-spacing: 2.5px !important;
}

html body.wanda-faq-zh .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner h2 {
  font-size: 28px !important;
  font-weight: 700 !important;
  line-height: 1.2 !important;
  letter-spacing: 0 !important;
}

html body.wanda-faq-zh .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner p {
  font-size: 16px !important;
  line-height: 1.85 !important;
}

html body.wanda-faq-zh .et_pb_toggle.et_pb_module .et_pb_toggle_title {
  font-size: 16px !important;
  font-weight: 700 !important;
  line-height: 1.6 !important;
}

html body.wanda-faq-zh .et_pb_toggle.et_pb_module .et_pb_toggle_content p,
html body.wanda-faq-zh .et_pb_toggle.et_pb_module .et_pb_toggle_content span,
html body.wanda-faq-zh .et_pb_toggle_content ul li,
#left-area .et_pb_toggle_content ul li:lang(zh),
.entry-content .et_pb_toggle_content ul li:lang(zh) {
  font-size: 16px !important;
  line-height: 1.85 !important;
}

html body.wanda-faq-zh h2.faq-index-title {
  font-size: 28px !important;
  font-weight: 700 !important;
  letter-spacing: 0 !important;
}
html body.wanda-faq-zh .faq-index-eyebrow { font-size: 16px !important; }
html body.wanda-faq-zh .faq-index-card .fi-t { font-size: 16px !important; line-height: 1.5 !important; }
html body.wanda-faq-zh .faq-index-card .fi-go { font-size: 13.5px !important; }
html body.wanda-faq-zh .faq-index-card .fi-n { font-size: 12px !important; }

html body.wanda-faq-zh .et_builder_inner_content > .et_pb_section:first-child .et_pb_text_inner p,
html body.wanda-faq-zh .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner p {
  font-size: 18px !important;      /* zh lead is pinned at 18px cross-page */
  line-height: 1.8 !important;
}

/* the zh CTA H2 stays pinned at 28px like every other page */
html body.wanda-faq-zh .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner h2,
html body.wanda-faq-zh .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner h3 {
  font-size: 28px !important;
  line-height: 1.25 !important;
  letter-spacing: 0 !important;
}

/* =============================================================================
   7. RESPONSIVE
   Every override repeats the full strong selector - a bare class rule inside a
   media query loses to the base rule and the breakpoint silently never applies
   (the /fees/ .svc-grid bug, styleguide S5).
   ============================================================================= */

@media (max-width: 1100px) {
  html body.wanda-faq ul.faq-index-grid,
  #left-area ul.faq-index-grid,
  .entry-content ul.faq-index-grid {
    grid-template-columns: repeat(auto-fit, minmax(196px, 1fr));
  }
}

@media (max-width: 980px) {
  html body.wanda-faq .et_builder_inner_content > .et_pb_section:first-child .et_pb_text_inner h1 {
    font-size: 42px !important;
  }
  html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner h2 {
    font-size: 21px !important;
  }
  html body.wanda-faq-zh .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner h2 {
    font-size: 25px !important;
  }
  html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) .et_pb_row {
    padding-top: 38px !important;
  }
}

@media (max-width: 760px) {
  html body.wanda-faq ul.faq-index-grid,
  #left-area ul.faq-index-grid,
  .entry-content ul.faq-index-grid {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: 11px;
  }
  html body.wanda-faq .faq-index-card {
    min-height: 0;
    padding: 15px 14px 13px;
    border-radius: 10px;
  }
  html body.wanda-faq .faq-index-card .fi-t { font-size: 14.5px !important; margin-bottom: 11px; }
  html body.wanda-faq-zh .faq-index-card .fi-t { font-size: 15px !important; }
  html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner h2,
html body.wanda-faq .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner h3 {
    font-size: 23px !important;
  }
  html body.wanda-faq-zh .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner h2,
html body.wanda-faq-zh .et_builder_inner_content > .et_pb_section:last-child .et_pb_text_inner h3 {
    font-size: 24px !important;
  }
}

@media (max-width: 600px) {
  html body.wanda-faq .et_builder_inner_content > .et_pb_section:first-child .et_pb_text_inner h1 {
    font-size: 34px !important;
  }
  html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_title {
    font-size: 15px !important;
    padding: 15px 38px 15px 0 !important;
  }
  html body.wanda-faq-zh .et_pb_toggle.et_pb_module .et_pb_toggle_title {
    font-size: 15.5px !important;
  }
  html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_title:before,
  html body.wanda-faq .et_pb_toggle.et_pb_toggle_close.et_pb_module .et_pb_toggle_title:before,
  html body.wanda-faq .et_pb_toggle.et_pb_toggle_open.et_pb_module .et_pb_toggle_title:before {
    font-size: 15px !important;
  }
  html body.wanda-faq .et_pb_toggle.et_pb_module .et_pb_toggle_content {
    padding: 0 0 18px 0 !important;
  }
  html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner h2 {
    font-size: 19.5px !important;
  }
  html body.wanda-faq-zh .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner h2 {
    font-size: 23px !important;
  }
  html body.wanda-faq .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner p {
    font-size: 14.5px !important;
  }
  html body.wanda-faq-zh .et_pb_section:not(.et_pb_section_parallax) .et_pb_text_inner p {
    font-size: 15.5px !important;
  }
}

@media (max-width: 460px) {
  html body.wanda-faq ul.faq-index-grid,
  #left-area ul.faq-index-grid,
  .entry-content ul.faq-index-grid {
    grid-template-columns: 1fr;
  }
  html body.wanda-faq .faq-index-card { min-height: 0; }
}