/*!
 * Dewhot gas consumption calculator - styles
 * Copyright (c) 2026 Dewhot. All rights reserved.
 * https://dewhot.co.za/gas-consumption-tool/
 *
 * Not licensed for reuse, redistribution, adaptation or embedding on any
 * other site. Written for Dewhot; if you are reading this somewhere other
 * than dewhot.co.za, it was taken.
 */
.dw-gcc {
    --ink: #22262e;
    --ink-soft: #5b626e;
    --ground: #f4f3f1;
    --panel: #ffffff;
    --line: #dcd9d4;
    --red: #ea0029;
    --navy: #001538;
    --blue: #236092;
    --blue-wash: #eaf1f7;
    --chip: #dfe1e2;
    --chip-hover: #d2d5d7;
    --focus: #236092;
    --display: Hind, sans-serif;
    --body: Hind, sans-serif;
  }
.dw-gcc {
    font-family: var(--body);
    font-size: 16px;
    line-height: 1.5;
  }

.dw-gcc .masthead { margin-bottom: 24px; }
.dw-gcc .eyebrow {
    font-family: var(--display);
    font-size: 12px;
    font-weight: 600;
    letter-spacing: 0.12em;
    text-transform: uppercase;
    color: var(--red);
    margin: 0 0 6px;
  }
.dw-gcc h1 {
    font-family: var(--display);
    font-weight: 300;
    font-size: clamp(28px, 4vw, 38px);
    line-height: 1.1;
    margin: 0 0 8px;
    text-wrap: balance;
  }
.dw-gcc .standfirst {
    margin: 0;
    max-width: 62ch;
    color: var(--ink-soft);
  }
.dw-gcc .tool {
    display: grid;
    grid-template-columns: 1fr;
    gap: 20px 40px;
    align-items: start;
  }

  @media (min-width: 900px) {
.dw-gcc .tool { grid-template-columns: minmax(0, 1.15fr) minmax(0, 1fr); }
  }
.dw-gcc .panel {
    background: var(--panel);
    border: 1px solid var(--line);
  border-radius: 0;
    padding: 22px;
  }
.dw-gcc .field { margin-bottom: 18px; }
.dw-gcc .field:last-child { margin-bottom: 0; }
.dw-gcc label, .dw-gcc .label {
    display: block;
    font-family: var(--display);
    font-weight: 500;
    font-size: 15px;
    margin-bottom: 7px;
  }
.dw-gcc .hint {
    font-size: 14px;
    color: var(--ink-soft);
    font-weight: 400;
  }
.dw-gcc select, .dw-gcc input[type="number"] {
    width: 100%;
    font: 400 16px var(--body);
    color: var(--ink);
    background: var(--panel);
    border: 1px solid var(--line);
  border-radius: 0;
    padding: 6px 11px;
  }
.dw-gcc input[type="number"] {
    width: 7.5em;
    font-variant-numeric: tabular-nums;
  }
.dw-gcc .u {
  display: flex;
  width: 100%;
    display: inline-flex;
    align-items: baseline;
    gap: 5px;
    background: var(--panel);
    border: 1px solid var(--line);
  border-radius: 0;
    padding: 6px 10px;
  }
.dw-gcc .u input[type="number"] {
    width: 2.6ch;
    border: 0;
    padding: 0;
    background: transparent;
    appearance: textfield;
    -moz-appearance: textfield;
  }
.dw-gcc .u input[type="number"]::-webkit-outer-spin-button, .dw-gcc .u input[type="number"]::-webkit-inner-spin-button {
    appearance: none;
    -webkit-appearance: none;
    margin: 0;
  }
.dw-gcc .u:focus-within { outline: 2px solid var(--focus); outline-offset: 0; }
.dw-gcc .u input[type="number"]:focus-visible { outline: 0; }
.dw-gcc .u .unit, .dw-gcc .u .prefix {
    font-size: 14px;
    color: var(--ink-soft);
    pointer-events: none;
  }
.dw-gcc .u .prefix { font-size: 16px; }
.dw-gcc .s-tank { max-width: 15em; }
.dw-gcc .u-price input[type="number"] { width: 4.4ch; }
.dw-gcc .u-flow input[type="number"], .dw-gcc .u-litres input[type="number"] { width: 3.4ch; }
.dw-gcc :is(select, input, button, summary):focus-visible {
    outline: 2px solid var(--focus);
    outline-offset: 0;
  }
.dw-gcc .pair {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
    gap: 14px;
  }
.dw-gcc .chips { display: flex; flex-wrap: wrap; gap: 8px; }
.dw-gcc .chips button {
    font: 400 15px var(--body);
    color: var(--ink);
    background: var(--panel);
    border: 1px solid var(--line);
  border-radius: 0;
    padding: 8px 14px;
    cursor: pointer;
  }
.dw-gcc .chips button[aria-pressed="true"] {
  border-color: var(--navy);
  background: var(--navy);
  color: #fff;
  font-weight: 600;
}

/* "Tap flow rate (9 is average)" sits in a `.pair` column only ~200px wide, so
   the hint wrapped onto its own line under the label. Keep it beside the label
   text; the smaller hint size keeps the pair fitting the narrowest column the
   auto-fit grid allows before it stacks. */
/* No nowrap any more. It was here while the flow field shared a row and the
   hint was two words; the hint now carries a sentence and a link, on a label
   that spans the panel, so it has to be allowed to break. */
.dw-gcc label.label-inline-hint { white-space: normal; }
.dw-gcc label.label-inline-hint .hint { display: inline; font-size: 13px; }
.dw-gcc .field .fixed-note { margin-top: 8px; }
.dw-gcc .fixed-note {
    font-size: 13px;
    color: var(--ink-soft);
    margin: 14px 0 0;
  }
