/* ==========================================================================
   AiDi 2026
   --------------------------------------------------------------------------
   Two layers:

   1. CHROME (.a26-nav, .a26-pagehead, .a26-foot) — site-wide, because
      header.php and footer.php are now the new design.
   2. SECTIONS (.aidi26 ...) — only output by the AiDi 2026 page template.

   Tokens are ported from Aidi/Theme/AidiTheme.swift, with --a-blue updated to
   the current brand royal blue. Every class is a26-/aidi26- prefixed, so
   nothing collides with the legacy style.css.
   ========================================================================== */

/* --------------------------------------------------------------------------
   Reset. style.css is no longer enqueued (its bare `header`/`footer` rules
   broke the new chrome), and the legacy header's normalize.css/reset.css went
   with it — so the baseline lives here now. Deliberately small.
   -------------------------------------------------------------------------- */
*,*::before,*::after{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0}
h1,h2,h3,h4,h5,h6,p,figure,blockquote,dl,dd{margin:0}
/* :where() keeps this at zero specificity. Written as a bare
   `ul[class]` it scores higher than a single class, so it silently beat
   .a26-ticks, .a26-text ul and every other list rule in this file — the
   margins were set and then overridden by the reset. */
:where(ul[class],ol[class]){list-style:none;margin:0;padding:0}
img,svg,video{max-width:100%;display:block}
button,input,select,textarea{font:inherit;color:inherit}
a{color:inherit}
table{border-collapse:collapse}

:root{
  --a-blue:#0F62F2;          /* brand royal blue */
  /* The bar and the footer. #1E6BF3 is as light as a blue can go and still
     clear 4.5:1 for white text (4.72:1) — the next step up drops to 4.32 and
     fails — so this is the only one of the three blues that takes white type
     at any size. Both ends of the page therefore use it. */
  --a-blue-chrome:#1E6BF3;
  --a-nav:var(--a-blue-chrome);
  /* The inner page title band, sitting between them. Lighter, which is what
     separates it from the bar directly above it.

     White on this is 3.81:1: enough for WCAG's 3:1 large-text rule, not for
     the 4.5:1 normal-text one. The h1 is large by any measure; the crumb
     above it is sized up to 19px semibold so that it is too. Nothing smaller
     than that goes in white on this band — dark ink (4.55:1) is the only
     option if something ever has to. */
  --a-blue-band:#337DFF;
  --a-blue-dark:#0B4FC8;     /* blue TEXT on the wash — #0F62F2 is 4.22:1 there, under AA */
  --a-wash:#EEF4FF;
  --a-wash-hover:#E2EBFE;
  --a-ink:#141A2B;
  --a-body:#3D4250;
  --a-muted:#5C6474;         /* NOT #6B7280 — that fails AA on the wash */
  --a-line:#E4E9F2;
  --a-teal:#2DD4BF;          /* identity accent — decorative only, never text */
  --a-pink:#FF95B7;
  --a-pink-ink:#B03A63;
  --a-r:14px;
  /* The content column. 1280 left a lot of room unused on a 1440+ screen,
     which is what most of this site's desktop traffic will be on. The
     measure caps below do the readability work, so a wider column widens the
     grids and the images without stretching any line of text. */
  --a-max:1440px;

  /* Accents, sampled from the App Store screenshots. The pastels are the
     app's own content-type colours; the highlight ink is what sits on them. */
  --a-yellow:#FFE066;
  --a-mint:#8DEBBE;
  --a-coral:#FFA8C8;
  --a-peach:#FFC98A;
  --a-lilac:#D1D9FF;
  --a-mark-ink:#1B2A66;   /* 7.4:1 or better on every pastel above */
  --a-icon-ink:#0B4FC8;   /* 5.08:1 on lilac — #0F62F2 is only 3.72:1 */

  /* Handbook tiles: a light fill and a dark ink per tone, both derived from the
     base hue rather than picked by eye. Each ink clears 4.5:1 on its own tile —
     well past the 3:1 WCAG 1.4.11 asks of a meaningful icon — and every tile is
     lighter than the base tone it came from. */
  --a-lilac-tile:#DBE1FD; --a-lilac-ink:#1234D9;   /* 6.40:1 */
  --a-mint-tile:#E0F8EC;  --a-mint-ink:#167E4C;    /* 4.57:1 */
  --a-coral-tile:#FDDBE7; --a-coral-ink:#C61053;   /* 4.56:1 */
  --a-peach-tile:#FDEDDB; --a-peach-ink:#A05C0D;   /* 4.52:1 */

  /* The same idea applied to the brand yellow, for tiles that carry a blue
     mark rather than one of their own. --a-blue on this is 4.71:1. */
  --a-yellow-tile:#FFF4CC;
  /* And in blue, for the showcase tiles. --a-blue on this is 4.21:1, still
     well past the 3:1 a meaningful icon needs. */
  --a-blue-tile:#DCE8FF;
}

/* The legacy stylesheet paints body blue at 20px. The new design is a white
   page — override here rather than editing style.css, so the old templates
   still work if one is ever loaded. */
body.a26-site{
  background:#fff;
  color:var(--a-body);
  font-family:'Lexend',-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,sans-serif;
  font-size:20.5px;
  line-height:1.62;
  -webkit-font-smoothing:antialiased;
}
body.a26-site #main{padding:0;margin:0}
body.a26-site #page{margin:0;padding:0;max-width:none}

/* Sticky footer. A short page — the handbook's top level, a thin legal page —
   used to leave the body background showing under the footer, which read as
   the page having run out rather than ended.

   Fixed structurally rather than by painting the body the footer's colour:
   that would only have hidden the gap, and it would have been the wrong
   colour above the fold on any page whose nav is white. #a26-main takes the
   slack so the footer is pushed to the bottom of the viewport and no further.
   min-height:100svh, not vh, so mobile browser chrome doesn't add a scroll. */
body.a26-site{display:flex;flex-direction:column;min-height:100vh;min-height:100svh}
body.a26-site > #a26-main{flex:1 0 auto}
body.a26-site > .a26-foot{flex:none}

/* One family for everything. Headings used to be Funnel Display over a Lexend
   body; they are now Lexend as well, which removes the second webfont request
   along with it — and one fewer third party is one fewer entry for the DPIA.

   Lexend is wider and rounder than Funnel Display was, so the leading and
   tracking that suited the old face would crowd this one. Both are opened a
   notch below. */
