/*
Theme Name: Oryx Executive Search
Theme URI: https://staging.oryxes.co.uk/
Description: Custom theme for Oryx Executive Search, built from the Figma "Oryx" file.
Author: Talent Hero Media
Version: 0.2.0
Text Domain: oryx
*/

/* ==========================================================================
   Design tokens — from the Figma "Oryx" file (GLOBAL_VARS fills/text styles)
   ========================================================================== */

:root {
	/* Brand */
	--color-purple: #662483;
	--color-purple-alt: #652981;
	--color-purple-tint: #F4DBFF;

	/* Neutrals */
	--color-ink: #1D1D1B;
	--color-charcoal-1: #221B2E;   /* headings on light backgrounds */
	--color-charcoal-2: #2A2233;   /* chip / small text */
	--color-deep-teal: #07232F;
	--color-grey: #9D9D9C;

	/* Off-whites / paper tones */
	--color-paper-1: #F8F7F3;
	--color-paper-2: #F4F0E7;      /* also the card border colour */
	--color-paper-3: #EEE9DE;
	--color-grey-light: #EFEFEF;
	--color-white: #FFFFFF;

	/* Accent */
	--color-gold: #C8B27A;

	/* Type */
	--font-display: 'Literata', Georgia, 'Times New Roman', serif;
	--font-body: 'Figtree', -apple-system, BlinkMacSystemFont, 'Segoe UI', Arial, sans-serif;

	/* Fluid type. The comp is a single 1920px frame, so every size below is the
	   comp value at the top end and a deliberately chosen phone value at the
	   bottom — 72px display type wraps to five lines on a 375px screen. */
	--step-display: clamp(2.25rem, 1.35rem + 3.84vw, 4.5rem);   /* 36 → 72 */
	--step-h2:      clamp(1.75rem, 1.19rem + 2.4vw, 3.4375rem); /* 28 → 55, centred section headings */
	--step-h2-block: clamp(1.625rem, 1.13rem + 2.1vw, 3.125rem); /* 26 → 50, two-column block headings */
	--step-h3:      clamp(1.375rem, 1.13rem + 1.07vw, 2rem);    /* 22 → 32 */
	--step-lead:    clamp(1.125rem, 1.0rem + 0.53vw, 1.4375rem);/* 18 → 23 */
	--step-body:    clamp(1rem, 0.96rem + 0.18vw, 1.125rem);    /* 16 → 18 */
	--step-small:   1.0625rem;                                   /* 17, nav */

	/* Layout. The comp insets content 375px inside a 1920px frame, i.e. a
	   1170px column; below that the gutter shrinks rather than the column. */
	--content-max: 1170px;
	--gutter: 24px;
	/* TWO SPACINGS, NOT ONE. Every section carried 100px top and bottom, so two
	   adjacent ones put 200px between them — and the comp's own content gaps
	   are 60 to 116. The 100px in the file is a BAND's internal padding: those
	   frames are absolutely positioned rather than stacked, so a frame's top
	   and bottom padding never both land in the same gap.

	   So a plain section spends half, and a pair of them adds up to the comp's
	   figure. A section that paints its own background keeps the full 100
	   inside it, which is what the file actually specifies. */
	--band-y:    clamp(56px, 3.5rem + 2.5vw, 100px);
	--section-y: clamp(28px, 1.75rem + 1.25vw, 50px);
}

@media (min-width: 768px) {
	:root { --gutter: 40px; }
}

@media (min-width: 1280px) {
	:root { --gutter: 64px; }
}

/* ==========================================================================
   Base
   ========================================================================== */

*, *::before, *::after { box-sizing: border-box; }

html { -webkit-text-size-adjust: 100%; }

body {
	margin: 0;
	font-family: var(--font-body);
	font-size: var(--step-body);
	line-height: 1.667;              /* 30px on 18px, per the comp */
	color: var(--color-ink);
	background: var(--color-white);
	-webkit-font-smoothing: antialiased;
}

img { max-width: 100%; height: auto; }

a { color: inherit; }

h1, h2, h3, h4 {
	font-family: var(--font-display);
	font-weight: 300;
	line-height: 1.2;
	margin: 0;
	color: var(--color-charcoal-1);
}

h1 { font-size: var(--step-display); }
h2 { font-size: var(--step-h2); }
h3 { font-size: var(--step-h3); }

p { margin: 0 0 1.25em; }
p:last-child { margin-bottom: 0; }

/* Focus is never removed, only restyled — keyboard users need to see it. */
:focus-visible {
	outline: 2px solid var(--color-purple);
	outline-offset: 3px;
}

.screen-reader-text {
	position: absolute;
	width: 1px; height: 1px;
	padding: 0; margin: -1px;
	overflow: hidden;
	clip-path: inset(50%);
	white-space: nowrap;
}

/* Anything holding a .screen-reader-text has to be a positioned ancestor.
   Otherwise the label's containing block is the initial one: it escapes its
   clipping parent, lands at document coordinates, and drags the page's
   scrollable width out with it — 3901px against a 1920px viewport, showing as
   a horizontal scrollbar with no visible cause. */
.person-card__linkedin,
.site-footer__linkedin,
.alliance__button { position: relative; }

/* ==========================================================================
   Layout primitives
   ========================================================================== */

.container {
	width: 100%;
	max-width: calc(var(--content-max) + var(--gutter) * 2);
	margin-inline: auto;
	padding-inline: var(--gutter);
}

.section {
	padding-block: var(--section-y);
}

/* A band's padding is its own, not a gap shared with the section next to it. */
.section--purple,
.section--paper { padding-block: var(--band-y); }

.section--purple {
	background: var(--color-purple);
	color: var(--color-white);
}
.section--purple h1,
.section--purple h2,
.section--purple h3 { color: var(--color-white); }

.section--paper { background: var(--color-paper-1); }

/* ==========================================================================
   Buttons

   NOTE: keep this block here, above the component sections. It has now been
   deleted TWICE by range-based edits that replaced a span of the component
   CSS and swallowed it — each time the CTA button silently degraded to
   underlined text with nothing failing. If you are replacing a range of this
   file, check what falls inside it.
   ========================================================================== */

.button {
	display: inline-flex;
	align-items: center;
	gap: 10px;
	min-height: 44px;
	padding: 14px 26px;
	background: var(--color-purple);
	color: var(--color-white);
	/* style_ed302c75 / style_41706a7d: Figtree 700 16px, 0.1em tracking,
	   UPPERCASE. The 600/0.02em/sentence-case here was a guess. */
	font-weight: 700;
	font-size: 1rem;
	line-height: 1.2;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	text-decoration: none;
	border: 0;
	border-radius: 50px;
	cursor: pointer;
}

.button:hover { background: var(--color-purple-alt); }

.button__arrow { flex: 0 0 auto; }

.button--ghost {
	background: transparent;
	border: 1px solid currentColor;
	color: inherit;
}

/* ==========================================================================
   Header
   ========================================================================== */

/* The comp's header frame has an EMPTY fill and sits at the top of the page
   frame, above the hero — it is not overlaid on the photograph. It reads as a
   white bar only because the page behind it is white. Building it as an
   absolutely-positioned overlay with white type was the single biggest visual
   difference from the design. */
.site-header {
	position: relative;
	z-index: 20;
	padding-block: 20px;
	color: var(--color-charcoal-2);
	background: transparent;
}

.site-header__inner {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 24px;
	width: 100%;
	max-width: none;      /* full-bleed: the node is 1920 wide with 50px padding */
	margin-inline: auto;
	padding-inline: 50px;
}

.site-header__logo {
	display: inline-flex;
	align-items: center;
	font-family: var(--font-display);
	font-size: 1.5rem;
	text-decoration: none;
	color: inherit;
}
.site-header__logo { color: var(--color-purple); }
.site-header__logo-mark {
	display: block;
	width: auto;
	height: 66px;          /* the comp's mark is 169x66 */
	max-width: 169px;
	color: currentColor;
}

.site-header__menu {
	display: flex;
	align-items: center;
	gap: 50px;
	margin: 0;
	padding: 0;
	list-style: none;
	font-size: var(--step-small);
	font-weight: 500;
	letter-spacing: 0.06em;
}

/* The comp marks the page you are on in brand purple. */
.site-header__menu .current-menu-item > a,
.site-header__menu .current-menu-ancestor > a,
.site-header__menu .current_page_item > a { color: var(--color-purple); }

.site-header__menu a {
	text-decoration: none;
	/* 44px of target around ~19px of text. The header's height comes from the
	   66px logo, so this costs nothing visually and fixes a 32px tap target at
	   1024 — iPad landscape, which is a touch device showing the desktop nav. */
	display: inline-block;
	padding-block: 12px;
}
.site-header__menu a:hover { text-decoration: underline; }

/* Sub-menus. Hidden by default at every width and revealed either by hover /
   focus-within (pointer) or by the toggle button (touch and keyboard), so the
   parent item stays a working link rather than a dead dropdown handle. */
.site-header__menu li { position: relative; }

.site-header__menu .sub-menu {
	margin: 0;
	padding: 0;
	list-style: none;
}

.site-header__submenu-toggle {
	min-width: 44px;
	min-height: 44px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 32px;
	height: 32px;
	margin-left: 2px;
	padding: 0;
	background: none;
	border: 0;
	color: inherit;
	cursor: pointer;
}

/* Drawn chevron, so there is no icon file to load or 404. */
.site-header__submenu-toggle::before {
	content: '';
	width: 7px;
	height: 7px;
	border-right: 2px solid currentColor;
	border-bottom: 2px solid currentColor;
	transform: translateY(-2px) rotate(45deg);
	transition: transform 0.15s ease;
}
.site-header__submenu-toggle[aria-expanded="true"]::before {
	transform: translateY(1px) rotate(-135deg);
}