.dw-gcc .result { background: var(--navy); border-color: var(--navy); color: #fff; }
.dw-gcc .result .cost {
    font-family: var(--display);
    font-weight: 300;
    font-size: clamp(44px, 9vw, 60px);
    line-height: 1;
    font-variant-numeric: tabular-nums;
    margin: 2px 0 4px;
  }
.dw-gcc .result .cost-label, .dw-gcc .result .lead {
    font-size: 14px;
    letter-spacing: 0.06em;
    text-transform: uppercase;
    font-family: var(--display);
    opacity: 0.75;
    margin: 0;
  }
.dw-gcc .result .headline {
    margin-top: 20px;
    padding-top: 16px;
    border-top: 1px solid rgba(255, 255, 255, 0.22);
  }
.dw-gcc .result .cost-month { font-size: clamp(34px, 7vw, 46px); }
.dw-gcc .result .versus {
    margin: 10px 0 0;
    font-size: 15px;
    opacity: 0.9;
  }
.dw-gcc .result .versus strong { font-weight: 600; }
.dw-gcc .result .versus-sub {
    display: block;
    margin-top: 2px;
    font-size: 14px;
    opacity: 0.75;
  }
.dw-gcc .result dl {
    display: grid;
    grid-template-columns: 1fr auto;
    gap: 10px 16px;
    margin: 20px 0 0;
    padding-top: 16px;
    border-top: 1px solid rgba(255, 255, 255, 0.22);
    font-size: 15px;
  }
.dw-gcc .result dt { opacity: 0.8; }
.dw-gcc .result dd { margin: 0; text-align: right; font-variant-numeric: tabular-nums; font-weight: 600; }
.dw-gcc .compare {
  margin-top: 16px;
  font-size: 15px;
}
.dw-gcc .compare p { margin: 0 0 8px; }
.dw-gcc .compare p:last-child { margin-bottom: 0; }
.dw-gcc .compare strong { font-weight: 600; }
.dw-gcc .sizing {
  margin-top: 16px;
  font-size: 15px;
  color: var(--ink-soft);
}

/* The theme colours paragraphs directly - style.css has `body, p, li, a
   { color:#333 }` and cali.css repeats it per section background
   (`.clear-box p` and friends). A direct rule always beats inheritance, so
   the result panel's white text was being overridden on every <p> while its
   <dt>/<dd> stayed white: dark navy panel, near-black text. These selectors
   are (0,2,1), enough to beat `.clear-box p` at (0,1,1). */
.dw-gcc .result,
.dw-gcc .result p,
.dw-gcc .result dt,
.dw-gcc .result dd,
.dw-gcc .result strong,
.dw-gcc .result span {
  color: #fff;
}

/* Page-level headings, matching the size guide.
   That page gets 31px/500 from `.choose-my-geyser .section-heading h2` in
   choose-geyser.css; the theme's default is 28px/300, which reads markedly
   lighter beside it. These are the same values under this page's own class.
   (Not prefixed .dw-gcc - they style the page's section headings, not the
   calculator, and this stylesheet only loads where the calculator is.) */
.dw-gcc-page .section-heading h2 {
  font-size: 31px;
  font-weight: 500;
}

/* The calculator's heading is inside .dw-gcc, so the section generator's
   heading-space class does not reach it. Same 30px the theme uses. */
.dw-gcc h2 {
  margin-bottom: 30px;
}

/* On a phone this heading sits directly under the page's own h1, which asks
   the same thing in bigger type, and at the theme's 31px the pair of them
   pushed the first control below the fold - on a 375x812 screen it started
   at 830px. The wording stays, because "gas geyser consumption calculator"
   is a query this page ranks for; it just does not need to be the second
   largest thing on a phone screen. */
@media (max-width: 600px) {
  /* Carries both classes deliberately. The tool renders inside the section
     generator's .section-heading wrapper, so `.dw-gcc-page .section-heading
     h2` (0,2,1) above outranks a plain `.dw-gcc h2` (0,1,1), and a media
     query contributes no specificity of its own. Written the short way this
     rule parsed, matched, and did nothing. */
  .dw-gcc-page .section-heading .dw-gcc h2 {
    font-size: 22px;
    margin-bottom: 20px;
  }



  /* The intro band opens with 80px of air above the h1 (.padding-top, which
     goes to 100px from 768px up). On a desktop that is the page breathing;
     on a phone it is a tenth of the screen spent before the first word, and
     this page's job is to get someone to a control. Halved here only. */
  .dw-gcc-page .default-intro.padding-top {
    padding-top: 40px;
  }

  /* The theme sets 32px from `.main-heading h1`, which breaks this question
     over three lines on a 320px screen. Fluid between 320 and 600 so it is
     two lines the whole way across, and never larger than the theme's own
     size. The 40px below it is desktop spacing on a phone. */
  .dw-gcc-page .main-heading h1 {
    font-size: clamp(23px, 7vw, 32px);
    margin-bottom: 24px;
  }
}

/* the size link is a theme button, so it needs clearing from the sentence above it */
.dw-gcc .sizing .btn {
  display: block;
  width: fit-content;
  margin-top: 14px;
}

/* The number boxes fill their grid column so every field is the same width
   when the pairs sit side by side; the number itself keeps its own width and
   the unit label follows it rather than being pushed to the far edge. */
.dw-gcc .u {
  display: flex;
  width: 100%;
  box-sizing: border-box;
}

.dw-gcc .field > .u {
  max-width: none;
}

/* Bottle sizes: equal widths, spread across the row, largest first. */
.dw-gcc .chips {
  display: grid;
  grid-template-columns: repeat(3, 1fr);
  gap: 8px;
}

.dw-gcc .chips button {
  width: 100%;
  text-align: center;
}

/* The native select renders taller than the .u number boxes beside it and
   draws the browser's own arrow. Strip that and match the boxes: same border,
   padding and height, with a chevron drawn as a background image. The extra
   right padding keeps the longest option clear of it. */
.dw-gcc select {
  appearance: none;
  -webkit-appearance: none;
  -moz-appearance: none;
  height: 40px;
  padding: 6px 30px 6px 10px;
  font-size: 15px;
  line-height: 1.2;
  text-overflow: ellipsis;
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='12' height='8' viewBox='0 0 12 8'%3E%3Cpath d='M1 1l5 5 5-5' fill='none' stroke='%235b626e' stroke-width='1.6' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E");
  background-repeat: no-repeat;
  background-position: right 12px center;
  cursor: pointer;
}

/* One white container holding both columns, so the form and the results read
   as a single tool rather than two objects side by side. The white sits on
   .tool itself - the inner .panel keeps only its spacing, or the white would
   be drawn twice with a border between the two halves. */
.dw-gcc .tool {
  background: #f2f2f2;
  border: 0;
  padding: 24px;
}

.dw-gcc .tool > .panel {
  background: transparent;
  border: 0;
  padding: 0;
}

/* The figure is the thing being read, so it carries the weight. The inputs
   have fixed ch widths (they have to - a number input will not size to its
   content), so a short value like "8" left a gap before its unit. Aligning
   right pins the number against the unit whatever its length, which does the
   job without having to tune a width per field. */
.dw-gcc .u input[type="number"] {
  font-weight: 600;
  text-align: right;
}

.dw-gcc .u {
  gap: 4px;
}

.dw-gcc .u .prefix {
  font-weight: 400;
}

/* Bootstrap sets `dt { font-weight: 700 }`, which made the result labels
   heavier than their own values. Back to regular - the figure should carry
   the weight, not its label. */
.dw-gcc .result dt {
  font-weight: 400;
}


/* Padding matched to the 40px column gap, so the space around the two columns
   equals the space between them. Must come after the `.tool { padding: 24px }`
   rule above - a media query carries no extra specificity, so this is decided
   purely on source order. Two columns only: stacked on a phone, 40px a side
   plus the section container's own 30px gutters leaves too little width. */
@media (min-width: 900px) {
  .dw-gcc .tool {
    padding: 40px;
  }
}

/* ---------------------------------------------------------------------------
   UX pass, November 2026
   --------------------------------------------------------------------------- */

/* Assumptions. Ten controls were on show before the tool said anything; six of
   them are defaults nobody needs to touch. Folding them away leaves only what
   a visitor actually knows. The summary prints the live values, so they are
   folded, not hidden - you can see the gas price without opening anything. */
.dw-gcc .assumptions {
  margin-top: 20px;
}

.dw-gcc .assumptions > summary {
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  gap: 4px 10px;
  list-style: none;
  cursor: pointer;
  padding: 2px 0;
}

.dw-gcc .assumptions > summary::-webkit-details-marker { display: none; }

.dw-gcc .assumptions > summary .sum-title {
  font-family: var(--display);
  font-weight: 500;
  font-size: 15px;
  color: var(--blue);
}

/* The disclosure triangle, drawn rather than inherited so it can sit tight
   against the words and turn with the state. */
.dw-gcc .assumptions > summary .sum-title::before {
  content: "";
  display: inline-block;
  width: 0;
  height: 0;
  margin-right: 7px;
  vertical-align: 1px;
  border-left: 5px solid currentColor;
  border-top: 4px solid transparent;
  border-bottom: 4px solid transparent;
  transition: transform 0.15s ease;
}

.dw-gcc .assumptions[open] > summary .sum-title::before { transform: rotate(90deg); }

.dw-gcc .assumptions > summary .sum-values {
  font-size: 13px;
  color: var(--ink-soft);
}

.dw-gcc .assumptions-body { padding-top: 16px; }
.dw-gcc .assumptions-body > .field,
.dw-gcc .assumptions-body > .pair { margin-bottom: 18px; }

/* Gas against electric. The whole point of the page was a grey line of body
   copy ("Electric geyser equivalent: R602/month") while two equally large
   numbers competed above it. Same scale, two bars, one sentence. */
.dw-gcc .result .vs {
  margin-top: 20px;
  padding-top: 16px;
  border-top: 1px solid rgba(255, 255, 255, 0.22);
}

.dw-gcc .result .vs-row {
  display: grid;
  grid-template-columns: 4.6em 1fr 4.4em;
  align-items: center;
  gap: 10px;
  margin-bottom: 8px;
  font-size: 14px;
}

.dw-gcc .result .vs-key { opacity: 0.8; }

.dw-gcc .result .vs-track {
  height: 13px;
  border-radius: 999px;
  background: rgba(255, 255, 255, 0.14);
}

.dw-gcc .result .vs-bar {
  display: block;
  height: 100%;
  width: 0;
  border-radius: 999px;
  transition: width 0.25s ease;
}

.dw-gcc .result .vs-gas { background: var(--red); }
.dw-gcc .result .vs-elec { background: rgba(255, 255, 255, 0.55); }

.dw-gcc .result .vs-val {
  text-align: right;
  font-variant-numeric: tabular-nums;
  font-weight: 600;
}

.dw-gcc .result .vs-saving {
  margin: 12px 0 0;
  font-size: 16px;
  line-height: 1.35;
}

.dw-gcc .result .vs-saving strong { font-weight: 600; }
.dw-gcc .result .vs .versus-sub { margin-top: 4px; }

/* The peek bar. Stacked on a phone the result sits under a long form, so
   anyone adjusting a value was editing blind. Sticky within .tool - never
   fixed to the viewport, which on this site would mean sitting over the
   cookie banner. Hidden once the real panel is on screen. */
.dw-gcc .dwgcc-peek { display: none; }

@media (max-width: 899px) {
  .dw-gcc .dwgcc-peek {
    display: flex;
    gap: 18px;
    align-items: baseline;
    position: sticky;
    top: var(--dwgcc-peek-top, 0px);
    z-index: 20;
    margin: 0 -24px;
    padding: 10px 24px;
    background: var(--navy);
    color: #fff;
    font-size: 13px;
    letter-spacing: 0.04em;
    text-transform: uppercase;
    font-family: var(--display);
    transition: opacity 0.2s ease, visibility 0.2s ease;
  }

  .dw-gcc .dwgcc-peek b {
    font-size: 19px;
    font-weight: 500;
    letter-spacing: 0;
    font-variant-numeric: tabular-nums;
  }

  /* Removed, not just hidden. Holding its slot cost 69px - 49px of bar plus
     the grid's 20px row gap - of empty panel above the first control, on
     every load, for everyone, including the many who never scroll far enough
     to see it. display:none drops the grid item entirely, so there is no row
     and no gap. The bar's flow position is above the viewport by the time it
     switches on, so the browser's scroll anchoring absorbs the change rather
     than shunting the page under the reader's thumb. */
  .dw-gcc .dwgcc-peek.is-off {
    display: none;
  }
}

/* Two clauses would not sit on one line in a 374px panel at this tracking, so
   they are two lines by design rather than a wrap waiting to happen. */
.dw-gcc .result .lead-sub { margin-top: 2px; opacity: 0.6; }

/* A chip is one choice, so it breaks as one thing or not at all - at 375px
   "Summer · 22°C" was splitting across two lines inside its own button. */
.dw-gcc .chips button { white-space: nowrap; }

/* The theme sets `a { font-size: 18px }` site-wide, which blew up any note or
   sentence here the moment it contained a link. Said once for every link in
   the tool rather than per block - the buttons keep their own size. */
.dw-gcc a:not(.btn) { font-size: inherit; }


/* The values are what the tool is about, so they are set a size up from the
   labels rather than a size down. The inputs are sized in ch, so they widen
   with the type instead of clipping it; the steppers give back the four
   pixels this costs the longest unit ("litres a minute"). */
.dw-gcc select,
.dw-gcc input[type="number"] { font-size: 18px; }

.dw-gcc .u .unit { font-size: 15px; }
.dw-gcc .u .prefix { font-size: 17px; }



/* Sliders. The value box stays - it is where an exact figure gets typed and
   read - and the slider under it is for trying numbers, which is what people
   actually do with a calculator like this. The track fills to the current
   value through --p, set on each render, because a range input cannot style
   the portion behind its own thumb. */
.dw-gcc .slide { margin-top: 10px; }

.dw-gcc .range {
  -webkit-appearance: none;
  appearance: none;
  display: block;
  width: 100%;
  height: 20px;
  margin: 0;
  padding: 0;
  background: transparent;
  cursor: pointer;
}

.dw-gcc .range::-webkit-slider-runnable-track {
  height: 7px;
  border-radius: 999px;
  background: linear-gradient(to right, var(--navy) 0 var(--p, 0%), var(--line) var(--p, 0%) 100%);
}

.dw-gcc .range::-moz-range-track {
  height: 7px;
  border-radius: 999px;
  background: linear-gradient(to right, var(--navy) 0 var(--p, 0%), var(--line) var(--p, 0%) 100%);
}

/* -6.5px lifts a 20px thumb onto a 7px track: (track - thumb) / 2. The fill is
   a gradient, so its own leading edge stays square - it never shows, because
   the thumb is parked on it.

   The thumb is navy like the fill, not red. Red is spoken for on this page -
   the "Work out my size" button and the gas bar in the result - and spending
   it on six sliders would leave the one thing worth clicking no louder than a
   handle. The thumb is three times the height of its track, so the shape does
   the work of saying it can be dragged. */
.dw-gcc .range::-webkit-slider-thumb {
  -webkit-appearance: none;
  appearance: none;
  width: 20px;
  height: 20px;
  margin-top: -6.5px;
  border: 0;
  border-radius: 50%;
  background: var(--navy);
  box-shadow: 0 0 0 1px rgba(0, 0, 0, 0.08);
}

.dw-gcc .range::-moz-range-thumb {
  width: 20px;
  height: 20px;
  border: 0;
  border-radius: 50%;
  background: var(--navy);
  box-shadow: 0 0 0 1px rgba(0, 0, 0, 0.08);
}

.dw-gcc .range:focus-visible { outline: 0; }
.dw-gcc .range:focus-visible::-webkit-slider-thumb { box-shadow: 0 0 0 3px var(--focus); }
.dw-gcc .range:focus-visible::-moz-range-thumb { box-shadow: 0 0 0 3px var(--focus); }

/* The reading sits under the thumb and travels with it, which is why the row
   is a positioning context rather than a flex row. `left` is set from the
   script: the thumb's centre runs from half a thumb in to half a thumb from
   the end rather than the full width, and the reading is then held inside the
   row at either end, which needs its measured width. */
.dw-gcc .slide-read {
  position: relative;
  height: 20px;
  margin-top: 1px;
  font-size: 13px;
  line-height: 20px;
  font-variant-numeric: tabular-nums;
}

.dw-gcc .slide-val {
  position: absolute;
  top: 0;
  left: 0;
  transform: translateX(-50%);
  white-space: nowrap;
  font-weight: 600;
  color: var(--ink);
}

/* The ends sit on the reading's baseline. Both are absolutely positioned from
   the same `top`, so a different font size put them on different baselines -
   a smaller face in the same box drops its baseline about a pixel, which is
   exactly the sort of misalignment the eye catches on a row of numbers. Same
   size and same line-height; weight and colour do the separating. */
.dw-gcc .slide-end {
  position: absolute;
  top: 0;
  color: var(--ink-soft);
}

/* The fade is for a label the thumb is arriving at, not for the first paint -
   without this the end labels are drawn, then fade out on load. */
.dw-gcc.is-ready .slide-end { transition: opacity 0.12s ease; }

.dw-gcc .slide-min { left: 0; }
.dw-gcc .slide-max { right: 0; }

/* The reading would otherwise sit on top of an end label as it reaches it. */
.dw-gcc .slide-read.near-min .slide-min,
.dw-gcc .slide-read.near-max .slide-max { opacity: 0; }

/* `.chips` is a three-column grid, sized for the three bottles. The two-button
   rows were inheriting it and sitting in two of those three columns, stopping
   a third short of the edge. A pair gets two columns, so either row - Shower /
   Bath and Summer / Winter alike - fills the column in equal halves. */
.dw-gcc .chips-mode,
.dw-gcc .chips-pair,
.dw-gcc .chips-region {
  grid-template-columns: 1fr 1fr;
}

/* Shower / Bath wears the same chip as Summer / Winter - same height, type and
   colours. Only the spacing differs, since it heads the form. */
.dw-gcc .chips-mode { margin-bottom: 22px; }

/* The navy block slides between the halves instead of being redrawn on the
   one you picked.

   Stacking, since it is the whole trick: the block is a positioned
   ::before with z-index 1, so it paints over the buttons' own white
   backgrounds and borders. The buttons themselves get no z-index - that would
   trap their contents underneath - and each label is a positioned span at
   z-index 2, which lets it ride over the block as it arrives. */
.dw-gcc .chips-mode,
.dw-gcc .chips-pair,
.dw-gcc .chips-region { position: relative; }

.dw-gcc .chips-mode::before,
.dw-gcc .chips-pair::before,
.dw-gcc .chips-region::before {
  content: "";
  position: absolute;
  z-index: 1;
  top: 0;
  left: 0;
  width: calc((100% - 8px) / 2);
  height: 100%;
  background: var(--navy);
  transform: translateX(0);
}

/* Only from the second paint, like the slider end labels. The block starts at
   the left and is put where the state says on load - with Summer now the
   right-hand chip, and Summer the default, an ungated transition meant the
   block slid across the row every time the page opened. */
.dw-gcc.is-ready .chips-mode::before,
.dw-gcc.is-ready .chips-pair::before,
.dw-gcc.is-ready .chips-region::before {
  transition: transform 0.24s cubic-bezier(0.4, 0, 0.2, 1), opacity 0.15s ease;
}

/* A full half plus the gap is exactly the second column's offset. */
.dw-gcc .chips-mode.is-second::before,
.dw-gcc .chips-pair.is-second::before,
.dw-gcc .chips-region.is-second::before { transform: translateX(calc(100% + 8px)); }

/* Typing a temperature of your own leaves neither season chosen, and a block
   parked on one of them would be claiming otherwise. */
.dw-gcc .chips-pair.is-none::before,
.dw-gcc .chips-region.is-none::before { opacity: 0; }

.dw-gcc .chips-mode button span,
.dw-gcc .chips-pair button span,
.dw-gcc .chips-region button span {
  position: relative;
  z-index: 2;
}

/* The block is the only thing that marks the choice now, so the pressed chip
   keeps its own background and border out of the way. */
.dw-gcc .chips-mode button[aria-pressed="true"],
.dw-gcc .chips-pair button[aria-pressed="true"],
.dw-gcc .chips-region button[aria-pressed="true"] {
  background: var(--panel);
  border-color: var(--line);
}

@media (prefers-reduced-motion: reduce) {
  .dw-gcc.is-ready .chips-mode::before,
  .dw-gcc.is-ready .chips-pair::before,
  .dw-gcc.is-ready .chips-region::before { transition: none; }
}

/* A hint belongs beside the words it qualifies. Something upstream sets
   `.hint` to display:block, and this file used to patch that one label at a
   time, so say it once for every label here instead. `.label-inline-hint`
   still adds nowrap on top, for the one label in a column too narrow to risk
   a break. */
.dw-gcc label .hint { display: inline; }

/* The summary carries the values so nothing is lost while the block is shut.
   Once it is open the sliders are right underneath saying the same thing, so
   the line stands down and the summary is just a heading. */
.dw-gcc .assumptions[open] > summary .sum-values { display: none; }


/* Incoming water belongs to the season above it, so it sits under the chips at
   full width rather than being paired off with something unrelated. */
.dw-gcc .field.incoming { margin: 18px 0 0; }

/* A pair whose two readings are short - "40°C", "2 showers" - splits at 110px
   a side instead of the 200px `.pair` asks for. That larger minimum exists for
   "9 litres a minute" on the flow field, and imposing it here would stack two
   fields that fit side by side even on a phone. */
.dw-gcc .pair.pair-tight {
  grid-template-columns: repeat(auto-fit, minmax(110px, 1fr));
}

/* An unchosen chip is tinted rather than outlined. White on the panel's own
   near-white needed a border to exist at all; a grey a step darker holds its
   own shape, so the outline comes off and the row reads as blocks of colour -
   unchosen, chosen, panel - instead of boxes. The tint is a few steps down
   from the panel and a shade cooler than the theme's warm greys, which keeps
   it reading as a surface rather than as an edge; hover takes it one step
   further down the same scale.
   The padding gains the pixel each side that the border was contributing, so
   the height is unchanged and the sliding block still lands flush. */
.dw-gcc .chips button {
  background: var(--chip);
  border: 0;
  padding: 9px 14px;
}

/* Not on the chosen one: its navy is painted by the block in the two-button
   rows and by the button itself among the bottles, and a hover lightening
   either would read as the choice coming undone. */
.dw-gcc .chips button:not([aria-pressed="true"]):hover {
  background: var(--chip-hover);
}

/* In the rows with a sliding block, the chosen chip keeps the unchosen tint -
   the block is what marks it, and it is drawn on top. */
.dw-gcc .chips-mode button[aria-pressed="true"],
.dw-gcc .chips-pair button[aria-pressed="true"],
.dw-gcc .chips-region button[aria-pressed="true"] {
  background: var(--chip);
}

/* The unchosen label sits back at 70%. Set as a colour rather than `opacity`,
   which would take the chip's background down with it, and because the bottle
   chips have no inner span to fade on their own. That is --ink at 0.7, which
   lands near #5a5e64 over the chip - about 4.9:1 against it, still clear of
   the 4.5:1 a label needs, so it recedes without reading as disabled. */
.dw-gcc .chips button:not([aria-pressed="true"]) {
  color: rgba(34, 38, 46, 0.7);
}

/* A price and the thing it prices share a line: the figure is typed, so it
   needs a box rather than a track, and it is narrow enough to leave the
   bottle chips or the tank select the rest of the row. Flex rather than grid,
   so the break is decided by what the two actually need - below about 390px
   of column the second half drops to its own line, which is what happens on a
   phone. The price leads, as the narrower of the two. */
.dw-gcc .price-row {
  display: flex;
  flex-wrap: wrap;
  gap: 14px;
  margin-bottom: 18px;
}

.dw-gcc .price-row > .field {
  margin-bottom: 0;
  min-width: 0;
}

.dw-gcc .price-row > .field:first-child { flex: 0 1 150px; }
.dw-gcc .price-row > .field:last-child { flex: 1 1 220px; }

/* Three chips in half a row need their padding back - 14px a side was set
   when they had the whole width to themselves. */
.dw-gcc .price-row .chips button { padding: 9px 8px; }

/* The select is 40px and the price box 42px; matching them lines the two
   controls up along the bottom of the row. */
.dw-gcc .price-row select { height: 42px; }

/* The two comparisons are a label and a figure, so they are set as rows with
   the value against the right edge - the same shape as the list in the panel
   above, which makes the two figures comparable at a glance instead of being
   hunted for mid-sentence. Baseline alignment, so the bold figure sits on the
   label's line rather than on the box's. */
.dw-gcc .compare-row {
  display: flex;
  justify-content: space-between;
  align-items: baseline;
  gap: 16px;
}

.dw-gcc .compare-row strong {
  font-variant-numeric: tabular-nums;
  white-space: nowrap;
}

/* The custom-temperature wording carries two figures, which a two-column row
   has nowhere to put, so that one stays a sentence. */
.dw-gcc .compare-row.is-wide { display: block; }

/* Everything under the result panel lines up with the type inside it, not
   with the panel's outer edge. The panel carries 22px of padding, so its
   figures sit 22px in; without the same inset here, "The same shower in
   winter" started a full 22px to the left of "Each shower" directly above it,
   and the right-hand figures missed the column they belong to. */
.dw-gcc .compare,
.dw-gcc .sizing {
  padding-left: 22px;
  padding-right: 22px;
}

/* The summary shows at every width. It was hidden above 900px, on the view
   that the block is open there anyway and nobody collapses it - but that also
   removed the only thing naming the block, and the live values it prints
   beside itself. It is a real control again: open by default on the desktop,
   closable, and identical to the phone treatment. */
/* The tank is picked from a list of four, and the longest of them is wider
   than the 15em the select was capped at, so it fills its half of the row
   like the price box opposite fills its own. */
.dw-gcc .price-row select {
  max-width: none;
  width: 100%;
}

/* Spacing rhythm. Everything was sitting on roughly the same gap - 7px under
   a label, 10px more before a slider, 14-18px between fields - so nothing
   grouped: a label looked no more attached to its own control than to the
   field below it. Two distances now, one small and one large, named so they
   stay in step. */
.dw-gcc {
  --gap-label: 5px;
  --gap-field: 37px;
}

/* A phone shows one column, so every gap between fields is spent on height
   that pushes the result further away - six blocks at 30px was 180px of air
   in a 753px form. 20px still reads as four times the 5px under a label, so
   a field is as clearly one unit as it was; there is just less between them. */
@media (max-width: 600px) {
  .dw-gcc { --gap-field: 33px; }
}

.dw-gcc label,
.dw-gcc .label { margin-bottom: var(--gap-label); }

/* The slider carried its own 10px on top of the label's margin, which made
   the slider fields read looser than the boxed ones. The thumb overhangs the
   track by 6.5px either side, and that overhang is the air it needs. */
.dw-gcc .slide { margin-top: 0; }

.dw-gcc .field { margin-bottom: var(--gap-field); }
.dw-gcc .field:last-child { margin-bottom: 0; }

/* Row gap only: side by side the columns stay at 14px, stacked they take the
   full field gap. A `.field` inside a pair kept its own bottom margin too,
   which added to the grid gap and made stacked pairs drift wider than
   everything else. */
.dw-gcc .pair { gap: var(--gap-field) 14px; }
.dw-gcc .pair > .field { margin-bottom: 0; }

.dw-gcc .price-row {
  gap: var(--gap-field) 14px;
  margin-bottom: var(--gap-field);
}

.dw-gcc .chips-mode { margin-bottom: var(--gap-field); }
.dw-gcc .field.incoming { margin-top: var(--gap-field); }
.dw-gcc .assumptions { margin-top: var(--gap-field); }

/* A pair is a row of fields, so it closes with the same gap a field does.
   Without this the shower-length/flow pair ran straight into "Time of year" -
   most visibly under the bucket-test note, which is the lowest thing in that
   row and so the one that touched. */
.dw-gcc .pair { margin-bottom: var(--gap-field); }

/* The bucket-test note belongs to the flow field, but sitting inside it made
   that half of the row taller than the half beside it, so the left column
   carried a long empty run down to the next label - which read as a wider gap
   above "Time of year" even though it measured narrower. The note now sits
   under the whole row: both columns end level, and the note keeps the row's
   own gap to what follows. */
.dw-gcc #dwgcc-shower-fields { margin-bottom: var(--gap-field); }
.dw-gcc #dwgcc-shower-fields .pair { margin-bottom: 8px; }
/* 2px back: a link's inline box sits a little higher in its line than a
   slider's reading does, so the same margin measured 2.4px tighter to the eye
   than every other gap in the form. Padding, not margin - the note is the
   last child of a wrapper with its own bottom margin, which a margin here
   would simply collapse into. */
/* The bucket test is the one thing in the tool worth leaving the page for, so
   it is set in the brand red rather than the link blue the rest of the body
   copy uses - under the flow field, and again in the bath mode sizing line.
   Not the CTA, which is already a red button. */
.dw-gcc .note-flow a,
.dw-gcc .sizing a:not(.btn) { color: var(--red); }

/* The sizing block asks a question and answers it. The heading matches the
   field labels in size and family so it belongs to the tool, not to the page
   around it. */
.dw-gcc .sizing-block { margin-top: var(--gap-field); }

.dw-gcc .sizing-head {
  font-family: var(--display);
  font-weight: 500;
  font-size: 16px;
  line-height: 1.3;
  color: var(--ink);
  margin: 0;
  padding: 0 22px;
}

.dw-gcc .sizing { margin-top: var(--gap-label); }

/* Everything under the result panel reads at the same 15px as the list inside
   it. The `.compare` rule set that on the container, but the theme styles `p`
   directly - and a direct rule beats an inherited one - so the two comparison
   rows had been rendering at the theme's 18px, a size larger than the figures
   they sit under. Set on the paragraphs themselves, where it wins. */
.dw-gcc .compare p,
.dw-gcc .sizing { font-size: 15px; }

/* The zone switch sits under the gas price it writes into, so it reads as a
   shortcut for that box rather than a separate question. Same 10px the
   sliders take between a label and their track. */
.dw-gcc .chips-region { margin-top: 10px; }

/* Gas price and its zone switch share a line: the chips set what is in the
   box beside them, so standing them one above the other read as two separate
   questions. The label takes the full row so it still sits over the pair, and
   the chips keep their intrinsic width - they wrap under the box only when
   there is genuinely no room, which on this layout is below about 330px. */
.dw-gcc .field-gas {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 10px;
}

/* The price field was pinned to 150px so it would sit beside the bottle
   sizes. It now carries the zone switch as well, which needs about twice
   that, so it takes the width it needs and the bottle sizes drop to their
   own line underneath - a row of three full-width chips, which is how they
   read best anyway. Only this row wraps; the electricity row opposite still
   holds its price and tank side by side. */
.dw-gcc .price-row-gas { flex-wrap: wrap; }

/* Both selectors carry price-row and field twice over. `.dw-gcc .price-row >
   .field:first-child` sets the 150px and counts four class-level parts, so a
   three-part selector loses to it however far down the file it sits - the
   same trap the mobile h2 rule fell into. */
.dw-gcc .price-row.price-row-gas > .field.field-gas { flex: 1 1 300px; }

.dw-gcc .price-row.price-row-gas > .field:not(.field-gas) { flex: 1 1 100%; }

.dw-gcc .field-gas > label {
  flex: 0 0 100%;
  margin-bottom: 0;
}

.dw-gcc .field-gas > .u {
  flex: 1 1 140px;
  width: auto;
}

.dw-gcc .field-gas > .chips-region {
  flex: 0 0 auto;
  margin-top: 0;
}

/* The electricity price and the tank it applies to belong on one line, the
   way the pairs above them are. Their desktop bases are 150px and 220px,
   which with the 14px gap needs 384px and so wrapped on every phone. Equal
   halves instead: the pair reads as one question, and neither is wide enough
   to want more. The gas row above is excluded - it wraps on purpose, to give
   the zone switch room beside the price. */
/* No breakpoint. Fixed bases of 150px and 220px plus the 14px gap need 384px
   of row, and the form column is narrower than that twice over: on a phone,
   and again just above the two-column breakpoint where that layout makes
   it ~337px. Scoping the fix to one of those left the other stacked. The pair
   never wraps now - it holds a 2:3 split and shrinks, so the price keeps the
   narrow box and the tank keeps the wide one at every width. */
.dw-gcc .price-row:not(.price-row-gas) { flex-wrap: nowrap; }

.dw-gcc .price-row:not(.price-row-gas) > .field:first-child { flex: 2 1 0; min-width: 0; }

.dw-gcc .price-row:not(.price-row-gas) > .field:last-child { flex: 3 1 0; min-width: 0; }


/* The bucket test sits under the slider at every width. It used to move -
   beside the label on a wide screen, below the track on a phone - which took
   a flex row and an `order` swap to arrange, and put it in a different place
   depending on the window. Under the track is where it belongs anyway: you
   reach for it at the moment you try to set the flow and realise you do not
   know it, not before. Plain source order now, so the DOM reads the way the
   page does. */
.dw-gcc .field-flow > .note-flow { margin: 8px 0 0; }

/* Shallower controls. Everything sat at 42-43px - chips at 9px of padding
   either side of a 15px label, the price boxes at 6px around an 18px number,
   the tank select pinned to 42px. Three pixels off each pair takes them to
   36-37px without touching a font size, which is what keeps the numbers as
   legible as they were. The chips stay wide, so the tap area loses height
   and nothing else; 36px is still half again the 24px WCAG asks for. */
.dw-gcc .chips button {
  padding-top: 6px;
  padding-bottom: 6px;
}

.dw-gcc .price-row .chips button {
  padding-top: 6px;
  padding-bottom: 6px;
}

.dw-gcc .u {
  padding-top: 3px;
  padding-bottom: 3px;
}

.dw-gcc .price-row select { height: 36px; }

/* "per kWh" broke across two lines and made the box twice as tall as the one
   beside it. The unit holds its line now, and the price field is allowed to
   be as wide as its own content rather than shrinking past it - min-content,
   not 0. When the row is tight it is the tank select that gives way, which is
   the right one to lose: its text is a convenience, and tapping it still
   shows every option in full. */
.dw-gcc .u .unit { white-space: nowrap; }

.dw-gcc .price-row:not(.price-row-gas) > .field:first-child { min-width: min-content; }

/* Less air around the tool on a phone. The intro band opens with 40px top and
   bottom, the card adds 24px of its own, and the h1 carries 24px below it -
   120px of padding before a single control, on the screen with the least room
   for it. */
@media (max-width: 600px) {
  .dw-gcc-page .default-intro.padding-top { padding-top: 34px; }
  .dw-gcc-page .default-intro { padding-bottom: 24px; }
  .dw-gcc-page .main-heading h1 { margin-bottom: 16px; }
  .dw-gcc .tool { padding: 24px 30px; row-gap: 16px; }
}



/* The efficiency footnote now sits under the card rather than inside it, so
   it takes its distance from the box, not from a field. It stays at the
   .fixed-note size - it is a footnote to the tool, not a line of the page. */
.dw-gcc .tool-note { margin: 16px 0 0; }

/* Two columns on anything that is not a phone. The pair floors each column at
   200px, so a row needs 414px with the gap - but the two-column desktop
   layout hands the form only ~337px at 900px wide and 401px at 1024px, so the
   pair stacked on exactly the screens that have the most room overall. 160px
   is the floor that fits from the two-column breakpoint up. Phones keep the 200px
   floor and stay single column: at 414px a phone would otherwise split the
   row into two 176px sliders, which is not enough track to set a value on. */
@media (min-width: 601px) {
  .dw-gcc .pair {
    grid-template-columns: repeat(auto-fit, minmax(160px, 1fr));
  }
}

/* The intro reads at body size on this page, not as a lead. The theme sets
   `.main-1st-col p` to 20px, and 24px from 600px up, which on a page whose
   job is to get someone into a calculator made the first paragraph the
   loudest thing under the h1 and pushed the tool down for no gain. 18px is
   the theme's own paragraph size, so it matches the sections further down
   the page rather than competing with them. */
.dw-gcc-page .default-intro .main-1st-col p {
  font-size: 18px;
  line-height: 1.6;
}

/* Edge to edge, without vw. `calc(50% - 50vw)` looked elegant and was wrong:
   100vw counts the classic scrollbar that clientWidth does not, so on any
   desktop browser with one the card is pulled about 7px too far each side and
   its contents clip. Below 576px the theme's container is full width with a
   flat 30px gutter, so minus that gutter is an exact number and no viewport
   unit is needed. From 576px the container becomes a centred 540px box, where
   full bleed has nothing to gain, so it simply stops.

   The card's own padding matches the gutter it replaces, so its controls line
   up with the h1 and the intro above them instead of sitting nearer the glass
   than the rest of the page. */
@media (max-width: 575px) {
  .dw-gcc-page .section-heading .dw-gcc .tool {
    margin-left: -30px;
    margin-right: -30px;
  }
}

/* The tool splits into two columns at 900px, not 840px. At 840 the split left
   the form just 308px - narrower than it gets on a 375px phone - so the pair
   inside it stacked and the panel was more cramped than it had been one pixel
   earlier in a single column. Below 900 the tool stays full width, where it
   has 700px to play with. The peek bar and the assumptions fold follow the
   same number, in CSS and in the script, so all four agree. */

/* The heading lives inside the card now. As a grid child it would otherwise
   take one cell of the first row and sit beside the form, so it spans every
   column; and the card's own top padding is what gives it air, which is why
   that went back up to 24px on a phone. */
.dw-gcc .tool > h2 {
  grid-column: 1 / -1;
}

/* No white strip under the tool on a phone. The section carries padding below
   it and the grey section that follows carries its own 80px above, so the two
   stack into a band of empty white between blocks that are already separated
   by a change of colour. The section below supplies all the air needed, so
   this one gives none. `:has` rather than a class combination, because what
   is being selected is "the section the calculator is in", not a particular
   pair of spacing classes someone might change in the page builder. Desktop
   keeps its 60px - there the card is inset and the strip reads as margin
   rather than as a gap. */
@media (max-width: 600px) {
  .dw-gcc-page .columns:has(.dw-gcc) {
    padding-bottom: 0;
  }
}


/* The sub-heading inside a section-generator block renders at the theme's
   light h3 weight, which reads as body copy beside the paragraphs around it.
   It stays an h3 - it is a real sub-heading and belongs in the outline - and
   simply carries the weight that makes it look like one. */
.dw-gcc-page .columns h3 {
  font-weight: 600;
}

/* The four drivers as numbered cards. Two columns where there is room, one
   on a phone, and outlined rather than filled - the section sits on light
   grey, so a white card with a line round it reads as a card without adding
   another block of colour to a page that already has a navy result panel.
   The number is decorative: it is aria-hidden, because a screen reader gets
   the heading and the count is only there to say "four things". */
.dw-gcc-page .dw-drivers {
  display: grid;
  grid-template-columns: 1fr;
  gap: 16px;
  margin-top: 24px;
}

/* Two columns, fixed - not auto-fit. Four cards in an auto-fit grid became
   three across with a lone fourth underneath at desktop widths, which reads
   as a mistake. Two by two keeps the set balanced at every width that can
   hold it. */
@media (min-width: 700px) {
  .dw-gcc-page .dw-drivers { grid-template-columns: 1fr 1fr; }
}

.dw-gcc-page .dw-driver {
  /* The same grey as the calculator card above, so the drivers read as the
     same kind of object. Filled rather than outlined: on a white section the
     fill alone separates them, and a border on top of it only thickens the
     edge of something already distinct. */
  background: #f2f2f2;
  padding: 24px;
}

.dw-gcc-page .dw-driver__n {
  display: flex;
  align-items: center;
  justify-content: center;
  width: 40px;
  height: 40px;
  /* Optically centred, not box centred. A digit has no descender, so its ink
     sits about 1.4px above the middle of its own line box at this size - the
     circle looks right to a measuring tool and wrong to an eye. 3px of top
     padding inside a border-box moves the content down half that. */
  box-sizing: border-box;
  padding-top: 3px;
  border-radius: 50%;
  /* The same navy as the result panel, the header and the selected chips -
     #001538. Written out rather than var(--navy), because that custom
     property is declared on .dw-gcc and these cards sit outside the tool. */
  background: #001538;
  color: #fff;
  font-family: var(--display, inherit);
  font-size: 18px;
  font-weight: 600;
  line-height: 1;
}

.dw-gcc-page .dw-driver h3 {
  font-size: 19px;
  font-weight: 600;
  margin: 14px 0 8px;
}

.dw-gcc-page .dw-driver p {
  font-size: 16px;
  margin: 0;
}

@media (max-width: 600px) {
  .dw-gcc-page .dw-driver { padding: 18px; }
}

/* Four across once there is room for it. Two-by-two is right for the middle
   of the range, but on a wide screen the set reads better as one row - four
   drivers, four columns, no second row to scan. */
@media (min-width: 992px) {
  .dw-gcc-page .dw-drivers { grid-template-columns: repeat(4, 1fr); }
}

/* Four across starts at 992, where each card is about 206px. At the standard
   24px the text column drops to 156px and the body runs four words a line,
   so the padding eases off until there is room for it again at 1200. */
@media (min-width: 992px) and (max-width: 1199px) {
  .dw-gcc-page .dw-driver { padding: 18px; }
}

/* Headings break where the copy says, not where the column happens to run
   out. Each intended line is a .dw-line span - the same device the icon row
   uses, but the other way round: inline on a phone, where the card is full
   width and one line is fine, and block from 992 so all four headings are
   two lines and every card's body starts on the same baseline. */
.dw-gcc-page .dw-driver h3 .dw-line { display: inline; }

@media (min-width: 992px) {
  .dw-gcc-page .dw-driver h3 .dw-line { display: block; }
}

/* The values take a line of their own. Beside the title they read as part of
   the heading; under it they read as what they are - the figures the sums are
   using, which is the reason for showing them while the block is shut. */
.dw-gcc .assumptions > summary .sum-values {
  flex: 0 0 100%;
}

/* More air above Incoming water. It is the one label that follows a control
   rather than another label - it sits directly under the Winter / Summer
   chips, inside the same field - so at the standard gap it read as part of
   the chips rather than as its own question. */
.dw-gcc .field.incoming {
  margin-top: var(--gap-field);
}

/* Nothing escapes sideways. The card is pulled out by exactly the container's
   30px gutter, so it lands flush with the viewport edge - and flush is one
   rounding error away from overflowing on a device with a fractional pixel
   ratio, which is a page that scrolls left to right by three or four pixels.
   `clip` rather than `hidden` on purpose: `hidden` makes this a scroll
   container, which would break the peek bar's position:sticky. */
@media (max-width: 575px) {
  .dw-gcc-page .columns:has(.dw-gcc) {
    overflow-x: clip;
  }
}

/* Do / don't list. The thing that does not work used to sit in a paragraph
   under the list, where it read as an afterthought - as a marked item it is
   as visible as the three that do. Two pseudo-elements per row: ::before is
   the coloured disc, ::after is the glyph masked out of it in white, using
   the same tick.svg and cross.svg the size guide draws its icons from. The
   marks are decorative - each line says in words whether it helps - so a
   screen reader loses nothing by not announcing them. */
.dw-gcc-page .dw-check {
  list-style: none;
  margin: 16px 0 0;
  padding: 0;
}

.dw-gcc-page .dw-check li {
  position: relative;
  padding-left: 34px;
  margin-bottom: 12px;
}

.dw-gcc-page .dw-check li::before,
.dw-gcc-page .dw-check li::after {
  content: "";
  position: absolute;
  left: 0;
  top: 3px;
  width: 22px;
  height: 22px;
}

.dw-gcc-page .dw-check li::before {
  border-radius: 50%;
}

.dw-gcc-page .dw-check li::after {
  background: #fff;
  -webkit-mask: var(--dw-glyph) center / 52% 52% no-repeat;
          mask: var(--dw-glyph) center / 52% 52% no-repeat;
}

.dw-gcc-page .dw-check .dw-yes::before { background: #001538; }
.dw-gcc-page .dw-check .dw-yes::after  { --dw-glyph: url(../images/icons/tick.svg); }

.dw-gcc-page .dw-check .dw-no::before { background: #ea0029; }
.dw-gcc-page .dw-check .dw-no::after  { --dw-glyph: url(../images/icons/cross.svg); }

/* The tank's limit, under the cost footnote. Same muted treatment as the note
   above it, with a little air so it reads as its own statement rather than a
   runover of the line before. */
.dw-gcc .result .versus-limit {
    display: block;
    margin: 7px 0 0;
    font-size: 14px;   /* matches .versus-sub above it */
    opacity: 0.9;      /* a touch stronger: it is a statement, not a footnote */
}
.dw-gcc .versus-limit[hidden] { display: none; }

/* The electric comparison, sitting inside the dark results list directly under
   the gas price.

   NOT red. This panel already has a gas/electric colour key a few lines above:
   the gas bar is the brand red #ea0029 and the electric bar is white at 55%.
   Red here would have meant gas in one place and electric in the other, on the
   same panel. Following the key instead - the electric row takes the same
   muted white as the electric bar, so the two readings agree.

   0.62 rather than the bar's 0.55: a 3px bar can be fainter than 15px text and
   still register. This measures 6.0:1 on the navy, comfortably above 4.5:1. */
.dw-gcc .result dt.is-elec,
.dw-gcc .result dd.is-elec { color: rgba(255, 255, 255, 0.62); }
.dw-gcc .result dt.is-elec { opacity: 1; }   /* dt is otherwise muted twice over */

/* The gas counterpart to the tank's limit. Not muted like the note above it -
   this is the point the comparison is making, not a footnote to it. */
.dw-gcc .result .versus-gas {
    display: block;
    margin: 2px 0 0;
    font-size: 14px;
    font-weight: 600;
}

/* Result rows: one flex row each, replacing the two-column grid set at the
   top of this file. The grid sized its value column to the widest value in
   the whole list ("about 6 months", 105px), so every label was squeezed into
   what was left. On a 375px phone that is 148px, and "Showers per 48 kg
   bottle" needs 162px, so the word "bottle" dropped to a second line. A row
   that sizes on its own gives that label the whole width its own value ("354",
   23px) does not use, and it holds one line down to a 320px screen. The
   result is visually identical to the grid - labels flush left, values flush
   right - because the value column was already right-aligned to the panel
   edge. Must come after the `.result dl` grid rule above: same specificity,
   so source order decides. */
.dw-gcc .result dl {
  display: block;
}
.dw-gcc .result dl > div {
  display: flex;
  justify-content: space-between;
  align-items: baseline;
  gap: 16px;
}
.dw-gcc .result dl > div + div {
  margin-top: 10px;
}
