/**
 * OTA Footer styles.
 *
 * Figma node 193:6979, "Footer", 1440x593: a centred logo, a tagline with one
 * word in the accent colour, a subscribe field, one row of links, four social
 * icons, a copyright line, and the brand mark bleeding off the bottom right.
 *
 * Every colour is a colour theme role, mapped once in the token block below and
 * referenced by name after that. There is no background control here and there
 * should not be: the footer is chrome, and the page's own Colour Theme control
 * is what moves it. That is what `--ota-page-theme--*` is for, and a picked
 * colour on the footer would sit on top of it and stop the page setting working.
 *
 * The roles, binding for binding:
 *
 *   footer surface   bar/background     --ota-background     169:7922
 *   logo             follows the theme through currentColor   169:8001
 *   tagline          bar/text           --ota-text           169:7999
 *   tagline accent   bar/accent         --ota-accent         the "home" span
 *   field border     bar/text           --ota-text           169:7930
 *   field text       bar/text           --ota-text           169:7931
 *   Subscribe        .ota-btn--primary, which reads cta-bg / cta-text itself
 *   nav links        bar/White Text     --ota-white-text     169:7941 onwards
 *   social icons     bar/Ochre Button   --ota-ochre-button   169:7957
 *   copyright        bar/text-muted     --ota-text-muted     169:7974
 *   brand mark       bar/overlay        --ota-overlay        169:8033
 *
 * `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
 * the dark ones. The accent word is bound to `accent` rather than to
 * `ochre-button`: both resolve to #F04C3A in the frame's own mode, and `accent`
 * is the role that means "the highlight colour on this theme" while
 * `ochre-button` means "the ochre call to action". The word "home" is the first.
 *
 * Typography comes from the Elementor global fonts where the kit publishes a cut
 * for it. The tagline does not have one: the design calls it Heading/H5 at 32px
 * and the imported scale runs display, h2, h3, h4, lead, body, caption, small
 * and eyebrow with no H5. Rather than borrow H4 and be silently wrong wherever
 * that lands, the tagline states 2rem itself. Same reasoning the News Block uses
 * for the weights its scale has no cut for.
 */