@media (min-width: 1024px) {
	.site-header__menu > li.menu-item-has-children > a { padding-right: 2px; }

	/* Anchored to the RIGHT of its parent, not the left. The nav sits against
	   the right edge of the header, so a panel hung off the left of a late item
	   runs past the viewport — the Practice Areas panel is 425px wide (the
	   width of "Energy, Natural Resources and Renewables") and pushed the page
	   61px wider than the window at every desktop size, giving the whole site a
	   horizontal scrollbar with no visible cause. */
	.site-header__menu .sub-menu {
		position: absolute;
		top: 100%;
		left: auto;
		right: -20px;
		/* max-content, or the absolutely-positioned box shrinks to min-width and
		   every long area name wraps to three lines inside a 220px panel. It
		   sizes to the longest label — "Energy, Natural Resources and
		   Renewables" — and the cap is what makes a longer one wrap instead of
		   running off the screen. */
		width: max-content;
		min-width: 220px;
		max-width: min(920px, calc(100vw - 40px));
		/* So a hover block is clipped by the panel's own radius instead of
		   squaring off its corners. */
		overflow: hidden;
		padding: 12px 0;
		background: var(--color-white);
		border-radius: 12px;
		box-shadow: 0 18px 40px rgba(4, 1, 10, 0.18);
		opacity: 0;
		visibility: hidden;
		transform: translateY(-6px);
		transition: opacity 0.15s ease, transform 0.15s ease, visibility 0.15s;
	}

	/* THE PANEL IS WHITE ON EVERY PAGE, so its links are dark on every page.
	   .site-header--overlay — the transparent header over the home hero —
	   paints `.site-header__menu a` white, and that selector reaches inside the
	   dropdown as well as along the top row, so on the home page the panel
	   rendered white on white and looked empty. Exactly the mobile panel's bug
	   mirrored: a colour scoped to the header's state, applied to type sitting
	   on a surface that has no state. */
	.site-header__menu .sub-menu a,
	.site-header--overlay .site-header__menu .sub-menu a {
		color: var(--color-charcoal-1);
	}

	/* A long area name wraps rather than setting the panel's width. Fourteen
	   practice areas include two that are half a sentence long. */
	.site-header__menu .sub-menu a {
		display: block;
		padding: 12px 24px;
		white-space: normal;
		text-wrap: pretty;
	}

	/* Two columns once the list is long enough to be worth splitting — set by
	   JS, which counts the items, so adding a fifteenth practice area rebalances
	   instead of spilling into a third column. Column flow, not row flow: an
	   alphabetical list is read DOWN one column and then down the next, and
	   filling left-to-right across rows would put B beside A and make the order
	   unreadable. */
	.site-header__menu .sub-menu--split {
		display: grid;
		grid-auto-flow: column;
		grid-template-rows: repeat(var(--sub-rows, 7), auto);
		grid-auto-columns: minmax(0, 1fr);
		align-content: start;
	}

	/* The hover state is the whole row, not the words. The anchor is already
	   display:block, so it fills its column and the block is the full width of
	   that column. */
	.site-header__menu .sub-menu a:hover,
	.site-header__menu .sub-menu a:focus-visible,
	.site-header--overlay .site-header__menu .sub-menu a:hover,
	.site-header--overlay .site-header__menu .sub-menu a:focus-visible {
		color: var(--color-white);
		background: var(--color-purple);
		text-decoration: none;
	}

	/* THE PRACTICE AREAS PANEL — option A of the 2026-10-08 menu redesign.
	   A fixed 660px panel: a purple label, two columns of rows ruled in
	   paper, a cream row with a gold arrow on hover instead of the solid
	   purple block, and a cream footer strip linking to the Client Showcase.
	   The About dropdown keeps the plain treatment above. */
	.site-header__nav .sub-menu--split {
		width: 660px;
		box-sizing: border-box;
		padding: 61px 36px 0;
		/* Two explicit columns, so the footer strip's 1 / -1 spans both;
		   with only implicit columns, -1 is the first line and it covered one. */
		grid-template-columns: repeat(2, minmax(0, 1fr));
		column-gap: 40px;
		border-radius: 16px;
		box-shadow: 0 24px 60px rgba(7, 35, 47, 0.22), 0 2px 6px rgba(7, 35, 47, 0.08);
		letter-spacing: normal;
	}

	/* The label is decoration over a list that already says what it is (its
	   parent link reads "Practice Areas"), so a pseudo-element, not an item. */
	.site-header__nav .sub-menu--split::before {
		content: 'Practice areas';
		position: absolute;
		top: 28px;
		left: 36px;
		font-size: 0.8125rem;
		font-weight: 600;
		letter-spacing: 0.14em;
		text-transform: uppercase;
		color: var(--color-purple);
	}

	.site-header__nav .sub-menu--split > .menu-item { border-bottom: 1px solid var(--color-paper-2); }

	.site-header__nav .sub-menu--split > .menu-item > a {
		display: flex;
		align-items: center;
		justify-content: space-between;
		gap: 16px;
		margin: 0 -14px;
		padding: 13px 14px;
		border-radius: 8px;
		font-size: 1rem;
		font-weight: 500;
		line-height: 1.35;
		transition: background-color 0.15s ease, color 0.15s ease;
	}

	/* Drawn arrow, gold, slid in on hover. */
	.site-header__nav .sub-menu--split > .menu-item > a::after {
		content: '';
		flex: 0 0 16px;
		height: 16px;
		background: var(--color-gold);
		-webkit-mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath d='M3 8h10M9 4l4 4-4 4' fill='none' stroke='%23000' stroke-width='1.8' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E") center / contain no-repeat;
		        mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16'%3E%3Cpath d='M3 8h10M9 4l4 4-4 4' fill='none' stroke='%23000' stroke-width='1.8' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E") center / contain no-repeat;
		opacity: 0;
		transform: translateX(-4px);
		transition: opacity 0.15s ease, transform 0.15s ease;
	}

	.site-header__nav .sub-menu--split > .menu-item > a:hover,
	.site-header__nav .sub-menu--split > .menu-item > a:focus-visible {
		background: var(--color-paper-1);
		color: var(--color-purple);
	}
	.site-header__nav .sub-menu--split > .menu-item > a:hover::after,
	.site-header__nav .sub-menu--split > .menu-item > a:focus-visible::after {
		opacity: 1;
		transform: none;
	}

	/* The footer strip runs under both columns, below the last row. */
	.site-header__nav .sub-menu__footer {
		grid-column: 1 / -1;
		grid-row: -1 / span 1;
		display: flex;
		align-items: center;
		justify-content: space-between;
		gap: 24px;
		margin: 22px -36px 0;
		padding: 16px 36px;
		background: var(--color-paper-1);
		border-top: 1px solid var(--color-paper-2);
		font-size: 0.9375rem;
		color: var(--color-charcoal-2);
	}

	.site-header__nav .sub-menu .sub-menu__footer-link,
	.site-header--overlay .site-header__nav .sub-menu .sub-menu__footer-link {
		display: inline-flex;
		align-items: center;
		gap: 8px;
		padding: 0;
		font-size: 0.875rem;
		font-weight: 700;
		letter-spacing: 0.1em;
		text-transform: uppercase;
		color: var(--color-purple);
		background: none;
	}
	.site-header__nav .sub-menu .sub-menu__footer-link:hover,
	.site-header__nav .sub-menu .sub-menu__footer-link:focus-visible,
	.site-header--overlay .site-header__nav .sub-menu .sub-menu__footer-link:hover,
	.site-header--overlay .site-header__nav .sub-menu .sub-menu__footer-link:focus-visible {
		color: var(--color-purple);
		background: none;
		text-decoration: underline;
	}
	.sub-menu__footer-link .button__arrow { width: 14px; height: 14px; }

	.site-header__menu > li:hover > .sub-menu,
	.site-header__menu > li:focus-within > .sub-menu,
	.site-header__menu > li > .sub-menu.is-open {
		opacity: 1;
		visibility: visible;
		transform: translateY(0);
	}
}

@media (max-width: 1023px) {
	/* On a phone the sub-menu is a disclosure inside the panel, not an overlay. */
	.site-header__menu .sub-menu {
		padding-left: 16px;
	}
	.site-header__menu .sub-menu[hidden] { display: none; }
	/* The phone menu stays as it was; the Client Showcase is in About. */
	.sub-menu__footer { display: none; }
}

/* The nav collapses to a toggle below the first breakpoint; the toggle itself
   is hidden from desktop where the full menu shows. */
/* A hamburger, not the word "Menu". Three 2px rules that become a cross when
   the nav is open, so the control says what it will do next. The label stays in
   the accessibility tree — an icon-only button with no name is unusable with a
   screen reader. */
.site-header__toggle {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	background: none;
	border: 0;
	padding: 10px;
	margin: -10px;
	color: inherit;
	cursor: pointer;
	min-width: 44px;
	min-height: 44px;
	position: relative;
}

.site-header__bars {
	display: block;
	position: relative;
	width: 22px;
	height: 16px;
}
.site-header__bars span {
	position: absolute;
	left: 0;
	width: 100%;
	height: 2px;
	background: currentColor;
	border-radius: 2px;
	transition: transform 0.2s ease, opacity 0.15s ease;
}
.site-header__bars span:nth-child(1) { top: 0; }
.site-header__bars span:nth-child(2) { top: 7px; }
.site-header__bars span:nth-child(3) { top: 14px; }

.site-header__toggle[aria-expanded="true"] .site-header__bars span:nth-child(1) {
	transform: translateY(7px) rotate(45deg);
}
.site-header__toggle[aria-expanded="true"] .site-header__bars span:nth-child(2) { opacity: 0; }
.site-header__toggle[aria-expanded="true"] .site-header__bars span:nth-child(3) {
	transform: translateY(-7px) rotate(-45deg);
}

@media (prefers-reduced-motion: reduce) {
	.site-header__bars span { transition: none; }
}

@media (max-width: 1023px) {
	.site-header__nav {
		position: absolute;
		inset: 100% 0 auto 0;
		background: var(--color-charcoal-1);
		padding: var(--gutter);
	}
	.site-header__nav[hidden] { display: none; }
	.site-header__menu {
		flex-direction: column;
		align-items: stretch;
		gap: 4px;
	}
	.site-header__menu a {
		display: block;
		padding-block: 12px;   /* 44px touch target */
	}

	/* A parent item and its disclosure chevron sit on ONE line. The chevron is
	   inserted immediately after the link, but a block-level link fills the row
	   and pushed it onto the next one, so "About" had a stray arrow floating
	   underneath it. The row is the flex container; the link takes the space
	   and the chevron sits at its end. */
	.site-header__menu > li { display: flex; align-items: center; }
	.site-header__menu > li > a { flex: 1 1 auto; }
	.site-header__menu > li > .site-header__submenu-toggle { flex: 0 0 auto; }

	/* The sub-menu is a sibling of both, so it has to break to its own row. */
	.site-header__menu > li.menu-item-has-children { flex-wrap: wrap; }
	.site-header__menu > li > .sub-menu { flex: 1 0 100%; }

	/* THE PANEL IS DARK ON EVERY PAGE, so the type in it has to be light on
	   every page. White was only ever set under .site-header--overlay, which is
	   the home page's transparent-over-hero header — so on About, Services, a
	   practice area, anywhere interior, the menu painted the interior header's
	   dark ink onto the dark panel and the links were invisible. The home page
	   hid it, because there the overlay rule happened to supply the right
	   colour for the wrong reason.

	   The current-page marker has the same problem: brand purple on #221B2E is
	   barely a colour. Gold is what the overlay header already uses to mark
	   state on a dark ground. */
	.site-header__nav a,
	.site-header__nav .site-header__submenu-toggle { color: var(--color-white); }

	.site-header__nav .current-menu-item > a,
	.site-header__nav .current-menu-ancestor > a,
	.site-header__nav .current_page_item > a { color: var(--color-gold); }

	.site-header__nav a:hover,
	.site-header__nav a:focus-visible,
	.site-header__nav .site-header__submenu-toggle:hover { color: var(--color-gold); }
}

@media (min-width: 1024px) {
	.site-header__toggle { display: none; }
	.site-header__nav[hidden] { display: block; }
}

/* ==========================================================================
   Hero — full-bleed photograph, dark gradient, copy bottom-left
   ========================================================================== */

/* The band is 627 tall (y=106 to 733) and its content is SPREAD, not stacked:
   the H1 sits 104px below the top edge and the intro's baseline 82px above the
   bottom, with 181px of air between them. Built bottom-aligned, both landed in
   the lower third — the H1 was 154px too low and the intro 153px too high, and
   that reads as the whole hero being mispadded. */
.hero {
	position: relative;
	display: flex;
	align-items: stretch;
	min-height: min(70vh, 627px);
	padding-block: clamp(56px, 6vw, 104px) clamp(48px, 5vw, 82px);
	background: var(--color-charcoal-1);
	color: var(--color-white);
	overflow: hidden;
}

.hero__media {
	position: absolute;
	inset: 0;
	object-fit: cover;
	width: 100%;
	height: 100%;
}

/* The comp runs a left-to-right dark gradient over the photograph so the copy
   keeps contrast wherever the image is light. */
.hero::after {
	content: '';
	position: absolute;
	inset: 0;
	background: linear-gradient(90deg, rgba(4,1,10,0.92) 10%, rgba(4,1,10,0.6) 55%, rgba(4,1,10,0.25) 100%);
}

.hero__inner {
	position: relative;
	z-index: 1;
	display: flex;
	flex-direction: column;
	/* H1 to the top edge, intro to the bottom — the comp's 181px between them
	   is whatever is left over, which is what keeps it right for an H1 of any
	   length. The gap is the floor for a short viewport. */
	justify-content: space-between;
	gap: 28px;
}

/* A title bar for the text-only pages: no photograph, nothing under the H1, so
   the full 627px band would be most of a screen of empty dark (2026-09-18). */
.hero--compact {
	min-height: 0;
	padding-block: clamp(40px, 5vw, 72px);
}
.hero--compact .hero__inner { justify-content: center; }

/* The Location canvas has no intro line and centres the H1 in the band
   (y=325, height 190, in a 626px hero: 219 above, 217 below). */
.hero--bare .hero__inner { justify-content: center; }

/* Our Approach (#435:2722 / #435:2721): 66px above the H1, 112px below the
   copy, and the two 130px apart — a different rhythm from the other heroes. */
.hero--body { padding-block: clamp(40px, 4vw, 66px) clamp(56px, 6vw, 112px); }
.hero--body .hero__inner {
	justify-content: flex-start;
	gap: clamp(48px, 8vw, 130px);
}

/* 864px in the comp, not a ch-based guess — a character measure drifts with
   the typeface and landed 157px short of the drawn box. */
.hero h1 {
	color: var(--color-white);
	max-width: 864px;
	line-height: 1.32;     /* 95px on 72px in the comp, not the global 1.2 */
}

.hero__intro {
	margin-top: 0;
	max-width: 864px;
	font-size: var(--step-lead);
	line-height: 1.5;
}

/* ==========================================================================
   Strap line
   ========================================================================== */

/* The strap line's own section carries only 60px underneath it, and the slider
   that follows carries none on top. Both sections holding the default 100 put
   200px between the strap line and the first card where the comp has 60 — on
   the practice-area canvas (text ends 1662, row starts 1722) and on the
   location one (1470 -> 1530) alike. This is the single biggest spacing error
   on the page after the hero. */
.strapline-section { padding-block-end: 60px; }
.strapline-section + .slider-section.case-studies { padding-block-start: 0; }

.strapline {
	text-align: center;
	font-family: var(--font-display);
	font-weight: 300;
	font-size: var(--step-h2);
	line-height: 1.2;
	color: var(--color-charcoal-1);
	max-width: 970px;      /* the node's own width */
	margin-inline: auto;
}

/* ==========================================================================
   Two-column copy block (heading left, paragraph right on desktop)
   ========================================================================== */

.copy-block__grid {
	display: grid;
	gap: 32px;
}

/* 50px in the comp, not the 55px used for the centred section headings — one
   size had been applied to both. */
.copy-block__heading,
.split-block h2 { font-size: var(--step-h2-block); }

.copy-block__body { font-size: var(--step-body); }
.copy-block__body p { margin-bottom: 1.5em; }

@media (min-width: 1024px) {
	.copy-block__grid {
		/* Equal columns: the node is a row of two fill-width text frames, not a
		   1:1.15 split.

		   TOP-ALIGNED at the client's request, 2026-09-08. The node says
		   align-items:center and that is what shipped, but with a three-line
		   heading beside twenty lines of body copy the heading floated in the
		   middle of the band with nothing to relate it to. Do not "restore"
		   the centring from the file. */
		grid-template-columns: repeat(2, minmax(0, 1fr));
		gap: clamp(48px, 6.8vw, 130px);   /* reaches the node's 130px at 1920 */
		align-items: start;
	}

	/* Tops of two boxes are not two first lines. Literata 50px and Figtree 18px
	   carry different half-leading, so aligning the boxes leaves the heading's
	   first baseline noticeably below the body's. This pulls the heading up by
	   the difference, computed rather than nudged: half of (its own line box
	   minus its cap height) against the same for the body. */
	.copy-block__heading { margin-block-start: -0.12em; }
}

