/* ============================================
   base.css — Reset, base elements, utilities
   ============================================ */
* {
  box-sizing: border-box;
}
html {
  scroll-behavior: smooth;
  scroll-padding-top: 110px;
}
/* A form response is a document whose fragment points at the message the
   submission produced. `scroll-behavior: smooth` — which gives the in-page
   anchors their glide — also applies to the fragment scroll the browser performs
   while the response is loading, and Chromium abandons that animation once the
   document settles: measured on a rejected enquiry, focus moved to the summary
   at 4070px but scrollY stayed at 0, so the visitor saw the hero and the summary
   they had been sent to was four screens below the fold. A response page jumps
   instead of gliding; it is a new document, not an anchor being followed. */
html.sf-response {
  scroll-behavior: auto;
}
:focus-visible {
  outline: 3px solid var(--red-bright);
  outline-offset: 3px;
}
/* The default ring is --red-bright, which is also the top stop of the red
   button gradient — invisible on the three most important controls. Give the
   filled red buttons a dark ring and flatten the gradient while focused, so
   the indicator has 3:1 against the button it surrounds (verified 3.13:1)
   as well as against the page behind it. */
.button-red:focus-visible,
.nav-cta:focus-visible {
  outline-color: var(--ink);
  background: var(--red);
}
/* The shared material sheet gives a disclosure summary a 2px ring of its own.
   That sheet is byte-identical to shared/theme/material.css (check-theme-parity
   enforces it), so the landing restates the one treatment here rather than
   diverging from the synced copy. */
.sf-disclosure > summary:focus-visible {
  outline: 3px solid var(--red-bright);
  outline-offset: 3px;
}
body {
  margin: 0;
  background: var(--paper);
  color: var(--ink);
  font-family: var(--font-body);
  font-size: 15px;
  line-height: 1.65;
  -webkit-font-smoothing: antialiased;
  transition: background-color .28s ease, color .28s ease;
}
/* A single-word last line in a 204px card column reads as a mistake — the
   service card copy produced one ("…protection first." with "first." alone).
   `pretty` lets the browser adjust the earlier breaks to avoid the orphan;
   it changes no measurement and a browser that does not know it ignores it. */
p,
li,
dd {
  text-wrap: pretty;
}
img {
  display: block;
  max-width: 100%;
}
a {
  color: inherit;
  text-decoration: none;
}
button, input, textarea {
  font: inherit;
}
button, a {
  -webkit-tap-highlight-color: transparent;
}
::selection {
  background: var(--red);
  color: #fff;
}
.container {
  width: min(var(--container), calc(100% - 56px));
  margin-inline: auto;
}
.skip-link {
  position: fixed;
  z-index: 20;
  left: 16px;
  top: -60px;
  border-radius: var(--radius-md);
  background: var(--surface);
  padding: 12px var(--space-sm);
  color: var(--ink);
  box-shadow: 0 2px 12px rgba(0, 0, 0, .2);
}
.skip-link:focus {
  top: 12px;
}
/* Seen by a screen reader, not by the eye. Used for the "Error:" prefix a field
   message carries, so the sentence is announced as an error even when the
   colour that marks it is not perceived. The 1px box plus clip-path is the
   standard pattern; it must not use `display: none` or `visibility: hidden`,
   which would remove it from the accessibility tree too. */
.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}