.a26-site h1,.a26-site h2,.a26-site h3,.a26-site h4{
  font-family:'Lexend',-apple-system,BlinkMacSystemFont,sans-serif;
  font-weight:600;
  line-height:1.16;
  text-wrap:balance;
  margin:0;
  color:var(--a-ink);
  letter-spacing:-.01em;
}
.a26-site a:focus-visible,.a26-site button:focus-visible{outline:3px solid #fff;outline-offset:2px;border-radius:4px}
.aidi26 a:focus-visible,.aidi26 button:focus-visible,.aidi26 summary:focus-visible{
  outline:3px solid var(--a-blue);outline-offset:2px;border-radius:4px}
@media (prefers-reduced-motion:reduce){.a26-site *{transition:none!important;animation:none!important}}

.a26-in{max-width:var(--a-max);margin:0 auto;padding:0 44px}

.a26-skip{position:absolute;left:-9999px;top:0;background:#fff;color:var(--a-blue);
  padding:12px 20px;z-index:200;font-weight:600}
.a26-skip:focus{left:0}

/* ==========================================================================
   CHROME — navigation
   ========================================================================== */
/* Sticky, so Apply and the language switch stay reachable down a long page.
   No shadow and no rule under it: the bar is a different blue from the band
   below and from the white content, so it already has an edge. */
.a26-nav{background:var(--a-nav);position:sticky;top:0;z-index:100}
/* Anchor links land below the bar rather than under it. */
:target{scroll-margin-top:90px}
html{scroll-behavior:smooth}
@media (prefers-reduced-motion:reduce){html{scroll-behavior:auto}}
.a26-nav__in{max-width:var(--a-max);margin:0 auto;padding:18px 44px;
  display:flex;align-items:center;gap:34px}
.a26-nav__logo{flex:none;display:block;line-height:0}
.a26-nav__logo img{height:40px;width:auto;display:block}

.a26-nav__menu{margin-right:auto}
.a26-nav__menu ul{display:flex;gap:30px;list-style:none;margin:0;padding:0}
.a26-nav__menu li{position:relative}
.a26-nav__menu a{color:#fff;text-decoration:none;font-size:18.5px;font-weight:500;
  padding-bottom:3px;border-bottom:2px solid transparent;display:inline-block;white-space:nowrap}
.a26-nav__menu a:hover{border-bottom-color:rgba(255,255,255,.6)}
.a26-nav__menu .current-menu-item>a,
.a26-nav__menu .current_page_item>a,
.a26-nav__menu .current-menu-ancestor>a{border-bottom-color:#fff;color:#fff}

.a26-nav__menu .sub-menu{display:none;position:absolute;left:0;top:100%;margin-top:12px;
  background:#fff;border:1px solid var(--a-line);border-radius:var(--a-r);padding:8px;
  min-width:210px;flex-direction:column;
  box-shadow:0 16px 40px -16px rgba(20,26,43,.4);z-index:90}
.a26-nav__menu li:hover>.sub-menu,.a26-nav__menu li:focus-within>.sub-menu{display:flex}
.a26-nav__menu .sub-menu a{color:var(--a-ink);border:0;padding:10px 14px;border-radius:9px;
  font-size:16.5px;width:100%}
.a26-nav__menu .sub-menu a:hover{background:var(--a-wash);color:var(--a-blue-dark)}

.a26-nav__acts{display:flex;align-items:center;gap:11px;flex:none}
.a26-pill{border:1.5px solid rgba(255,255,255,.65);color:#fff;border-radius:999px;
  padding:8px 18px;font-size:16.5px;font-weight:600;text-decoration:none;white-space:nowrap;
  background:transparent}
.a26-pill:hover{background:rgba(255,255,255,.18);border-color:#fff}
/* The language pill's two-letter label. Swapped in on a narrow bar — see the
   560px block. */
.a26-pill__abbr{display:none}
/* Solid, so Apply is the one thing on the bar that isn't blue. */
.a26-pill--solid{background:#fff;color:var(--a-blue);border-color:#fff}
.a26-pill--solid:hover{background:#fff;opacity:.9;border-color:#fff}

.a26-nav__burger{display:none;appearance:none;background:transparent;border:0;cursor:pointer;
  padding:6px;color:#fff}
.a26-nav__burger svg{width:26px;height:26px;display:block}

/* ==========================================================================
   CHROME — inner page head
   ========================================================================== */
.a26-pagehead{background:var(--a-blue-band);padding:72px 0 80px;position:relative;overflow:hidden}
/* No measure cap. 18ch broke every two-word title onto two lines while most
   of the band sat empty — the cap was protecting against a long title that no
   page here has. balance keeps a genuinely long one from leaving one orphaned
   word on the second line. */
.a26-pagehead h1{color:#fff;font-size:clamp(36px,4.8vw,54px);line-height:1.06;
  text-wrap:balance}
/* 19px semibold, and full white rather than 90%: see --a-blue-band. */
.a26-pagehead__crumb{font-size:19px;font-weight:600;color:#fff;margin-bottom:13px}
.a26-pagehead__crumb a{color:#fff;text-decoration:none}
.a26-pagehead__crumb a:hover{text-decoration:underline}

/* ==========================================================================
   CHROME — footer
   ========================================================================== */
.a26-foot{background:var(--a-blue-chrome);color:#fff;padding:72px 0 36px;
  font-size:16px;line-height:1.6}
.a26-foot__grid{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:46px}
.a26-foot__logo{display:block;line-height:0;margin-bottom:18px}
.a26-foot__logo img{height:46px;width:auto;display:block}
/* Scoped to the grid: as `.a26-foot p` this also claimed the supporter
   credit line and capped it at 30ch, and it outranked .a26-foot__madeby. */
.a26-foot__grid p{margin:0;max-width:30ch}
.a26-foot h4{color:#fff;font-size:14px;letter-spacing:.08em;text-transform:uppercase;
  margin:0 0 12px;font-family:'Lexend',sans-serif;font-weight:700}
/* Likewise: this is the menu-column rule, not a rule for every list in the
   footer. Unscoped it forced the supporter logos into a centred column. */
.a26-foot__grid ul{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:11px}
/* Full white. At 16px, 92% white on --a-blue-chrome is 4.35:1 — under AA.
   The hover underline carries the affordance instead of a dimmed colour. */
.a26-foot a{color:#fff;text-decoration:none}
.a26-foot a:hover{text-decoration:underline}
/* Top band: brand lockup on the left, supporters opposite. */
.a26-foot__top{display:flex;flex-wrap:wrap;justify-content:space-between;
  align-items:flex-start;gap:36px 48px;margin-bottom:54px}
.a26-foot__brand p{margin:0;max-width:32ch}

.a26-foot__madeby b{font-weight:600}
/* The credit links carry no underline at rest — on a line that is already two
   names and a verb, two underlines would read as the main thing in the
   footer. The hover underline comes from .a26-foot a:hover. */
.a26-foot__madeby a{text-underline-offset:3px}

.a26-foot__supporters{margin-left:auto;text-align:right}
.a26-foot__support-label{margin:0 0 16px;font-size:13px;font-weight:700;letter-spacing:.1em;
  text-transform:uppercase;color:#fff;opacity:.85}

/* Optical sizing, not mechanical. Cyngor Gwynedd is a near-square stack
   (icon over wordmark) so matching its height to the wide marks would make it
   tower over them; each logo gets the height that makes it read the same
   weight as its neighbours. */
.a26-foot__logos{list-style:none;margin:0;padding:0;display:flex;flex-wrap:wrap;
  align-items:center;justify-content:flex-end;gap:24px 44px}
.a26-foot__logos li{display:flex;align-items:center}
/* The logos link out to each partner. A lift rather than a fade on hover:
   fading a white chip makes it translucent, so the blue shows through and the
   chip looks broken rather than dimmed. */
.a26-foot__logos a{display:block;line-height:0;border-radius:10px;
  transition:transform .15s ease}
.a26-foot__logos a:hover{transform:translateY(-2px)}
.a26-foot__logos a:focus-visible{outline:2px solid #fff;outline-offset:4px}
@media (prefers-reduced-motion:reduce){.a26-foot__logos a{transition:none}}
.a26-foot__logos img{width:auto;display:block}
/* Every mark sits on its own white chip. Both councils supplied
   light-background versions, so all four are now used exactly as issued —
   nothing recoloured, nothing flattened to a silhouette. */
.a26-foot__logos li{background:#fff;border-radius:12px;padding:13px 16px}
.a26-foot__logos .is-gwynedd{height:44px}
.a26-foot__logos .is-ynysmon{height:48px}
.a26-foot__logos .is-afc{height:44px}
.a26-foot__logos .is-outreach{height:50px}
.a26-foot__base{border-top:1px solid rgba(255,255,255,.3);margin-top:24px;padding-top:26px;
  display:flex;align-items:center;justify-content:space-between;gap:10px 26px;
  flex-wrap:wrap;font-size:15px}
/* Terms and privacy sit first on the base line, before the copyright. The
   margin-right pushes the credit to the far end on its own, so the three read
   as two groups rather than three equal thirds. */
.a26-foot__legal{display:flex;gap:22px;list-style:none;margin:0;padding:0}
.a26-foot__legal a{text-decoration:none}
.a26-foot__legal a:hover{text-decoration:underline}
.a26-foot__base > span:first-of-type{margin-right:auto;opacity:.85}
@media (max-width:560px){
  .a26-foot__base{gap:10px 18px}
  .a26-foot__legal{gap:18px}
}

/* ==========================================================================
   SECTIONS
   ========================================================================== */
.aidi26{background:#fff;color:var(--a-body);font-size:20.5px;line-height:1.62}
.aidi26 h1,.aidi26 h2,.aidi26 h3{color:var(--a-ink)}
.aidi26 h1{font:600 clamp(40px,5.4vw,66px)/1.1 'Lexend',sans-serif;letter-spacing:-.018em}
.aidi26 h2{font-size:clamp(30px,3.4vw,44px)}
.aidi26 h3{font-size:24px;letter-spacing:-.004em}
/* :where() again — as a bare `.aidi26 p` this scores 0,1,1 and beat every
   single-class rule in the file, including .a26-hero__lead (19px) and
   .a26-hero__meta (32px): both margins were declared and then thrown away,
   which is why the hero note sat flush against the buttons. */
:where(.aidi26) p{margin:0}
.aidi26 img{max-width:100%;height:auto}
.aidi26 *,.aidi26 *::before,.aidi26 *::after{box-sizing:border-box}

/* The mark is currently plain text — no fill, no tilt, no colour shift. The
   ==word== syntax and the per-tone classes stay in the content and in
   a26_marks(), so a treatment can be switched back on from these few rules
   without touching a single section or re-seeding anything.

   <mark> carries a UA background and colour of its own, so both are reset
   explicitly rather than just left undeclared. display:inline matters too:
   an inline-block can't break across lines, and a long Welsh phrase would
   overflow the column instead of wrapping. */
.a26-mark{
  background:none;
  color:inherit;
  padding:0;
  margin:0;
  border-radius:0;
  display:inline;
  transform:none;
  box-shadow:none;
}
.a26-mark.is-mint,
.a26-mark.is-coral,
.a26-mark.is-peach,
.a26-mark.is-lilac{background:none}

/* a26_marks() wraps mark + trailing punctuation to stop a comma orphaning off
   an inline-block. With the mark inline that can't happen, and holding the
   phrase together would only cost us a sensible wrap point. */
.a26-mark-wrap{white-space:normal}

.a26-eyebrow{font-size:13px;font-weight:700;letter-spacing:.12em;text-transform:uppercase;
  color:var(--a-blue-dark);margin:0 0 13px}

.a26-sec{padding:96px 0;border-top:1px solid var(--a-line);background:#fff}
.a26-sec.is-first{border-top:0}
.a26-sec.is-wash{background:var(--a-wash);border-top:0}
.a26-sec.is-blue{background:var(--a-blue);border-top:0;color:rgba(255,255,255,.94);
  position:relative;overflow:hidden}
/* The app's concentric rings, drawn rather than shipped as an image. Anchored
   bottom-left so they read as emanating from off-canvas, like the store art. */
.a26-sec.is-blue::before,.a26-pagehead::before{
  content:"";position:absolute;left:-18%;bottom:-120%;width:150%;aspect-ratio:1;
  background:repeating-radial-gradient(circle,transparent 0 86px,rgba(255,255,255,.085) 86px 88px);
  pointer-events:none}
.a26-sec.is-blue>*,.a26-pagehead>*{position:relative;z-index:1}
/* Both offsets above are percentages of the SECTION, and a section that is
   narrow and tall — which is every one of them once the layout stacks — pushes
   the ring field clean out of the bottom of its own box, where overflow:hidden
   then hides it completely. Measured on the live page: at 390px wide the
   square lands about 250px below the section it is supposed to decorate.

   Sizing in vw instead cuts the dependency on the section's height, so the
   same offsets work for a short page-title band and a tall stacked section. */
@media (max-width:1080px){
  .a26-sec.is-blue::before,.a26-pagehead::before{left:-30vw;bottom:-60vw;width:160vw}
}
.a26-sec.is-blue h2,.a26-sec.is-blue h3{color:#fff}
/* No measure cap: at 56ch a two-clause intro wrapped after a few words and
   read as a mistake rather than a line break. The 1280px container and the
   split layouts already keep the line length reasonable. */
.a26-head{margin-bottom:48px}
.a26-head p{margin:15px 0 0;font-size:21.5px;color:var(--a-muted)}
.a26-sec.is-blue .a26-head p{color:rgba(255,255,255,.93)}

/* buttons (AidiButtonStyles, ported) */
.aidi26 .a26-btn{display:inline-flex;align-items:center;justify-content:center;
  border-radius:var(--a-r);border:0;font:inherit;font-size:17.5px;font-weight:600;
  text-decoration:none;padding:16px 34px;cursor:pointer;transition:opacity .15s;
  gap:11px}
.aidi26 .a26-btn:hover{opacity:.88}

/* Platform mark on a store button. Inline SVG in currentColor, with the width
   and height coming from a26_store_icon() because the two marks have very
   different aspect ratios — forcing both into one square box would squash the
   Android head or stretch the Apple. Nudged up a hair: both marks are optically
   centred slightly low against a cap-height label. */
/* One box for both glyphs, because the button is a flex row and takes its
   height from the tallest child. The Apple mark is taller than it is wide
   (0.84) and the Android robot is the opposite (1.77), so at their natural
   sizes — 19px and 12px tall — the iOS button stood 7px taller than the
   Android one sitting beneath it.

   Both SVGs carry a viewBox, so a fixed box scales each to fit and centres it
   without distortion: the Apple mark fills the height, the robot fills the
   width, and the two buttons match. */
.aidi26 .a26-btn__store{flex:none;display:block;width:22px;height:18px;margin-top:-1px}

/* Store buttons are secondary to Apply, so they are sized that way: smaller
   type, tighter padding, and the glyph doing some of the labelling. Three
   buttons at equal weight read as three equal choices, which these are not —
   and at full size the Welsh pair ("Lawrlwytho ar Android") will not share a
   line with the primary action at any sensible column width.

   :has() rather than a modifier class, so this follows the store icon itself
   and needs no change to the markup or the seeded content. */
.aidi26 .a26-btn:has(.a26-btn__store){
  font-size:16px;padding:12px 20px;gap:9px}
@media (max-width:520px){
  .aidi26 .a26-btn:has(.a26-btn__store){font-size:15.5px;padding:11px 16px}
}

/* Button rows on a phone: the primary action takes the full width, and the
   secondary ones share the row beneath it.

   flex-grow on the secondaries rather than a flat 50%, so the rule holds
   however many there are: two share the row, and a single one — "Open the
   handbook", say — grows to fill it instead of sitting stranded at half
   width. The basis subtracts half the 16px gap, which is what a plain 50%
   would miss, pushing the pair onto separate lines. */
@media (max-width:620px){
  .aidi26 .a26-btns{align-items:stretch}
  .aidi26 .a26-btns .a26-btn--primary{flex:1 0 100%}
  .aidi26 .a26-btns .a26-btn--outline,
  .aidi26 .a26-btns .a26-btn--secondary,
  .aidi26 .a26-btns .a26-btn--white{flex:1 1 calc(50% - 8px)}
}
.aidi26 .a26-btn--primary{background:var(--a-blue);color:#fff}
.aidi26 .a26-btn--secondary{background:var(--a-wash);color:var(--a-blue-dark)}
.aidi26 .a26-btn--outline{background:#fff;color:var(--a-blue-dark);box-shadow:inset 0 0 0 1.5px var(--a-line)}
/* Ink, not blue. These sit on the blue band, where blue-on-white inside a
   white pill on blue was three blues deep and the label stopped reading as a
   label. The store glyphs are drawn in currentColor, so they follow. */
.aidi26 .a26-btn--white{background:#fff;color:var(--a-ink)}
.a26-btns{display:flex;gap:16px;flex-wrap:wrap}

/* Buttons that follow a feature grid. The margin lives here rather than in an
   inline style on the section so it can be overridden; under the showcase they
   are the section's closing move, so they get air and sit centred under the
   three columns rather than hanging off the first one. */
.a26-feats ~ .a26-btns{margin-top:28px}
.a26-feats.is-showcase ~ .a26-btns{margin-top:58px;justify-content:center}

/* hero */
/* overflow:hidden contains the phone backdrop. It's deliberately wider than
   the column so the shapes bleed past the phones, and without this the
   document's scrollWidth grows by ~90px — not scrollable today, because an
   ancestor happens to clip it, but a latent scrollbar the moment that changes. */
.a26-hero{padding:90px 0 98px;background:#fff;overflow:hidden}
.a26-hero__grid{display:grid;grid-template-columns:1.1fr .9fr;gap:70px;align-items:center}
.a26-hero__lead{margin:19px 0 0;font-size:clamp(20px,2vw,24px);color:var(--a-body);max-width:50ch}
.a26-hero .a26-btns{margin-top:34px}
.a26-hero__meta{margin-top:32px;font-size:16px;color:var(--a-muted)}

/* identity card artwork */
.a26-card{width:100%;max-width:385px;margin:0 auto;background:#fff;border-radius:18px;
  box-shadow:0 18px 44px -18px rgba(20,26,43,.38);overflow:hidden}
.a26-card__top{background:var(--a-blue);padding:14px 17px;display:flex;align-items:center;
  justify-content:space-between;gap:10px}
.a26-card__top img{height:21px;width:auto;display:block}
.a26-card__top span{font-size:12px;letter-spacing:.07em;text-transform:uppercase;
  font-weight:700;color:rgba(255,255,255,.88)}
.a26-card__accent{height:4px;background:var(--a-teal)}
.a26-card__accent.is-pink{background:var(--a-pink)}
.a26-card__accent.is-blue{background:var(--a-blue)}
.a26-card__body{padding:22px;display:flex;gap:18px}
.a26-card__photo{width:92px;height:112px;border-radius:10px;flex:none;
  background:linear-gradient(155deg,#D9E6FE,#A8C4F7);
  display:flex;align-items:flex-end;justify-content:center;overflow:hidden}
.a26-card__photo svg{width:60px;height:72px;display:block}
.a26-card__fields{flex:1;min-width:0;display:flex;flex-direction:column;gap:8px}
.a26-card__name{font-family:'Lexend',sans-serif;font-weight:600;
  font-size:22.5px;color:var(--a-ink);line-height:1.15}
.a26-card__f{display:flex;flex-direction:column}
.a26-card__f b{font-size:11px;letter-spacing:.1em;text-transform:uppercase;color:var(--a-muted);font-weight:700}
.a26-card__f span{font-size:16px;color:var(--a-body);font-variant-numeric:tabular-nums}
.a26-card__foot{border-top:1px solid var(--a-line);padding:13px 22px;display:flex;
  align-items:center;justify-content:space-between;gap:10px}
.a26-card__foot small{font-size:12.5px;color:var(--a-muted)}
.a26-card__qr{width:46px;height:46px;flex:none}

/* Two app screens, one behind the other.
   These images ship with their own device frame and transparent corners, so
   they get no .a26-phone bezel — only a drop shadow that follows the frame. */
.a26-duo{position:relative;width:100%;max-width:440px;margin:0 auto;
  aspect-ratio:440/560;display:block}
/* These mockups already render their own metal frame, so they read as
   dimensional without help. The shadow only has to lift them off the white —
   the previous one was heavy enough that two overlapping shadows pooled into
   a grey cloud with a visible straight edge where the rotated frames ended. */
/* The shapes behind the phones. This is the app's own backdrop asset, copied
   from Aidi/Assets.xcassets/promo_bg.imageset — the circle, rounded triangle
   and tilted square that sit behind the "apply for a card" band. Same file, so
   the web and the app can't drift apart; a redraw would have been three
   approximations of it.

   Oversized and bled past the phones on purpose: what shows is the middle of
   it, so the shapes read as something the phones are standing on rather than a
   picture placed behind them. Inert — aria-hidden isn't needed on a CSS
   background, and it carries no meaning to announce. */
.a26-duo::before{content:"";position:absolute;inset:-40% -34% -22%;
  background:url("../../img/hero-shapes.svg") center/contain no-repeat;
  z-index:0;pointer-events:none;
  animation:a26-drift 18s ease-in-out infinite}
@keyframes a26-drift{
  0%,100%{transform:translate3d(0,0,0) scale(1)}
  50%    {transform:translate3d(0,-10px,0) scale(1.015)}
}
@media (prefers-reduced-motion:reduce){.a26-duo::before{animation:none}}

.a26-duo img{position:absolute;display:block;width:60%;height:auto;z-index:1;
  filter:drop-shadow(0 10px 18px rgba(10,20,60,.14))}
.a26-duo__back{left:0;top:0;transform:rotate(-4deg)}
.a26-duo__front{right:0;top:9%;transform:rotate(3deg)}

/* Icon chips drifting around the phones. Decorative: the whole layer is
   aria-hidden and pointer-events:none, so it can sit over the images without
   stealing a tap meant for them.

   Each chip runs the same keyframes at a different duration with a negative
   delay, which starts it mid-cycle — four identical bobs in lockstep read as
   one object moving, not four. The durations are deliberately not multiples
   of each other, so the set never resynchronises. */
.a26-float{position:absolute;inset:0;z-index:2;pointer-events:none}
.a26-float__i{position:absolute;width:84px;height:84px;border-radius:26px;
  display:grid;place-items:center;
  box-shadow:0 16px 34px -18px rgba(10,20,60,.5);
  animation:a26-bob 7s ease-in-out infinite}
.a26-float__i svg{width:38px;height:38px}

/* Same four tile/ink pairs as the handbook tiles — a light fill with a darker
   cut of its own hue for the icon. Each ink clears 4.5:1 on its own tile, so
   these stay legible rather than relying on the white page behind them, which
   is what a white chip with a coloured icon was doing. Order runs lilac,
   coral, peach, mint around the phones so no two neighbours share a hue. */
.a26-float .is-1{left:-14%;top:20%;
  background:var(--a-lilac-tile);color:var(--a-lilac-ink);animation-duration:7.5s}
.a26-float .is-2{right:-10%;top:0;
  background:var(--a-coral-tile);color:var(--a-coral-ink);
  animation-duration:6.2s;animation-delay:-1.4s}
.a26-float .is-3{left:1%;bottom:-6%;
  background:var(--a-peach-tile);color:var(--a-peach-ink);
  animation-duration:8.4s;animation-delay:-3s}
.a26-float .is-4{right:-8%;bottom:16%;
  background:var(--a-mint-tile);color:var(--a-mint-ink);
  animation-duration:6.8s;animation-delay:-2.2s}
@keyframes a26-bob{
  0%,100%{transform:translate3d(0,0,0) rotate(-3deg)}
  50%    {transform:translate3d(0,-12px,0) rotate(3deg)}
}
@media (prefers-reduced-motion:reduce){.a26-float__i{animation:none}}
@media (max-width:860px){
  .a26-float__i{width:66px;height:66px;border-radius:21px}
  .a26-float__i svg{width:30px;height:30px}
}
/* Below this the duo is about 300px wide, so the chips sit ON the phones
   rather than around them. That is the point at which they stop being a
   border and start being part of the picture, which is fine — what is not
   fine is a chip in the page gutter, so the offsets come in to single
   figures and the chips come down to 52px. */
@media (max-width:700px){
  .a26-float__i{width:52px;height:52px;border-radius:17px}
  .a26-float__i svg{width:24px;height:24px}
  .a26-float .is-1{left:-5%;top:18%}
  .a26-float .is-2{right:-4%;top:2%}
  .a26-float .is-3{left:3%;bottom:-2%}
  .a26-float .is-4{right:-3%;bottom:15%}
}

@media (max-width:860px){
  /* Not enough width to sit the logos beside the credit line — stack them and
     return everything to the left edge the rest of the footer uses. */
  .a26-foot__supporters{margin-left:0;text-align:left;width:100%}
  .a26-foot__logos{justify-content:flex-start}
  .a26-foot__logos li{padding:11px 13px}
  .a26-foot__logos .is-gwynedd{height:38px}
  .a26-foot__logos .is-ynysmon{height:42px}
  .a26-foot__logos .is-afc{height:38px}
  .a26-foot__logos .is-outreach{height:44px}
}

@media (max-width:1080px){
  .a26-duo{max-width:380px}
  /* Stacked, the top bleed is no longer in empty space beside the copy — it
     rises into the paragraph above and the shapes paint over the words,
     because a positioned element draws above in-flow text it overlaps. It
     can't simply be pushed behind with a negative z-index either: .a26-hero
     has a white background and no stacking context of its own, so that would
     hide the shapes under it entirely. So the bleed is trimmed at the top
     instead, to less than the grid gap even at the far end of the drift. */
  .a26-duo::before{inset:-2% -30% -26%}
}
@media (max-width:460px){
  .a26-duo img{width:62%}
}

/* app screenshot in a phone bezel */
.a26-phone{width:100%;max-width:400px;margin:0 auto;border-radius:40px;overflow:hidden;
  background:#0E1430;padding:9px;box-shadow:0 26px 60px -22px rgba(10,20,60,.55)}
.a26-phone img{display:block;width:100%;height:auto;border-radius:32px}

/* Beside a column of text, 400px makes the screenshot the loudest thing in the
   section — it out-weighs the heading it is meant to illustrate. Smaller here,
   with the bezel scaled to match so it still reads as a phone rather than a
   thin frame around a big picture. The hero's own single-image fallback keeps
   the full 400px, since there it IS the subject. */
.a26-split .a26-phone{max-width:300px;border-radius:34px;padding:7px}
.a26-split .a26-phone img{border-radius:27px}

/* --------------------------------------------------------------------------
   Photo beside a tick list. Square, rounded, with the app's own backdrop
   shapes bleeding out from behind it — the same promo_bg asset the hero uses,
   so the two pages share one visual language rather than inventing a second.

   The wrapper must NOT clip: the shapes are meant to escape it. The radius
   therefore lives on the <img>, and the section clips instead so the bleed
   can't inflate the document's scrollWidth.
   -------------------------------------------------------------------------- */
/* --------------------------------------------------------------------------
   A device cropped by the bottom of the band, so it reads as half-sunk into
   whatever follows rather than as a picture that happens to be cut off.

   The crop is a fixed-height window with overflow:hidden rather than a
   negative margin: a negative margin would pull the phone over the next
   section and sit it on top of the footer's own content.
   -------------------------------------------------------------------------- */
.a26-sec.has-device{padding:74px 0 0;overflow:hidden}
/* The device hangs from the bottom; the copy stays optically centred against
   the band rather than being dragged down with it. */
.a26-sec.has-device .a26-split{align-items:end}
.a26-sec.has-device .a26-split > div:first-child{align-self:center;padding-bottom:74px}

.a26-device{position:relative;width:min(272px,100%);margin:0 auto;
  height:clamp(240px,24vw,350px);overflow:hidden;
  /* Faded rather than guillotined. A hard crop at the band's edge reads as a
     mistake — the eye looks for the rest of the phone and finds a colour
     change. Dissolving the last third makes the cut the point. */
  -webkit-mask-image:linear-gradient(to bottom,#000 58%,rgba(0,0,0,.55) 82%,transparent 100%);
  mask-image:linear-gradient(to bottom,#000 58%,rgba(0,0,0,.55) 82%,transparent 100%)}
.a26-device img{display:block;width:100%;height:auto}

/* Two screens, one behind the other, both cut off by the band.

   The pair is absolutely positioned inside the same masked window, so the
   fade still applies to both as one picture rather than to each phone
   separately — two independent fades would cross and show their own edges.
   The angles are the hero duo's, mirrored, so the two compositions on a page
   don't lean the same way. */
/* The offsets are what stop the pair being sliced down both sides. Rotating
   a tall phone widens its bounding box by roughly its height times the sine
   of the angle — around 15px each side here — so a phone pinned to left:0 has
   a corner outside the box, and the overflow:hidden that crops the bottom
   into the band crops that corner too. The same applies at the top, which is
   why neither phone starts at top:0.

   Padding on the wrapper does NOT solve this: an absolutely positioned child
   is laid out against its container's PADDING box, so padding moves nothing
   and only shrinks what the percentage widths resolve against. The phones
   have to be inset themselves. The inset is a percentage of the same box the
   widths use, so the clearance scales with the composition. */
.a26-device.has-two{width:min(390px,100%)}
.a26-device.has-two img{position:absolute;width:58%}
.a26-device.has-two .a26-device__back{left:6%;top:4%;transform:rotate(-4.5deg)}
.a26-device.has-two .a26-device__front{right:6%;top:11%;transform:rotate(3.5deg)}
@media (max-width:1080px){
  .a26-device.has-two{width:min(300px,100%)}
}
/* Stacked, the device would be a letterbox under the copy — less width, and
   enough height that the screen is still readable. */
@media (max-width:1080px){
  .a26-sec.has-device .a26-split > div:first-child{padding-bottom:0}
  .a26-device{height:240px;width:min(230px,100%)}
}

.a26-photo{position:relative;width:100%;max-width:440px;margin:0 auto;aspect-ratio:1/1}
.a26-photo::before{content:"";position:absolute;inset:-20% -18%;
  background:url("../../img/hero-shapes.svg") center/contain no-repeat;
  z-index:0;pointer-events:none}
.a26-photo img{position:relative;z-index:1;width:100%;height:100%;object-fit:cover;
  display:block;border-radius:28px;
  box-shadow:0 18px 44px -26px rgba(10,20,60,.5)}
/* On the blue band the pale shapes vanish, so the photo takes the app's
   own blue-ground variant of the same three shapes — promo_login_bg,
   the file it uses behind the login promo for exactly this reason. */
.a26-sec.is-blue .a26-photo::before{
  background-image:url("../../img/hero-shapes-blue.svg")}
.a26-sec.is-blue .a26-photo img{box-shadow:0 20px 50px -26px rgba(5,12,40,.6)}
.a26-sec:has(.a26-photo){overflow:hidden}

@media (max-width:1080px){
  .a26-photo{max-width:380px}
}

/* routes */
.a26-routes{display:grid;grid-template-columns:1fr 1fr;gap:22px}
.a26-route{position:relative;background:#fff;border:1px solid var(--a-line);border-radius:22px;
  padding:34px 36px 36px;display:flex;flex-direction:column;gap:11px;overflow:hidden;
  box-shadow:0 14px 34px -24px rgba(20,26,43,.35)}
/* The coloured top edge is gone. The partner logo in the card's foot already
   says who handles the route, so the strip was saying it a second time in a
   colour that fought the age badge. The ACF accent field is still read in
   routes.php and still sets --a-route-accent, so bringing it back is one rule. */
.a26-sec.is-wash .a26-route{border-color:transparent}

/* Who checks this application — the partner strip along the card's foot. */
/* No tint behind the strip: both partner logos are supplied on white, and a
   tinted band turns them into stickers. A hairline is enough separation. */
/* Pulled flush to the card's edges, eating the card's own bottom padding. */
/* position:relative so the info panel can span the whole foot rather than
   hang off the button — anchored to the button it would run past the card's
   right edge on a narrow column, and clamping it there is a losing game. */
.a26-route__partner{margin:30px -36px -36px;padding:20px 36px 22px;border-top:1px solid var(--a-line);
  display:flex;align-items:center;gap:18px;justify-content:space-between;position:relative}
.a26-route__partner-who{display:flex;flex-direction:column;gap:5px;min-width:0}
.a26-route__partner-label{font-size:13px;font-weight:600;letter-spacing:.04em;
  text-transform:uppercase;color:var(--a-muted);line-height:1.35}
.a26-route__partner-name{font-size:17.5px;font-weight:600;color:var(--a-ink);
  line-height:1.3;display:flex;align-items:center;gap:9px;flex-wrap:wrap}
.a26-route__partner img{height:52px;width:auto;flex:none;display:block}

/* The info disclosure. <details> rather than a hover tooltip: hover doesn't
   exist on a phone, and WCAG 1.4.13 wants a hover tooltip to be dismissible
   and hoverable, which is a lot of machinery for two sentences. This opens on
   click or Enter, and works with the JavaScript switched off. */
.a26-info{display:inline-flex}
.a26-info > summary{
  list-style:none;cursor:pointer;width:23px;height:23px;border-radius:999px;
  background:var(--a-wash);color:var(--a-blue-dark);
  display:grid;place-items:center;font:700 13.5px/1 'Lexend',sans-serif;
  transition:background .15s ease}
.a26-info > summary::-webkit-details-marker{display:none}
.a26-info > summary::marker{content:""}
.a26-info > summary:hover{background:#E2EBFF}
.a26-info > summary:focus-visible{outline:2px solid var(--a-blue);outline-offset:2px}
.a26-info[open] > summary{background:var(--a-blue);color:#fff}

/* Brand blue rather than ink. White on #0F62F2 is 5.19:1, so the panel still
   clears AA at this size, and it reads as part of the site rather than as the
   operating system's own tooltip, which is what the near-black looked like. */
.a26-info__panel{
  position:absolute;left:18px;right:18px;bottom:calc(100% - 12px);z-index:6;
  background:var(--a-blue);color:#fff;border-radius:14px;padding:15px 17px;
  font-size:15.5px;line-height:1.5;font-weight:400;letter-spacing:0;
  text-transform:none;
  box-shadow:0 20px 44px -22px rgba(8,40,120,.7)}

@media (prefers-reduced-motion:reduce){.a26-info > summary{transition:none}}
/* One colour for both cards now: the badge states the age band, which isn't a
   per-partner property. #0F62F2 on the card's white is 5.19:1. */
.a26-route__badge{align-self:flex-start;font-size:16px;font-weight:700;letter-spacing:.06em;
  text-transform:uppercase;color:var(--a-blue)}
.a26-route h3{font-size:28px}
.a26-route p{color:var(--a-muted);font-size:19px;flex:1}
.aidi26 .a26-route__go{font-weight:600;color:var(--a-blue-dark);font-size:15px;
  text-decoration:none;align-self:flex-start;font-size:18px}
.aidi26 .a26-route__go:hover{text-decoration:underline}

/* The note under both route cards. White like the cards so it reads as part
   of the same group, and laid out to take a photo of the physical card beside
   the copy whenever one is dropped in. */
/* The plastic-card note. Blue rather than white: it sits under two white
   route cards on a wash band, and as a third white box it read as a footnote
   to the second card rather than as something true of both. #FFF on #0F62F2
   is 5.19:1. */
.a26-routes__note{margin-top:22px;background:var(--a-blue);border:0;
  border-radius:var(--a-r);padding:22px 26px;display:flex;align-items:center;
  gap:24px;box-shadow:0 16px 34px -22px rgba(15,98,242,.95)}
.a26-routes__note p{margin:0;font-size:17.5px;color:#fff}
.a26-routes__note-i{width:54px;height:54px;border-radius:15px;flex:none;
  background:rgba(255,255,255,.17);color:#fff;display:grid;place-items:center}
.a26-routes__note-i svg{width:29px;height:29px;display:block}
.a26-routes__note img{height:150px;width:auto;flex:none;display:block;
  border-radius:10px}
@media (max-width:700px){
  .a26-routes__note{flex-direction:column;align-items:flex-start;gap:16px}
  .a26-routes__note img{height:120px}
}

/* --------------------------------------------------------------------------
   Llwyfan content (/llawlyfr/), rendered by the llwyfan-cms-bridge plugin.

   Styled from here rather than by editing the plugin's own stylesheet: that
   plugin is shared with the other Llwyfan sites and a plugin update would wipe
   a local edit. .aidi26 as the scope puts these at 0,3,0 against the plugin's
   0,2,0, so load order doesn't matter either.
   -------------------------------------------------------------------------- */
/* The filter button. The plugin ships a quiet grey pill; on this site it is
   the one control on the page, so it gets the brand's colour and says what it
   does rather than naming the mechanism. Sits square — the tilt belongs to the
   highlight mark, and on a control it read as a rendering fault. */
.aidi26 .llwyfan-cms .llwyfan-filter-button{
  background:var(--a-blue);color:#fff;border:0;border-radius:999px;
  padding:13px 22px 13px 48px;font:600 16.5px/1 'Lexend',sans-serif;cursor:pointer;
  display:inline-flex;align-items:center;gap:10px;
  background-image:url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%23ffffff' stroke-width='2.2' stroke-linecap='round'><path d='M4 7h10M18 7h2M4 17h4M12 17h8'/><circle cx='16' cy='7' r='2.3'/><circle cx='10' cy='17' r='2.3'/></svg>");
  background-repeat:no-repeat;background-position:20px 50%;background-size:19px 19px;
  box-shadow:0 10px 22px -14px rgba(15,98,242,.9);
  transition:transform .15s ease,box-shadow .15s ease,background-color .15s ease}
.aidi26 .llwyfan-cms .llwyfan-filter-button:hover{
  background-color:var(--a-blue-dark);transform:translateY(-2px);
  box-shadow:0 14px 26px -14px rgba(15,98,242,.95)}
.aidi26 .llwyfan-cms .llwyfan-filter-button:focus-visible{
  outline:3px solid var(--a-blue-dark);outline-offset:3px}

/* The count sits in the brand yellow so it reads as a tally, not a warning.
   #1B2A66 on #FFE066 is 10.26:1. */
.aidi26 .llwyfan-cms .llwyfan-filter-count{
  background:var(--a-yellow);color:var(--a-mark-ink);border:0;
  font-weight:700;font-size:13px;min-width:22px;height:22px;border-radius:999px}

/* --- The filter dialog ----------------------------------------------------
   The plugin ships bare browser checkboxes in a flat list. Here each option
   becomes a tappable row with its own hit area, because the people using this
   are often on a phone one-handed — a 14px checkbox is not a target, the whole
   row is. :has(:checked) does the selected state in CSS, so no JS is added to
   a plugin that is shared with the other Llwyfan sites. */
.aidi26 .llwyfan-cms dialog.llwyfan-dialog{
  width:min(520px,94vw);padding:26px;border-radius:22px;
  font-family:'Lexend',sans-serif;color:var(--a-ink);
  box-shadow:0 40px 90px -40px rgba(10,20,60,.6)}
.aidi26 .llwyfan-cms dialog.llwyfan-dialog::backdrop{
  background:rgba(14,24,56,.52)}
.aidi26 .llwyfan-cms .llwyfan-dialog-header h2{
  font-size:26px;font-weight:700;margin:0;letter-spacing:-.01em}
.aidi26 .llwyfan-cms .llwyfan-dialog-header p{
  color:var(--a-muted);opacity:1;font-size:15.5px;margin-top:6px}
.aidi26 .llwyfan-cms .llwyfan-dialog-close{
  width:34px;height:34px;border-radius:999px;background:var(--a-wash);
  color:var(--a-blue-dark);font-size:20px;flex:none;
  transition:background .15s ease}
.aidi26 .llwyfan-cms .llwyfan-dialog-close:hover{background:#E2EBFF}

.aidi26 .llwyfan-cms .llwyfan-tag-group{margin:0 0 22px}
.aidi26 .llwyfan-cms .llwyfan-tag-group legend{
  font-size:12.5px;font-weight:700;letter-spacing:.09em;text-transform:uppercase;
  color:var(--a-blue);padding:0 0 10px}

/* The row. 1.5px inset ring rather than a border so selecting an option
   doesn't shift the text by half a pixel. */
.aidi26 .llwyfan-cms .llwyfan-tag-option{
  gap:14px;padding:13px 16px;margin-bottom:8px;border-radius:14px;
  font-size:16.5px;font-weight:500;line-height:1.3;
  box-shadow:inset 0 0 0 1.5px var(--a-line);background:#fff;
  transition:box-shadow .15s ease,background .15s ease}
.aidi26 .llwyfan-cms .llwyfan-tag-option:hover{
  background:var(--a-wash);box-shadow:inset 0 0 0 1.5px #C9D8FF}
.aidi26 .llwyfan-cms .llwyfan-tag-option:has(input:checked){
  background:var(--a-wash);color:var(--a-blue-dark);font-weight:600;
  box-shadow:inset 0 0 0 2px var(--a-blue)}
.aidi26 .llwyfan-cms .llwyfan-tag-option:has(input:focus-visible){
  outline:3px solid var(--a-blue);outline-offset:2px}

/* The box itself: appearance:none, then the tick is a background image so it
   can't be knocked out of alignment by the row's line-height. */
.aidi26 .llwyfan-cms .llwyfan-tag-option input[type="checkbox"]{
  appearance:none;-webkit-appearance:none;margin:0;flex:none;
  width:24px;height:24px;border-radius:8px;cursor:pointer;
  box-shadow:inset 0 0 0 2px var(--a-line);background:#fff;
  transition:background .15s ease,box-shadow .15s ease}
.aidi26 .llwyfan-cms .llwyfan-tag-option input[type="checkbox"]:checked{
  background:var(--a-blue) url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%23ffffff' stroke-width='3.2' stroke-linecap='round' stroke-linejoin='round'><path d='M5 12.5l4.5 4.5L19 7.5'/></svg>") center/15px 15px no-repeat;
  box-shadow:inset 0 0 0 2px var(--a-blue)}
.aidi26 .llwyfan-cms .llwyfan-tag-option input[type="checkbox"]:focus-visible{outline:none}

.aidi26 .llwyfan-cms .llwyfan-dialog-actions{
  border-top:1px solid var(--a-line);margin-top:20px;padding-top:18px}
.aidi26 .llwyfan-cms .llwyfan-filter-apply{
  background:var(--a-blue);color:#fff;font:600 16.5px/1 'Lexend',sans-serif;
  padding:14px 26px;border-radius:999px;
  transition:background .15s ease,transform .15s ease}
.aidi26 .llwyfan-cms .llwyfan-filter-apply:hover{
  background:var(--a-blue-dark);transform:translateY(-1px)}
.aidi26 .llwyfan-cms .llwyfan-filter-apply:focus-visible{
  outline:3px solid var(--a-blue-dark);outline-offset:3px}
.aidi26 .llwyfan-cms .llwyfan-filter-clear{
  opacity:1;color:var(--a-muted);font-weight:600;font-size:15.5px;
  text-decoration:none;border-bottom:1.5px solid var(--a-line)}
.aidi26 .llwyfan-cms .llwyfan-filter-clear:hover{
  color:var(--a-blue-dark);border-bottom-color:var(--a-blue)}

@media (prefers-reduced-motion:reduce){
  .aidi26 .llwyfan-cms .llwyfan-tag-option,
  .aidi26 .llwyfan-cms .llwyfan-tag-option input[type="checkbox"],
  .aidi26 .llwyfan-cms .llwyfan-filter-apply,
  .aidi26 .llwyfan-cms .llwyfan-dialog-close{transition:none}
}

/* Back on the left, filter on the right, on one line.

   The plugin renders the filter bar and then the back link as siblings, so
   they are floated rather than wrapped — there is nowhere to put a flex
   parent without editing markup that four other sites share. The two clear
   rules do the work a wrapper would: whatever follows the pair starts a new
   block, and the back link itself is the one element allowed to sit beside
   the float. Top-level pages have no back link, which is why the first rule
   has to exist at all. */
.aidi26 .llwyfan-cms .llwyfan-filter-bar{float:right;margin:0 0 20px 18px}
/* Everything in the block clears the float except the float itself and the
   back link, which is the one thing meant to sit beside it.

   A blanket rule with two exceptions, not `+ *`: the filter markup is a div
   AND a <dialog>, so the filter bar's next sibling is the hidden dialog, not
   the content. On a page with no back link that left the card grid wrapping
   around the button in a short column. */
.aidi26 .llwyfan-cms > *{clear:both}
.aidi26 .llwyfan-cms > .llwyfan-filter-bar,
.aidi26 .llwyfan-cms > .llwyfan-top-heading,
.aidi26 .llwyfan-cms > .llwyfan-back{clear:none}

/* Sits opposite the filter button on the top-level view, where the back link
   sits everywhere else — so the row reads as a pair rather than a button
   adrift above the grid. Matched to the back chip's height so the two line up
   across the row whichever one is showing. */
.aidi26 .llwyfan-cms .llwyfan-top-heading{
  margin:0 0 20px;font-size:25px;line-height:46px;letter-spacing:-.01em}
/* Side by side needs room the Welsh doesn't always leave: "Dangos beth sydd
   i mi" next to "Yn ôl i'r cyfan" is most of a phone's width. Below this they
   stack, filter first, which is where they were before anyway. */
@media (max-width:620px){
  .aidi26 .llwyfan-cms .llwyfan-filter-bar{float:none;margin:0 0 14px}
}

/* Back links: a chip rather than a bare underlined link, with the arrow
   sliding on hover so the direction is felt as well as read.

   Both controls are pinned to the same 46px so their centres line up across
   the row — floats align on their top edges, and the filter pill is the
   taller of the two by about 6px. */
.aidi26 .llwyfan-cms .llwyfan-back{margin:0 0 20px}
.aidi26 .llwyfan-cms .llwyfan-back a{
  display:inline-flex;align-items:center;min-height:46px;
  background:var(--a-wash);color:var(--a-blue-dark);
  text-decoration:none;font-weight:600;font-size:15.5px;
  padding:0 20px;border-radius:999px;
  transition:background .15s ease,transform .15s ease}
.aidi26 .llwyfan-cms .llwyfan-back a:hover{
  background:#E2EBFF;transform:translateX(-3px)}
.aidi26 .llwyfan-cms .llwyfan-back a:focus-visible{
  outline:2px solid var(--a-blue);outline-offset:3px}

@media (prefers-reduced-motion:reduce){
  .aidi26 .llwyfan-cms .llwyfan-filter-button,
  .aidi26 .llwyfan-cms .llwyfan-back a{transition:none}
}

/* The theme zeroes every heading margin (.a26-site h1-h4), which is right for
   sections built from ACF where the gap is the layout's job — but the Llwyfan
   article is plain flowing prose, so its title was sitting on top of the first
   paragraph. Put the space back for this one context only. */
.aidi26 .llwyfan-cms .llwyfan-article > h1{margin:0 0 22px}
.aidi26 .llwyfan-cms .llwyfan-heading h2{margin:0 0 10px}

/* --------------------------------------------------------------------------
   Article prose.

   The plugin sets no type scale of its own, so the body inherited the site's
   20.5px under a 66px h1 across the full container width — technically the
   same size as every other paragraph on the site, and small-looking next to
   that heading and over that measure. Three things fix it: a slightly larger
   body size, a heading scale that doesn't tower over it, and a measure.

   The copy arrives pasted from Word (<p class="MsoNormal"><span lang="…">),
   which carries no sizing of its own but does sometimes arrive with collapsed
   margins, so the spacing is set here rather than assumed.

   Only the text blocks are measured. Images, embeds and maps keep the full
   width — a photo narrowed to the text column would look like a mistake.
   -------------------------------------------------------------------------- */
/* Long unbroken strings. Measured on a 375px phone: the autolinked addresses
   — gwyneddyoungcarers@actionforchildren.org.uk is the worst at 449px — are a
   single unbreakable word, so they pushed the document 124px wider than the
   screen and every page scrolled sideways.

   anywhere rather than break-word on the links: break-word only breaks a word
   that is alone on its line, and these sit mid-sentence. Applied to the legal
   documents and the handbook, which are the two places a raw address or url
   appears in running text. */
.a26-legal__doc,
.a26-legal__intro,
.aidi26 .llwyfan-cms .llwyfan-article{overflow-wrap:break-word}
.a26-legal__doc a,
.a26-legal__doc td,
.a26-legal__intro a,
.aidi26 .llwyfan-cms .llwyfan-article a{overflow-wrap:anywhere}

.aidi26 .llwyfan-cms .llwyfan-article{font-size:21px;line-height:1.66}
.aidi26 .llwyfan-cms .llwyfan-article p,
.aidi26 .llwyfan-cms .llwyfan-article li{
  font-size:21px;line-height:1.66;margin:0 0 18px}
.aidi26 .llwyfan-cms .llwyfan-article li{margin-bottom:9px}
.aidi26 .llwyfan-cms .llwyfan-article ul,
.aidi26 .llwyfan-cms .llwyfan-article ol{margin:0 0 20px;padding-left:24px}
.aidi26 .llwyfan-cms .llwyfan-article p:last-child{margin-bottom:0}

.aidi26 .llwyfan-cms .llwyfan-article > h1{
  font-size:clamp(34px,3.6vw,48px);line-height:1.1}
.aidi26 .llwyfan-cms .llwyfan-article h2{
  font-size:30px;line-height:1.2;margin:36px 0 12px}
.aidi26 .llwyfan-cms .llwyfan-article h3{
  font-size:24px;line-height:1.25;margin:28px 0 10px}
.aidi26 .llwyfan-cms .llwyfan-article h2:first-child,
.aidi26 .llwyfan-cms .llwyfan-article h3:first-child{margin-top:0}

/* Word's inline styles, neutralised.

   Some of this copy is pasted from Word, which brings its own type with it:

     <p class="MsoNormal" style="line-height:15.0pt">
       <span style="font-size:10.5pt;font-family:'Segoe UI',sans-serif">

   10.5pt is 14px, which is why those paragraphs were small — and being an
   inline style, nothing in a stylesheet could reach it without !important.
   That is what the !important here is for; it is not covering up a
   specificity mistake.

   The properties are reset to inherit rather than to fixed values, so the
   prose rules above stay the single place the article's type is defined.
   Bold, italic, links and headings are untouched, so an editor's actual
   formatting survives — only the pasted typeface, size and leading go.

   The real fix is upstream: strip inline styles on paste in the Llwyfan
   editor. Until that happens, this keeps the page consistent whatever state
   the copy arrives in. */
.aidi26 .llwyfan-cms .llwyfan-article [style*="font-size"],
.aidi26 .llwyfan-cms .llwyfan-article [style*="font-family"],
.aidi26 .llwyfan-cms .llwyfan-article [style*="line-height"],
.aidi26 .llwyfan-cms .llwyfan-article .MsoNormal,
.aidi26 .llwyfan-cms .llwyfan-article .MsoNormal *{
  font-size:inherit!important;
  font-family:inherit!important;
  line-height:inherit!important}

/* No measure. The handbook runs the full width of the container, as the terms
   and privacy pages do — the size and leading above are what carry the
   readability here instead. */

/* --------------------------------------------------------------------------
   Article images.

   Bounded by HEIGHT, not width, and never cropped.

   A fixed ratio with object-fit:cover was the first attempt and it was wrong:
   several of these images are portrait diagrams and flowcharts, and cropping
   a diagram to a letterbox destroys it — half the flowchart simply wasn't
   there. Nothing in CSS can tell a photograph from a diagram, so the rule has
   to be one that is safe for both.

   Capping the height does that. A tall image shrinks until it fits and its
   width follows, centred; a wide one is limited by the column instead. No
   image can take over the screen, and every image is whole.

   The trade is that a landscape photo no longer runs the full width of the
   container — at this measure a 3:2 photo would be 1200px tall, so full width
   and a sane height cannot both be had without cutting something off. Centred
   and clearly narrower reads as deliberate, where an image stopping just
   short of the text reads as a bug, which is what started this.
   -------------------------------------------------------------------------- */
/* The band behind the picture. A height-capped image is narrower than the
   column, which left it floating in white with the text squared off either
   side of it. The wash gives it somewhere to sit, full width, so the page
   keeps its left and right edges while the picture stays whole and uncropped.

   The figure is added in PHP (a26_wrap_article_images): the CMS emits a bare
   <img>, and a band wider than the picture needs an element wider than the
   picture to paint it. */
.aidi26 .llwyfan-cms .llwyfan-article .a26-fig{
  margin:0 0 30px;padding:10px 0;background:var(--a-wash);
  border-radius:24px;text-align:center;font-size:0}
.aidi26 .llwyfan-cms .llwyfan-article img.llwyfan-block-image{
  display:block;width:auto;height:auto;
  max-width:100%;max-height:min(620px,70vh);
  margin:0 auto;border-radius:16px}

/* No container on a phone: 10px of wash either side of a picture that is
   already nearly the full width reads as a rendering fault rather than a
   frame. The image takes the width instead. */
@media (max-width:620px){
  .aidi26 .llwyfan-cms .llwyfan-article .a26-fig{
    background:none;padding:0;border-radius:0;margin-bottom:24px}
  .aidi26 .llwyfan-cms .llwyfan-article img.llwyfan-block-image{
    width:100%;max-height:none;border-radius:16px}
}

.aidi26 .llwyfan-cms .llwyfan-card{
  background:#fff;border:1px solid var(--a-line);border-radius:var(--a-r);
  transition:border-color .15s ease,box-shadow .15s ease}
.aidi26 .llwyfan-cms .llwyfan-card:hover,
.aidi26 .llwyfan-cms .llwyfan-card:focus-visible{
  background:#fff;border-color:var(--a-blue);
  box-shadow:0 8px 20px -14px rgba(20,26,43,.4)}

/* Top-tier topics only. The content-type grid renders a bare .llwyfan-card;
   every nested row carries .llwyfan-card-folder or .llwyfan-card-article, so
   :not() on those two means "top tier" without the plugin needing a new class.

   !important is doing real work here, not papering over specificity: the fill
   is an inline style the renderer writes from each type's colour in the API
   (llwyfan_render_icon_box), and an inline style can't be beaten any other way. */
.aidi26 .llwyfan-cms .llwyfan-card:not(.llwyfan-card-folder):not(.llwyfan-card-article)
  .llwyfan-icon-box{background-color:transparent!important}

/* The link block (plugin v1.1.0). Styled like .a26-route__go so an outbound
   link in Llwyfan content reads the same as every other forward link here. */
.aidi26 .llwyfan-cms .llwyfan-block-link a{
  font-weight:600;color:var(--a-blue-dark);text-decoration:none;font-size:18px}
.aidi26 .llwyfan-cms .llwyfan-block-link a:hover{text-decoration:underline}
.aidi26 .llwyfan-cms .llwyfan-block-link-arrow{transition:transform .15s ease}
.aidi26 .llwyfan-cms .llwyfan-block-link a:hover .llwyfan-block-link-arrow{transform:translateX(3px)}
@media (prefers-reduced-motion:reduce){
  .aidi26 .llwyfan-cms .llwyfan-block-link-arrow{transition:none}
}

/* handbook tiles */
.a26-types{display:grid;grid-template-columns:repeat(4,1fr);gap:20px}
/* White, with the same hairline the Llwyfan cards use, so the handbook tiles
   here and the real content on /llawlyfr/ read as one family. */
.aidi26 .a26-type{background:#fff;border:1px solid var(--a-line);border-radius:var(--a-r);
  padding:30px 26px;text-decoration:none;display:flex;flex-direction:column;gap:6px;
  color:inherit;transition:border-color .15s ease,box-shadow .15s ease}
/* A 2px edge on hover, drawn as the 1px border plus a 1px inset shadow rather
   than by thickening the border itself. Changing border-width changes the
   box, so the card's contents would shift a pixel on hover and the grid would
   twitch; an inset shadow paints inside the existing box and moves nothing. */
.aidi26 .a26-type:hover{border-color:var(--a-blue);
  box-shadow:inset 0 0 0 1px var(--a-blue),0 8px 20px -14px rgba(20,26,43,.4)}
.a26-type__i{width:46px;height:46px;border-radius:12px;
  background:var(--a-lilac-tile);color:var(--a-lilac-ink);
  display:flex;align-items:center;justify-content:center;margin-bottom:5px;flex:none}
/* The four content types carry the app's own colours, in the app's order:
   Gwybodaeth, Gostyngiadau, Digwyddiadau, Cysylltiadau. Reordering the tiles
   reorders the colours — they follow position, not content.

   Fill and ink move together: the icon is a darker cut of its own tile rather
   than one blue across all four, so each tone stays a single idea. */
.a26-types .a26-type:nth-child(1) .a26-type__i{background:var(--a-lilac-tile);color:var(--a-lilac-ink)}
.a26-types .a26-type:nth-child(2) .a26-type__i{background:var(--a-mint-tile); color:var(--a-mint-ink)}
.a26-types .a26-type:nth-child(3) .a26-type__i{background:var(--a-coral-tile);color:var(--a-coral-ink)}
.a26-types .a26-type:nth-child(4) .a26-type__i{background:var(--a-peach-tile);color:var(--a-peach-ink)}
.a26-type__i svg{width:24px;height:24px;display:block}
.a26-type h3{font-size:21px}
.a26-type p{font-size:17px;color:var(--a-muted)}

/* feature grid */
.a26-feats{display:grid;gap:52px 44px}
.a26-feats[data-cols="1"]{grid-template-columns:1fr;gap:34px}
.a26-feats[data-cols="2"]{grid-template-columns:repeat(2,1fr)}
.a26-feats[data-cols="3"]{grid-template-columns:repeat(3,1fr)}
.a26-feats[data-cols="4"]{grid-template-columns:repeat(4,1fr)}
.a26-feat{display:flex;flex-direction:column;gap:7px}
/* White with a hairline, not a tinted tile: on the pale wash these sections
   usually sit on, a lilac tile and a lilac band were two shades of the same
   idea. #0F62F2 on white is 5.19:1. */
.a26-feat__i{width:72px;height:72px;border-radius:20px;background:#fff;color:var(--a-blue);
  box-shadow:inset 0 0 0 1px var(--a-line),0 4px 12px -8px rgba(10,20,60,.5);
  display:flex;align-items:center;justify-content:center;margin-bottom:4px;flex:none}
.a26-sec.is-blue .a26-feat__i{background:rgba(255,255,255,.16);color:#fff}
.a26-feat__i svg{width:34px;height:34px;display:block}
.a26-feat h3{font-size:22px}
.a26-feat p{font-size:18.5px;color:var(--a-muted)}
.a26-sec.is-blue .a26-feat p{color:rgba(255,255,255,.93)}
.a26-feat__only{align-self:flex-start;font-size:13px;font-weight:700;letter-spacing:.04em;
  color:var(--a-mark-ink);background:var(--a-yellow);border-radius:999px;padding:5px 14px;
  text-transform:none;margin-top:2px}
.a26-sec.is-blue .a26-feat__only{color:var(--a-mark-ink);background:var(--a-yellow)}

/* --------------------------------------------------------------------------
   Showcase features — the blue band's layout. No tiles: the animated mark is
   the graphic, at 96px, with room around it.

   Specificity is deliberately higher than .a26-sec.is-blue .a26-feat__i (both
   would otherwise be 0,3,0 and decided by source order, which is exactly the
   trap that cost us the hero margins).
   -------------------------------------------------------------------------- */
/* Six separate cards, not one divided block. The touching grid this replaced
   read as a single table on the blue band — the dividing hairlines grouped
   the cells into rows and columns, which implied a relationship between
   neighbours that doesn't exist. Six cards with air around them read as six
   independent things, which is what they are.

   The gap is deliberately smaller than the base grid's 52/44: these cells
   carry their own padding and shadow now, so the same gap would have pushed
   them much further apart than they look here. */
.a26-feats.is-showcase{gap:24px}
.a26-feats.is-showcase .a26-feat{
  gap:10px;padding:36px 32px 40px;background:#fff;border-radius:20px;
  box-shadow:0 20px 44px -28px rgba(6,18,54,.55)}
.a26-feats.is-showcase .a26-feat h3{font-size:25px}

/* The band is blue but this grid is not, so the blue band's own white type
   rules have to be undone inside it — they're 0,3,0 and would otherwise paint
   white text onto white. */
.a26-sec.is-blue .a26-feats.is-showcase .a26-feat h3{color:var(--a-ink)}
.a26-sec.is-blue .a26-feats.is-showcase .a26-feat p{color:var(--a-muted)}

/* The mark sits on a tile of its own tone rather than standing bare. At 96px
   the line drawing was the loudest thing in the cell — louder than the
   heading it introduces — and six saturated marks in a row read as a signal
   rather than a set. The tile carries the colour as a large pale shape
   instead, which is the handbook's own pattern. */
.a26-sec.is-blue .a26-feats.is-showcase .a26-feat__i{
  width:84px;height:84px;border-radius:23px;margin-bottom:12px;
  display:flex;align-items:center;justify-content:center}
.a26-sec.is-blue .a26-feats.is-showcase .a26-feat__i svg{
  width:46px;height:46px;
  /* The marks are drawn on a 48 viewBox at stroke 2.1, which was weighted for
     96px. At 46 that renders as a 2px hairline, so it's reset here rather
     than in the markup — the same mark still has to work at 96 elsewhere. */
  stroke-width:2.5}

/* One tile, one ink: brand blue on a light cut of the brand blue. The
   four-tone cycle this replaced had to repeat itself across six cells, and
   each repeat read as a category that didn't exist.

   #0F62F2 on #DCE8FF is 4.21:1, past the 3:1 WCAG 1.4.11 asks of a meaningful
   icon, and enough that the mark still reads at 46px.

   Each tile sits at a slightly different angle. The glyph inside is turned
   back by the same amount, so the tile tilts and the icon stays upright —
   rotating both reads as a rendering fault at these sizes, where rotating
   only the frame reads as deliberate. The angles cycle every six, which is
   exactly the number of cells, so no two tiles in the grid share one. */
.a26-feats.is-showcase .a26-feat .a26-feat__i{
  background:var(--a-blue-tile);color:var(--a-blue)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+1) .a26-feat__i{transform:rotate(-5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+1) .a26-feat__i svg{transform:rotate(5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+2) .a26-feat__i{transform:rotate(3.5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+2) .a26-feat__i svg{transform:rotate(-3.5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+3) .a26-feat__i{transform:rotate(-2deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+3) .a26-feat__i svg{transform:rotate(2deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+4) .a26-feat__i{transform:rotate(4.5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+4) .a26-feat__i svg{transform:rotate(-4.5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+5) .a26-feat__i{transform:rotate(-3.5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+5) .a26-feat__i svg{transform:rotate(3.5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+6) .a26-feat__i{transform:rotate(2.5deg)}
.a26-feats.is-showcase .a26-feat:nth-child(6n+6) .a26-feat__i svg{transform:rotate(-2.5deg)}

/* --------------------------------------------------------------------------
   The marks' motion. Inert until the section is in view (.is-live, set by the
   observer in functions-aidi26.php) and silent under reduced motion.
   -------------------------------------------------------------------------- */
.a26-g{overflow:visible}
.a26-g *{transform-box:fill-box;transform-origin:center}

@keyframes a26-g-scan{0%,12%{transform:translateY(-9px);opacity:0}
  20%{opacity:.75}80%{opacity:.75}88%,100%{transform:translateY(9px);opacity:0}}
@keyframes a26-g-page{0%,18%{transform:scaleX(1)}50%{transform:scaleX(-1)}82%,100%{transform:scaleX(1)}}
@keyframes a26-g-ring{0%{transform:scale(.45);opacity:0}18%{opacity:.85}100%{transform:scale(1.5);opacity:0}}
@keyframes a26-g-drop{0%{transform:translateY(-13px);opacity:0}22%{opacity:1}72%{opacity:1}100%{transform:translateY(16px);opacity:0}}
@keyframes a26-g-fill{0%,10%{transform:translateY(20px)}45%,100%{transform:translateY(0)}}
/* Three options answering in turn. Rests at .22 rather than 0 so the mark
   still reads as three choices when the section is off screen or the animation
   is off — a pill that fades to nothing leaves a gap, not a quiet option. */
@keyframes a26-g-pick{0%,100%{opacity:.22}20%,46%{opacity:1}}
@keyframes a26-g-beat{0%,42%{transform:scale(1)}50%{transform:scale(1.14)}58%{transform:scale(1)}
  66%{transform:scale(1.08)}74%,100%{transform:scale(1)}}
@keyframes a26-g-swapA{0%,42%{opacity:1}50%,92%{opacity:.38}100%{opacity:1}}
@keyframes a26-g-swapB{0%,42%{opacity:.38}50%,92%{opacity:1}100%{opacity:.38}}

.a26-g-cy{opacity:1}.a26-g-en{opacity:.38}
.a26-g-page{transform-origin:left center}

.is-live .a26-g-scan {animation:a26-g-scan 3.2s ease-in-out infinite}
.is-live .a26-g-page {animation:a26-g-page 4s ease-in-out infinite}
.is-live .a26-g-ring {animation:a26-g-ring 2.6s ease-out infinite}
.is-live .a26-g-ring2{animation-delay:.85s}
.is-live .a26-g-ring3{animation-delay:1.7s}
.is-live .a26-g-drop {animation:a26-g-drop 2.4s ease-in infinite}
.is-live .a26-g-drop2{animation-delay:.5s}
.is-live .a26-g-drop3{animation-delay:1s}
.is-live .a26-g-pick {animation:a26-g-pick 2.8s ease-in-out infinite}
.is-live .a26-g-pick2{animation-delay:.3s}
.is-live .a26-g-pick3{animation-delay:.6s}
.is-live .a26-g-fill {animation:a26-g-fill 3.4s cubic-bezier(.4,0,.2,1) infinite}
.is-live .a26-g-heart{animation:a26-g-beat 3.4s ease-in-out infinite}
.is-live .a26-g-cy   {animation:a26-g-swapA 4.4s ease-in-out infinite}
.is-live .a26-g-en   {animation:a26-g-swapB 4.4s ease-in-out infinite}

@media (prefers-reduced-motion:reduce){
  .is-live .a26-g-scan,.is-live .a26-g-page,.is-live .a26-g-ring,.is-live .a26-g-drop,
  .is-live .a26-g-pick,.is-live .a26-g-fill,.is-live .a26-g-heart,
  .is-live .a26-g-cy,.is-live .a26-g-en{
    animation:none}
}

/* steps */
.a26-steps{display:grid;grid-template-columns:repeat(3,1fr);gap:48px}
.a26-step{display:flex;flex-direction:column;gap:7px}
/* Animated step graphic: a pastel tile with the step number badged on it.
   Motion is CSS-only and every animation is disabled under
   prefers-reduced-motion, where each graphic rests at its finished state. */
.a26-step__g{position:relative;display:block;width:84px;height:84px;margin-bottom:14px;flex:none}
.a26-step__g svg{width:100%;height:100%;display:block;overflow:visible}
.a26-step__g b{position:absolute;right:-4px;bottom:-4px;width:30px;height:30px;border-radius:50%;
  background:var(--a-blue);color:#fff;font-family:'Lexend',sans-serif;
  font-weight:600;font-size:15px;display:flex;align-items:center;justify-content:center;
  box-shadow:0 0 0 4px #fff}
.a26-sec.is-wash .a26-step__g b{box-shadow:0 0 0 4px var(--a-wash)}

/* 1 — the form writes itself in */
.a26-g-l1,.a26-g-l2,.a26-g-l3{transform-box:fill-box;transform-origin:left center}
.a26-g-l1{animation:a26-write 4.5s ease-in-out infinite}
.a26-g-l2{animation:a26-write 4.5s ease-in-out .35s infinite}
.a26-g-l3{animation:a26-write 4.5s ease-in-out .7s infinite}
@keyframes a26-write{
  0%,8%{transform:scaleX(0)}
  28%,78%{transform:scaleX(1)}
  92%,100%{transform:scaleX(0)}
}

/* 2 — the tick draws */
.a26-g-tick{stroke-dasharray:42;stroke-dashoffset:42;
  animation:a26-draw 4.5s ease-in-out infinite}
@keyframes a26-draw{
  0%,12%{stroke-dashoffset:42}
  40%,80%{stroke-dashoffset:0}
  95%,100%{stroke-dashoffset:42}
}

/* 3 — the arrow drops into the phone */
.a26-g-arrow{transform-box:fill-box;transform-origin:center;
  animation:a26-drop 4.5s ease-in-out infinite}
@keyframes a26-drop{
  0%,10%{transform:translateY(-10px);opacity:0}
  30%{transform:translateY(0);opacity:1}
  55%{transform:translateY(16px);opacity:0}
  56%,100%{transform:translateY(16px);opacity:0}
}
.a26-g-phone{transform-box:fill-box;transform-origin:center;
  animation:a26-land 4.5s ease-in-out infinite}
@keyframes a26-land{
  0%,50%{transform:scale(1)}
  58%{transform:scale(1.08)}
  70%,100%{transform:scale(1)}
}

/* 3b — the card rises out of the envelope. Drawn behind the envelope front in
   source order, so it slides up from inside rather than over the top of it. */
.a26-g-card{transform-box:fill-box;transform-origin:center;
  animation:a26-postup 4.5s ease-in-out infinite}
@keyframes a26-postup{
  0%,12%{transform:translateY(22px)}
  40%,78%{transform:translateY(0)}
  94%,100%{transform:translateY(22px)}
}

@media (prefers-reduced-motion:reduce){
  .a26-g-l1,.a26-g-l2,.a26-g-l3,.a26-g-tick,.a26-g-arrow,.a26-g-phone,
  .a26-g-card{animation:none}
  .a26-g-tick{stroke-dashoffset:0}
  .a26-g-arrow{opacity:1;transform:none}
  .a26-g-card{transform:none}
}

/* --------------------------------------------------------------------------
   Digital / physical card switch.

   Two radios rather than JavaScript: the control keeps working with scripts
   off, and a radio is what this actually is — one of two, always one chosen.
   The inputs are visually hidden but still focusable, so the pair is operable
   from the keyboard with the arrow keys and announces itself properly.
   -------------------------------------------------------------------------- */
.a26-switch{border:0;padding:0;margin:0;min-width:0}
.a26-switch__sr,
/* Visible only to assistive tech. Used for the "opens in a new tab" note on
   every off-site button: forcing a new window without saying so is the part
   people with screen readers and magnifiers actually object to. */
.a26-sr{position:absolute;width:1px;height:1px;padding:0;margin:-1px;
  overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap;border:0}
/* Digital shows by default and physical is the one that gets revealed, rather
   than both starting hidden and the :checked rules turning one on. If any part
   of this fails — the selector, the markup, a stylesheet that didn't load —
   the failure is "both lists show", not "the section is empty". A decorative
   toggle must never be able to hide the content it toggles.

   Attribute selectors rather than ids: the ids carry a per-section counter so
   two switches on one page can't share a radio group. */
.a26-switch__pane.is-physical{display:none}
.a26-switch__sr[id^="a26-card-p"]:checked ~ .a26-switch__pane.is-physical{display:block}
.a26-switch__sr[id^="a26-card-p"]:checked ~ .a26-switch__pane.is-digital{display:none}

.a26-switch__link{margin:38px 0 0}
.a26-switch__link label{
  display:inline-flex;align-items:center;gap:9px;cursor:pointer;
  font-weight:600;font-size:17.5px;color:var(--a-blue-dark)}
.a26-switch__link label:hover{text-decoration:underline}
.a26-switch__link svg{width:19px;height:19px;flex:none;transition:transform .15s ease}
.a26-switch__link label:hover svg{transform:translateX(3px)}
.is-physical .a26-switch__link label:hover svg{transform:translateX(-3px)}
/* The focus ring belongs on the visible label, not the hidden input. */
.a26-switch__sr:focus-visible + .a26-switch__pane .a26-switch__link label,
.a26-switch__link label:focus-visible{outline:2px solid var(--a-blue);outline-offset:4px;border-radius:4px}
@media (prefers-reduced-motion:reduce){.a26-switch__link svg{transition:none}}

.a26-step__n{font-family:'Lexend',sans-serif;font-weight:600;font-size:16px;
  color:#fff;background:var(--a-blue);width:36px;height:36px;border-radius:50%;
  display:flex;align-items:center;justify-content:center;margin-bottom:5px;flex:none}
.a26-step h3{font-size:20.5px}
.a26-step p{font-size:17.5px;color:var(--a-muted)}
/* A step's own call to action. Smaller than a section-level button — it
   belongs to the step, not the section, and shouldn't outweigh the heading. */
.a26-step__cta{display:flex;flex-wrap:wrap;gap:10px;margin-top:14px}
.a26-step__cta .a26-btn{padding:12px 22px;font-size:16.5px}

/* tick list */
.a26-ticks{list-style:none;margin:36px 0 0;padding:0;display:flex;flex-direction:column;gap:15px}
.a26-ticks li{display:flex;gap:15px;align-items:flex-start;font-size:19.5px}
.a26-ticks svg{width:24px;height:24px;flex:none;margin-top:4px;color:var(--a-blue)}
.a26-split{display:grid;grid-template-columns:1fr 1fr;gap:62px;align-items:center}

/* --------------------------------------------------------------------------
   Features beside a phone. The items stack in half a column, so they are laid
   out across rather than down — the icon moves beside the heading instead of
   above it. That alone took about 150px off the column, which is what was
   leaving the phone marooned against a long run of white.
   -------------------------------------------------------------------------- */
.a26-split .a26-feats[data-cols="1"]{gap:30px}
.a26-split .a26-feat{
  display:grid;grid-template-columns:54px 1fr;column-gap:18px;row-gap:5px;
  align-items:start}
/* Top-aligned, not centred across the row: centring puts the tile level with
   the body copy on a three-line item, which reads as belonging to the
   paragraph rather than introducing the heading. */
.a26-split .a26-feat__i{grid-row:span 2;margin-bottom:0;align-self:start;margin-top:1px}
.a26-split .a26-feat h3{grid-column:2}
.a26-split .a26-feat p{grid-column:2}
.a26-split .a26-feat__only{grid-column:2;justify-self:start}
.a26-split .a26-feat__i{width:54px;height:54px;border-radius:16px}
.a26-split .a26-feat__i svg{width:27px;height:27px}

/* --------------------------------------------------------------------------
   Icons popping up around the phone.

   Two nested elements per badge on purpose: the outer one owns the pop and
   the inner one owns the idle movement. Both are transforms, and a single
   element can only run one transform animation — the second silently wins.

   The wrapper is sized to the phone rather than the column so the offsets can
   be percentages and hug the device at any width.
   -------------------------------------------------------------------------- */
.a26-phonewrap{position:relative;width:min(300px,100%);margin:0 auto}

.a26-pop{position:absolute;z-index:3;width:104px;height:104px;pointer-events:none;
  animation:a26-pop-in 9s ease-in-out infinite both}
.a26-pop__in{display:block;width:100%;height:100%}
.a26-pop svg{width:100%;height:100%;display:block;
  filter:drop-shadow(0 10px 18px rgba(10,20,60,.3))}

.a26-pop.is-bell {left:-21%;top:7%}
.a26-pop.is-smile{right:-23%;top:36%;animation-delay:.7s}
.a26-pop.is-clock{left:-18%;bottom:12%;animation-delay:1.4s}

/* Overshoot and settle, then away again before the loop restarts — the badges
   are gone for about a second, which is what makes the next pop read as an
   arrival rather than a glitch. */
@keyframes a26-pop-in{
  0%        {transform:scale(.2);opacity:0}
  6%        {transform:scale(1.2);opacity:1}
  10%       {transform:scale(.94)}
  14%,88%   {transform:scale(1);opacity:1}
  96%,100%  {transform:scale(.2);opacity:0}
}

/* The bell rings just after it lands, then holds still. Hung from the top so
   it swings rather than spinning about its middle. */
.is-bell .a26-pop__in{transform-origin:50% 14%;animation:a26-ring 9s ease-in-out infinite}
@keyframes a26-ring{
  0%,14%  {transform:rotate(0)}
  17%     {transform:rotate(-15deg)}
  21%     {transform:rotate(13deg)}
  25%     {transform:rotate(-9deg)}
  29%     {transform:rotate(6deg)}
  33%     {transform:rotate(-3deg)}
  37%,100%{transform:rotate(0)}
}

.is-smile .a26-pop__in{animation:a26-bobble 3.4s ease-in-out infinite}
@keyframes a26-bobble{
  0%,100%{transform:translateY(0) rotate(-3deg)}
  50%    {transform:translateY(-8px) rotate(3deg)}
}

/* Time passing: the minute hand goes round in four seconds, the hour hand in
   forty-eight — a 12:1 ratio, so the clock is telling a coherent time the
   whole way round rather than two hands moving independently. */
.a26-hand{transform-box:fill-box;transform-origin:50% 100%}
.a26-hand--m{animation:a26-tick 4s linear infinite}
.a26-hand--h{animation:a26-tick 48s linear infinite}
@keyframes a26-tick{to{transform:rotate(360deg)}}

@media (prefers-reduced-motion:reduce){
  .a26-pop,.a26-pop__in,.a26-hand{animation:none}
}
/* Stacked under the text, the phone is narrower and the page gutter is only
   28px, so a badge hung as far out as the desktop one lands in the margin or
   past it. They are brought in to overlap the phone's edge instead of
   clearing it, and sized down to match — a notification sitting on the device
   reads as naturally as one floating beside it, and nothing can push the
   document wider than the window. */
@media (max-width:1080px){
  .a26-pop{width:76px;height:76px}
  .a26-pop.is-bell {left:-6%;top:5%}
  .a26-pop.is-smile{right:-7%;top:34%}
  .a26-pop.is-clock{left:-5%;bottom:11%}
}
@media (max-width:520px){
  .a26-pop{width:62px;height:62px}
}

/* contacts */
.a26-contacts{display:grid;grid-template-columns:1fr 1fr;gap:1px;background:var(--a-line);
  border:1px solid var(--a-line);border-radius:12px;overflow:hidden}
.a26-contact{background:#fff;padding:30px 32px;display:flex;flex-direction:column;gap:4px}
.a26-sec.is-wash .a26-contact{background:var(--a-wash)}
/* Logos sit above the name, not beside it: these four are a tall heart, two
   wide wordmarks and a crest, and nothing lines up if they share a row with
   text. A common height and a free width is the only thing that makes a mixed
   set like this sit evenly. */
.a26-contact__logo{display:block;height:42px;margin:0 0 15px}
.a26-contact__logo img{height:100%;width:auto;max-width:210px;
  object-fit:contain;object-position:left center;display:block}
.a26-contact b{font-size:19.5px;color:var(--a-ink)}
.a26-contact span{font-size:18px;color:var(--a-muted)}
.aidi26 .a26-contact a{color:var(--a-blue-dark);text-decoration:none;font-size:18px;word-break:break-word}
.aidi26 .a26-contact a:hover{text-decoration:underline}

/* accordion */
/* Full container width — the rules and the +/- want to reach the edge.
   The answer text keeps its own reading-width cap below. */
.a26-acc{border-top:1px solid var(--a-line)}
.a26-acc details{border-bottom:1px solid var(--a-line)}
.a26-acc summary{cursor:pointer;list-style:none;padding:26px 0;font-weight:600;font-size:21.5px;
  color:var(--a-ink);display:flex;justify-content:space-between;gap:16px;align-items:center}
.a26-acc summary::-webkit-details-marker{display:none}
.a26-acc summary::after{content:"+";color:var(--a-blue);font-size:27px;font-weight:400;line-height:1}
.a26-acc details[open] summary::after{content:"\2013"}
/* Full width, no measure cap. Long lines are harder to track back from the
   end of one to the start of the next, which is what the 64ch was for — but
   these answers are two or three sentences, so they rarely wrap more than
   twice and the saving in vertical space is worth more here. */
.a26-acc__body{padding:0 0 28px;font-size:19.5px;color:var(--a-muted)}
.aidi26 .a26-acc__body a{color:var(--a-blue-dark);text-decoration:underline;
  text-underline-offset:3px;word-break:break-word}
.a26-acc__body p{margin:0 0 10px}
.a26-acc__body ul,.a26-acc__body ol{margin:16px 0 14px;padding-left:22px}
.a26-acc__body li{margin-bottom:6px}
.a26-acc__body p:last-child{margin:0}

/* rich text — also the wrapper the Llwyfan handbook renders inside */
.a26-text{max-width:70ch}
.a26-text.is-wide{max-width:none}
.a26-text h2,.a26-text h3{margin:28px 0 10px}
.a26-text h2:first-child,.a26-text h3:first-child{margin-top:0}
.a26-text p{margin:0 0 15px}
.a26-text ul,.a26-text ol{margin:20px 0 18px;padding-left:22px}
.a26-text li{margin-bottom:7px}
.aidi26 .a26-text a{color:var(--a-blue-dark)}

/* ==========================================================================
   Responsive
   ========================================================================== */
@media (max-width:1080px){
  .a26-nav__in{position:relative;flex-wrap:wrap;gap:14px}
  .a26-nav__menu{display:none;order:4;width:100%;margin:0}
  .a26-nav.is-open .a26-nav__menu{display:block}
  .a26-nav__menu ul{flex-direction:column;gap:0}
  .a26-nav__menu li{border-top:1px solid rgba(255,255,255,.25)}
  .a26-nav__menu a{display:block;padding:12px 0;border:0;font-size:17px}
  .a26-nav__menu .sub-menu{display:flex;position:static;background:transparent;box-shadow:none;
    margin:0 0 8px;padding:0 0 0 14px;min-width:0}
  .a26-nav__menu .sub-menu a{color:rgba(255,255,255,.88);padding:8px 0;font-size:15.5px}
  .a26-nav__menu .sub-menu a:hover{background:transparent;color:#fff}
  /* One row: logo, then the two pills pushed right, then the burger. The
     wrap is kept for the menu alone, which is order 4 at full width, so it
     opens underneath rather than squeezing in beside them. */
  .a26-nav__burger{display:block;order:3;margin-left:0}
  .a26-nav__acts{order:2;margin-left:auto}

  .a26-hero__grid,.a26-split{grid-template-columns:1fr;gap:32px}
  .a26-routes,.a26-steps,.a26-contacts{grid-template-columns:1fr}
  .a26-types,.a26-feats[data-cols="3"],.a26-feats[data-cols="4"]{grid-template-columns:repeat(2,1fr)}
  /* Routes are boxes now, not hairline-separated columns. These used to zero
     the horizontal padding, which left the partner strip's -36px margin with
     nothing to pull against — so the strip, its label and the logo all hung
     outside the card. Keep real padding and match the strip's pull to it. */
  .a26-route{padding:30px 26px}
  .a26-route__partner{margin:26px -26px -30px;padding:18px 26px 20px}
  .a26-in{padding:0 28px}
  .a26-sec{padding:64px 0}
  .a26-foot__grid{grid-template-columns:1fr 1fr}
}
@media (max-width:560px){
  .a26-types,.a26-feats[data-cols="2"],.a26-feats[data-cols="3"],.a26-feats[data-cols="4"]{grid-template-columns:1fr}
  .a26-foot__grid{grid-template-columns:1fr}
}

/* ==========================================================================
   LEGAL PAGES — terms and privacy
   ========================================================================== */

/* The draft notice. Yellow rather than red: this is a "not finished yet"
   warning, not an error, and red on a carer-facing page reads as alarm. */
.a26-legal__draft{
  background:var(--a-yellow-tile);border-left:5px solid #E8A50B;
  border-radius:0 12px 12px 0;padding:16px 20px;margin:0 0 34px;
  font-size:18px;line-height:1.55;color:var(--a-ink);max-width:70ch}
.a26-legal__draft strong{display:block;font-size:15px;letter-spacing:.06em;
  text-transform:uppercase;margin-bottom:4px}

.a26-legal__intro{margin-bottom:34px}

/* The young/adult switch. The fieldset is reset to nothing — it is here for
   the grouping a screen reader needs, not for a box. */
.a26-legal__switch{border:0;padding:0;margin:0;min-width:0}
.a26-tabs{display:inline-flex;gap:4px;padding:4px;margin:0 0 38px;
  background:var(--a-wash);border-radius:999px}
.a26-tabs label{
  padding:10px 22px;border-radius:999px;cursor:pointer;
  font-size:17.5px;font-weight:600;color:var(--a-blue-dark);
  white-space:nowrap;transition:background .12s ease,color .12s ease}
.a26-tabs label:hover{background:var(--a-wash-hover)}
/* Higher specificity than the hover rule above (an id beats two classes), so
   the selected tab stays selected while the pointer is over its neighbour. */
#a26-legal-young:checked ~ .a26-tabs label[for="a26-legal-young"],
#a26-legal-adult:checked ~ .a26-tabs label[for="a26-legal-adult"]{
  background:var(--a-blue);color:#fff}
.a26-legal__switch input:focus-visible ~ .a26-tabs label{outline:2px solid var(--a-blue);outline-offset:3px}

/* Fail-safe: young is the page with no CSS at all, and adult is revealed. */
.a26-legal__pane.is-adult{display:none}
#a26-legal-adult:checked ~ .a26-legal__pane.is-adult{display:block}
#a26-legal-adult:checked ~ .a26-legal__pane.is-young{display:none}

/* These two pages use the full width of the container, and they use it by
   putting the contents in a column of its own rather than by stretching the
   prose: a twenty-section document set 160 characters to the line is wide,
   not readable. The contents stays in view while the document scrolls, which
   is the thing a long legal page most needs and the thing the empty right
   half of the page was previously doing instead. */
.a26-text.a26-legal{max-width:none;display:grid;
  grid-template-columns:clamp(240px,22vw,330px) minmax(0,1fr);
  gap:0 60px;align-items:start}
.a26-legal__note{grid-column:1 / -1}

.a26-legal__toc{background:var(--a-wash);border-radius:16px;padding:24px 26px;
  margin:0;position:sticky;top:104px;
  /* So a document with more sections than the window is tall can still be
     scrolled through inside its own panel. */
  max-height:calc(100vh - 136px);overflow:auto}
.a26-legal__toc h2{font-size:16px;letter-spacing:.06em;text-transform:uppercase;
  color:var(--a-muted);margin:0 0 12px}
/* No numbers: the headings carry their own, and a second set beside them read
   as a different numbering of the same thing. */
.a26-legal__toc ul{margin:0;padding:0;list-style:none;font-size:17px;line-height:1.4}
.a26-legal__toc li{margin-bottom:10px}
.aidi26 .a26-legal__toc a{color:var(--a-blue-dark);text-decoration:none}
.aidi26 .a26-legal__toc a:hover{text-decoration:underline}

/* Below the breakpoint the contents goes back above the document, where it
   is a list to skim past rather than a column to keep. */
@media (max-width:900px){
  .a26-text.a26-legal{display:block}
  .a26-legal__toc{position:static;max-height:none;margin-bottom:34px}
  .a26-legal__toc ul{columns:2;column-gap:30px}
  .a26-legal__toc li{break-inside:avoid}
}
@media (max-width:620px){.a26-legal__toc ul{columns:1}}

/* The language fallback note, shown when a Welsh translation is missing. */
.a26-legal__note{background:var(--a-wash);border-radius:12px;padding:14px 18px;
  margin:0 0 28px;font-size:17.5px;color:var(--a-body)}

/* The document itself. Capped at a readable measure inside its column, so
   the extra width goes to the contents and the margin rather than to the
   line length. */
.a26-legal__doc{max-width:76ch}
.a26-legal__doc h2{font-size:27px;line-height:1.2;margin:46px 0 14px;
  /* The nav is sticky, so an anchor jump would otherwise land the heading
     underneath it. */
  scroll-margin-top:96px}
.a26-legal__doc h2:first-child{margin-top:0}
.a26-legal__doc h3{font-size:21px;margin:30px 0 8px;scroll-margin-top:96px}
.a26-legal__doc p,.a26-legal__doc li{font-size:19.5px;line-height:1.66}

/* Tables carry the retention schedules and the lawful bases, which is where
   someone checking compliance will look first. Left-aligned, generous rows,
   and a header that is a tint rather than a rule. */
.a26-legal__doc table{width:100%;border-collapse:collapse;margin:22px 0 26px;
  font-size:17.5px;line-height:1.5}
.a26-legal__doc th,.a26-legal__doc td{
  text-align:left;vertical-align:top;padding:12px 14px;
  border-bottom:1px solid var(--a-line)}
.a26-legal__doc th{background:var(--a-wash);color:var(--a-ink);font-weight:700;
  border-bottom:1px solid var(--a-line)}
.a26-legal__doc tr:last-child td{border-bottom:0}
/* Horizontal scroll rather than a squashed three-column table on a phone. */
@media (max-width:620px){
  .a26-legal__doc table{display:block;overflow-x:auto;white-space:normal}
  .a26-legal__doc th,.a26-legal__doc td{min-width:9rem}
}

/* The [TO CONFIRM] notes. Deliberately not styled like the prose around
   them: these are editorial, they are addressed to the people reviewing the
   document rather than to a carer, and they come out before it is published.
   A dashed rule says "working note" in a way a solid one does not. */
.a26-legal__doc blockquote{
  margin:24px 0;padding:16px 20px;border-left:4px dashed #B9C4DA;
  background:#F7F9FE;border-radius:0 12px 12px 0;color:var(--a-body)}
.a26-legal__doc blockquote p{margin:0;font-size:17.5px}
.a26-legal__doc blockquote p + p{margin-top:10px}

/* --------------------------------------------------------------------------
   Narrow bar. Everything on the bar has to fit on one line: the logo, Apply,
   the language pill and the burger. In Welsh that line reads "Gwneud cais"
   and "English", which is the widest it ever gets and does not go in 360px at
   the full sizes — so the logo comes down, the gaps close up, and the
   language pill drops to CY / EN.
   -------------------------------------------------------------------------- */
@media (max-width:560px){
  .a26-nav__in{padding:12px 16px;gap:7px}
  .a26-nav__logo img{height:27px}
  .a26-nav__acts{gap:7px}
  .a26-pill{font-size:14.5px;padding:6px 13px;border-width:1.25px}
  .a26-pill__full{display:none}
  .a26-pill__abbr{display:inline}
  .a26-nav__burger{padding:3px}
  .a26-nav__burger svg{width:24px;height:24px}
}
/* Below this the logo is the only thing left to give. */
@media (max-width:380px){
  .a26-nav__in{padding:12px 13px;gap:6px}
  .a26-nav__logo img{height:24px}
  .a26-pill{font-size:14px;padding:6px 11px}
}


/* --------------------------------------------------------------------------
   Contact rows in handbook articles.

   The plugin prints an emoji — a phone, an envelope, a pin — which renders
   differently on every platform and reads as a stray character rather than a
   control. These are the most actionable things on the page: a carer who has
   read this far wants the number. So the emoji is hidden and the row is
   rebuilt as a card, with the icon drawn from a mask so it takes the brand
   colour.

   The SVGs use SINGLE quotes inside the data URI. With double quotes the CSS
   string closes at the first attribute, the mask never loads, and what is
   left is the bare blue box the mask was meant to cut a shape out of.

   The plugin carries a type class from 1.6.0, which is what each icon keys
   off; anything it does not recognise keeps the link icon.

   Every selector here is qualified with .llwyfan-article on purpose. The link
   block is a <p>, and the article's own paragraph rule — three classes and an
   element — outscores three classes alone, so without this the margin above
   each card was silently dropped and the cards sat tight under the text.
   -------------------------------------------------------------------------- */
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact,
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link{
  display:flex;align-items:center;gap:15px;
  margin:32px 0 12px;padding:13px 20px 13px 14px;
  background:var(--a-wash);border-radius:16px;
  max-width:max-content;
  transition:background .15s ease,box-shadow .15s ease}
/* A run of them is one group, so only the first takes the gap above. */
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact + .llwyfan-block-contact,
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact + .llwyfan-block-link,
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link + .llwyfan-block-contact,
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link + .llwyfan-block-link{margin-top:0}
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact:hover,
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link:hover{
  background:var(--a-wash-hover);
  box-shadow:0 10px 24px -18px rgba(10,20,60,.7)}

/* The emoji goes; the span becomes the tile that holds our own icon. */
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact-icon{
  flex:none;width:42px;height:42px;border-radius:13px;background:#fff;
  box-shadow:inset 0 0 0 1px var(--a-line);
  display:grid;place-items:center;
  font-size:0;color:transparent;text-indent:-9999px;overflow:hidden}
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact-icon::before{
  content:"";width:21px;height:21px;background:var(--a-blue);
  -webkit-mask:var(--a-ico) center/contain no-repeat;
          mask:var(--a-ico) center/contain no-repeat;
  --a-ico:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M14.5 3.5h6v6'/%3E%3Cpath d='M10 14 20.5 3.5'/%3E%3Cpath d='M20 13.5v5a2 2 0 0 1-2 2H5.5a2 2 0 0 1-2-2V6a2 2 0 0 1 2-2h5'/%3E%3C/svg%3E")}

.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact--phone   .llwyfan-block-contact-icon::before{--a-ico:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M22 16.9v3a2 2 0 0 1-2.2 2 19.8 19.8 0 0 1-8.6-3.1 19.5 19.5 0 0 1-6-6A19.8 19.8 0 0 1 2.1 4.2 2 2 0 0 1 4.1 2h3a2 2 0 0 1 2 1.7c.1 1 .4 1.9.7 2.8a2 2 0 0 1-.5 2.1L8.1 9.9a16 16 0 0 0 6 6l1.3-1.3a2 2 0 0 1 2.1-.4c.9.3 1.8.6 2.8.7a2 2 0 0 1 1.7 2z'/%3E%3C/svg%3E")}
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact--email   .llwyfan-block-contact-icon::before{--a-ico:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Crect x='2.5' y='4.5' width='19' height='15' rx='2.5'/%3E%3Cpath d='m3 7 9 6 9-6'/%3E%3C/svg%3E")}
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact--address .llwyfan-block-contact-icon::before{--a-ico:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M20 10c0 6-8 12-8 12s-8-6-8-12a8 8 0 0 1 16 0z'/%3E%3Ccircle cx='12' cy='10' r='3'/%3E%3C/svg%3E")}
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact--date    .llwyfan-block-contact-icon::before{--a-ico:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Crect x='3.5' y='5' width='17' height='15' rx='2.5'/%3E%3Cpath d='M8 2.5V6M16 2.5V6M3.5 10h17'/%3E%3C/svg%3E")}

/* The link block has no icon span of its own, so the tile is drawn in front
   of it — same shape, so contacts and links read as one set.

   The colour is baked into this one rather than masked. A mask needs its own
   box, and an absolutely positioned box inside a flex row takes its static
   position from the content edge — which put the icon outside the card
   altogether. A background image on the tile has no such problem. */
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link::before{
  content:"";flex:none;width:42px;height:42px;border-radius:13px;
  background:#fff url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%230F62F2' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M14.5 3.5h6v6'/%3E%3Cpath d='M10 14 20.5 3.5'/%3E%3Cpath d='M20 13.5v5a2 2 0 0 1-2 2H5.5a2 2 0 0 1-2-2V6a2 2 0 0 1 2-2h5'/%3E%3C/svg%3E") center/21px 21px no-repeat;
  box-shadow:inset 0 0 0 1px var(--a-line)}

.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact a,
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact span:not(.llwyfan-block-contact-icon),
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link a{
  font-size:19.5px;font-weight:600;line-height:1.3;text-decoration:none;
  color:var(--a-blue-dark)}
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact a:hover,
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link a:hover{text-decoration:underline}
.aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link-arrow{margin-left:8px}

@media (max-width:620px){
  .aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact,
  .aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link{max-width:none;padding:12px 16px 12px 12px;gap:12px}
  .aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-contact-icon,
  .aidi26 .llwyfan-cms .llwyfan-article .llwyfan-block-link::before{width:38px;height:38px;border-radius:12px;background-size:19px 19px}
}