/* ==========================================================================
   Typical roles

   Derived, not chosen — `figma_spec.py "Practice Area" --css 206:8640` plus the
   EL- templates behind the rows:

     section   column, gap 60px, padding 100px 375px, background #F8F7F3
     heading   Literata 300 55px #221B2E, centred
     columns   row, gap 130px; each column 520px wide, column, gap 30px
     row       row, padding-left 10px, align center, gap 10px,
               1px #EEE9DE rule top AND bottom  (strokeWeight "1px 0px")
     label     row, padding 12px 0 12px 20px, 1px #EEE9DE rule on the LEFT
               (strokeWeight "0px 0px 0px 1px")
     icon      30x30

   The first pass had a hand-drawn 12x7 tick, a single bottom border and 16px
   gaps. None of those numbers came from the file.
   ========================================================================== */

.roles__heading {
	text-align: center;
	margin-bottom: 0;
}

.roles .container {
	display: flex;
	flex-direction: column;
	gap: 60px;
}

.roles__list {
	display: grid;
	gap: 30px;
	margin: 0;
	padding: 0;
	list-style: none;
}

@media (min-width: 1024px) {
	.roles__list {
		grid-template-columns: repeat(2, minmax(0, 520px));
		gap: 30px clamp(48px, 7vw, 130px);
		justify-content: center;
	}
}

.roles__item {
	display: flex;
	align-items: center;
	gap: 10px;
	padding-left: 10px;
	border-top: 1px solid var(--color-paper-3);
	border-bottom: 1px solid var(--color-paper-3);
	color: var(--color-charcoal-2);
	font-size: var(--step-body);
	line-height: 1.3;
}

/* The 30x30 tick. Drawn rather than shipped as an asset so it inherits colour
   and cannot 404. */
.roles__item::before {
	content: '';
	flex: 0 0 auto;
	width: 30px;
	height: 30px;
	background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 30 30'%3E%3Cpath fill='none' stroke='%23C8B27A' stroke-width='2' stroke-linecap='round' stroke-linejoin='round' d='M7 15.5l5 5 11-11'/%3E%3C/svg%3E");
	background-repeat: no-repeat;
	background-position: center;
}

.roles__label {
	flex: 1;
	padding: 12px 0 12px 20px;
	border-left: 1px solid var(--color-paper-3);
}

/* ==========================================================================
   Sliders

   Two of these on a practice area page: case studies and consultants. The comp
   draws both as rows that start inside the left gutter and run off the right
   edge — the crop is the affordance that says "this scrolls".

   The track is a native horizontal scroller HERE, in the stylesheet, so the row
   works and every card is reachable before JavaScript loads or if it fails. The
   moment Embla takes over it removes that scrolling, because a container Embla
   transforms must not also be scrolled by the browser: two authorities on one
   position is what made the old hand-rolled slider jitter under a thumb.
   ========================================================================== */

.slider-section { overflow: hidden; }

/* Embla's viewport. It clips; the track inside it is what moves.

   `touch-action: pan-y` hands the browser every vertical gesture and keeps the
   horizontal ones for Embla. Without it a finger that starts sideways can be
   claimed by the page instead of the row, and — worse on a phone — a finger
   that starts vertically can be swallowed by the row, so the page will not
   scroll while the thumb happens to be over a slider. */
.slider.is-embla { overflow: hidden; touch-action: pan-y; }

/* The resting crop. The comp draws the case-study row at x=-276 in a 1920
   frame: the first card is part-cropped off the left edge, and that crop is the
   affordance that says the row scrolls.

   A margin, not a scroll offset and not a transform. Embla keeps its position
   in its own engine, so a transform written behind its back is discarded the
   moment anything moves the row. A margin is layout — Embla's transform
   composes on top of it and neither has to know about the other.

   Desktop only. The comp is a single 1920 frame and mobile is ours to decide:
   at 390 the crop cuts the first card mid-word, so you land on "...and Brown"
   and have to scroll BACKWARDS to read the first case study. The card peeking
   in from the right already says the row scrolls. */
@media (min-width: 1024px) {
	.slider.is-embla[data-slider-rest] .slider__track { margin-left: -280px; }
}

/* A row too short to loop at this width. Embla quietly turns looping off, and
   the crop would then hold the first card off the left edge for good, so it
   goes, and the row runs from its first card to its last (main.js). If it all
   fits, it sits centred and does not pretend to scroll. */
.slider.is-embla.is-bounded[data-slider-rest] .slider__track { margin-left: 0; }
.slider.is-bounded.is-static .slider__track { justify-content: center; }
.slider.is-static.is-scrollable .slider__track { cursor: default; }

.slider__track {
	display: flex;
	gap: 24px;
	margin: 0;
	padding: 0 var(--gutter);
	list-style: none;
	overflow-x: auto;
	overscroll-behavior-x: contain;
	/* Snapping is off — see the note below. */
	/* And this is what makes snap respect that padding rather than treat the
	   content edge as the snap edge. Without it the two fight each other. */
	scroll-padding-inline: var(--gutter);
	scrollbar-width: none;          /* the progress bar is the indicator */
}
.slider__track::-webkit-scrollbar { display: none; }

.slider__item {
	flex: 0 0 auto;
	display: flex;
}

/* NO SCROLL SNAPPING on any of these rows, and it is not an oversight.
   Snapping fights everything else these sliders do, twice over:

   - It undid the resting crop. `mandatory` force-scrolled the track past its
     own inline padding on load; downgraded to `proximity` it then judged the
     clamped second snap point nearer than the first on a three-card row and
     threw the track to its end about a second after paint — so it looked
     right, then broke.
   - It cancels programmatic movement outright. A snapping row refuses a
     scrollLeft that is not a snap point: 12.6px set on the team row came
     straight back as 0, which killed the arrow keys, Home/End and the
     scrubber on every row that still had it.

   The physics model in main.js decelerates to a rest of its own, which is the
   job snapping was there to do. */
.slider__track { scroll-snap-type: none; }

@media (min-width: 768px) {
	.slider__track { gap: 46px; }
}

/* Centre the track on the container while still bleeding off both edges. */
/* The tracks do NOT align to the 1170 container — that was an assumption, and
   it is what squeezed the sliders down to two and a half cards.

   The comp's rows sit at x=4 (team, five 371px cards across 1920) and x=-276
   (case studies, mid-scroll with the first card cropped). Both run essentially
   edge to edge, so the inset here is ~4px at the design width and centres a
   1912px band on anything wider.

   The case-study row's negative x is the comp drawn part-way through a scroll.
   We start at the first card instead: parking a half-card on screen at rest is
   poor behaviour, and the crop on the right already signals that it scrolls.
   100% is the track's own width; 100vw would include the scrollbar. */
@media (min-width: 1280px) {
	.slider__track {
		padding-inline: max(4px, calc((100% - 1912px) / 2));
		scroll-padding-inline: max(4px, calc((100% - 1912px) / 2));
	}
	.slider--consultants .slider__track { gap: 29px; }
}

/* ---- Progress bar — 1170x22 with a 250x4 gold thumb in the comp ---------- */

.slider-progress {
	margin-top: 40px;
	height: 22px;
	display: flex;
	align-items: center;
}

.slider-progress__track {
	position: relative;
	flex: 1;
	height: 4px;
	border-radius: 50px;
	background: rgba(29, 29, 27, 0.12);
}

.slider-progress__thumb {
	position: absolute;
	top: 0;
	left: 0;
	height: 100%;
	width: 21.5%;                   /* 250 of 1165, the comp's resting state */
	border-radius: 50px;
	background: var(--color-gold);
	transition: transform 0.12s linear, width 0.12s linear;
}

/* ---- Plain text pages (privacy policy, cookie policy) -------------------
   One measured column, held to the width the case-study card uses so the line
   length matches the rest of the site rather than running the full container. */
.page-prose {
	max-width: 770px;
	margin-inline: auto;
	color: var(--color-charcoal-2);
}
.page-prose > *:first-child { margin-top: 0; }
.page-prose h2 {
	font-size: var(--step-h2-block);
	color: var(--color-charcoal-1);
	margin: 48px 0 16px;
}
.page-prose h3 {
	font-size: var(--step-h3);
	color: var(--color-charcoal-1);
	margin: 32px 0 12px;
}
.page-prose p,
.page-prose li { margin: 0 0 16px; }
.page-prose ul,
.page-prose ol { margin: 0 0 24px; padding-left: 24px; }
.page-prose a { color: var(--color-purple); }
.page-prose a:hover { text-decoration: none; }
.page-prose strong { color: var(--color-charcoal-1); }

/* ---- Case study card ---------------------------------------------------
   Values below are the node's own, via `figma_spec.py "Practice Area" --css
   206:8704` — not read off a screenshot. The card is a COLUMN with
   align-items:flex-end, so the logo sits on its own row pushed right and the
   text block follows underneath; building it as a logo-beside-name row was an
   invention. The client name is Literata 400 30px, not a bold sans.
   ---------------------------------------------------------------------- */

.case-card {
	display: flex;
	flex-direction: column;
	align-items: flex-end;
	gap: 10px;
	width: min(770px, 84vw);
	padding: clamp(28px, 4vw, 60px);
	background: var(--color-deep-teal);
	border-radius: 20px;
	color: var(--color-white);
}

/* Every client mark sits on a light plate, in its own colours.
   ---------------------------------------------------------------------------
   This replaces `filter: brightness(0) invert(1)`, which flattened each logo to
   black and then inverted it to a solid white silhouette. That is faithful for
   exactly one kind of mark — neutral dark ink on transparency — and destructive
   for the rest. Bureau Veritas is the clearest failure: its badge is a white
   knockout inside a coloured frame, so flattening filled the knockout in and
   the mark became a featureless white blob.

   The alternative of leaving every logo on the teal does not work either.
   `scripts/classify_logos.py` measures each of the 53 against the card colour
   and against white with the WCAG contrast formula: only a handful clear a
   legibility bar on #07232F, so any threshold splits the set into some marks
   floating on the teal and some on plates, and a row mixing the two reads worse
   than either. The plate is the one treatment that is right for all 53, and it
   is the ground these logos were drawn for.

   Re-run that script after changing any logo URL. Its `weak_on_plate` list is
   the marks whose ink is light enough to sit poorly on white; those need
   recolouring at source and self-hosting, exactly as Moog, Ultra Electronics
   and Flagstone did in the 2026-08 audit. */
.case-card__logo {
	display: flex;
	align-items: center;
	justify-content: flex-end;
}

.case-card__logo img {
	/* The plate is a fixed slot so every card's mark lines up with the next
	   one's, whatever the logo's own proportions. Height alone is not enough of
	   a constraint: a wide wordmark then runs to 300px and dwarfs the card's
	   30px heading, which is what Currie & Brown was doing. The comp sizes each
	   client's mark individually — 87x60 for Currie & Brown on the practice-area
	   card, 70x70 for Coats on the location one — so there is no single slot to
	   copy; 120 keeps a wordmark legible without exceeding the widest the comp
	   draws by much. */
	display: block;
	width: 100%;
	height: 100%;
	object-fit: contain;
	object-position: center;
	background: var(--color-white);
	border-radius: 12px;
	padding: 12px 16px;
	max-width: 168px;
	min-height: 72px;
}

.case-card__text {
	display: flex;
	flex-direction: column;
	gap: 30px;
	align-self: stretch;
}

.case-card__title {
	margin: 0;
	font-family: var(--font-display);
	font-weight: 400;
	font-size: clamp(1.375rem, 1.1rem + 1.2vw, 1.875rem);   /* 22 -> 30 */
	letter-spacing: 0;
	color: var(--color-gold);
}

.case-card__body {
	font-size: var(--step-body);
	line-height: 1.667;
	color: var(--color-grey-light);
}

/* Practice-area chips — Location cards only.
   `--css 308:1467` → EL-2a7abb0d: row, padding 12px 16px, transparent fill,
   2px #C8B27A border, radius 50px; label Figtree 700 14px, uppercase,
   0.1em tracking, white. 10px between chips; the chip row is a child of the
   text column so it inherits that column's 30px. The card's outer gap on this
   canvas is 40px (logo to text), not the practice-area card's 10px. */
.case-card--tagged { gap: 40px; }

.case-card__tags {
	display: flex;
	flex-wrap: wrap;
	gap: 10px;
	margin: 0;
	padding: 0;
	list-style: none;
}

/* The padding sits on the LINK, not the list item: with it on the item the
   anchor was only its own 17px of text, well under the 44px touch minimum,
   while the pill around it looked like the target. */
.case-card__tag {
	border: 2px solid var(--color-gold);
	border-radius: 50px;
	font-size: 0.875rem;
	font-weight: 700;
	line-height: 1;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	color: var(--color-white);
}

.case-card__tag > a,
.case-card__tag > span {
	display: block;
	padding: 15px 16px;   /* 15+14+15 = 44, the touch minimum */
}

/* ---- Consultant card ---------------------------------------------------
   Derived via `figma_spec.py "Practice Area" --css 415:1291` and the EL-
   templates behind it:

     card      column, gap 20px, padding 20px, #F8F7F3, radius 20px, 371 wide
     photo     radius 20px
     row       row, gap 20px, justify-content flex-end, align-items flex-end
     identity  column, gap 2px; name #662483, title #2A2233
     linkedin  50x50, padding 13px, TRANSPARENT fill, 2px #C8B27A border,
               radius 33.2px, icon 21x22
     tenure    row, padding 0 15px, #FFFFFF, radius 30px, text #662483

   Two values here were previously set from a low-resolution screenshot and
   were wrong: the tenure text is purple, not gold, and the LinkedIn button is
   an outlined gold circle, not a filled white one.
   ---------------------------------------------------------------------- */

/* 60px to the row below, not 48 — the comp's team heading ends at 4144 and
   the row starts at 4204. */
.consultants__heading { text-align: center; margin-bottom: 60px; }

