/**
 * OTA Hero Carousel widget styles.
 *
 * A two-tone heading, an intro, two buttons and a cut-out image, rotating
 * through slides.
 *
 * Every colour is a colour theme role, mapped once in the block below and
 * referenced by name after that. Nothing here is a picked colour, which is what
 * lets the block follow the theme in force above it: its own, else the
 * container's, else the page's, else the site's. The roles come from the "Hero
 * carousel" component in the OTA design file, binding for binding:
 *
 *   surface        bar/background   --ota-background
 *   heading, copy  bar/white-text   --ota-white-text
 *   accent word    bar/logo         --ota-logo, see the note below
 *   primary btn    bar/cta-bg       --ota-cta-bg
 *   primary text   bar/cta-text     --ota-cta-text
 *   secondary      bar/cta-bg       --ota-cta-bg
 *   dots, idle     bar/white-text   --ota-white-text
 *   arrow fill     bar/background   --ota-background
 *   arrow line     bar/text         --ota-text
 *
 * `white-text` is not literally white. It is the role for text that reads on
 * this theme's background, so it resolves navy on the light themes and white on
 * navy, teal and ochre. Using it for the heading is what keeps the hero legible
 * on all nine rather than only the dark ones.
 *
 * Typography comes from the Elementor global fonts rather than being stated
 * here: Heading/Display Bold for the heading and Body/Lead for the intro, which
 * are the styles the Figma frame binds. Each value is a `var()` with the Figma
 * number as its fallback, so the block still renders to spec on a site whose
 * kit has not had the scale imported. Family is left to inherit, as before.
 *
 * The small screen sizes come with them, because the globals hold tablet and
 * mobile values of their own. That is why there are no type overrides in the
 * narrow block at the end of this file.
 *
 * Two deliberate departures, both documented at the rules themselves. The
 * heading's first line is Regular where its style is Bold, because the file has
 * no Regular cut at 116px. The intro takes Body/Lead as published, Regular,
 * where the frame had it Bold: nothing in the type scale is Bold above 17px and
 * the intro is a block of running text, which is what SC 1.4.8 governs.
 *
 * The buttons are left alone on purpose, since the design has no button text
 * style yet.
 */