.ota-footer {
	--oft-surface: var(--ota-background, #f0e7d8);
	--oft-text: var(--ota-text, #003038);
	--oft-muted: var(--ota-text-muted, #005361);
	--oft-accent: var(--ota-accent, #f04c3a);
	--oft-link: var(--ota-white-text, #003038);
	--oft-social: var(--ota-ochre-button, #f04c3a);
	/*
	 * The colour theme publishes no error role, and the frame draws no error
	 * state. `ochre-button` is the warm role on every theme, which is the nearest
	 * honest thing to point at. See the validation section for what it colours and
	 * what it deliberately does not.
	 */
	--oft-error: var(--ota-ochre-button, #f04c3a);
	--oft-overlay: var(--ota-overlay, #f04c3a);

	/* The frame's own measurements. */
	--oft-max: 1003px;
	--oft-brand-max: 800px;
	--oft-pad: 1.5rem;

	position: relative;
	/*
	 * The theme puts `d-flex flex-grow-1 flex-column` on <body>, which makes the
	 * footer a flex item in a column, and the two declarations below are both
	 * about surviving that.
	 *
	 * `flex-shrink: 0` because a flex item's automatic minimum size is zero, not
	 * its content height, as soon as its overflow is anything but visible. The
	 * `overflow: hidden` on the next line is exactly that, so on a short page the
	 * column shrank this footer to its own padding and clipped all 310px of
	 * content inside 115px of band. It looked like a stylesheet conflict and was
	 * nothing of the kind.
	 *
	 * `width: 100%` because the same column stretches its items by default but
	 * an item that has been shrunk in the cross axis by anything upstream would
	 * otherwise stay narrow, and this footer bleeds to the page edge by design.
	 */
	flex-shrink: 0;
	width: 100%;
	/* Crops the brand mark exactly as the frame crops it. */
	overflow: hidden;
	/*
	 * 62px above the logo and 53px below the copyright, which is what the frame
	 * leaves once its content is measured off the 593px band.
	 */
	padding-block: 62px 53px;
	background-color: var(--oft-surface);
	color: var(--oft-text);
}

/* --- The brand mark ------------------------------------------------------ */

/*
 * Node 169:8033. A masked element rather than an <img>, so its colour is the
 * overlay role and follows the theme: nothing can reach inside an <img>.
 *
 * Anchored to the bottom LEFT corner and then pushed back out past it by a
 * share of its own size, rather than positioned with the frame's percentages of
 * the artboard. The two draw the same thing at 1440x593 and only this one keeps
 * drawing it once the footer is taller than the frame, which it is on any page
 * where the links wrap to two lines. 46.8% of the mark's width is the 273px it
 * hangs past the edge, and 46.36% of its height is the 262px it hangs below the
 * bottom.
 *
 * LEFT RATHER THAN RIGHT, AND MIRRORED WITH IT. Moved on 14 Aug 2026 so the
 * content page mast can take the bottom right corner with the same mark and the
 * two do not both crowd the same side of the page. `scaleX(-1)` is not
 * decoration: the mark is asymmetric and drawn to bleed off a right hand
 * corner, so moving it without mirroring shows the wrong half of it. Drop the
 * `scaleX(-1)` and negate the X translate to put it back.
 */
.ota-footer__mark {
	position: absolute;
	inset-inline-start: 0;
	bottom: 0;
	/* 583.487 of the artboard's 1440. */
	width: 40.52%;
	aspect-ratio: 583.487 / 564.91;
	transform: translate(-46.8%, 46.36%) scaleX(-1);
	background-color: var(--oft-overlay);
	-webkit-mask: url("../img/ota-footer-mark.svg") no-repeat center / contain;
	mask: url("../img/ota-footer-mark.svg") no-repeat center / contain;
	/*
	 * Behind everything. The mark reaches under the copyright line at narrow
	 * widths and the text has to stay on top of it.
	 */
	z-index: 0;
	pointer-events: none;
}

/* --- Layout -------------------------------------------------------------- */

.ota-footer__inner {
	position: relative;
	/* Above the mark. */
	z-index: 1;
	box-sizing: border-box;
	display: flex;
	flex-direction: column;
	align-items: center;
	width: 100%;
	max-width: calc(var(--oft-max) + 2 * var(--oft-pad));
	margin-inline: auto;
	padding-inline: var(--oft-pad);
}

.ota-footer__brand {
	display: flex;
	flex-direction: column;
	align-items: center;
	/* Logo to tagline in the frame. */
	gap: 36px;
	width: 100%;
	max-width: var(--oft-brand-max);
	text-align: center;
}

.ota-footer__logo {
	display: flex;
	justify-content: center;
}

/*
 * EVERY LINK COLOUR IN THIS FILE IS RESTATED FOR :hover, AND HAS TO BE
 *
 * The Agend theme's skin-2020 bundle carries one rule:
 *
 *   a, a:hover { color: var(--at-color-text-body-link); }
 *
 * `--at-color-text-body-link` is the navy this footer paints itself with, so on
 * a navy surface a link that hands its hover state to the theme is a link that
 * disappears under the pointer. That is not a hypothetical: it was every link in
 * the footer.
 *
 * It wins because of the half of that selector nobody reads. At rest only the
 * `a` half applies, at 0,0,1, and any rule here beats it. On hover the `a:hover`
 * half applies at 0,1,1, which beats `.ota-footer__logo-link` and
 * `.ota-footer__social-link` at 0,1,0 outright and ties `.ota-footer__nav-list a`
 * at 0,1,1. The tie goes to whichever sheet loads last, and skin-2020 is
 * enqueued after this file, so the theme takes every one of them.
 *
 * Adding `:hover` and `:focus-visible` to each selector lifts it to 0,2,0 or
 * 0,2,1 and settles it on specificity rather than on load order, which is worth
 * having: the order is a function of how the theme and the plugin enqueue, and
 * that is not a thing this stylesheet should depend on. Restating the colour is
 * also the honest fix rather than `color: inherit`, because the three links here
 * are three different colours on purpose.
 */
.ota-footer__logo-link,
.ota-footer__logo-link:hover,
.ota-footer__logo-link:focus-visible {
	display: inline-flex;
	/*
	 * The logo follows the theme through currentColor, which is the whole point
	 * of inlining it rather than serving an <img>. See
	 * Mega_Menu_Renderer::inline_logo_svg().
	 */
	color: var(--oft-accent);
	text-decoration: none;
}

.ota-footer__logo svg,
.ota-footer__logo img {
	display: block;
	/* Node 169:8001 draws it 166x62. */
	width: auto;
	height: 62px;
	max-width: 100%;
}

.ota-footer__tagline {
	margin: 0;
	/* 445px in the frame, which is what puts "of occupational" on line two. */
	max-width: 445px;
	color: var(--oft-text);
	/* Heading/H5, 32/34.56. The kit publishes no H5: see the note at the top. */
	font-size: 2rem;
	font-weight: 400;
	line-height: 1.08;
}

.ota-footer__accent {
	color: var(--oft-accent);
}

/* --- Subscribe ----------------------------------------------------------- */

/*
 * Node 169:7929. The frame draws one pill with the field inside it on the left
 * and the button inside the same pill on the right, and what is inside that pill
 * is a Gravity Form. So this section reaches into Gravity Forms' markup, which
 * is the trade for the field being a real form with its own validation, storage
 * and notifications rather than an input of our own posting somewhere.
 *
 * Kept as shallow as it can be: the pill is drawn on the `<form>`, the label is
 * hidden rather than removed so the field keeps its accessible name, and the
 * input is stripped rather than restyled. Nothing here reaches for a
 * `#gform_wrapper_4`, so changing which form the Customizer points at does not
 * break the styling.
 */
.ota-footer__subscribe {
	width: 100%;
	/* 36px below the tagline in the frame, near enough the gap above it. */
	margin-block-start: 1px;
}

.ota-footer__subscribe .gform_wrapper {
	margin: 0;
}

.ota-footer__subscribe form {
	display: flex;
	align-items: center;
	gap: 10px;
	box-sizing: border-box;
	width: 100%;
	/*
	 * Node 193:7001 draws the pill at 462px: 12px of padding and a 1.5px border
	 * each side, a 265px text column and the button, with a 10px gap. At the
	 * old 372px the button still fit but the text column was squeezed to 199px,
	 * which is where the field started looking like a box rather than a line.
	 */
	max-width: 462px;
	margin-inline: auto;
	padding: 12px;
	border: 1.5px solid var(--oft-text);
	border-radius: 999px;
}

/*
 * Gravity Forms lays its fields out on a grid. One field in a row that is
 * already a flex row does not want a grid inside it as well, and the stock grid
 * brings its own row gap that pushes the button off the pill's centre line.
 */
.ota-footer__subscribe .gform-body,
.ota-footer__subscribe .gform_body {
	flex: 1 1 auto;
	min-width: 0;
	margin: 0;
}

.ota-footer__subscribe .gform_fields {
	display: block;
	grid-template-columns: none;
	margin: 0;
	padding: 0;
	row-gap: 0;
}

.ota-footer__subscribe .gfield {
	padding: 0;
}

/*
 * Hidden, not removed. The field still needs an accessible name, and Gravity
 * Forms' own "hidden label" setting removes it from the markup on some field
 * types rather than just from view.
 */
.ota-footer__subscribe .gfield_label,
.ota-footer__subscribe .gform_hidden_label,
.ota-footer__subscribe .gfield_required {
	position: absolute;
	width: 1px;
	height: 1px;
	margin: -1px;
	padding: 0;
	overflow: hidden;
	clip: rect(0 0 0 0);
	clip-path: inset(50%);
	white-space: nowrap;
	border: 0;
}

/*
 * The asterisk above is hidden, so the legend explaining it is too. Tied to the
 * footer rather than the form, so it holds whichever form the Customizer picks.
 */
.ota-footer__subscribe .gform_required_legend {
	display: none;
}

/*
 * Plain declarations, and they stay plain because Footer::subscribe_opt_out()
 * flags this field's container with `data-agendtheme-initialised` before the
 * page loads. The theme's `embellish-form-inputs.js` skips a container carrying
 * that flag, so the `.agendtheme-form-input` wrapper is never built and the
 * `!important` field skin that comes with it never applies here.
 *
 * Without that opt-out this block was a specificity fight it could not win: the
 * theme sets background, border, radius, colour, size, padding and height on
 * `.agendtheme-form-input input`, every one of them `!important`.
 */
.ota-footer__subscribe input[type="text"],
.ota-footer__subscribe input[type="email"] {
	box-sizing: border-box;
	width: 100%;
	margin: 0;
	/* The frame pads the text 8px in from the pill's own 12px. */
	padding: 0 0 0 8px;
	border: 0;
	background: transparent;
	color: var(--oft-text);
	/* Node 169:7931 draws the placeholder at 18px. */
	font-size: 1.125rem;
	line-height: 1.6;
}

.ota-footer__subscribe input[type="text"]:focus,
.ota-footer__subscribe input[type="email"]:focus {
	outline: none;
}

/*
 * The pill takes the focus ring on the field's behalf, because the field has no
 * edge of its own to draw one on. Removing the ring and putting nothing back is
 * what this is avoiding.
 */
.ota-footer__subscribe form:focus-within {
	outline: 2px solid var(--oft-accent);
	outline-offset: 2px;
}

.ota-footer__subscribe input::placeholder {
	color: var(--oft-text);
	opacity: 0.75;
}

/*
 * Autofill. Chrome paints a pale blue field and near black text over anything
 * the stylesheet asks for, which on this dark pill reads as a white box sitting
 * inside the outline. `background-color` cannot reach it; the UA styles the
 * control itself. An inset shadow the depth of the field is the way in, and
 * `-webkit-text-fill-color` is what actually colours autofilled text.
 *
 * The shadow paints the footer's own surface, so a square fill inside a rounded
 * pill is invisible: the field sits 12px in from the border with the same
 * colour behind it either way.
 *
 * Firefox is separate again and takes a plain background.
 */
.ota-footer__subscribe input:-webkit-autofill,
.ota-footer__subscribe input:-webkit-autofill:hover,
.ota-footer__subscribe input:-webkit-autofill:focus,
.ota-footer__subscribe input:-webkit-autofill:active {
	-webkit-box-shadow: 0 0 0 1000px var(--oft-surface) inset;
	box-shadow: 0 0 0 1000px var(--oft-surface) inset;
	-webkit-text-fill-color: var(--oft-text);
	caret-color: var(--oft-text);
	/*
	 * Chrome re-applies its own background on an unpredictable delay after the
	 * fill. Parking the transition well beyond any session means the painted
	 * value never arrives rather than arriving late.
	 */
	transition: background-color 100000s ease-in-out 0s;
}

.ota-footer__subscribe input:autofill {
	background: transparent;
	color: var(--oft-text);
}

/*
 * The pill is one row 91px tall. Three separate spacings were stacking inside
 * it and taking it to 136px, all of them written for a form whose submit sits
 * on its own line below the fields:
 *
 *   .gform-footer      16px of vertical padding and a 6px top margin
 *   .ginput_container  16px of bottom margin under the field
 *   .gform_button      8px of bottom margin under the button
 *
 * Gravity Forms scopes its own rules as `.gform_wrapper.gravity-theme .x` and
 * its stylesheet is enqueued after this one, so matching that specificity only
 * draws, and the tie goes to whoever loads last. Naming the theme class here
 * puts these one class ahead and settles it without `!important`. Both the
 * hyphen and underscore class names are listed because Gravity Forms puts both
 * on the same element and has moved between them across versions.
 */
.ota-footer__subscribe .gform_wrapper.gravity-theme .gform-footer,
.ota-footer__subscribe .gform_wrapper.gravity-theme .gform_footer {
	flex: 0 0 auto;
	width: auto;
	margin: 0;
	padding: 0;
}

/*
 * Gravity Forms spaces stacked fields with a bottom margin on the container.
 * In a one field row that margin is dead space under the input, and it pushes
 * the text off the button's centre line.
 */
.ota-footer__subscribe .gform_wrapper.gravity-theme .ginput_container {
	margin: 0;
}

.ota-footer__subscribe .gform_wrapper.gravity-theme .gform_footer .ota-btn {
	margin: 0;
}

/*
 * THE ARROW BADGE, DRAWN HERE RATHER THAN ADDED TO THE MARKUP
 *
 * Gravity_Forms_Buttons puts `.ota-btn ota-btn--primary ota-btn-arrow--none` on
 * every Gravity Forms submit, and the `--none` is load bearing: the shared
 * badge is drawn on an inner `.ota-btn__inner` span that Gravity Forms' button
 * does not have, so a form button without that class reads visibly lopsided.
 * See the "NO ARROW, DELIBERATELY" note in class-gravity-forms-buttons.php.
 *
 * The design does draw the badge on this one button (node 485:24184), so it is
 * rebuilt on the button's own pseudo-elements instead, scoped to the footer.
 * That keeps the decision where it belongs: no filter on a site-wide hook, no
 * markup surgery on a label an editor typed, and every other form's button is
 * exactly as it was. The `--ob-*` tokens are the button stylesheet's own, so the
 * badge picks up the same colours and the same 32px circle as everywhere else.
 */
.ota-footer__subscribe .gform_footer .ota-btn {
	position: relative;
	/* The frame's 29px leading against 9px trailing, which the badge sits in. */
	--ob-pad-end: 9px;

	/*
	 * Named, because the glyph below has to subtract it. Flex puts a gap before
	 * every item after the first, including the glyph, so a glyph pulled back
	 * over the badge lands one gap to the right of centre unless the pull
	 * includes it. That is a 12px error, which is most of the badge's radius.
	 */
	--ofs-gap: 12px;

	display: inline-flex;
	align-items: center;
	gap: var(--ofs-gap);
}

.ota-footer__subscribe .gform_footer .ota-btn::after {
	content: "";
	flex: 0 0 auto;
	width: var(--ob-badge, 32px);
	height: var(--ob-badge, 32px);
	border-radius: 50%;
	background-color: var(--ob-badge-bg);
}

/*
 * THE GLYPH RIDES THE BADGE, RATHER THAN BEING MEASURED FROM THE PILL'S EDGE.
 *
 * This was the known defect carried into PR #3: on the stacked mobile footer
 * the arrow vanished. Absolutely positioned against the button, the glyph is
 * measured from the pill's trailing edge, and that only lands on the badge
 * while the pill is exactly as wide as its own content. It is not: the stacked
 * footer stretches the button to the field's width (308px against 161px on the
 * desktop row) and the button centres its content, so the badge moves to the
 * middle and the glyph stays pinned near the right edge, alone on the fill.
 * Every previous attempt added another magic number to `inset-inline-end`,
 * which can only ever be right at one width.
 *
 * Making the glyph a flex child removes the width from the sum entirely. It is
 * laid out after the badge with `order`, then pulled back over it:
 *
 *   start  -(gap + (badge + icon) / 2) = -36px, which puts its left edge 8px
 *                                 into the badge, so the two share a centre.
 *                                 The gap is in there because flex inserts one
 *                                 before this item too.
 *   end     (badge - icon) / 2  =   8px, which gives back what the pull took,
 *                                 so the glyph contributes zero width and the
 *                                 badge does not shift when it is added
 *                                 (12 gap - 36 + 16 wide + 8 = 0)
 *
 * Both are expressed in the same `--ob-*` tokens as the badge, so a button size
 * change moves them together and there is no number here to go stale.
 *
 * `order: 1` is what puts it after the badge: a `::before` is the first child
 * by default, which would otherwise place the arrow in front of the label.
 */
.ota-footer__subscribe .gform_footer .ota-btn::before {
	content: "";
	order: 1;
	flex: 0 0 auto;
	width: var(--ob-icon, 16px);
	height: var(--ob-icon, 16px);
	margin-inline-start: calc(-1 * (var(--ofs-gap, 12px) + (var(--ob-badge, 32px) + var(--ob-icon, 16px)) / 2));
	margin-inline-end: calc((var(--ob-badge, 32px) - var(--ob-icon, 16px)) / 2);
	background-color: var(--ob-glyph);
	-webkit-mask: var(--ob-arrow) no-repeat center / contain;
	mask: var(--ob-arrow) no-repeat center / contain;
}

/* --- Validation and confirmation, which the frame has no state for -------- */

/*
 * The frame draws no error state, and left alone this one was drawn for it by
 * two stylesheets that have never seen this pill:
 *
 *   .gform_validation_errors  Gravity Forms' summary box, a near white panel
 *                             with a red border and 48px of left padding for its
 *                             icon, sitting above the pill and repeating the
 *                             field's message word for word.
 *   .validation_message       the theme's `#8B0000` filled block with 16px of
 *                             padding, every declaration `!important`
 *                             (_gravity-forms.scss, `.gfield.gfield_error`).
 *
 * The filled block is the worse of the two, because this form is set to
 * `validation_above`: the message renders before the input, inside the pill, so
 * a dark red slab pushed the field out of the pill and off the button's centre
 * line. The summary then said the same sentence again above it.
 *
 * So: one message, not two. The summary is hidden from view but kept in the
 * markup, because Gravity Forms focuses it after an invalid submission and it is
 * what a screen reader hears first; `display: none` would drop that focus on the
 * floor. The field's own message is stripped back to a line of text and lifted
 * out of the flow so the pill stays one row, and the pill's border carries the
 * error instead.
 */

.ota-footer__subscribe .gform_confirmation_message {
	max-width: 372px;
	margin-inline: auto;
	color: var(--oft-text);
	font-size: var(--e-global-typography-small-font-size, 0.9375rem);
	text-align: center;
}

/*
 * Heard, not seen. See the note above before turning this into display: none.
 *
 * Every selector from here down carries `.ota-footer` and, where it is undoing
 * Gravity Forms rather than the theme, `.gform_wrapper.gravity-theme` as well.
 * That is not decoration: Gravity Forms' stylesheet is enqueued after this one,
 * so a selector that only draws with it loses the tie, and the theme's error
 * rules are `!important` on top of three classes. These sit one class ahead of
 * both.
 */
.ota-footer .ota-footer__subscribe .gform_wrapper.gravity-theme .gform_validation_errors {
	position: absolute;
	width: 1px;
	height: 1px;
	margin: -1px;
	padding: 0;
	overflow: hidden;
	clip: rect(0 0 0 0);
	clip-path: inset(50%);
	white-space: nowrap;
	border: 0;
}

/*
 * The pill takes the error the way it takes the focus ring: on the field's
 * behalf, because the field has no edge of its own.
 *
 * `ochre-button` rather than `accent` or a red of our own. `accent` is the role
 * that means "the highlight colour on this theme" and on the theme this footer
 * ships with it resolves to the cyan #49C7DA, which reads as focus, not as a
 * problem. `ochre-button` is warm on every theme by definition. A hard coded red
 * would be the one thing in this footer that does not move with the page's
 * Colour Theme, and there is no error role in the set to reach for.
 */
.ota-footer .ota-footer__subscribe .gform_wrapper.gform_validation_error form {
	position: relative;
	border-color: var(--oft-error);
}

/*
 * Out of flow, under the pill. `position: absolute` against the form is what
 * keeps the pill one row tall: the message is inside `.gfield`, three levels
 * down, so there is no reordering it below the pill without moving markup.
 *
 * `!important` throughout, which is not the habit in this file. The theme sets
 * background, colour, radius, padding, margin and line-height on
 * `.gfield .validation_message` with `!important` on every one of them, so this
 * is the only way to undo it from outside the theme. The alternative was an
 * opt-out flag like the one the input skin uses, and there is no hook on this
 * message to hang one from.
 */
.ota-footer .ota-footer__subscribe .gform_wrapper .gfield .validation_message,
.ota-footer .ota-footer__subscribe .gform_wrapper .gfield_error .validation_message {
	position: absolute !important;
	/* Clear of the 1.5px border, inside the 70px gap above the links row. */
	inset-block-start: calc(100% + 10px) !important;
	inset-inline: 0 !important;
	margin: 0 !important;
	padding: 0 !important;
	border: 0 !important;
	border-radius: 0 !important;
	background: none !important;
	/*
	 * Text in the footer's own text role, not in the error colour. The ochre
	 * reaches 3.8:1 on this footer's background, which is enough for a border and
	 * short of the 4.5:1 a 15px sentence needs. The border and the field carry the
	 * colour; the sentence carries the contrast.
	 */
	color: var(--oft-text) !important;
	font-size: var(--e-global-typography-small-font-size, 0.9375rem) !important;
	line-height: 1.4 !important;
	text-align: center !important;
}

/*
 * And the field itself. Gravity Forms draws `.gfield_error [aria-invalid=true]`
 * as a 1px #C02B0A box with padding of its own, which inside the pill is a
 * second border around a field that is meant to read as a line of text. Off it
 * comes, and the caret and the value take the error colour instead: the value is
 * short, sits at 18px, and is the thing being complained about.
 */
.ota-footer .ota-footer__subscribe .gform_wrapper.gravity-theme .gfield_error [aria-invalid="true"] {
	padding: 0 0 0 8px;
	border: 0;
	color: var(--oft-error);
	caret-color: var(--oft-error);
}

.ota-footer .ota-footer__subscribe .gform_wrapper.gravity-theme .gfield_error [aria-invalid="true"]::placeholder {
	color: var(--oft-error);
	opacity: 0.75;
}

/* --- Links, social, legal ------------------------------------------------ */

.ota-footer__base {
	display: flex;
	flex-direction: column;
	align-items: center;
	/* The frame's own gap inside the bottom group. */
	gap: 27px;
	width: 100%;
	/* And the gap between the subscribe field and that group. */
	margin-block-start: 70px;
}

.ota-footer__nav {
	width: 100%;
}

.ota-footer__nav-list {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: center;
	/* Node 169:7940 sets its links 28px apart. */
	gap: 8px 28px;
	margin: 0;
	padding: 0;
	list-style: none;
}

.ota-footer__nav-list li {
	margin: 0;
	padding: 0;
	list-style: none;
}

/* The hover states are here to hold the colour. See the note on the logo link. */
.ota-footer__nav-list a,
.ota-footer__nav-list a:hover,
.ota-footer__nav-list a:focus-visible {
	color: var(--oft-link);
	/* 15px Medium, 24.75 line height. */
	font-size: 0.9375rem;
	font-weight: 500;
	line-height: 1.65;
	text-decoration: none;
}

/*
 * Must follow the rule above rather than sit beside it: that one sets
 * `text-decoration: none` on the same two states at the same weight, so an
 * underline declared earlier would be turned straight back off.
 */
.ota-footer__nav-list a:hover,
.ota-footer__nav-list a:focus-visible {
	text-decoration: underline;
	text-underline-offset: 0.25em;
}

.ota-footer__nav-list .current-menu-item > a {
	text-decoration: underline;
	text-underline-offset: 0.25em;
}

.ota-footer__social {
	display: flex;
	align-items: center;
	justify-content: center;
	/*
	 * Node 169:7957 draws four 42px circles 10px apart. Enlarged on client
	 * request (Teamwork 49698976, "increase size of social icons") to 56px
	 * circles with a 28px glyph, and the gap opened to 14px to keep the row in
	 * proportion.
	 */
	gap: 14px;
	margin: 0;
	padding: 0;
	list-style: none;
}

.ota-footer__social-item {
	margin: 0;
	padding: 0;
	list-style: none;
}

/*
 * The hover state is here to hold the colour, and it matters more here than
 * anywhere else in this file: the glyphs are inline SVG painted with
 * currentColor, so the theme repainting the anchor repaints the icon itself.
 * See the note on the logo link.
 */
.ota-footer__social-link,
.ota-footer__social-link:hover,
.ota-footer__social-link:focus-visible {
	display: flex;
	align-items: center;
	justify-content: center;
	width: 56px;
	height: 56px;
	border-radius: 50%;
	color: var(--oft-social);
	text-decoration: none;
	transition: color 0.2s ease;
}

/*
 * The glyph changes colour rather than the circle gaining a wash. The earlier
 * version tinted the background 12% ochre, which on the dark themes read as a
 * muddy dark red patch behind the icon and is not a state the style guide has.
 *
 * `white-text` is the role for text that reads on this theme's background, so
 * it resolves white on the dark themes and navy on the light ones. That gives
 * the hover the contrast it needs in both directions without either state
 * having to know which theme it is in.
 */
.ota-footer__social-link:hover,
.ota-footer__social-link:focus-visible {
	color: var(--oft-link);
}

/* currentColor so the ring follows the glyph into its hovered colour. */
.ota-footer__social-link:focus-visible {
	outline: 2px solid currentColor;
	outline-offset: 2px;
}

.ota-footer__social-link svg {
	display: block;
	width: 28px;
	height: 28px;
}

/* The accessible name for an icon-only link. */
.ota-footer__social-label {
	position: absolute;
	width: 1px;
	height: 1px;
	margin: -1px;
	padding: 0;
	overflow: hidden;
	clip: rect(0 0 0 0);
	clip-path: inset(50%);
	white-space: nowrap;
	border: 0;
}

/*
 * The Acknowledgement of Country. Not in the Figma frame: added on client
 * request (Teamwork 49698976). Set in the copyright line's muted role so it
 * reads as part of the footer's legal block, one step larger so a full
 * paragraph is comfortable to read, and held to a measure so it does not run
 * the full 1440 frame as a single line.
 */
.ota-footer__acknowledgement {
	max-width: 46rem;
	margin: 0;
	color: var(--oft-muted);
	/* 14px Light. */
	font-size: 0.875rem;
	font-weight: 300;
	line-height: 1.65;
	text-align: center;
	text-wrap: pretty;
}

.ota-footer__legal {
	margin: 0;
	color: var(--oft-muted);
	/* 13px Light, 21.45 line height. */
	font-size: 0.8125rem;
	font-weight: 300;
	line-height: 1.65;
	text-align: center;
}

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

@media (max-width: 782px) {
	.ota-footer {
		padding-block: 48px 40px;
	}

	.ota-footer__base {
		margin-block-start: 48px;
	}

	.ota-footer__tagline {
		font-size: 1.625rem;
	}

	/*
	 * The pill breaks. At this width the field and a 62px button cannot both sit
	 * on one line without the field being too narrow to read what was typed into
	 * it, so the pill becomes a rounded box with the button under the field.
	 */
	.ota-footer__subscribe form {
		flex-direction: column;
		align-items: stretch;
		gap: 12px;
		padding: 16px;
		border-radius: 24px;
	}

	.ota-footer__subscribe input[type="text"],
	.ota-footer__subscribe input[type="email"] {
		padding: 4px 8px;
	}

	.ota-footer__subscribe .gform_footer .ota-btn {
		justify-content: center;
		width: 100%;
	}

	/*
	 * Nothing to correct here any more. The glyph is laid out against the badge
	 * rather than against the pill, so it follows it when the button stretches
	 * to the field's width. This override used to add 16px to the trailing
	 * inset, which is the number that was right on one phone and wrong on the
	 * rest, and it is what made the arrow disappear.
	 */

	/*
	 * The error message comes back into the flow once the pill has broken. Out of
	 * flow it reserved no height, and under a box this tall that put a two line
	 * message inside the 48px above the links row with nothing to spare. In flow it
	 * pushes the links down instead, which is what a taller box should do.
	 *
	 * `order` rather than markup: the form is set to `validation_above`, so the
	 * message renders before the field. Under a stacked field it belongs after it.
	 */
	.ota-footer .ota-footer__subscribe .gform_wrapper .gfield_error {
		display: flex;
		flex-direction: column;
	}

	.ota-footer .ota-footer__subscribe .gform_wrapper .gfield .validation_message,
	.ota-footer .ota-footer__subscribe .gform_wrapper .gfield_error .validation_message {
		position: static !important;
		order: 1;
		margin-block-start: 8px !important;
		text-align: start !important;
	}

	/* The error state keeps the stacked field's own padding, not the pill's. */
	.ota-footer .ota-footer__subscribe .gform_wrapper.gravity-theme .gfield_error [aria-invalid="true"] {
		padding: 4px 8px;
	}

	/*
	 * The mark loses its bleed and most of its size. At 583px wide against a
	 * 390px screen it stops reading as a graphic in the corner and becomes a
	 * wash behind the copyright line.
	 *
	 * NO OPACITY. It used to fade to 0.6 here, which worked while the overlay
	 * role resolved to ochre on Ash: a pale ochre on sand still read as brand.
	 * Since overlay moved to navy on 14 Aug 2026 the same 0.6 lands on a muddy
	 * grey that belongs to no palette on the site, which is what it looked like
	 * on a narrow window.
	 *
	 * TAKING THE FADE OFF MEANT MOVING IT. The fade was doing a second job
	 * nobody had written down: at 60% and a 30/40 bleed the mark reaches up
	 * under the link row and across the copyright line, and 0.6 was what kept
	 * that readable. Navy text over a solid navy mark is not readable at any
	 * z-index, so the mark is smaller here and pushed further into the corner
	 * until it clears the copy instead of being faded out from behind it.
	 */
	.ota-footer__mark {
		width: 48%;
		transform: translate(-42%, 56%) scaleX(-1);
	}
}

/*
 * Phone widths need one more step down. The copyright line is centred and runs
 * nearly the full width at 390, so there is no corner left for the mark to sit
 * in: at 48% it still reaches under the "© 2026". Dropping it further down than
 * across is what buys the room, because the line is wide but shallow, so the
 * mark ends up as a low arc under the copy rather than a shape beside it.
 */
@media (max-width: 430px) {
	.ota-footer__mark {
		width: 44%;
		transform: translate(-46%, 74%) scaleX(-1);
	}
}

/*
 * No subscribe field: logged-in members, who manage their newsletters on the
 * dashboard (see Updates_Signup), and any site with no form chosen. The 70px
 * above the links is the frame's gap under the subscribe pill, and with no
 * pill it opened a hole under the tagline. Pulled in to the brand column's
 * own rhythm instead. `:has()` rather than a modifier class from PHP so the
 * rule follows whatever the renderer actually printed.
 *
 * Specificity 0,3,0 against the plain 0,1,0 margin, inside and outside the
 * narrow query, so source order does not matter for this one.
 */
.ota-footer__brand:not(:has(.ota-footer__subscribe)) + .ota-footer__base {
	margin-block-start: 48px;
}

@media (max-width: 782px) {
	.ota-footer__brand:not(:has(.ota-footer__subscribe)) + .ota-footer__base {
		margin-block-start: 36px;
	}
}

@media (prefers-reduced-motion: reduce) {
	.ota-footer__social-link {
		transition: none;
	}
}
