/* ==========================================================================
   Policies template — list styling
   ==========================================================================

   WHY THIS FILE EXISTS

   The compiled bundle styles `.policies-content h2-h5`, `.policies-content p` and
   `.policies-content a` — but has NO rule for `li`, `ul` or `ol`, and there is no
   `html`/`body` font-family rule anywhere in the sheet to fall back on. Font family is
   set per element throughout this theme.

   The consequence: any list inside a policies page renders in the browser's default
   serif (Times New Roman) at the UA default size — visibly broken, and obviously so on
   a regulatory page. Privacy Policy, Cookie Policy and Terms of service happen to
   contain no lists, so this was never exercised until the Complaints Handling Procedure,
   which has 15 list items.

   app.min.css is a frozen artefact, sha256-verified after every deploy, so the fix lives
   here and is enqueued only for page-template/policies.php.

   Values below MIRROR the bundle's own `.policies-content a, .policies-content p` rules
   exactly — same family, colour, sizes and the same three breakpoints — so list text is
   indistinguishable from the paragraph text around it rather than merely "close".
   Contrast is therefore identical to existing body copy: rgba(8,13,15,.8) on #fff.
   ========================================================================== */

.policies-content ul,
.policies-content ol {
  margin: 0;
  padding-block: 8px 16px;
  padding-inline-start: 24px;
}

.policies-content li {
  font-feature-settings: "liga" off, "clig" off;
  color: rgba(8, 13, 15, .8);
  font-family: RoobertRegular;
  font-size: 18px;
  line-height: 24px;
  margin-bottom: 10px;
}

.policies-content li::marker {
  color: rgba(8, 13, 15, .55);
}

/* Links inside list items: the bundle sets .policies-content a to 18px with its own
   padding-block, which inside an <li> would push the line box out. Neutralise only the
   padding, keep the underline and colour. */
.policies-content li a {
  padding-block: 0;
}

/* ==========================================================================
   Literal strings — cookie names in the Privacy Policy and Cookie Policy
   ==========================================================================

   The bundle has NO `code` rule of any kind (grep `code` against app.min.css
   returns nothing), so a <code> element falls through to the UA default: a
   monospace family at the UA's own monospace default size, which in Chrome is
   13px regardless of the 18px around it. On a page whose entire credibility
   rests on naming cookies exactly right, that renders the one string that must
   be read character-by-character smaller and visually broken.

   <code> is used deliberately rather than <strong> or plain text: wptexturize
   lists `code` in its no-texturize tags, so `_ga_C5EJFMLBN5` and
   `frm_cookie_consent` reach the browser byte-for-byte and cannot be mangled
   into smart quotes or dashes by a future content filter.

   Sized in `em` so it tracks whichever context it sits in — 18px paragraph,
   16px below 1440, or the .9375vw fluid size above it — without needing to
   restate all three breakpoints. Contrast on the tinted chip is 14.1:1.
   ========================================================================== */

.policies-content code {
  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, "Liberation Mono", monospace;
  font-size: .9em;
  color: rgba(8, 13, 15, .9);
  background: rgba(8, 13, 15, .05);
  border-radius: 3px;
  padding: .1em .35em;
  overflow-wrap: break-word;
}

@media (min-width: 1440px) {
  .policies-content li {
    font-size: .9375vw;
    line-height: 1.25vw;
  }
}

@media (max-width: 1440px) {
  .policies-content li {
    font-size: 16px;
    line-height: 22px;
  }
}

@media (max-width: 768px) {
  .policies-content ul,
  .policies-content ol {
    padding-inline-start: 20px;
  }

  .policies-content li {
    margin-bottom: 8px;
  }
}