/* 83px above the heading in the comp — the split block ends at 3995 and the
   heading starts at 4078. That 83 is the WHOLE gap between the two sections,
   so this side pays only the part the section above does not: 83 minus
   --section-y. Setting the full 83 here made the pair 133. */
/* The comp puts 83px of white between the split block and "Meet the Oryx
   Team". A location page gets there on its own: the section above is white, so
   its own 50px of bottom padding is part of that gap. On a practice-area page
   the section above is the DEEP TEAL split band, so those 50px are dark and
   invisible, and only this padding shows — 33px, a third of what it should be
   (2026-09-18). The sibling rule pays the difference in the dark case only. */
.consultants { padding-block-start: clamp(20px, 1.72vw, 33px); }
.split-block + .consultants { padding-block-start: clamp(40px, 4.32vw, 83px); }

.person-card {
	display: flex;
	flex-direction: column;
	gap: 20px;
	width: min(371px, 78vw);
	padding: 20px;
	background: var(--color-paper-1);
	border-radius: 20px;
}

.person-card__media { border-radius: 20px; overflow: hidden; }
.person-card__media img {
	display: block;
	width: 100%;
	aspect-ratio: 331 / 300;
	object-fit: cover;
	object-position: center top;
}
/* A card with no headshot drops the frame entirely rather than showing an
   empty grey box, which reads as a broken image. It keeps the card's own
   height so a slider row stays level. */
.person-card--no-photo { justify-content: flex-end; }

.person-card__row {
	display: flex;
	align-items: flex-end;
	justify-content: space-between;
	gap: 20px;
}

.person-card__identity {
	display: flex;
	flex-direction: column;
	gap: 2px;
	flex: 1;
}

.person-card__name {
	margin: 0;
	font-weight: 600;
	color: var(--color-purple);
}
.person-card__title {
	margin: 0;
	font-size: 0.9375rem;
	color: var(--color-charcoal-2);
}

.person-card__linkedin {
	position: relative;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	flex: 0 0 auto;
	width: 50px;
	height: 50px;
	padding: 13px;
	background: transparent;
	border: 2px solid var(--color-gold);
	border-radius: 50%;
	color: var(--color-purple);
}
.person-card__linkedin:hover {
	background: var(--color-gold);
	color: var(--color-white);
}
.person-card__linkedin svg { width: 21px; height: 22px; }

.person-card__tenure {
	align-self: flex-start;
	margin: 0;
	padding: 0 15px;
	line-height: 2.2;      /* height comes from line-height, per the node's 0 vertical padding */
	background: var(--color-white);
	border-radius: 30px;
	/* 12px was below the readable minimum on a phone; 0.1em of tracking on
	   uppercase makes it read smaller still. */
	font-size: 0.875rem;
	font-weight: 600;
	letter-spacing: 0.08em;
	text-transform: uppercase;
	color: var(--color-purple);
}

/* ==========================================================================
   Media block — the Location page's first body section

   `figma_spec.py "Location" --css 280:15`: column, gap 60px,
   padding 100px 375px, no background; a 569x390 photograph beside a copy
   column with 30px between its parts. The Location canvas has no purple
   section and no deep-teal split — reusing the Practice Area parts here is
   what made the page wrong.
   ========================================================================== */

.media-block__inner {
	display: grid;
	gap: 40px;
	/* Top-aligned, not centred: layout_33d4e75c sets no alignItems, and the
	   comp runs the copy well past the bottom of the photograph. */
	align-items: start;
}

/* Square corners: EL-19a01ca0 declares no borderRadius, and the comp draws
   none. The case cards and consultant cards are the rounded things here. */
.media-block__media img {
	display: block;
	width: 100%;
	max-width: 569px;
	aspect-ratio: 569 / 390;
	object-fit: cover;
}

.media-block__copy { display: grid; gap: 30px; }
.media-block__heading { font-size: var(--step-h2-block); }
.media-block__body { color: var(--color-charcoal-2); }

@media (min-width: 1024px) {
	.media-block__inner {
		grid-template-columns: 569px minmax(0, 1fr);
		/* 135px, from layout_33d4e75c on the row — the 60px that was here is
		   the SECTION's column gap, a different number one level up. */
		gap: clamp(48px, 7vw, 135px);
	}
}

/* Location's second body block: heading left in a 571px column, copy right,
   133px apart — `--css 276:427`. Wider gap and a bigger heading than the
   Practice Area's two-column block. */
.copy-block--wide .copy-block__heading { font-size: var(--step-h2); }

@media (min-width: 1024px) {
	.copy-block--wide .copy-block__grid {
		grid-template-columns: 571px minmax(0, 1fr);
		gap: clamp(48px, 7vw, 133px);
		align-items: start;
	}
}

/* ==========================================================================
   Split block — copy beside a portrait photograph, on deep teal
   ========================================================================== */

.split-block {
	background: var(--color-deep-teal);
	color: var(--color-white);
}
.split-block h2 { color: var(--color-white); }

.split-block__inner {
	display: grid;
	gap: 40px;
	align-items: center;
}

.split-block__media img {
	display: block;
	width: 100%;
	max-width: 520px;
	aspect-ratio: 520 / 750;
	object-fit: cover;
	border-radius: 20px;
}

.split-block__copy { display: grid; gap: 30px; }

.split-block__body { color: rgba(255, 255, 255, 0.86); }

@media (min-width: 1024px) {
	.split-block__inner {
		grid-template-columns: 520fr 520fr;
		gap: clamp(48px, 7vw, 130px);
	}
	.split-block--flip .split-block__media { order: 2; }
}

/* ==========================================================================
   CTA band — 1920x496, photograph under a dark gradient
   ========================================================================== */

.cta-band {
	position: relative;
	display: flex;
	align-items: center;
	min-height: 496px;
	background: var(--color-charcoal-1);
	color: var(--color-white);
	overflow: hidden;
}

