body.page-id-280067 section[class^="container-"] {
	color: #0b1b45;
}

/* JP-1032 — FFN Connect (/de/ffn-connect = page-id 280067,
   /en/ffn-connect = page-id 289533). The EN twin's <body> carries BOTH ids
   because WPML stamps the original's id onto the translation, so the
   page-id-280067 rules below already reach both languages — verified by
   reading the rendered <body class> on both URLs.

   The rules in this file recolour the old grey body copy to Dark Blue. Their
   scope is section[class^="container-"], which matches the page's content
   sections but NOT the contact section (section#kontaktieren.redesign-styles).
   That left three lines still grey — see the follow-up block at the end. */

body.page-id-280067 section[class^="container-"] p,
body.page-id-280067 section[class^="container-"] li,
body.page-id-280067 section[class^="container-"] strong,
body.page-id-280067 section[class^="container-"] em,
body.page-id-280067 section[class^="container-"] h2,
body.page-id-280067 section[class^="container-"] h3,
body.page-id-280067 section[class^="container-"] h4,
body.page-id-280067 section[class^="container-"] h5,
body.page-id-280067 section[class^="container-"] h6 {
	color: #0b1b45 !important;
}

/* ── Follow-up: the navy Kontakt-Box ──────────────────────────────────────
   Remaining symptom, measured on the rendered page after the rules above:
   exactly 3 visible elements per twin still compute to rgb(51,51,51) — the two
   paragraphs and the phone <strong> inside the contact box. They are not
   reached by section[class^="container-"] (that section's class list starts
   with "redesign-styles", not "container-").

   Why they are grey: they carry no colour of their own and inherit the
   product-landing template default
       .page-template-product-landing main { color: #333333; }
   from the widget plugin's global stylesheet
   (wpb-oop-widget-with-global/assets/scss/style.scss:134).

   Why they must be WHITE and not #0b1b45 like the rest of the page: this box
   has a #0b1b45 fill, so Dark Blue text would be invisible against it. The
   theme already paints this module's copy white, but keys that on
   `#kontaktieren .redesign-styles__text` — a marker class this page's instance
   does not carry (it has redesign-styles__title only). Setting the
   fall-through colour on the text column reproduces the theme's own treatment
   of the same module without touching the module or the other instances.

   The hook is structural and language-neutral rather than the German
   #kontaktieren anchor, so it cannot rot if the EN anchor ever diverges.
   Verified: `.basic-br > .col-lg-6:not(.container-contact)` matches exactly 1
   element on each twin. The form column (.container-contact) is excluded — it
   has its own styling. Elements with their own colour (the white title) are
   unaffected; only what falls through is repainted. */

body.page-id-280067
	section.redesign-styles .basic-br > .col-lg-6:not(.container-contact) {
	color: #ffffff;
}

/* The box's overline renders #0b1b45 on the #0b1b45 fill — invisible. This
   instance uses the old `hero-product-section__content--subtitle text-wawi`
   markup instead of the redesign's `redesign-styles__overtitle`, so the
   theme's Light Blue overline rule never matches it. Restore the same Light
   Blue the theme gives this module's overline.

   !important is required, not a smell: custom-clone.css paints every heading on
   this template navy with
       body.page-template-product-landing main section:not(.section-1690) h2
           { color: #0b1b45 !important }
   That rule has no way to know a heading sits on a dark fill, so on this box it
   produces navy-on-navy. Specificity alone cannot beat an !important
   declaration, so this one matches it and wins on order. */

body.page-id-280067
	section.redesign-styles .basic-br > .col-lg-6:not(.container-contact)
	h2.hero-product-section__content--subtitle {
	color: #89d2ff !important;
}