.ota-hero {
	/*
	 * The accent word, and the one binding the two frames disagree on. The
	 * desktop frame uses `brand/ochre`, a fixed brand constant; the mobile
	 * frame uses `bar/logo`, which is a real theme role. The role is taken,
	 * because the constant is broken on two of the nine themes and the role is
	 * not:
	 *
	 *   theme  logo      background   fixed ochre would be
	 *   ash    #F04C3A   #F0E7D8      fine
	 *   navy   #F04C3A   #003038      fine
	 *   teal   #D4F0D9   #005361      fine
	 *   ochre  #003038   #F04C3A      invisible, ochre on ochre
	 *   gold   #003038   #F68B1F      poor, ochre on orange
	 *
	 * So `logo` is the brand ochre exactly where the desktop frame expects it
	 * and flips to navy on the two backgrounds that ochre cannot sit on. The
	 * brand value stays as the fallback for a site with no colour theme set.
	 *
	 * Kept on its own property so it is one line to change if the designers
	 * would rather pin it after all.
	 */
	--ota-hero-accent: var(--ota-logo, #f04c3a);

	/* Roles, with the Ash values as fallbacks so the block is never unstyled
	   when no colour theme is configured. */
	--oh-surface: var(--ota-background, #f0e7d8);
	--oh-text: var(--ota-white-text, #003038);
	--oh-cta-bg: var(--ota-cta-bg, #003038);
	--oh-cta-text: var(--ota-cta-text, #ffffff);
	--oh-line: var(--ota-text, #003038);

	/*
	 * The header's container, restated so the hero's copy lines up with the
	 * logo and the nav rather than with the viewport. `.ota-utility__inner` and
	 * `.ota-header__inner` in ota-mega-menu.css are `max-width: 1440px` centred
	 * with `padding-inline: 2rem`, and the gutter below is the left edge that
	 * produces: the centring margin plus that padding once the viewport is wide
	 * enough to have one, and the bare padding before that.
	 *
	 * Held as a length rather than the design's 5.83% because a percentage
	 * tracks the viewport and the nav does not, so the two only agreed at
	 * exactly 1440px. 5.83% of 1440 is 84px, which is what the design shows;
	 * this reproduces it there and stays aligned either side of it.
	 */
	--oh-max: 1440px;
	--oh-pad: 2rem;
	--oh-gutter: max(var(--oh-pad), calc((100% - var(--oh-max)) / 2 + var(--oh-pad)));

	--oh-speed: 0.4s;
	/* The cross fade between slides. Long enough to read as a dissolve rather
	   than a cut, short enough not to hold up someone clicking through. */
	--oh-fade: 0.6s;

	position: relative;
	overflow: hidden;
	background: var(--oh-surface);
	color: var(--oh-text);
}

/*
 * The slides stack rather than sit in a track. A track would mean owning the
 * width arithmetic and a transform per slide; stacking means the only state is
 * which one is visible, which is also the only state the dots and the script
 * have to agree on.
 */
.ota-hero__slides {
	display: grid;
}

/*
 * The slide is the container, carrying the header's own max-width, centring and
 * padding, so the copy starts on the same line as the logo.
 *
 * Done here rather than with `--oh-gutter` on the body because a percentage in
 * a custom property is resolved by the element that uses it, not the one that
 * declares it. The body sits in a half-width grid column, so its `100%` was
 * half the hero and the gutter collapsed to the bare padding above 1440px. The
 * dots and arrows are direct children of `.ota-hero`, so their `100%` is the
 * hero's width and the variable is correct for them.
 */
.ota-hero__slide {
	grid-area: 1 / 1;
	display: grid;
	grid-template-columns: 1fr 1fr;
	align-items: center;
	box-sizing: border-box;
	/*
	 * `width: 100%` is load bearing. Auto inline margins cancel a grid item's
	 * default `stretch`, so with the margins alone the slide sized itself to
	 * its content and came out narrower than its cap. The explicit width gives
	 * it something to stretch against; `max-width` then caps it and the auto
	 * margins centre what is left.
	 */
	width: 100%;
	max-width: var(--oh-max);
	margin-inline: auto;
	padding-inline: var(--oh-pad);
	/*
	 * 34rem (544px). The frame's 47rem was cut 20% to 37.6rem in Teamwork
	 * 49453519 (3 Sep 2026), and the client asked for it shorter again in
	 * Teamwork 49833766 (11 Nov), with no figure given, so about 10% more.
	 * Desktop only, by Bryce's call: the mobile rule further down already
	 * releases this to `min-height: 0` and lets the copy and the square photo
	 * set the height, so there is no fixed height there to take from.
	 *
	 * THE IMAGE CROSSOVER FOLLOWS THIS NUMBER. See the `min-width` media query
	 * on `.ota-hero__image` below: change one, change the other.
	 */
	min-height: 34rem;
}

/* Told again because a display on a class outranks the browser's own [hidden]
   rule, the same trap as `.ota-header [hidden]` in ota-mega-menu.css. This is
   the no-JS state: one slide shown, the rest not generating a box at all. */
.ota-hero__slide[hidden] {
	display: none;
}

/*
 * The cross fade.
 *
 * Only once the script has taken over, which is what `.is-enhanced` marks.
 * Until then the slides are switched with the `hidden` attribute and there is
 * nothing to fade, so these rules must not apply or every slide would sit at
 * opacity 0 on a page whose JavaScript never ran.
 *
 * All the slides share one grid cell, so the outgoing one fades out underneath
 * the incoming one fading in, rather than the two swapping through a gap.
 *
 * `visibility` is doing the accessibility work, not opacity. An element at
 * opacity 0 is still focusable and still read out; `visibility: hidden` takes
 * it out of the accessibility tree and out of the tab order. It is delayed by
 * the length of the fade on the way out so the slide stays visible while it is
 * fading, and switched instantly on the way in.
 */
.ota-hero.is-enhanced .ota-hero__slide {
	opacity: 0;
	visibility: hidden;
	transition: opacity var(--oh-fade) ease, visibility 0s linear var(--oh-fade);
}

.ota-hero.is-enhanced .ota-hero__slide.is-current {
	opacity: 1;
	visibility: visible;
	transition: opacity var(--oh-fade) ease, visibility 0s;
}

/*
 * Opacity only. The copy holds its position through the change: a slide had the
 * body drift up as it arrived, and against a heading this large the movement
 * read as a jolt rather than as easing, so there is deliberately no transform
 * here. Both halves of the hero simply dissolve.
 */

/*
 * The bottom padding reserves the band the dots row sits in. The row is pinned
 * `bottom: 3.25rem` and is 2.25rem tall (the pause pill), so the band is 5.5rem
 * of the slide's height; 7rem keeps 1.5rem of air above it. Without this the
 * copy is centred against the whole slide, and once the slide came down to
 * 37.6rem (Teamwork 49453519) a three-line intro plus two buttons left the
 * buttons ending exactly where the dots begin, and anything longer ran over
 * them (Teamwork 49553727). Padding rather than a smaller centring box so a
 * slide whose copy outgrows `min-height` still grows past the band instead of
 * into it. The 2rem at the top is the matching floor above the heading, so a
 * slide long enough to fill the band still does not start at the edge. The
 * mobile rule further down resets both; the dots sit over the image there,
 * not under the copy.
 */
.ota-hero__body {
	position: relative;
	z-index: 1;
	padding-block: 2rem 7rem;
}

/*
 * No band to reserve when there is nothing to put in it. A hero with a single
 * slide never shows the dots row, and with 7rem kept for it the copy sat well
 * above the middle of the band: 91px over the heading against 171px under the
 * buttons on the homepage (Teamwork 49833766). Counted from the markup rather
 * than keyed off the row's `hidden` attribute, which the script lifts only
 * after load, so a multi-slide hero never paints centred and then jumps up.
 * Desktop only: the one-column layout below 1025px has its own padding and
 * puts the dots over the image, not under the copy.
 */
@media (min-width: 1025px) {
	.ota-hero:not(:has(.ota-hero__slide + .ota-hero__slide)) .ota-hero__body {
		padding-block: 2rem;
	}
}

/*
 * The two halves are one heading. Written as a block-level span each so they
 * stack without a <br>, which would be markup carrying a line break that is
 * really a layout decision.
 */
/*
 * Heading/Display Bold, the hero's own style: 116px at a 0.96 ratio, Bold.
 * Size, line height and tracking belong to the heading as a whole, because
 * both halves are one heading and the metrics that decide how the two lines
 * sit together have to be set on the element that holds them.
 */
.ota-hero__heading {
	margin: 0;
	font-size: var(--e-global-typography-display-bold-font-size, 7.25rem);
	font-weight: var(--e-global-typography-display-bold-font-weight, 700);
	line-height: var(--e-global-typography-display-bold-line-height, 0.96em);
	letter-spacing: var(--e-global-typography-display-bold-letter-spacing, -2.32px);
}

.ota-hero__heading-lead,
.ota-hero__heading-accent {
	display: block;
}

/*
 * The first line is the one exception to reading everything from a global.
 * The design sets it Regular at the same 116px, and the file has no Regular
 * cut of Display Bold to point at: Heading/Display is Regular but it is 84px,
 * so linking to it would change the size as well as the weight. So the weight
 * alone is overridden here and the rest still comes from Display Bold above.
 *
 * If a Heading/Display Bold Regular is ever added in Figma, this becomes a
 * var() like the others and this comment goes.
 */
.ota-hero__heading-lead {
	font-weight: 400;
	color: var(--oh-text);
}

.ota-hero__heading-accent {
	color: var(--ota-hero-accent);
}

/*
 * 40rem, up from the frame's 32rem, Teamwork 49553727. The client caps hero
 * intros at 40 words, which at 32rem wrapped to five lines and pushed the
 * buttons into the dots; at 40rem the same copy is four lines and about 65
 * characters each, still inside a readable measure. The copy column is
 * (1440px - 2 x 2rem) / 2 = 688px at the cap, so 40rem (640px) leaves 48px
 * before the photo's edge.
 */
.ota-hero__intro {
	max-width: 40rem;
	margin: 2.25rem 0 0;
	font-size: var(--e-global-typography-lead-font-size, 1.375rem);
	font-weight: var(--e-global-typography-lead-font-weight, 400);
	line-height: var(--e-global-typography-lead-line-height, 1.5em);
	letter-spacing: var(--e-global-typography-lead-letter-spacing, -0.22px);
	color: var(--oh-text);
}

.ota-hero__actions {
	display: flex;
	flex-wrap: wrap;
	gap: 0.9375rem;
	/* The value everywhere, including a hero outside the theme's <main> (an
	   Elementor Canvas page), where the rule below does not reach. */
	margin-top: var(--oh-actions-gap, 2.25rem);
}

/*
 * The space above the buttons, at id strength because the theme takes it.
 * `_content.scss` gives any `p + div` inside the content wrapper
 * `margin-top: .5rem` from a selector led by `main#agendtheme-content`
 * (1,2,3), and the intro is a <p> followed by this <div>, so the 2.5rem the
 * frame asks for was being painted as 8px: the buttons sat right under the
 * intro (Teamwork 49833766). This chain weighs (1,3,1).
 *
 * 2.25rem now, the same as the heading's gap to the intro above it, which is
 * the space the client marked and asked to see repeated here. The mobile rule
 * sets its own value through the variable.
 */
main#agendtheme-content .ota-hero .ota-hero__body .ota-hero__actions {
	margin-top: var(--oh-actions-gap, 2.25rem);
}

/* --- Buttons ------------------------------------------------------------- */

/*
 * These are the design's Button component, Medium, and the numbers below are the
 * ones assets/css/ota-buttons.css draws it at: 64px tall with a 32px badge and a
 * 16px glyph, 30px of leading padding against 10px of trailing so the badge sits
 * near the edge. Figma reports 62.445 / 31.445 / 15.297, which are instance
 * resize artefacts of the same button, rounded there and here alike.
 *
 * They were 47px, which is neither the Medium the hero instances are nor the 48px
 * the Event Listing and Dashboard frames draw, so the hero's pair read a size
 * smaller than every other button on the site.
 *
 * Restated here rather than reached by putting `.ota-btn` on the markup. The two
 * are one markup change apart, and the reason to hold off is that the widget's
 * own Buttons typography control writes `font-size` without `!important`, which
 * the button baseline marks, so converting would leave that control unable to
 * set a size. Worth doing together with a decision about that, not before it.
 */
.ota-hero__btn {
	display: inline-flex;
	align-items: center;
	gap: 0.75rem;
	min-height: 4rem;
	padding: 1rem 0.625rem 1rem 1.875rem;
	border-radius: 999px;
	font-size: 1.0625rem;
	font-weight: 700;
	line-height: 1;
	text-decoration: none;
	transition: filter var(--oh-speed) ease;
}

.ota-hero__btn:hover {
	filter: brightness(0.94);
	text-decoration: none;
}

.ota-hero__btn-badge {
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	width: 2rem;
	height: 2rem;
	border-radius: 50%;
}

.ota-hero__btn-badge svg {
	display: block;
	width: 1rem;
	height: 1rem;
}

/*
 * Primary: the CTA pair, filled. The badge inverts within the button, so its
 * glyph takes the button's own fill rather than a third colour. That is what
 * keeps it correct on all nine themes without a per-theme rule.
 */
.ota-hero__btn--primary {
	background: var(--oh-cta-bg);
	color: var(--oh-cta-text);
}

.ota-hero__btn--primary .ota-hero__btn-badge {
	background: var(--oh-cta-text);
	color: var(--oh-cta-bg);
}

/*
 * Secondary: the same pair, unfilled, so it reads as the quieter of the two
 * while still being the theme's colour rather than a washed out version of it.
 * This is the design's Ghost, which is why there is no line: its badge is the
 * fill and its glyph the colour that goes on the fill, the same inversion the
 * primary makes in the other direction. The glyph took the hero's surface
 * before, which is a third colour and is not what the design draws.
 */
.ota-hero__btn--secondary {
	background: transparent;
	color: var(--oh-cta-bg);
}

.ota-hero__btn--secondary .ota-hero__btn-badge {
	background: var(--oh-cta-bg);
	color: var(--oh-cta-text);
}

/* --- Media --------------------------------------------------------------- */

/*
 * The image arrives pre-masked, so its shape is the artwork's own and nothing
 * here re-cuts it. Three things follow from that.
 *
 * It is never cropped. The height is the hero's and the width follows from the
 * image's own ratio, so the whole mask is always visible; `object-fit: contain`
 * is the backstop for the case where a box is imposed on it anyway. `cover`
 * would be wrong here: it fills by throwing away edges, which is exactly what
 * a pre-masked cut-out cannot survive.
 *
 * It is anchored right. The mask is drawn against the right edge, so it stays
 * pinned there and any surplus width runs off to the left, behind the copy,
 * rather than centring and leaving a gap.
 *
 * It sits behind. z-index 0 against the body's 1, so long headings and the
 * buttons stay over the artwork instead of being pushed off it.
 *
 * Two classes, not for style but for specificity. Elementor ships
 * `.elementor img { height: auto; max-width: 100% }` at (0,1,1), which beats a
 * lone `.ota-hero__image`: `height: auto` would collapse the box to the
 * image's intrinsic size and `max-width` would squash a wide mask. Same trap
 * as the one fixed on the category feature.
 */
/*
 * The media owns the right half and nothing else, which is what keeps it off
 * the copy no matter what shape the artwork is. `left: 50%` works because the
 * slide is a centred container, so the hero's midpoint and the container's
 * midpoint are the same line: the copy sits in the container's left column and
 * the image starts exactly where that column ends. It still bleeds to the right
 * edge of the viewport rather than stopping at the container.
 */
.ota-hero__media {
	position: absolute;
	z-index: 0;
	inset: 0 0 0 50%;
	pointer-events: none;
}

/*
 * `cover`, so the half is always filled.
 *
 * `contain` was the first answer and it was wrong below about 1440: the half
 * narrows faster than the hero shortens, so the artwork stopped filling the
 * height and simply got smaller, with a growing band of background above and
 * below it. Filling and trimming reads far better than shrinking.
 *
 * `object-position: left` decides what gets trimmed. The half is usually
 * narrower than the artwork is tall, so the surplus is horizontal, and
 * anchoring left means it comes off the right hand edge: the outside of the
 * frame, away from the subject, which on these images sits centre-left. On a
 * very wide viewport the half becomes wider than it is tall and the surplus
 * turns vertical instead, trimmed evenly top and bottom by the `center` half
 * of the pair.
 *
 * The mask still meets the viewport edge, because the box it fills runs to
 * that edge; it is the artwork inside the box that is cropped, not the box.
 */
.ota-hero .ota-hero__image {
	display: block;
	width: 100%;
	max-width: none;
	height: 100%;
	object-fit: cover;
	object-position: left center;
}

/*
 * Above the crossover, stop trimming and go back to fitting.
 *
 * 1088px is where the two behaviours meet rather than a round number: the half
 * is 50% of the viewport and the hero is 34rem (544px) tall, so the half stops
 * being the narrower dimension at 544 * 2 = 1088. It was 1504px at 47rem and
 * 1204px at 37.6rem. Below that the
 * surplus is horizontal and `cover` above trims it off the right; above it the
 * surplus turns vertical, and trimming that would start cutting heads and feet
 * out of the photograph for no reason, since the artwork already fills the
 * height on its own. The value follows the slide's `min-height`: when that
 * changes, this must change with it. A slide
 * whose copy pushes it taller than the minimum moves its own crossover up, so
 * the figure is exact for the frame and approximate for a long slide.
 *
 * So: fits exactly at the crossover, fills and trims below it, fits with a
 * little slack on the inside edge above it. Never shrinks.
 */
@media (min-width: 1088px) {
	.ota-hero .ota-hero__image {
		object-fit: contain;
		object-position: right center;
	}
}

/* --- Dots ---------------------------------------------------------------- */

/* Every control below sets a display on its class, and a display on a class
   outranks the browser's own [hidden] rule, the same trap the
   `.ota-hero__slide[hidden]` rule above is told about. Without this the controls ship visible: the
   pause button survives `syncPlayback()` hiding it under reduced motion, and
   with no JavaScript at all the whole row renders and does nothing. */
.ota-hero__nav[hidden],
.ota-hero__playback[hidden],
.ota-hero__arrows[hidden] {
	display: none;
}

/*
 * The dots and the pause button share one row, and the row is what is placed.
 * The dots used to carry the positioning themselves; it moved out here when the
 * pause button arrived, because two absolutely positioned boxes would each need
 * to know the other's width to sit beside it.
 */
.ota-hero__nav {
	position: absolute;
	bottom: 3.25rem;
	left: var(--oh-gutter);
	z-index: 1;
	display: flex;
	align-items: center;
	gap: 1rem;
}

.ota-hero__dots {
	display: flex;
	align-items: center;
	gap: 0.5rem;
}

/*
 * The pause control. Smaller than an arrow, because it is the one control here
 * that is not about choosing a slide, but on the same pill and the same line so
 * it reads as part of the set.
 *
 * 2.25rem is 36px, which clears the 24px minimum of SC 2.5.8 with room to spare
 * and stays under the dots' own line.
 */
.ota-hero__playback {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 2.25rem;
	height: 2.25rem;
	padding: 0;
	border: 1.5px solid var(--oh-text);
	border-radius: 999px;
	background: transparent;
	color: var(--oh-text);
	cursor: pointer;
	transition: background-color var(--oh-speed) ease, color var(--oh-speed) ease;
}

.ota-hero__playback:hover {
	background: var(--oh-text);
	color: var(--oh-surface);
}

.ota-hero__playback:focus-visible {
	outline: 2px solid var(--oh-text);
	outline-offset: 3px;
}

.ota-hero__playback-glyph {
	display: block;
	width: 1rem;
	height: 1rem;
}

/* One glyph at a time, chosen by the state the script writes onto the button. */
.ota-hero__playback[data-paused="false"] .ota-hero__playback-glyph--play,
.ota-hero__playback[data-paused="true"] .ota-hero__playback-glyph--pause {
	display: none;
}

.ota-hero__dot {
	width: 0.6875rem;
	height: 0.3125rem;
	padding: 0;
	border: 0;
	border-radius: 9px;
	background: var(--oh-text);
	cursor: pointer;
	transition: width var(--oh-speed) ease, background-color var(--oh-speed) ease;
}

/* The active dot stretches rather than only changing colour, so the current
   slide is still legible to anyone who cannot separate the two hues. */
.ota-hero__dot[aria-selected="true"] {
	width: 2rem;
	background: var(--ota-hero-accent);
}

.ota-hero__dot:focus-visible {
	outline: 2px solid var(--oh-text);
	outline-offset: 3px;
}

/* --- Arrows -------------------------------------------------------------- */

.ota-hero__arrows {
	position: absolute;
	right: var(--oh-gutter);
	bottom: 3.25rem;
	z-index: 1;
	display: flex;
	gap: 0.625rem;
}

.ota-hero__arrow {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 2.875rem;
	height: 2.875rem;
	padding: 0;
	border: 1.5px solid var(--oh-line);
	border-radius: 999px;
	background: var(--oh-surface);
	color: var(--oh-line);
	cursor: pointer;
	transition: background-color var(--oh-speed) ease, color var(--oh-speed) ease;
}

.ota-hero__arrow:hover {
	background: var(--oh-line);
	color: var(--oh-surface);
}

.ota-hero__arrow svg {
	display: block;
	width: 1.125rem;
	height: 1.125rem;
}

.ota-hero__arrow:focus-visible {
	outline: 2px solid var(--oh-line);
	outline-offset: 3px;
}

/* --- Narrow -------------------------------------------------------------- */

/*
 * The image goes above the copy rather than beside it. Below this width the two
 * columns leave the heading too little room to hold its line breaks, and the
 * design's cut-out has nothing to cut into.
 */
/*
 * Mobile, from the "Navy Home - Mobile" frame.
 *
 * One column, and the image goes below the copy rather than above it. That is
 * the design's order and it is also the right one: the heading is the first
 * thing on the page, so it should not be pushed under a screen's worth of
 * photograph.
 *
 * The frame is 393 wide and its gutter is 4.83%, which is 19px, so the desktop
 * 2rem narrows here. Everything else keys off `--oh-pad` already, so moving the
 * one value moves the copy, the dots and the arrows together.
 */
@media (max-width: 1024px) {
	.ota-hero {
		--oh-pad: 1.1875rem;
	}

	/*
	 * Two rows, and the copy takes the slack.
	 *
	 * The slides share one grid cell, so the cell is as tall as the wordiest
	 * slide. With the rows sized to their content, a slide with shorter copy
	 * ended short and left a band of background under its image while its
	 * neighbour reached the bottom. Giving the body `1fr` and the media `auto`
	 * means the body absorbs the difference and every slide's image lands on
	 * the bottom edge, whatever its copy runs to.
	 */
	.ota-hero__slide {
		grid-template-columns: 1fr;
		grid-template-rows: 1fr auto;
		/* Top of its row, not centred in it. The base rule centres the two
		   desktop columns against each other; here the copy row is the one
		   that grows, so centring inside it would float the heading down the
		   screen by however much the wordiest slide runs to. */
		align-items: start;
		align-content: stretch;
		max-width: none;
		min-height: 0;
		padding-inline: 0;
	}

	.ota-hero__body {
		padding: 2.5rem var(--oh-pad) 2.25rem;
	}

	/*
	 * Below the copy, full bleed, and squared off.
	 *
	 * The ratio is pinned rather than left to the file. The supplied artwork is
	 * consistently about 1:1, and a known height is what lets the side arrows
	 * be centred on the image without measuring it in script.
	 *
	 * It runs to the bottom of the hero with nothing under it, so the block
	 * ends on the photograph rather than on a strip of background.
	 */
	.ota-hero__media {
		position: static;
		width: 100%;
		aspect-ratio: 1 / 1;
	}

	.ota-hero .ota-hero__image {
		width: 100%;
		height: 100%;
		object-position: center;
	}

	/*
	 * No type here. The globals carry the artboard's small screen scale
	 * themselves, 48px display and 19px lead, so restating a size would only
	 * be a second copy of the spec to keep in step.
	 *
	 * One seam worth knowing: the globals step down at the kit's tablet
	 * breakpoint of 992 while this layout goes to one column at 1024, so
	 * between 993 and 1024 the copy is single column at the desktop scale.
	 */

	/* The frame keeps it clear of the right edge. */
	.ota-hero__intro {
		max-width: none;
		margin-top: 1.75rem;
		padding-right: 1.5rem;
	}

	/* Matches the intro's 1.75rem above, the same pairing as on desktop. */
	.ota-hero {
		--oh-actions-gap: 1.75rem;
	}

	/*
	 * The arrows split to either edge and sit over the image, rather than
	 * pairing up in a corner as they do on the desktop.
	 *
	 * Centred on the image by arithmetic, not measurement: the media is full
	 * bleed and pinned to 1:1 just above and runs to the bottom of the hero, so
	 * its middle is half the viewport width up from that bottom edge. The
	 * arrow's own half height comes back off so it centres on the line rather
	 * than hanging below it.
	 *
	 * The strip spans the full width and is click-through, so only the two
	 * buttons themselves take the pointer and the image stays draggable and
	 * selectable between them.
	 */
	.ota-hero__arrows {
		left: 0;
		right: 0;
		bottom: calc(50vw - 1.4375rem);
		justify-content: space-between;
		padding-inline: var(--oh-pad);
		pointer-events: none;
	}

	.ota-hero__arrow {
		pointer-events: auto;
	}

	/*
	 * Centred along the bottom, over the image rather than under it. The row
	 * already sits above the media in the stacking order, so this needs no
	 * z-index of its own: `.ota-hero__media` is z-index 0 and `.ota-hero__nav`
	 * is 1.
	 */
	.ota-hero__nav {
		left: 50%;
		transform: translateX(-50%);
		bottom: 1.5rem;
	}
}

/*
 * Rotation is the block's motion, and the script already stops the timer for
 * this preference. What is left is the transitions, which become arrivals.
 * Matches the blocks in ota-mega-menu.css and ota-category-feature.css.
 */
@media (prefers-reduced-motion: reduce) {
	.ota-hero__btn,
	.ota-hero__dot,
	.ota-hero__arrow,
	.ota-hero__playback {
		transition: none;
	}

	/*
	 * The slides still change, they just cut rather than dissolve. Autoplay is
	 * already off under this preference, so this only affects a change the
	 * reader asked for with the dots or the arrows.
	 */
	.ota-hero.is-enhanced .ota-hero__slide,
	.ota-hero.is-enhanced .ota-hero__slide.is-current {
		transition: none;
	}
}