.cta-band__media {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

.cta-band::after {
	content: '';
	position: absolute;
	inset: 0;
	/* Dark enough on the left for the white heading to hold contrast, light
	   enough on the right that the photograph actually reads. At 0.95 the
	   overlay swamped the image entirely and the band looked like flat colour. */
	background: linear-gradient(90deg, rgba(4,1,10,0.86) 0%, rgba(4,1,10,0.55) 45%, rgba(4,1,10,0.12) 100%);
}

.cta-band__inner {
	position: relative;
	z-index: 1;
	display: flex;
	flex-direction: column;
	align-items: flex-start;
	gap: 50px;
	padding-block: var(--band-y);
}

.cta-band__heading {
	margin: 0;
	max-width: 18ch;
	color: var(--color-white);
}

/* No type override here: .button now carries the node's own 16px / 0.1em /
   uppercase, and this block was quietly shrinking one button out of five. */

/* ==========================================================================
   Footer — a white 600px band in the comp, not a dark bar
   ========================================================================== */

.site-footer {
	background: var(--color-white);
	color: var(--color-ink);
	padding-block: clamp(48px, 4vw, 70px);
	border-top: 1px solid var(--color-paper-2);
}

.site-footer__inner {
	display: grid;
	gap: 48px;
}

@media (min-width: 1024px) {
	/* The comp's 158px between the brand block and the columns assumes THREE
	   columns; the Q&A added a fourth (Locations), and holding 158 left the
	   contact column 0px wide with its heading stacked one word per line.
	   The gap gives way before the columns do. */
	/* 32px narrower than it was, so the phone number's handset icon and its
	   slightly larger type are paid for out of the space between the brand
	   block and the Menu column rather than out of the columns themselves:
	   measured, the contact column grew 32px in all. The old gap was
	   clamp(48px, 5vw, 96px); `5vw - 32px` takes exactly that at every screen
	   size. The brand block's 300px track is wider than the logo and copyright
	   it holds, so the white space a reader sees before Menu is still 80px+. */
	.site-footer__inner {
		grid-template-columns: minmax(0, 300px) minmax(0, 1fr);
		gap: 48px clamp(19px, calc(5vw - 32px), 64px);
	}
}

.site-footer__logo { display: block; color: var(--color-ink); }
.site-footer__logo svg { width: auto; height: 88px; max-width: 239px; }

.site-footer__blurb {
	margin: 24px 0 0;
	max-width: 34ch;
	color: var(--color-grey);
}

.site-footer__cols {
	display: grid;
	gap: 40px;
}

@media (min-width: 600px) {
	.site-footer__cols { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}
/* 1200, not 1024. Not four equal quarters either: the node's columns are sized
   to their content — 88 for the short menu, 309 for the practice-area list —
   and equal quarters squeezed both the "Practice areas" and "Get in touch"
   headings onto two lines and broke the phone number in half. Locations is our
   own column (the Q&A moved it to the footer).

   At exactly 1024 there is not enough width for four: the container is 944,
   the brand block takes 300, and what is left clipped the "Practice areas"
   heading inside its own 73px box. Two columns from 600 to 1199, four above. */
@media (min-width: 1200px) {
	.site-footer__cols {
		grid-template-columns:
			max-content              /* Menu — 88 in the comp */
			minmax(0, 1fr)           /* Practice areas — 309 in the comp, the
			                            one column that can afford to wrap */
			max-content              /* Locations */
			max-content;             /* Get in touch */
		gap: clamp(28px, 2.6vw, 48px);
	}
}

.site-footer__heading {
	font-family: var(--font-body);
	line-height: 1.2;           /* it was an h3; keep the h3's line height */
	font-size: 0.9375rem;
	font-weight: 600;
	letter-spacing: 0.08em;
	text-transform: uppercase;
	color: var(--color-purple);
	margin: 0 0 21px;
}

.site-footer__menu {
	margin: 0;
	padding: 0;
	list-style: none;
	display: grid;
	gap: 21px;              /* the node's own */
}

.site-footer__menu a {
	text-decoration: none;
	color: var(--color-charcoal-1);
	display: inline-block;
	/* 19px of text alone is far under the 44px touch minimum, and the footer
	   carries about thirty links. Pad the tappable area on small screens and
	   pull the list gap in so the rhythm does not balloon; desktop keeps the
	   node's 21px spacing with no padding. */
	padding-block: 12px;
}
.site-footer__menu a:hover { text-decoration: underline; }

@media (max-width: 1199px) {
	.site-footer__menu { gap: 0; }
}

/* The padded target stays until the four-column desktop footer. 768 and 1024
   are tablet widths — touch devices — and the 28px link the old 768 cut-off
   produced there is well under the 44px minimum. */
@media (min-width: 1200px) {
	.site-footer__menu a { padding-block: 0; }
}

/* A UK number with spaces in it is one token to a reader and must not break
   across lines, whatever the column does. */
.site-footer__office { margin-bottom: 28px; }
.site-footer__office:last-of-type { margin-bottom: 21px; }
.site-footer__office .site-footer__heading { margin-bottom: 12px; }

.site-footer__copyright {
	margin: 24px 0 0;
	/* #9D9D9C on white is 2.7:1, under the 4.5:1 small text needs. */
	color: #6F6F6E;
	font-size: 0.9375rem;
}

.site-footer__value { margin: 0 0 12px; }

/* The handset sits on the number's left, inside the link, and never shrinks —
   a flex item with a long number beside it would otherwise be squashed. */
/* A touch larger than the address above it: the number is the one thing in
   this column a visitor acts on. */
.site-footer__value--phone { font-size: 1.1em; }
.site-footer__value--phone a {
	white-space: nowrap;
	display: inline-flex;
	align-items: center;
	gap: 8px;
}
/* Centred on the NUMBER, not on the line box. Digits have no descenders, so
   their ink sits low in the line, and `align-items: center` alone left the
   handset 3.6px high. The nudge is in em so it holds as the footer's type
   scales, plus 0.6px: measured off 4x screenshots of the rendered link, the
   number sits 3.7px low at desktop type and 4.3px at mobile, and this lands
   both within half a pixel. */
.site-footer__phone-icon {
	flex: none;
	width: 22px;
	height: 22px;
	transform: translateY(calc(0.2em + 0.6px));
}
.site-footer__value a {
	color: var(--color-charcoal-1);
	display: inline-block;
	padding-block: 12px;    /* 44px touch target on mobile */
}

@media (min-width: 768px) {
	.site-footer__value { margin-bottom: 21px; }
}

/* The padded tap target stays until the desktop footer at 1200. 768 and 1024
   are tablet widths, and the phone number was a 28px target there. */
@media (min-width: 1200px) {
	.site-footer__value a { padding-block: 0; }
}

/* The shape of LinkedIn's own mark — a rounded square, not a disc — outlined
   in purple. LinkedIn's icon rounds its corners at about 22% of the side. */
.site-footer__linkedin {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 66px;
	height: 66px;
	border: 2px solid var(--color-purple);
	border-radius: 22%;
	background: var(--color-paper-1);
	color: var(--color-purple);
}
.site-footer__linkedin:hover { background: var(--color-purple); color: var(--color-white); }
/* The glyph fills a little more of the tile than the 21px it had, closer to
   LinkedIn's own proportions. */
.site-footer__linkedin svg { width: 26px; height: 27px; }

/* ==========================================================================
   Reduced motion
   ========================================================================== */

@media (prefers-reduced-motion: reduce) {
	*, *::before, *::after {
		animation-duration: 0.01ms !important;
		animation-iteration-count: 1 !important;
		transition-duration: 0.01ms !important;
		scroll-behavior: auto !important;
	}
}

/* ==========================================================================
   HOME PAGE
   ========================================================================== */

/* ---- Overlaid header ----------------------------------------------------
   #159:96 — the same header frame, but laid over the hero photograph with
   white type and 30px of vertical padding rather than 20px. #159:95 is a
   1920x306 top-down scrim behind it, which is what keeps the nav legible over
   a bright sky; it is drawn by .home-hero::before.
   ---------------------------------------------------------------------- */
.site-header--overlay {
	position: absolute;
	inset-inline: 0;
	padding-block: 30px;
	color: var(--color-white);
}

/* ---- Hero ---------------------------------------------------------------
   #159:94: 1920x856 photograph, two 35–40% #221B2E washes and a purple
   bottom bleed over it. Copy at y=387 in a 912 column: H1 + intro 30px
   apart, then 40px to the button.
   ---------------------------------------------------------------------- */
.home-hero {
	position: relative;
	display: flex;
	align-items: center;
	min-height: min(88vh, 856px);
	padding-block: clamp(140px, 16vw, 200px) clamp(56px, 6vw, 100px);
	background: var(--color-charcoal-1);
	color: var(--color-white);
	overflow: hidden;
}

.home-hero__media {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

/* The two flat washes from the node, plus its purple bottom bleed. */
.home-hero::after {
	content: '';
	position: absolute;
	inset: 0;
	background:
		linear-gradient(180deg, rgba(15, 15, 15, 0) 62%, rgba(102, 36, 131, 0.3) 100%),
		rgba(34, 27, 46, 0.4),
		rgba(34, 27, 46, 0.35);
}

/* The scrim the header sits on (#159:95, 1920x306). */
.home-hero::before {
	content: '';
	position: absolute;
	inset: 0 0 auto;
	height: 306px;
	z-index: 2;
	background: linear-gradient(180deg, rgba(39, 31, 55, 0.56) 19%, rgba(39, 31, 55, 0.31) 60%, rgba(39, 31, 55, 0) 100%);
	pointer-events: none;
}

.home-hero__inner {
	position: relative;
	z-index: 1;
	max-width: calc(912px + var(--gutter) * 2);
	margin-inline: 0 auto;
}

.home-hero__title {
	max-width: 828px;
	color: var(--color-white);
	line-height: 1.32;         /* 95px on 72px, as on the interior heroes */
}

.home-hero__intro {
	margin: 30px 0 0;
	max-width: 828px;
	font-size: var(--step-lead);
	line-height: 1.5;
}

.home-hero__button { margin-top: 40px; }

@media (min-width: 1280px) {
	/* Centre the 912 column on the same 1170 container the rest of the page
	   uses, rather than letting it drift with the viewport. */
	.home-hero__inner {
		max-width: calc(var(--content-max) + var(--gutter) * 2);
		margin-inline: auto;
	}
}

/* The interior logo is purple on white; over the hero it is white, and the
   inlined SVG follows currentColor. */
.site-header--overlay .site-header__logo,
.site-header--overlay .site-header__menu a { color: var(--color-white); }

/* ---- Logo wall ----------------------------------------------------------
   #159:138: 100px section, centred, 70px under the heading; three rows 69px
   apart of 101x47 logo slots inside 50px side padding. Built as three
   marquees per the Q&A, not the comp's static grid.
   ---------------------------------------------------------------------- */
.logo-wall__heading {
	font-size: var(--step-h2);
	text-align: center;
	margin-bottom: 70px;
}

.logo-wall__rows {
	display: grid;
	gap: 40px;
	padding-inline: 0;
}

.logo-wall__row {
	overflow: hidden;
	/* Fade the logos out at both edges so a mark is never half-cut against a
	   hard boundary — the comp's grid has no edge, and a moving row does. */
	-webkit-mask-image: linear-gradient(90deg, transparent, #000 6%, #000 94%, transparent);
	mask-image: linear-gradient(90deg, transparent, #000 6%, #000 94%, transparent);
}

.logo-wall__track {
	display: flex;
	align-items: center;
	gap: 60px;
	width: max-content;
	margin: 0;
	padding: 0;
	list-style: none;
	animation: oryx-marquee var(--marquee-duration, 40s) linear infinite;
}

/* The list is rendered twice, so translating by exactly half the track's width
   lands the copy where the original started — the loop has no seam and needs
   no JavaScript to measure anything. */
@keyframes oryx-marquee {
	from { transform: translate3d(0, 0, 0); }
	to   { transform: translate3d(-50%, 0, 0); }
}

.logo-wall__row--reverse .logo-wall__track { animation-direction: reverse; }

.logo-wall__row:hover .logo-wall__track,
.logo-wall__row:focus-within .logo-wall__track { animation-play-state: paused; }

@media (max-width: 767px) {
	/* 60px between 101px logos shows barely two per screen and reads as an
	   empty band. */
	.logo-wall__track { gap: 28px; }
	.logo-wall__row {
		-webkit-mask-image: linear-gradient(90deg, transparent, #000 3%, #000 97%, transparent);
		mask-image: linear-gradient(90deg, transparent, #000 3%, #000 97%, transparent);
	}
}

.logo-wall__item {
	flex: 0 0 auto;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 101px;
	height: 48px;
}

.logo-wall__item img {
	max-width: 100%;
	max-height: 100%;
	width: auto;
	object-fit: contain;
}

.logo-wall__actions {
	display: flex;
	justify-content: center;
	margin-top: 70px;
}

@media (prefers-reduced-motion: reduce) {
	/* Stop it dead and let the row scroll by hand instead — a paused marquee
	   that cannot be reached is worse than no marquee. */
	.logo-wall__track { animation: none; }
	.logo-wall__row { overflow-x: auto; scrollbar-width: none; }
	.logo-wall__row::-webkit-scrollbar { display: none; }
}

/* ---- Home intro block ---------------------------------------------------
   #159:188: padding 100px 374px, row space-between; heading in a 571 column
   (Literata 300 55px), copy hugging at ~462 with 24px between paragraphs and
   28px to the button. The body here is 19px/32px, not the 18px used elsewhere.
   ---------------------------------------------------------------------- */
.copy-block--lead .copy-block__heading { font-size: var(--step-h2); }

.copy-block--lead .copy-block__body {
	font-size: clamp(1.0625rem, 1rem + 0.2vw, 1.1875rem);   /* 17 → 19 */
	line-height: 1.684;                                      /* 32 on 19 */
	color: var(--color-charcoal-2);
}

.copy-block--lead .copy-block__body p { margin-bottom: 24px; }
.copy-block__button { margin-top: 4px; }

@media (min-width: 1024px) {
	.copy-block--lead .copy-block__grid {
		grid-template-columns: 571px minmax(0, 462px);
		justify-content: space-between;
		gap: 40px;
		align-items: start;
	}
}

/* ---- Lense and Lumen alliance pill --------------------------------------
   #159:260: 1170 wide, row, padding 15px 24px, space-between, centre;
   #F9F8F4 on a 1px #F4F0E7 stroke, 25px radius. The mark is 80x80 and sits
   30px from a Literata 400 27px line.
   ---------------------------------------------------------------------- */
/* Measured off the comp render: the intro section's own 100px bottom padding
   is the whole gap above the pill, and there is a further 100px below it
   before the #07232F strip. */
.alliance { padding-block: 0 var(--section-y); }

.alliance__pill {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: space-between;
	gap: 20px;
	padding: 15px 24px;
	background: #F9F8F4;
	border: 1px solid var(--color-paper-2);
	border-radius: 25px;
}

.alliance__identity {
	display: flex;
	align-items: center;
	gap: 30px;
	min-width: 0;
}

.alliance__mark {
	flex: 0 0 auto;
	display: block;
	width: 80px;
	height: 80px;
	color: var(--color-charcoal-1);
}
.alliance__mark svg { display: block; width: 100%; height: 100%; }

.alliance__text {
	margin: 0;
	font-family: var(--font-display);
	font-weight: 400;
	font-size: clamp(1.125rem, 0.95rem + 0.75vw, 1.6875rem);   /* 18 → 27 */
	line-height: 1.2;
	letter-spacing: 0.002em;
	color: var(--color-charcoal-2);
}

/* ---- Practice-area strip ------------------------------------------------
   #159:201: a 1920x764 #07232F band; the row is 42px-gapped, 470-tall cards
   with 30px padding, a 3px radius, a 28% dark wash and the label pinned to
   the bottom in Literata 400 28px on a 307px measure. The section heading is
   the SECOND item in that row, not a block above it.
   ---------------------------------------------------------------------- */
.practice-strip {
	background: var(--color-deep-teal);
	color: var(--color-white);
}

.practice-strip .slider__track { gap: 42px; align-items: center; }

.practice-strip__heading {
	width: 425px;
	max-width: 78vw;
	margin: 0;
	font-size: var(--step-h2);
	color: var(--color-white);
}

.slider__item--heading { align-items: center; }

/* Below desktop the in-row heading is unusable — one card fits, and the
   heading then runs off the right edge mid-word. The real one sits above the
   row instead; the in-row copy is decorative. */
.practice-strip__heading--above {
	width: auto;
	max-width: none;
	margin-bottom: 40px;
}

@media (min-width: 1024px) {
	/* Clipped rather than display:none, so the heading stays in the
	   accessibility tree and is still announced exactly once. */
	.practice-strip__heading--above {
		position: absolute;
		width: 1px; height: 1px;
		margin: -1px; padding: 0;
		overflow: hidden;
		clip-path: inset(50%);
		white-space: nowrap;
	}
}

@media (max-width: 1023px) {
	.slider__item--heading { display: none; }
}

.area-card {
	position: relative;
	display: flex;
	align-items: flex-end;
	justify-content: center;
	width: 367px;
	height: 470px;
	padding: 30px;
	border-radius: 3px;
	overflow: hidden;
	background: rgba(255, 255, 255, 0.06);
	color: var(--color-white);
	text-decoration: none;
}

.area-card__media {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

/* The node's flat 28% wash, plus a bottom-weighted one of our own: 28% alone
   does not hold a 28px serif over a bright sky, and the comp's four images all
   happen to be dark where the label sits. */
.area-card::after {
	content: '';
	position: absolute;
	inset: 0;
	background:
		linear-gradient(180deg, rgba(15, 13, 20, 0) 45%, rgba(15, 13, 20, 0.65) 100%),
		rgba(15, 13, 20, 0.28);
}

/* No photograph yet: a plain card in the band's own colour, one shade up, so
   it still reads as a deliberate tile rather than a broken image. */
.area-card--plain {
	background: rgba(255, 255, 255, 0.07);
	border: 1px solid rgba(200, 178, 122, 0.35);
}
.area-card--plain::after { background: none; }

.area-card__label {
	position: relative;
	z-index: 1;
	width: 307px;
	max-width: 100%;
	font-family: var(--font-display);
	font-weight: 400;
	font-size: clamp(1.375rem, 1.2rem + 0.6vw, 1.75rem);   /* 22 → 28 */
	line-height: 1.2;
}

.area-card:hover .area-card__media { transform: scale(1.04); }
.area-card__media { transition: transform 0.4s ease; }

@media (prefers-reduced-motion: reduce) {
	.area-card__media { transition: none; }
	.area-card:hover .area-card__media { transform: none; }
}

@media (max-width: 767px) {
	.area-card { width: 264px; height: 360px; padding: 20px; }
	/* 100%, not auto. With `auto` the label shrinks to its text and the card's
	   own `justify-content: center` then centres it — so a short label like
	   "Engineering" centred while a long one filled the width and read as
	   left-aligned. The comp's label fills the card's content box. */
	.area-card__label { width: 100%; }
	.practice-strip .slider__track { gap: 20px; }
}

/* Same reason on the index, where the card is the grid column's width. */
.index-grid .area-card__label { width: 100%; }

/* ==========================================================================
   CASE STUDIES ARCHIVE
   ========================================================================== */

/* ---- Filter -------------------------------------------------------------
   layout_b49eb252: 371 wide, 20px padding, white on a 1px #662483 stroke,
   20px radius; label Figtree 400 18px/36px with the chevron pushed right.
   ---------------------------------------------------------------------- */
.case-filter {
	display: flex;
	align-items: center;
	gap: 16px;
	margin-bottom: 72px;
}

.case-filter__control {
	position: relative;
	width: 371px;
	max-width: 100%;
}

.case-filter__select {
	width: 100%;
	padding: 20px 56px 20px 20px;
	font-family: inherit;
	font-size: 1.125rem;
	line-height: 2;                 /* 36px on 18px */
	color: var(--color-charcoal-1);
	background: var(--color-white);
	border: 1px solid var(--color-purple);
	border-radius: 20px;
	appearance: none;
	cursor: pointer;
}

.case-filter__chevron {
	position: absolute;
	top: 50%;
	right: 20px;
	transform: translateY(-50%);
	pointer-events: none;
	color: var(--color-charcoal-1);
}

/* The filter, and on a filtered view the link to that sector's practice
   page, share one row: the link sits at the far right, and on a phone it
   wraps under the select. The row now carries the gap the filter used to. */
.case-archive__bar {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: space-between;
	gap: 16px 32px;
	margin-bottom: 72px;
}
.case-archive__bar .case-filter { margin-bottom: 0; }

/* Inline, not flex: a long sector name wraps on a phone, and as a flex item
   the label would take the whole line and strand the arrow at the far edge.
   Inline, the arrow follows the last word. */
.case-archive__practice-link {
	display: inline-block;
	padding-block: 10px;
	line-height: 1.45;
	font-weight: 600;
	font-size: 1.0625rem;
	color: var(--color-purple);
	text-decoration: none;
}
.case-archive__practice-link:hover span { text-decoration: underline; }
.case-archive__practice-link .button__arrow { margin-left: 8px; vertical-align: -3px; }

/* Hidden once the select can navigate on its own; still there, and still
   focusable, for anyone without JavaScript. */
.case-filter--enhanced .case-filter__submit { display: none; }

/* A <select> that runs out of room CLIPS its option text — no ellipsis, no
   shrink — so "All Practice Areas" rendered as "All Practice Ar". On a phone
   the control and the Filter button cannot share a line; wrapping hands the
   select the full width, and the chevron gutter comes in to match. */
@media (max-width: 599px) {
	.case-filter { flex-wrap: wrap; }
	.case-filter__control { flex: 1 0 100%; width: auto; }
	.case-filter__select { padding: 16px 44px 16px 16px; }
	.case-filter__chevron { right: 16px; }
}

/* ---- Card grid ----------------------------------------------------------
   The comp's two columns are 574 and 576 inside the 1170 container, 30px
   apart, with 50px between rows.
   ---------------------------------------------------------------------- */
.case-archive__grid {
	display: grid;
	gap: 50px 30px;
}

.case-archive__column {
	display: grid;
	align-content: start;
	gap: 50px;
	/* A list of cards since 2026-10-08, so it is announced and indexed as
	   one; the reset keeps it looking exactly as the plain column did. */
	list-style: none;
	margin: 0;
	padding: 0;
}

.case-archive__item { min-width: 0; }

@media (min-width: 900px) {
	.case-archive__grid {
		grid-template-columns: repeat(2, minmax(0, 1fr));
		align-items: start;
	}
}

/* In the grid the card fills its column rather than taking the slider's
   fixed 770. */
.case-archive__grid .case-card { width: 100%; }

/* The same grid standing in for a one- or two-card slider on a practice-area
   or location page. A lone card keeps the slider's 770 and sits centred. */
@media (min-width: 900px) {
	.case-studies--single .case-archive__grid {
		grid-template-columns: minmax(0, 770px);
		justify-content: center;
	}
}

.case-archive__empty {
	font-size: var(--step-lead);
	color: var(--color-charcoal-2);
}

/* ---- Pagination ---------------------------------------------------------
   EL-38e45a5b: centred row, 60px between the number group and the edges,
   20px inside it. Numbers are 60x60 pills; the current one is filled purple,
   the rest are a 2px gold outline with purple type.
   ---------------------------------------------------------------------- */
.pagination {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: center;
	gap: 60px;
	margin-top: 80px;
}

.pagination__numbers {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 20px;
}

.pagination__numbers .page-numbers {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 60px;
	height: 60px;
	border: 2px solid var(--color-gold);
	border-radius: 50px;
	font-weight: 700;
	font-size: 1rem;
	letter-spacing: 0.1em;
	color: var(--color-purple);
	text-decoration: none;
}

.pagination__numbers .page-numbers.current {
	background: var(--color-purple);
	border-color: var(--color-purple);
	color: var(--color-white);
}

.pagination__numbers a.page-numbers:hover {
	background: var(--color-purple);
	border-color: var(--color-purple);
	color: var(--color-white);
}

/* The dots paginate_links() inserts for a skipped range are not a button. */
.pagination__numbers .page-numbers.dots {
	width: auto;
	border: 0;
	color: var(--color-grey);
}

.pagination__edge .page-numbers {
	display: inline-flex;
	align-items: center;
	gap: 10px;
	padding: 14px 36px;
	background: var(--color-purple);
	border-radius: 50px;
	color: var(--color-white);
	font-weight: 700;
	font-size: 1rem;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	text-decoration: none;
}

.pagination__edge .page-numbers:hover { background: var(--color-purple-alt); }

@media (max-width: 599px) {
	.pagination { gap: 28px; }
	.pagination__numbers { gap: 12px; }
	.pagination__numbers .page-numbers { width: 48px; height: 48px; }
}

/* ---- Single case study --------------------------------------------------
   No design exists for this page; it reuses the site's own parts.
   ---------------------------------------------------------------------- */
.case-single__inner { max-width: 770px; }
.case-single__logo { margin-bottom: 40px; }
.case-single__logo img { max-height: 72px; width: auto; }
.case-single__body { font-size: var(--step-body); }

.case-single__tags {
	display: flex;
	flex-wrap: wrap;
	gap: 10px;
	margin: 40px 0 0;
	padding: 0;
	list-style: none;
}

.case-single__tag a {
	display: inline-block;
	padding: 12px 16px;
	border: 2px solid var(--color-gold);
	border-radius: 50px;
	font-size: 0.875rem;
	font-weight: 700;
	line-height: 1;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	color: var(--color-charcoal-1);
	text-decoration: none;
}

.case-single__back { margin-top: 40px; }
.case-single__back a {
	display: inline-block;
	padding-block: 13px;   /* 18px of text -> 44px, the touch minimum */
}

/* The chips are links on the archive and on a location page; on the card they
   inherit the card's white type rather than the page's. */
.case-card__tag a {
	color: inherit;
	text-decoration: none;
}
.case-card__tag:hover { background: rgba(200, 178, 122, 0.18); }

/* ==========================================================================
   HERO — body-copy variant (Our Approach)
   ========================================================================== */

/* #435:2721: the H1 and the copy are 130px apart in a 864-wide column, and
   the copy is 23px on 30px rather than the practice-area hero's intro line. */
.hero__body {
	margin-top: 0;
	max-width: 864px;
	font-size: var(--step-lead);
	line-height: 1.3;
	color: rgba(255, 255, 255, 0.86);
}
.hero__body p { margin-bottom: 1em; }

/* ==========================================================================
   ACCORDION — Our Approach
   ========================================================================== */

.accordion { display: grid; gap: 24px; }

.accordion__item {
	background: var(--color-paper-1);
	border: 1px solid var(--color-paper-2);
	border-radius: 25px;
	padding: clamp(28px, 4vw, 48px) 24px clamp(28px, 4vw, 48px) clamp(24px, 4vw, 48px);
}

.accordion__header {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: clamp(20px, 4vw, 48px);
	padding-left: 24px;
	/* EL-37582e75: a 2px gold rule on the header's left edge. */
	border-left: 2px solid var(--color-gold);
	cursor: pointer;
	list-style: none;
}
.accordion__header::-webkit-details-marker { display: none; }

.accordion__title {
	font-family: var(--font-display);
	font-weight: 300;
	font-size: clamp(1.5rem, 1.1rem + 1.6vw, 2.8125rem);   /* 24 → 45 */
	line-height: 1.2;
	letter-spacing: -0.01em;
	color: var(--color-charcoal-1);
}

.accordion__toggle {
	flex: 0 0 auto;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 36px;
	height: 36px;
	padding: 6px;
	border-radius: 50%;
	background: var(--color-purple);
	color: var(--color-white);
}

/* Plus becomes minus when the panel is open — the vertical bar is what goes. */
.accordion__item[open] .accordion__toggle-bar--v { display: none; }

.accordion__body {
	/* The comp indents the body 479px inside a 1098 content width. Expressed
	   as a fraction so it holds at any width and collapses on small screens. */
	margin-top: 48px;
	margin-left: 43.6%;
	display: grid;
	gap: 20px;
	font-size: var(--step-body);
	color: var(--color-charcoal-1);
}
.accordion__body p { margin-bottom: 0; }

@media (max-width: 899px) {
	.accordion__body { margin-left: 0; margin-top: 28px; }
}

/* ==========================================================================
   SERVICES
   ========================================================================== */

/* The purple band: 1920x220, #662483, a centred 55px title over a 23px
   subtitle 15px below it. */
.service__band {
	position: relative;
	background: var(--color-purple);
	color: var(--color-white);
	padding-block: 50px;
	text-align: center;
	overflow: hidden;
}

.service__title {
	margin: 0 0 15px;
	font-size: var(--step-h2);
	color: var(--color-white);
}

.service__subtitle {
	margin: 0;
	font-size: var(--step-lead);
	line-height: 1.5;
	color: rgba(255, 255, 255, 0.82);
}

/* #226:9026: the container, 100px of vertical padding, the paragraphs beside
   the list with 50px between them. */
.service__inner {
	display: grid;
	gap: 50px;
	padding-block: var(--band-y);
}

@media (min-width: 900px) {
	.service__inner { grid-template-columns: minmax(0, 1fr) minmax(0, 1fr); }
}

.service__body { font-size: var(--step-body); }
.service__body p { margin-bottom: 24px; }

.service__list { display: grid; gap: 30px; align-content: start; }
.service__list-heading { margin: 0; font-size: var(--step-body); }

.service__list ul {
	display: grid;
	gap: 0;
	margin: 0;
	padding: 0;
	list-style: none;
}

/* Same tick-and-rule treatment as the practice-area typical roles list, which
   is the only list pattern the design defines. */
.service__list li {
	position: relative;
	padding: 16px 0 16px 44px;
	border-bottom: 1px solid var(--color-paper-3);
	font-size: var(--step-body);
}
.service__list li:first-child { border-top: 1px solid var(--color-paper-3); }

.service__list li::before {
	content: '';
	position: absolute;
	left: 4px;
	top: 22px;
	width: 18px;
	height: 10px;
	border-left: 2px solid var(--color-gold);
	border-bottom: 2px solid var(--color-gold);
	transform: rotate(-45deg);
}

/* ---- Process timeline --------------------------------------------------- */

.process__inner { display: grid; gap: 40px; }

@media (min-width: 900px) {
	/* #226:9022: a 361 heading column beside the 770 content column. */
	.process__inner { grid-template-columns: 361px minmax(0, 770px); align-items: start; }
}

.process__heading { font-size: var(--step-h2-block); }
.process__column { display: grid; gap: 40px; }
.process__intro, .process__outro { font-size: var(--step-body); }

/* Two-up, which is what the comp draws: #226:8984 is a 770px COLUMN whose
   children are ROWS of two cards (#226:8985 → #226:8986 + #226:8993), 30px
   apart. Built as one card per row it read as a stack down the right half of
   the page with nothing beside it. */
.process__steps {
	display: grid;
	gap: 30px;
	margin: 0;
	padding: 0;
	list-style: none;
	counter-reset: none;
}

@media (min-width: 700px) {
	.process__steps { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}

.process__step {
	display: grid;
	gap: 30px;
	padding: 30px;
	background: var(--color-paper-1);
	border: 1px solid var(--color-paper-2);
	border-radius: 20px;
}

/* EL-a40e2f0d right-aligns the label and number. LEFT here is a deliberate
   departure the client asked for — do not "fix" it back to the comp. 3px
   apart, 20px under them, as the file has it. */
.process__weeks {
	margin: 0;
	display: grid;
	gap: 3px;
	justify-items: start;
	text-align: left;
}

.process__weeks-label {
	font-size: 0.9375rem;
	font-weight: 600;
	letter-spacing: 0.06em;
	text-transform: uppercase;
	color: var(--color-charcoal-2);
}

.process__weeks-number {
	font-size: clamp(1.75rem, 1.4rem + 1.2vw, 2.1875rem);   /* 28 → 35 */
	font-weight: 600;
	line-height: 1;
	color: var(--color-purple);
}

.process__text { margin: 0; font-size: var(--step-body); }

/* ==========================================================================
   ABOUT
   ========================================================================== */

/* The comp (#206:7073) starts the map at x=3 in a 1920 frame — hard against
   the left edge, outside the 375px container gutter — and the build reproduced
   that. The client's call is that it reads badly: the map crowds the viewport
   edge while a wide gap opens between it and the copy, and every other
   two-column section on the site sits inside the container. So this one does
   too. A deliberate departure from the file; do not "restore" it.
   ========================================================================== */
.offset-block__inner {
	display: grid;
	gap: 40px;
	align-items: center;
	width: 100%;
	max-width: calc(var(--content-max) + var(--gutter) * 2);
	margin-inline: auto;
	padding-inline: var(--gutter);
}

.offset-block__media img {
	display: block;
	width: 100%;
	object-fit: cover;
}

/* The UK map is a tall illustration, not a cropped photograph — 1000px against
   a 743 width. Left to `width: 100%` it dominates the phone layout, so it is
   capped there and allowed its full height only where there is room. */
@media (max-width: 1023px) {
	.offset-block__media img {
		width: auto;
		max-width: 100%;
		max-height: 420px;
		margin-inline: auto;
	}
}

.offset-block__copy { display: grid; gap: 40px; }
.offset-block__heading { font-size: var(--step-h2); }
.offset-block__body { font-size: clamp(1.0625rem, 1rem + 0.2vw, 1.1875rem); line-height: 1.684; }
.offset-block__body p { margin-bottom: 24px; }

@media (min-width: 1024px) {
	/* Two columns inside the container, on the site's own two-column rhythm
	   rather than the comp's full-bleed proportions. Top-aligned: the copy is
	   taller than the map at every width, and centring parks the map in the
	   middle of the difference. */
	.offset-block__inner {
		grid-template-columns: 40% minmax(0, 1fr);
		column-gap: clamp(48px, 6.8vw, 130px);
		align-items: start;
	}
}

/* No photograph: one full-width column of copy rather than a narrow one with
   two thirds of the page empty beside it. */
.offset-block--no-media .offset-block__inner { grid-template-columns: minmax(0, 1fr); }

@media (min-width: 1024px) {
	.offset-block--no-media .offset-block__inner {
		grid-template-columns: 571px minmax(0, 1fr);
		column-gap: clamp(48px, 7vw, 133px);
	}
	.offset-block--no-media .offset-block__copy { display: contents; }
}

/* ---- Team grid ---------------------------------------------------------- */

.team-grid {
	display: grid;
	gap: 29px;
	margin: 0;
	padding: 0;
	list-style: none;
}

@media (min-width: 600px) {
	.team-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}
@media (min-width: 1024px) {
	/* Three across at x=374 / 774 / 1174 in the comp. */
	.team-grid { grid-template-columns: repeat(3, minmax(0, 1fr)); }
}

.team-grid__item { display: flex; }
.team-grid .person-card { width: 100%; }

/* ==========================================================================
   CONTACT
   ========================================================================== */

/* One form since the candidate form was removed (2026-09-15). Held to the
   width of the comp's case-study card, so a single panel does not stretch its
   fields across the full 1170 container, and centred in it (2026-09-16). */
/* The Contact page's panel border: a step darker and a pixel heavier than the
   paper-2 card border used elsewhere, which on white all but disappeared
   (2026-09-17). Scoped here so other cards keep theirs. */
.contact { --contact-border: #E2DBCC; }
.contact__grid { display: grid; gap: 24px; }
.contact__grid > .contact-form,
.contact__grid > .contact-bar { width: 100%; max-width: 770px; margin-inline: auto; }

/* Telephone and email above the form, side by side, in a thin border that
   matches the form panel below it so the two read as one unit. Stacks on a
   phone, where two lines of contact detail side by side will not fit. */
.contact-bar {
	list-style: none;
	margin: 0;
	padding: 20px clamp(20px, 4vw, 48px);
	display: flex;
	flex-direction: column;
	gap: 4px;
	background: var(--color-white);
	border: 2px solid var(--contact-border);
	border-radius: 25px;
}
.contact-bar__item { margin: 0; }
.contact-bar__link {
	display: inline-flex;
	align-items: center;
	gap: 10px;
	padding-block: 8px;          /* 44px touch target with the line height */
	color: var(--color-charcoal-1);
	text-decoration: none;
	white-space: nowrap;
	transition: color 0.15s ease;
}
.contact-bar__icon {
	flex: none;
	width: 22px;
	height: 22px;
	color: var(--color-purple);
}
/* Underline the words only, never the gap after the icon. */
.contact-bar__link:hover { color: var(--color-purple); }
.contact-bar__link:hover .contact-bar__text { text-decoration: underline; }

/* Two equal halves with the divider on the bar's exact midpoint, and each
   item centred in its own half — the handset and number on the centre line of
   the left half, the envelope and address on the centre line of the right. */
@media (min-width: 600px) {
	/* No side padding once it splits: a half runs from the visible border to
	   the divider, and the stacked layout's 48px of inline padding pulled each
	   half's centre 24px toward the divider. The items carry their own. */
	.contact-bar {
		display: grid;
		grid-template-columns: 1fr 1fr;
		gap: 0;
		padding-inline: 0;
	}
	.contact-bar__item {
		display: flex;
		align-items: center;
		justify-content: center;
		padding-inline: 12px;
	}
	.contact-bar__item + .contact-bar__item {
		border-left: 2px solid var(--contact-border);
		margin-left: -1px;      /* half the line, so its centre is the midpoint */
	}
	/* One value only: no halves, so centre the item across the whole bar. */
	.contact-bar__item:only-child { grid-column: 1 / -1; }
}

/* "A proper border around the forms" — the client's own words in the Q&A. */
.contact-form {
	padding: clamp(28px, 4vw, 48px);
	background: var(--color-white);
	border: 2px solid var(--contact-border);
	border-radius: 25px;
}

.contact-form__heading { font-size: var(--step-h2-block); margin-bottom: 16px; }
.contact-form__intro { color: var(--color-charcoal-2); }

.contact-form__form { display: grid; gap: 24px; }

.contact-form__field { display: grid; gap: 8px; margin: 0; }

.contact-form__field label {
	font-size: 0.9375rem;
	font-weight: 600;
	letter-spacing: 0.04em;
	text-transform: uppercase;
	color: var(--color-charcoal-2);
}

.contact-form__required { color: var(--color-purple); }

.contact-form__field input,
.contact-form__field textarea {
	width: 100%;
	padding: 14px 16px;
	font-family: inherit;
	font-size: var(--step-body);
	color: var(--color-ink);
	background: var(--color-paper-1);
	border: 1px solid var(--color-paper-2);
	border-radius: 12px;
}

.contact-form__field input:focus-visible,
.contact-form__field textarea:focus-visible {
	outline: 2px solid var(--color-purple);
	outline-offset: 1px;
}

/* Guidance under a field, from its 'hint'. */
.contact-form__hint {
	display: block;
	margin-top: 6px;
	font-size: 0.875rem;
	color: var(--color-charcoal-2);
}

/* The honeypot. Not display:none — some bots skip hidden fields, and some
   password managers refuse to touch them. */
.contact-form__trap {
	position: absolute;
	left: -9999px;
	width: 1px;
	height: 1px;
	overflow: hidden;
}

.contact-form__actions { margin: 8px 0 0; }

.contact-form__notice {
	margin: 0 0 24px;
	padding: 16px 20px;
	border-radius: 12px;
	font-size: var(--step-body);
}
.contact-form__notice--ok {
	background: var(--color-paper-1);
	border: 1px solid var(--color-gold);
}
.contact-form__notice--error {
	background: #FDF3F3;
	border: 1px solid #D8A0A0;
}
.contact-form__notice ul { margin: 8px 0 0; padding-left: 20px; }

/* ==========================================================================
   INDEX PAGES — Practice Areas, Clients (no design exists for either)
   ========================================================================== */

.index-section__intro {
	max-width: 770px;
	margin-bottom: 60px;
	font-size: var(--step-body);
}

.index-grid,
.client-grid {
	display: grid;
	margin: 0;
	padding: 0;
	list-style: none;
}

.index-grid {
	gap: 29px;
	grid-template-columns: repeat(auto-fill, minmax(260px, 1fr));
}

.index-grid .area-card { width: 100%; height: 420px; }

/* On a white page the plain tile needs its own contrast, not the strip's. */
.area-card--light {
	background: var(--color-paper-1);
	border-color: var(--color-paper-2);
	color: var(--color-charcoal-1);
}

.client-grid {
	gap: 40px 24px;
	grid-template-columns: repeat(auto-fill, minmax(140px, 1fr));
	align-items: center;
}

.client-grid__item {
	display: flex;
	align-items: center;
	justify-content: center;
	height: 60px;
}

.client-grid__item img {
	max-width: 100%;
	max-height: 100%;
	width: auto;
	object-fit: contain;
}

.index-section__actions { margin-top: 60px; }

/* ==========================================================================
   INTERACTION STATES

   Every link, button and control on the site gets a hover response, and every
   one of them pairs it with :focus-visible so a keyboard reaches the same
   affordance. Audited against the templates rather than added ad hoc — the
   gaps were: both header toggles, the footer's telephone, the case-study
   filter, the accordion header, the whole-card links, the case-study single's
   chips and back link, and every link inside body copy, which had no styling
   at all and was indistinguishable from the text around it.
   ========================================================================== */

/* ---- Links inside body copy ---------------------------------------------
   A link in a paragraph has to be tellable from the paragraph. Underlined at
   rest with a gold offset, purple on hover. */
.copy-block__body a:not(.button),
.media-block__body a:not(.button),
.offset-block__body a:not(.button),
.split-block__body a:not(.button),
.hero__body a:not(.button),
.accordion__body a:not(.button),
.service__body a:not(.button),
.process__intro a:not(.button),
.process__outro a:not(.button),
.index-section__intro a:not(.button),
.case-single__body a:not(.button),
.case-card__body a:not(.button) {
	color: inherit;
	text-decoration: underline;
	text-decoration-color: var(--color-gold);
	text-underline-offset: 0.2em;
	text-decoration-thickness: 1px;
	transition: color 0.15s ease, text-decoration-color 0.15s ease;
}

.copy-block__body a:not(.button):hover,
.media-block__body a:not(.button):hover,
.offset-block__body a:not(.button):hover,
.hero__body a:not(.button):hover,
.accordion__body a:not(.button):hover,
.service__body a:not(.button):hover,
.process__intro a:not(.button):hover,
.process__outro a:not(.button):hover,
.index-section__intro a:not(.button):hover,
.case-single__body a:not(.button):hover {
	color: var(--color-purple);
	text-decoration-color: var(--color-purple);
}

/* On the dark cards and bands, purple has no contrast — go gold instead. */
.split-block__body a:not(.button):hover,
.case-card__body a:not(.button):hover {
	color: var(--color-gold);
	text-decoration-color: var(--color-gold);
}

/* ---- Header -------------------------------------------------------------- */
.site-header__logo,
.site-header__toggle,
.site-header__submenu-toggle {
	transition: color 0.15s ease, opacity 0.15s ease;
}

.site-header__logo:hover { opacity: 0.75; }
.site-header__toggle:hover,
.site-header__submenu-toggle:hover { color: var(--color-purple); }
.site-header--overlay .site-header__toggle:hover,
.site-header--overlay .site-header__submenu-toggle:hover,
.site-header--overlay .site-header__menu a:hover { color: var(--color-gold); }

/* ---- Footer -------------------------------------------------------------- */
.site-footer__value a {
	text-decoration: none;
	transition: color 0.15s ease;
}
.site-footer__value a:hover {
	color: var(--color-purple);
	text-decoration: underline;
}
/* On the phone link, underline the number only. Set on the flex link itself,
   the line was drawn from the icon's edge, across the gap, so it started a
   space-width before the first digit. */
.site-footer__value--phone a:hover { text-decoration: none; }
.site-footer__value--phone a:hover span { text-decoration: underline; }

/* ---- Cards that are entirely a link -------------------------------------- */
/* The image already scales; the label needs to move too, or the hover reads as
   an accident of the photograph rather than a link. */
.area-card__label { transition: color 0.15s ease; }
.area-card:hover .area-card__label,
.area-card:focus-visible .area-card__label { color: var(--color-gold); }

/* ---- Case study chips and back link -------------------------------------- */
.case-card__tag,
.case-single__tag a {
	transition: background-color 0.15s ease, color 0.15s ease;
}
.case-single__tag a:hover {
	background: var(--color-purple);
	border-color: var(--color-purple);
	color: var(--color-white);
}

.case-single__back a {
	text-decoration: underline;
	text-decoration-color: var(--color-gold);
	text-underline-offset: 0.2em;
	transition: color 0.15s ease;
}
.case-single__back a:hover { color: var(--color-purple); }

/* ---- Filter -------------------------------------------------------------- */
.case-filter__select,
.case-filter__chevron { transition: border-color 0.15s ease, color 0.15s ease; }
.case-filter__select:hover { border-color: var(--color-purple-alt); }
.case-filter__control:hover .case-filter__chevron { color: var(--color-purple); }

/* ---- Accordion ----------------------------------------------------------- */
.accordion__header .accordion__title,
.accordion__toggle { transition: color 0.15s ease, background-color 0.15s ease; }
.accordion__header:hover .accordion__title { color: var(--color-purple); }
.accordion__header:hover .accordion__toggle { background: var(--color-purple-alt); }

/* ---- Buttons -------------------------------------------------------------
   A .button inside body copy is still a button. The prose-link rules above
   were repainting it charcoal and underlining it in gold; the :not(.button)
   there is the fix, and this is the guard against the next such rule. */
.button,
.button:hover,
.button:focus-visible {
	color: var(--color-white);
	text-decoration: none;
}
/* The arrow shifts with the fill so the whole control reads as one thing. */
.button { transition: background-color 0.15s ease, color 0.15s ease; }
.button__arrow { transition: transform 0.15s ease; }
.button:hover .button__arrow { transform: translate(2px, 2px); }
.button--ghost:hover { background: rgba(255, 255, 255, 0.12); }

/* Contact form controls. */
.contact-form__field input,
.contact-form__field textarea { transition: border-color 0.15s ease; }
.contact-form__field input:hover,
.contact-form__field textarea:hover { border-color: var(--color-gold); }

@media (prefers-reduced-motion: reduce) {
	/* Keep every hover, drop the movement. */
	.button__arrow,
	.button,
	.site-header__logo,
	.site-header__toggle,
	.site-header__submenu-toggle,
	.site-footer__value a,
	.area-card__label,
	.case-card__tag,
	.case-single__tag a,
	.case-single__back a,
	.case-filter__select,
	.case-filter__chevron,
	.accordion__header .accordion__title,
	.accordion__toggle,
	.contact-form__field input,
	.contact-form__field textarea { transition: none; }
	.button:hover .button__arrow { transform: none; }
}

/* ==========================================================================
   SLIDER CONTROLS

   The rows scroll natively, so touch, trackpad and keyboard work with no JS.
   These styles are the affordances a desktop MOUSE user needs, which native
   scrolling gives them none of: something that looks draggable, and a progress
   bar that looks operable. The comp draws no arrow buttons, so none are added.
   ========================================================================== */

/* Only a row that actually overflows should look draggable. The class is set
   by JS from the real scrollWidth, so a two-card row on a wide screen does not
   invite a drag that does nothing. */
.slider.is-scrollable .slider__track { cursor: grab; }

/* Native image drag-and-drop is off inside a slider. Without this, pressing on
   a card's photograph and moving offers the browser's own drag — ghost image,
   drop cursor — instead of scrolling the row. The JS also cancels `dragstart`,
   but this stops the gesture being offered in the first place, so there is no
   flicker of a ghost before the handler runs. */
.slider__track img,
.slider__track a {
	-webkit-user-drag: none;
	user-select: none;
	-webkit-user-select: none;
}
.slider .slider__track.is-dragging {
	cursor: grabbing;
	/* Kill the text selection that otherwise follows the pointer across a card
	   mid-drag, and the momentum fight on trackpads. */
	user-select: none;
	scroll-behavior: auto;
}
.slider .slider__track.is-dragging * { pointer-events: none; }

/* Keyboard focus has to be visible on a scroller — it is a real control. */
.slider__track:focus-visible {
	outline: 2px solid var(--color-gold);
	outline-offset: -2px;
}

/* ---- The progress bar, now a scrubber -----------------------------------
   Same 1170x22 geometry the comp draws; what changes is that it responds.
   The 22px frame is already a comfortable pointer target around a 4px line. */
.slider-progress { cursor: pointer; touch-action: none; }

.slider-progress__thumb {
	transition: height 0.12s ease, transform 0.12s linear, width 0.12s linear;
}

/* Grow the thumb on hover and while scrubbing so the bar reads as operable.
   The track keeps its height, so nothing around it moves. */
.slider-progress:hover .slider-progress__thumb,
.slider-progress.is-scrubbing .slider-progress__thumb {
	height: 6px;
	top: -1px;
}
.slider-progress.is-scrubbing { cursor: grabbing; }

/* A scrubber that cannot move is worse than none: JS hides the bar outright
   when there is nothing to scroll, and this covers the pre-JS moment. */
.slider:not(.is-scrollable) .slider-progress { cursor: default; }

@media (prefers-reduced-motion: reduce) {
	.slider-progress__thumb { transition: none; }
}

/* ==========================================================================
   Gravity Forms — the contact form wears the theme, not Orbital's defaults

   The contact form moved from our own markup to Gravity Forms and no CSS
   moved with it, so the panel kept its designed border while everything
   inside it reverted to the plugin's stock look: blue submit button, 38px
   grey-bordered fields, 14px text. Three consequences beyond looking wrong —
   38px is under the 44px touch minimum, 14px input text makes iOS Safari zoom
   the page on focus, and none of it matched the panel around it.

   Gravity Forms 2.7+ ships a CSS custom-property API, and these are set on
   OUR wrapper rather than overriding its selectors, so the plugin keeps
   ownership of layout and we only state the values. The old hand-built
   form's tokens are reused exactly: 12px radius, paper-1 field fill,
   paper-2 border, body type, purple focus.
   ========================================================================== */

.contact-form .gform_wrapper.gform-theme.gform-theme--framework {
	/* Fields */
	--gf-ctrl-bg-color: var(--color-paper-1);
	--gf-ctrl-bg-color-focus: var(--color-white);
	--gf-ctrl-bg-color-hover: var(--color-white);
	--gf-ctrl-border-color: var(--color-paper-2);
	/* The field border resolves through the colour layer, not
	   --gf-ctrl-border-color: that one drives choices and other controls,
	   while a text input reads --gf-color-in-ctrl-dark-lighter (#686e77
	   by default, which is the grey that was showing). */
	--gf-color-in-ctrl-dark-lighter: var(--color-paper-2);
	--gf-color-out-ctrl-dark-lighter: var(--color-paper-2);
	--gf-ctrl-border-color-hover: var(--color-gold);
	--gf-ctrl-border-color-focus: var(--color-purple);
	--gf-ctrl-border-width: 1px;
	--gf-ctrl-radius: 12px;
	--gf-ctrl-accent-color: var(--color-purple);
	/* 16px minimum: anything smaller and iOS Safari zooms the page on focus. */
	--gf-ctrl-font-size: 1rem;
	--gf-ctrl-padding-x: 16px;
	--gf-ctrl-padding-y: 14px;
	--gf-ctrl-size: 52px;
	--gf-ctrl-size-md: 52px;
	--gf-ctrl-size-lg: 52px;

	/* Labels — the old form's uppercase 15px in charcoal, purple asterisk */
	--gf-ctrl-label-color-primary: var(--color-charcoal-2);
	--gf-ctrl-label-color-secondary: var(--color-charcoal-2);
	--gf-ctrl-label-color-req: var(--color-purple);
	--gf-ctrl-label-font-size-primary: 0.9375rem;
	--gf-ctrl-label-font-size-req: 0.9375rem;

	/* Rhythm — 24px between fields, as .contact-form__form had */
	--gf-field-gap-y: 24px;
	--gf-form-gap-y: 24px;

	/* Submit — the theme's pill, not Orbital's blue rectangle */
	--gf-ctrl-btn-bg-color-primary: var(--color-purple);
	--gf-ctrl-btn-bg-color-hover-primary: var(--color-purple-alt);
	--gf-ctrl-btn-bg-color-focus-primary: var(--color-purple-alt);
	--gf-ctrl-btn-border-color-primary: var(--color-purple);
	--gf-ctrl-btn-border-color-hover-primary: var(--color-purple-alt);
	--gf-ctrl-btn-border-color-focus-primary: var(--color-purple-alt);
	--gf-ctrl-btn-color-primary: var(--color-white);
	--gf-ctrl-btn-radius: 50px;
	/* --gf-ctrl-btn-font-size defaults to the -md variant, so setting the
	   base alone leaves the button at Orbital's 14px. */
	--gf-ctrl-btn-font-size: 1rem;
	--gf-ctrl-btn-font-size-md: 1rem;
	--gf-ctrl-btn-padding-x: 26px;
	--gf-ctrl-btn-padding-y: 14px;
	--gf-ctrl-btn-size: 47px;
	--gf-ctrl-btn-size-md: 47px;
	/* GF's own button selector is six classes deep, so weight, tracking
	   and case are unreachable by a plain rule and are set here. */
	--gf-ctrl-btn-font-weight: 700;
	--gf-ctrl-btn-letter-spacing: 0.1em;
	--gf-ctrl-btn-text-transform: uppercase;
}

/* The API carries colour and metric but not family, weight or case, so the
   label and the button state theirs. */
.contact-form .gform_wrapper .gfield_label {
	font-family: inherit;
	font-weight: 600;
	letter-spacing: 0.04em;
	text-transform: uppercase;
}

.contact-form .gform_wrapper input,
.contact-form .gform_wrapper textarea {
	font-family: inherit;
	color: var(--color-ink);
}

.contact-form .gform_wrapper textarea { min-height: 160px; }

/* Orbital centres the footer on some widths; the design has it left. */
.contact-form .gform_wrapper .gform_footer { justify-content: flex-start; }

/* Validation, in the notice colours the old form used rather than GF red. */
.contact-form .gform_wrapper .gform_validation_errors {
	background: #FDF3F3;
	border: 1px solid #D8A0A0;
	border-radius: 12px;
	box-shadow: none;
}
.contact-form .gform_wrapper .gform_confirmation_message {
	padding: 16px 20px;
	background: var(--color-paper-1);
	border: 1px solid var(--color-gold);
	border-radius: 12px;
	font-size: var(--step-body);
}

/* Gravity Forms prints a per-form block of its own, inline in the page:

     #gform_wrapper_1[data-form-index="0"].gform-theme { --gf-ctrl-border-color: #686e77; … }

   An ID beats any number of classes, so the handful of values it writes as
   LITERALS cannot be reached from a stylesheet at all — which is why the
   fields kept a grey border while every other token above took. (The values
   it writes as var() DO resolve through ours: that is how the button picked
   up 47px and 16px.) Setting the form's own style settings does not help
   either; it emits these defaults regardless of that meta.

   !important is the only thing that outranks it, and it is confined to the
   two declarations the inline block hard-codes. */
.contact-form .gform_wrapper.gform-theme {
	--gf-ctrl-border-color: var(--color-paper-2) !important;
	--gf-ctrl-label-color-primary: var(--color-charcoal-2) !important;
	--gf-ctrl-label-color-secondary: var(--color-charcoal-2) !important;
}

/* ==========================================================================
   Pre-launch fixes, 2026-09-19
   ========================================================================== */

/* ---- Case-study cards: clamp the long ones ------------------------------
   Every card in a row is stretched to the tallest, so one long summary left
   three quarters of the shorter cards as empty teal — 750px of it on a 320px
   phone. The body is clamped to six lines and a "+ Read more" opens it.

   The clamp and the button are both added by main.js, so a visitor without
   JavaScript sees the whole summary rather than a truncated one with a dead
   button next to it. */
.case-card__body--clamped {
	display: -webkit-box;
	-webkit-box-orient: vertical;
	-webkit-line-clamp: 6;
	line-clamp: 6;
	overflow: hidden;
}
.case-card.is-open .case-card__body--clamped {
	-webkit-line-clamp: unset;
	line-clamp: unset;
}

.case-card__more {
	align-self: flex-start;
	margin-top: 14px;
	padding: 0;
	font-family: inherit;
	font-size: 1rem;
	font-weight: 600;
	letter-spacing: 0.02em;
	color: var(--color-gold);
	background: none;
	border: 0;
	border-bottom: 1px solid currentColor;
	cursor: pointer;
}
.case-card__more:hover { color: var(--color-white); }

/* ---- The alliance badge at the narrowest widths -------------------------
   The roundel and the text sit side by side, which left the text about 130px
   wide at 320 and wrapped it onto six ragged lines. Below 480 the roundel
   goes above the text so the line has the full width of the pill. */
@media (max-width: 480px) {
	.alliance__identity {
		flex-direction: column;
		align-items: flex-start;
		gap: 16px;
	}
	.alliance__text { font-size: 1.125rem; }
}

/* ---- Button labels at the narrowest widths ------------------------------
   "FIND YOUR NEXT HIRE" and "LEARN MORE ABOUT ORYX" need more width than a
   320 or 360 screen leaves, so the label broke onto a second line while the
   arrow stayed pinned right, leaving a hole between the two. Smaller type and
   tighter tracking fit them on one line; the button keeps its 44px height. */
@media (max-width: 400px) {
	.button {
		padding-inline: 20px;
		font-size: 0.8125rem;
		letter-spacing: 0.06em;
	}
}

/* ---- Cookie banner with the phone held sideways -------------------------
   Complianz sizes the panel from the viewport, so a 375px-tall landscape
   screen shrank the whole thing to 316x213 with roughly 7px body text and
   100x17px buttons. It is given the width of the screen and its own scroll,
   and every control is brought back to a tappable size. */
@media (max-height: 500px) and (orientation: landscape) {
	/* zoom: 0.6 is Complianz's own, applied to fit the panel into a short
	   screen. It scales EVERYTHING — which is why the body text measured
	   about 7px and the policy links 4px tall, and why setting font sizes
	   here did nothing: they were shrunk by the same 40%. Undo the zoom and
	   give the panel the width of the screen instead, which is the dimension
	   a landscape phone actually has to spare. */
	/* The zoom is applied per element, not once on the panel — the buttons
	   carry their own zoom: 0.5 — so it has to be cleared right through. */
	#cmplz-cookiebanner-container .cmplz-cookiebanner,
	#cmplz-cookiebanner-container .cmplz-cookiebanner * {
		zoom: 1 !important;
	}
	#cmplz-cookiebanner-container .cmplz-cookiebanner {
		/* The panel is a grid with its row heights written out in pixels
		   (78.45px for the header row, and so on), sized for a portrait
		   phone. That is where the empty band under the title comes from —
		   the header itself is 10px tall sitting in a 78px row. Letting the
		   rows size to their content removes it. */
		grid-template-rows: auto !important;
		inset-inline: 2vw !important;
		width: auto !important;
		max-width: none !important;
		max-height: 85vh !important;
		overflow-y: auto !important;
	}
	/* The empty band under the title: the header is a grid pinned to
	   height: 10px while the title and close button inside it are 25 and 44
	   tall, so they overflow and the divider below sits where the grid says
	   rather than where the content ends. Let it size to its content. */
	#cmplz-cookiebanner-container .cmplz-cookiebanner .cmplz-header {
		height: auto !important;
		min-height: 0 !important;
		margin-bottom: 8px !important;
		align-items: center;
	}
	/* Side by side rather than stacked: the room here is horizontal. */
	#cmplz-cookiebanner-container .cmplz-cookiebanner .cmplz-buttons {
		display: flex !important;
		flex-wrap: wrap;
		gap: 10px !important;
	}
	/* Complianz gives each button the full width, which stacks three of them
	   down a screen that has no vertical room and none to spare. Sideways
	   there is width instead, so they share a row. */
	/* Only the three buttons this banner actually shows. Forcing display on
	   every .cmplz-btn brought back the ones Complianz hides for this variant
	   — a second "View preferences" and a "Save preferences" appeared beside
	   the real ones. */
	#cmplz-cookiebanner-container .cmplz-cookiebanner .cmplz-accept,
	#cmplz-cookiebanner-container .cmplz-cookiebanner .cmplz-deny,
	#cmplz-cookiebanner-container .cmplz-cookiebanner .cmplz-view-preferences {
		display: inline-flex !important;
		flex: 1 1 auto;
		align-items: center;
		justify-content: center;
		width: auto !important;
		min-width: 0 !important;
		min-height: 44px !important;
		margin: 0 !important;
	}
}

/* ---- Cookie banner and policy: controls you can actually hit -------------
   The close control was 20x20, the policy links 15px tall, the category
   toggles 25x25 and the statistics opt-in 13x13. 44px is the minimum for
   something a finger has to land on. */
#cmplz-cookiebanner-container .cmplz-cookiebanner .cmplz-close {
	display: inline-flex !important;
	align-items: center;
	justify-content: center;
	min-width: 44px !important;
	min-height: 44px !important;
}

.cmplz-document .cmplz-category-toggle,
.cmplz-document button.cmplz-category-toggle {
	min-width: 44px !important;
	min-height: 44px !important;
}

.cmplz-document input[type="checkbox"],
.cmplz-document .cmplz-checkbox {
	width: 24px !important;
	height: 24px !important;
}
/* The hit area rather than the box: the control stays 24px but the label it
   sits in gives the finger 44px to land on. */
.cmplz-document label:has(input[type="checkbox"]) {
	display: inline-flex;
	align-items: center;
	min-height: 44px;
	gap: 10px;
}
