/**
 * OTA header and mega menu.
 *
 * This styles markup the plugin owns end to end, so there are no overrides of
 * the base theme here and no ID selectors used to win specificity fights.
 *
 * No typography on purpose. Font family, size and weight come from the
 * Elementor globals and the theme; this file does layout and colour only.
 *
 * Colour comes from the colour theme roles where the design themes it. The
 * dropdown panel is deliberately fixed: only the bar re-colours per theme.
 */

.ota-header {
	/* Bar, themed. Falls back to the Ash values so the header is never
	   unstyled if no colour theme is configured. */
	--ota-bar-bg: var(--ota-background, #f0e7d8);
	--ota-bar-text: var(--ota-text, #003038);
	--ota-bar-divider: var(--ota-divider, rgba(0, 48, 56, 0.2));
	--ota-bar-logo: var(--ota-logo, #f04c3a);
	--ota-bar-active-bg: var(--ota-active-bg, #003038);
	--ota-bar-active-text: var(--ota-active-text, #f0e7d8);
	--ota-bar-cta-bg: var(--ota-ochre-button, #f04c3a);
	--ota-bar-cta-text: var(--ota-ochre-button-text, #000000);
	/* The darker of the two button roles. Join in the mobile login sheet takes
	   this where Log in takes the ochre one, which is how the design pairs
	   them, so both follow the colour theme rather than being pinned. */
	--ota-bar-join-bg: var(--ota-cta-bg, #003038);
	--ota-bar-join-text: var(--ota-cta-text, #ffffff);

	/* Panel, fixed by design: the dropdown does not follow the theme. */
	--ota-menu-bg: #ffffff;
	--ota-menu-text: #003038;
	--ota-menu-heading: #005361;
	--ota-menu-divider: rgba(0, 48, 56, 0.14);
	--ota-menu-rule: rgba(0, 48, 56, 0.1);
	--ota-menu-field-border: rgba(0, 48, 56, 0.3);
	--ota-menu-accent: #f04c3a;
	--ota-menu-accent-text: #ffffff;
	--ota-menu-accent-soft: color-mix(in srgb, var(--ota-menu-accent) 10%, transparent);
	--ota-menu-muted: #f0e7d8;
	--ota-menu-placeholder: #8a9699;
	--ota-menu-scrim: rgba(0, 0, 0, 0.25);
	--ota-menu-shadow: rgba(0, 24, 30, 0.12);
	--ota-menu-shadow-soft: rgba(0, 24, 30, 0.06);
	/* The panel's own link pill, painted on hover. Figma binds bar/cta-bg and
	   bar/cta-text, which in the panel's mode are the navy fill and the white
	   on it. */
	--ota-menu-link-bg: #003038;
	--ota-menu-link-text: #ffffff;
	--ota-menu-feature-bg: #003038;
	--ota-menu-feature-text: #f0e7d8;
	--ota-menu-feature-eyebrow: #49c7da;
	/* The CTA dot on hover. Figma binds these to bar/cta-bg and bar/cta-text,
	   which in this card's mode resolve to the card's own text and background,
	   so they are expressed that way rather than pinned to the ochre button. */
	--ota-menu-feature-dot-bg: var(--ota-menu-feature-text);
	--ota-menu-feature-dot-icon: var(--ota-menu-feature-bg);
	/* Placeholder until the global radius scale lands, at which point this
	   should point at that token rather than carry its own value. */
	--ota-menu-feature-radius: 14px;
	--ota-menu-on-feature: #ffffff;
	--ota-menu-on-feature-line: color-mix(in srgb, var(--ota-menu-on-feature) 50%, transparent);

	position: fixed;
	z-index: 100;
	top: var(--ota-admin-bar, 0px);
	left: 0;
	right: 0;
	background: var(--ota-bar-bg);
	color: var(--ota-bar-text);
}

/*
 * The open mobile menu clears the theme's back to top button.
 *
 * That button is `body > .back-to-top` at `z-index: 9999`, a sibling of the
 * header rather than a descendant, so nothing inside the header at 100 can get
 * over it: the whole header is one stacking context and its children compete
 * only with each other. The menu covers the viewport when it is open and the
 * button floated on top of it, over the account strip in the bottom right.
 *
 * Raised only while the menu is open, keyed off the class ota-mega-menu.js
 * already puts on the body, rather than lifting the header everywhere. The
 * resting header has no quarrel with anything at this level and a permanent
 * 10000 would put it over any plugin that reasonably expects to sit above a
 * site header. Still below `#wpadminbar` at 99999, which should stay on top.
 */
body.ota-nav-open .ota-header {
	z-index: 10000;
}

/*
 * How far down the page starts. Carried as a variable because two things need
 * it: the fixed header sits below the admin bar, and the mobile sheet's height
 * is the viewport less the header less this. WordPress switches the admin bar
 * to its tall variant at 782px, which is not where this menu's breakpoint is,
 * so the two can no longer share a media query.
 */
body.admin-bar {
	--ota-admin-bar: 32px;
}

@media screen and (max-width: 782px) {
	body.admin-bar {
		--ota-admin-bar: 46px;
	}
}

/*
 * At 600px and below core switches #wpadminbar to position: absolute, so it
 * scrolls away with the page. Holding the fixed header 46px down from there
 * leaves a permanent empty band above it for any logged-in user on a phone.
 * Sitting at the top instead means the bar overlaps the header at rest, which
 * is what core's own fixed elements do.
 */
@media screen and (max-width: 600px) {
	body.admin-bar {
		--ota-admin-bar: 0px;
	}

	/*
	 * And the spacer has to give back what the admin bar already took.
	 *
	 * Core adds `html { margin-top: 46px }` for the admin bar, which moves the
	 * whole document down. The header is fixed, so it ignores that and sits at
	 * the top of the viewport, meaning its first 46px are behind the bar and
	 * only the rest of it actually covers any document. The spacer was still
	 * reserving the header's full height inside a document that had already
	 * been pushed down, so the two offsets added up and left a 46px band of
	 * page background between the header and the first block. On a dark hero
	 * that reads as a stripe of the wrong colour.
	 *
	 * Subtracting the bar's height is what makes the sum come out once rather
	 * than twice. Clamped at zero so a short header cannot produce a negative.
	 *
	 * Only at this width. Above it the admin bar is fixed and
	 * `--ota-admin-bar` already holds the header below it, so the spacer is
	 * correct as measured.
	 */
	body.admin-bar .ota-header__spacer {
		height: max(0px, calc(var(--ota-header-height, 0px) - 46px));
	}
}

/*
 * Holds the space the fixed header no longer occupies. The height is written
 * by the script from the header's real size, so it stays correct as the bar
 * wraps or the utility strip changes.
 */
.ota-header__spacer {
	/* The theme makes body a column flex container, so a plain height would be
	   shrunk away. */
	flex: none;
	height: var(--ota-header-height, 0px);
}

/*
 * Hover as well as rest, and that is not belt and braces.
 *
 * The theme sets `a:hover { color: $at-color-text-body-link }`, which is navy and
 * the same weight as the rest state here, so it won on load order and every link
 * in the header went navy under the pointer. On the bar and on the featured card,
 * both of which are navy surfaces, the label disappeared. Naming the state takes
 * this to 0,2,1 and settles it. Anything in here that wants its own hover colour
 * is further down the file and still wins, since the panel's link pill and the
 * account card's links are all at least as specific.
 */
.ota-header a,
.ota-header a:hover {
	color: inherit;
}

/*
 * A display declared on a class outranks the browser's own `[hidden]` rule, so
 * anything in here that is toggled by the attribute has to be told again. The
 * search and reveal controls both ship hidden and are revealed by script.
 */
.ota-header [hidden] {
	display: none;
}

/* --- Search -------------------------------------------------------------- */

/*
 * Two of these. In the utility strip the field takes the Search button's place
 * and the row, being right aligned, grows leftwards to make room. Below the nav
 * breakpoint the strip is gone, so a drawer under the bar takes over. Only one
 * is ever on screen; their parents see to that.
 */

/* --- Search: inline in the utility strip --- */

/*
 * Grows out of the Search button's slot rather than appearing whole. Width is
 * animated through max-width because the row is right aligned, so the field
 * opens leftwards on its own. `hidden` stays the resting state for no-JS; the
 * script drops it a frame before adding the class so there is something to
 * transition from, and puts it back once the collapse has finished.
 */
.ota-search--utility {
	display: flex;
	flex: 0 1 32.1875rem;
	min-width: 0;
	max-width: 0;
	overflow: hidden;
	opacity: 0;
	transition: max-width 0.28s ease, opacity 0.2s ease;
}

.ota-search--utility.is-open {
	max-width: 32.1875rem;
	opacity: 1;
}

/*
 * Fixed 30px to match the controls beside it. Held by height rather than
 * padding because the input's line height is inherited, so padding alone gives
 * a taller box on any site whose body type is larger than expected.
 */
.ota-search--utility .ota-search__form {
	display: flex;
	flex: 1 1 auto;
	align-items: center;
	gap: 0.5rem;
	min-width: 0;
	height: 1.875rem;
	padding: 0 0.75rem;
	border-bottom: 1px solid var(--ota-bar-text);
}

.ota-search--utility .ota-search__field {
	gap: 0.5rem;
	border: 0;
}

.ota-search--utility .ota-search__input {
	padding: 0;
}

.ota-search--utility .ota-search__input::placeholder {
	color: color-mix(in srgb, var(--ota-bar-text) 55%, transparent);
}

/* The collapsed button and the open field occupy the same slot. */
.ota-utility__search[aria-expanded="true"] {
	display: none;
}

.ota-search__go {
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	width: 1.125rem;
	height: 1.125rem;
	padding: 0;
	border: 0;
	border-radius: 50%;
	background: var(--ota-bar-join-bg);
	color: var(--ota-bar-join-text);
	cursor: pointer;
}

.ota-search__go .ota-icon--arrow {
	width: 0.5625rem;
	height: 0.5625rem;
}

/* --- Search: drawer under the bar, once the strip is gone --- */

/* The drawer opens downward instead. max-height rather than height, because
   the content's height is not known up front. */
.ota-search--bar {
	display: none;
	max-height: 0;
	overflow: hidden;
	opacity: 0;
	border-top: 1px solid var(--ota-bar-divider);
	background: var(--ota-menu-bg);
	color: var(--ota-menu-text);
	transition: max-height 0.28s ease, opacity 0.2s ease;
}

.ota-search--bar.is-open {
	max-height: 10rem;
	opacity: 1;
}

.ota-search--bar .ota-search__form {
	display: flex;
	align-items: center;
	gap: 0.75rem;
	max-width: 1440px;
	margin: 0 auto;
	padding: 0.5rem 2rem;
}

/*
 * The rule belongs to the row, not the input, so focus reads as a line under
 * the whole field rather than the browser's box around a borderless input.
 * Same treatment the login card's fields use.
 */
.ota-search__field {
	display: flex;
	flex: 1 1 auto;
	align-items: center;
	gap: 0.75rem;
	min-width: 0;
	border-bottom: 1px solid var(--ota-menu-rule);
}

.ota-search--bar .ota-search__field:focus-within {
	border-bottom-color: var(--ota-menu-accent);
}

.ota-search__form .ota-icon--search {
	flex: none;
	opacity: 0.55;
}

.ota-search__input {
	flex: 1 1 auto;
	min-width: 0;
	padding: 0.85rem 0;
	border: 0;
	background: none;
	color: inherit;
	font: inherit;
}

/* Scoped past `.ota-header :focus-visible`, which would otherwise draw a box
   around a field that already shows focus on its underline. */
.ota-header .ota-search__input:focus-visible {
	outline: none;
}

/*
 * The browser draws its own clear button inside a search input once it has a
 * value. It cannot be recoloured, and on the dark bar it all but disappears,
 * so it is suppressed in favour of the one below.
 */
.ota-search__input::-webkit-search-cancel-button,
.ota-search__input::-webkit-search-decoration {
	-webkit-appearance: none;
	appearance: none;
	display: none;
}

.ota-search__clear {
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	width: 1.375rem;
	height: 1.375rem;
	padding: 0;
	border: 0;
	border-radius: 50%;
	background: none;
	color: inherit;
	opacity: 0.7;
	cursor: pointer;
}

.ota-search__clear:hover,
.ota-search__clear:focus-visible {
	opacity: 1;
}

.ota-search__input::placeholder {
	color: var(--ota-menu-placeholder);
	opacity: 1;
}

.ota-search__input:focus {
	outline: none;
}

.ota-search__submit {
	flex: none;
	padding: 0.55rem 1.25rem;
	border: 0;
	border-radius: 999px;
	background: var(--ota-bar-cta-bg);
	color: var(--ota-bar-cta-text);
	font: inherit;
	cursor: pointer;
}

.ota-search__close {
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	width: 2.25rem;
	height: 2.25rem;
	padding: 0;
	border: 0;
	border-radius: 50%;
	background: none;
	color: inherit;
	cursor: pointer;
}

.ota-search__close:hover {
	background: var(--ota-menu-muted);
}

/* --- Utility bar -------------------------------------------------------- */

.ota-utility {
	border-bottom: 1px solid var(--ota-bar-divider);
}

.ota-utility__inner,
.ota-header__inner {
	display: flex;
	align-items: center;
	max-width: 1440px;
	margin: 0 auto;
	padding-inline: 2rem;
}

.ota-utility__inner {
	justify-content: flex-end;
	/* 18px between the groups, which is what the design's Membership row has
	   around its divider. Login and join pair closer than that: see the group
	   below. */
	gap: 1.125rem;
	padding-block: 0.5625rem;
}

/*
 * THE STRIP'S CONTROLS ARE THE DESIGN'S BUTTONS
 *
 * Figma draws all three as the Button component: Search and Member Login Card
 * as Ghost, Become a member as Primary in ochre. So the markup carries the
 * `.ota-btn` classes and assets/css/ota-buttons.css paints them. That is what
 * keeps the bar's hover, focus ring and ochre pill the same drawing as the
 * buttons in the page below rather than a second one that can drift.
 *
 * Three things are left for the bar to own.
 *
 * Size. The design's Small is 52px tall and the strip it draws is 48px, so the
 * bar is not a size in that scale: its pills are 30px with 14px labels. These
 * tokens are that size, in the names ota-buttons.css consumes. `--ob-badge` is
 * the glyph rather than a circle badge, because the icons here are real markup
 * and the pill's vertical padding is derived from this value.
 *
 * Colour, for the two Ghosts. Their fill is the bar's own text colour, so they
 * follow the colour theme with the rest of the strip. The site's CTA role would
 * put navy on a navy bar.
 *
 * Hover, for the login control. See the exception below.
 *
 * Two weights, deliberately.
 *
 * The tokens and the bar's colours are 0,2,0, above the 0,1,0 ota-buttons.css
 * declares its own defaults at, so the bar's size holds whichever order the two
 * stylesheets load in. Setting them at 0,1,0 does not work: a custom property is
 * resolved per element like any other declaration, so the baseline's Medium won
 * on load order and the strip came out 64px tall.
 *
 * The resets are 0,1,0 and lose to ota-buttons.css on purpose, since that is the
 * file that should be painting these. It is enqueued at priority 20 against this
 * file's 10. If the button design is switched off in the customiser, what is left
 * is the plain text controls, with a themed ochre pill, that the strip had before.
 */
.ota-utility .ota-utility__item,
.ota-utility .ota-utility__join {
	--ob-height: 30px;
	--ob-badge: 18px;
	--ob-icon: 14px;
	--ob-font-size: 14px;
	--ob-pad-inline: 12px;
	--ob-pad-badge-side: 12px;
	--ob-gap: 8px;
	--ob-border: 1px;
}

.ota-utility .ota-utility__item {
	--ob-fill: var(--ota-bar-text);
	--ob-on-fill: var(--ota-bar-bg);
}

.ota-utility__item,
.ota-utility__join {
	display: inline-flex;
	align-items: center;
	gap: var(--ob-gap, 0.5em);
	/* The design's 6px and 12px. A shorthand, so the three longhands
	   ota-buttons.css derives from the height replace it whole when it is there,
	   and the pill is not left flush against its label when it is not. */
	padding: 0.375rem 0.75rem;
	border: 0;
	background: none;
	font: inherit;
	text-decoration: none;
	cursor: pointer;
}

/*
 * The theme underlines a link on hover, which is right for a link and wrong for
 * a pill: the two controls that are anchors came out underlined inside their own
 * button. The states these controls do have are the fill and the outline above.
 */
.ota-utility .ota-utility__item:hover,
.ota-utility .ota-utility__join:hover {
	text-decoration: none;
}

/*
 * Past `.ota-header a`, which would otherwise take the paint off the two controls
 * that are links rather than buttons. The token is read rather than restated, so
 * the type's hover swap still reaches them, and it falls back to inherit when the
 * button stylesheet is not loaded. Hover is named because the rule it has to beat
 * names it too.
 */
.ota-header .ota-utility__item,
.ota-header .ota-utility__item:hover {
	color: var(--ob-text, inherit);
}

/* The join's fallback is its own role rather than the bar's text: this pill is
   ochre either way, and ochre wants the black the contrast fix put on it. */
.ota-header .ota-utility__join,
.ota-header .ota-utility__join:hover {
	color: var(--ob-text, var(--ota-bar-cta-text));
}

/*
 * The one place the bar departs from the shared button rules.
 *
 * Ghost inverts to a solid fill on hover everywhere else. The design's Member
 * Login Card does not: its hover is a 1px outline in the bar's text colour with
 * no fill, which is what the screenshots of the bar show. This is 0,4,0 so it
 * holds over ota-buttons.css's 0,3,0 whichever order the two load in.
 */
.ota-utility .ota-btn.ota-btn--ghost:hover {
	--ob-bg: transparent;
	--ob-text: var(--ob-fill);
	--ob-line: var(--ob-fill);
}

/*
 * Login and join sit closer to each other than to the rest of the row: the
 * design pairs them at 8px inside the row's 18px.
 */
.ota-utility__group {
	display: flex;
	align-items: center;
	gap: 0.5rem;
}

/* 16px, as the design draws it, rather than the full height of the row. */
.ota-utility__divider {
	width: 1px;
	height: 1rem;
	align-self: center;
	background: var(--ota-bar-divider);
}

.ota-utility__avatar img {
	display: block;
	width: 1.4em;
	height: 1.4em;
	border-radius: 50%;
	object-fit: cover;
}

/*
 * Become a member, the design's Primary in ochre. The pill is stated here as
 * well as by `.ota-btn-colour--ochre`, at a weight ota-buttons.css outranks, so
 * the call to action is still an ochre pill if the button design is switched
 * off. Both read the same colour theme role, so they cannot disagree.
 */
.ota-utility__join {
	border-radius: 999px;
	background: var(--ota-bar-cta-bg);
}

/*
 * The design sets this label in Medium and the other two in Bold. Nothing in the
 * type scale is 14px or weight 500, so the bar carries its own numbers here;
 * 0,2,0 to hold over the button's own Bold.
 */
.ota-utility .ota-utility__join {
	font-weight: 500;
}

.ota-utility__join:hover .ota-icon--arrow {
	transform: translateX(0.2rem);
}

/* --- Main bar ----------------------------------------------------------- */

.ota-header__inner {
	gap: 1.5rem;
	padding-block: 1rem;
}

.ota-header__logo {
	flex: none;
	display: flex;
	align-items: center;
}

/*
 * Both logo heights are the frame's values plus 30%, Teamwork 49453520
 * (3 Sep 2026): the inline SVG from 3.25rem to 4.25rem, the `img` fallback
 * from 3.5rem to 4.5rem. Nothing pins the bar's height, so it grows by the
 * same 1rem around the mark rather than clipping it.
 */
.ota-header__logo img {
	display: block;
	width: auto;
	max-height: 4.5rem;
}

/*
 * The SVG logo is inlined so its fill can follow the theme. Its paths are
 * rewritten to currentColor, so setting colour here paints the whole mark.
 */
/* Two classes deep so it beats `.ota-header a { color: inherit }` above,
   which would otherwise paint the logo in the bar's text colour. */
.ota-header .ota-header__logo-link {
	display: block;
	color: var(--ota-bar-logo);
}

.ota-header__logo-svg {
	display: block;
	width: auto;
	height: 4.25rem;
}

/*
 * The cart. One in the utility strip, one in the bar's controls, each shown
 * only where its parent is. Same pill as the other utility controls, and the
 * glyph is inline SVG on currentColor so it takes the bar's colour like search.
 */
.ota-cart {
	position: relative;
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	padding: 0.375rem 0.75rem;
	border-radius: 999px;
	color: inherit;
	text-decoration: none;
}

/* Sized in em so it tracks whatever type the bar inherits, keeping this file
   to layout and colour. */
.ota-cart__count {
	position: absolute;
	top: -0.1em;
	right: 0;
	min-width: 1.5em;
	padding: 0.05em 0.35em;
	border-radius: 999px;
	background: var(--ota-bar-cta-bg);
	color: var(--ota-bar-cta-text);
	text-align: center;
}

.ota-cart__count[hidden] {
	display: none;
}

/*
 * Search and the burger travel together. On desktop the whole group is hidden:
 * search lives in the utility strip and there is no burger. The group appears
 * once the nav collapses, and search only joins it once the utility strip is
 * gone, so the two search controls are never on screen at the same time.
 */
.ota-header__actions {
	display: none;
	align-items: center;
	gap: 0.125rem;
	margin-left: auto;
}

/* Both a link and a button, depending on whether script ran, so it carries the
   button resets as well. */
.ota-header__search {
	display: none;
	align-items: center;
	justify-content: center;
	width: 2.625rem;
	height: 2.625rem;
	padding: 0;
	border: 0;
	border-radius: 50%;
	background: none;
	color: inherit;
	font: inherit;
	text-decoration: none;
	cursor: pointer;
}

.ota-header__search .ota-icon {
	width: 1.25rem;
	height: 1.25rem;
}

.ota-header__burger {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 2.75rem;
	height: 2.75rem;
	padding: 0;
	border: 0;
	border-radius: 50%;
	background: var(--ota-bar-active-bg);
	color: var(--ota-bar-active-text);
	cursor: pointer;
}

/* Both glyphs ship in the button and CSS picks one, so no script rewrites the
   button's contents on toggle. */
.ota-header__burger .ota-icon--close,
.ota-header__burger[aria-expanded="true"] .ota-icon--burger {
	display: none;
}

.ota-header__burger[aria-expanded="true"] .ota-icon--close {
	display: block;
}

/* --- Nav ---------------------------------------------------------------- */

.ota-nav {
	margin-left: auto;
}

.ota-nav__list {
	display: flex;
	align-items: center;
	gap: 0.15rem;
	margin: 0;
	padding: 0;
	list-style: none;
}

.ota-nav__item {
	display: flex;
	align-items: center;
}

.ota-nav__toggle,
.ota-nav__link {
	display: inline-flex;
	align-items: center;
	gap: 0.4em;
	padding: 0.5em 0.75em;
	border: 0;
	border-radius: 999px;
	background: transparent;
	color: inherit;
	font: inherit;
	white-space: nowrap;
	text-decoration: none;
	cursor: pointer;
}

.ota-nav__toggle:hover,
.ota-nav__link:hover,
.ota-nav__item--current > .ota-nav__toggle,
.ota-nav__item--current > .ota-nav__link {
	text-decoration: underline;
	text-underline-offset: 0.3em;
}

/*
 * The open item's pill is the panel's own colour carried up into the bar: white,
 * with the panel's navy on it and the chevron in the brand ochre, which is how
 * Figma exports that glyph. Those are the panel's fixed values rather than the
 * bar's active roles, for the same reason the panel does not follow the colour
 * theme: the pill and the panel are one surface and it reads as a tab into it.
 * The active roles are still what the burger takes.
 */
.ota-nav__toggle[aria-expanded="true"] {
	background: var(--ota-menu-bg);
	color: var(--ota-menu-text);
	text-decoration: none;
}

.ota-nav__toggle[aria-expanded="true"] .ota-icon--chevron {
	color: var(--ota-menu-accent);
}

.ota-icon--chevron {
	flex: none;
	transition: transform 0.18s ease;
}

/*
 * The close glyph comes from the Font Awesome kit, which sizes its icons to 1em
 * and would otherwise track whatever type it inherits. Sized here so it holds
 * whether it is still the `<i>` or the `<svg>` the kit swaps in.
 */
.ota-header .ota-icon--close {
	width: 1.125rem;
	height: 1.125rem;
}

.ota-nav__toggle[aria-expanded="true"] .ota-icon--chevron,
.ota-utility__account[aria-expanded="true"] .ota-icon--chevron {
	transform: rotate(180deg);
}

.ota-header :focus-visible {
	outline: 2px solid currentColor;
	outline-offset: 2px;
}

/* --- Panel -------------------------------------------------------------- */

/*
 * The header is the containing block, so the panel spans it with no
 * measuring. That is the whole benefit of owning the markup: the previous
 * version had to be positioned from JavaScript because the theme's nav item
 * was position:relative and its header carried a transform.
 */
.ota-nav__panel {
	position: absolute;
	z-index: 10;
	top: 100%;
	left: 0;
	width: 100%;
	/*
	 * Teamwork 49530951. The panel is as tall as its content, and the header
	 * above it is fixed, so on a short viewport the bottom of the panel fell
	 * past the bottom of the screen with no way to reach it: the page scrolls
	 * behind a fixed header, not the panel hanging off it. Measured on a 650px
	 * viewport the last 58px were unreachable, which is what a 768px laptop
	 * gives once the browser's own chrome is taken off.
	 *
	 * Cap it at what is actually left below the header and let it scroll. The
	 * two custom properties are the same pair the mobile sheet already uses for
	 * this at the foot of this file: --ota-header-height is measured in
	 * ota-mega-menu.js and kept current by a ResizeObserver, and
	 * --ota-admin-bar is the strip above the header when one is signed in.
	 * dvh second so a browser that has it wins, since on mobile Safari vh is
	 * the larger, address-bar-hidden height and would overshoot.
	 *
	 * overflow-x is pinned to hidden rather than left alone: with one axis set
	 * to auto the other computes from visible to auto too, and that would hang
	 * a horizontal scrollbar under a panel that has nothing to scroll sideways.
	 *
	 * overscroll-behavior for the same reason the mobile sheet has it: the panel
	 * is a scroll container now, and a trackpad flick that reaches its end would
	 * otherwise chain to the document and scroll the page behind the open menu.
	 * Body scroll is only locked for the sheet, so nothing else stops that here.
	 *
	 * The cap is a desktop-only concern. The sheet resets it at the foot of this
	 * file, where the panel flows at full height inside the list instead.
	 */
	max-height: calc(100vh - var(--ota-header-height, 0px) - var(--ota-admin-bar, 0px));
	max-height: calc(100dvh - var(--ota-header-height, 0px) - var(--ota-admin-bar, 0px));
	overflow-x: hidden;
	overflow-y: auto;
	overscroll-behavior: contain;
	background: var(--ota-menu-bg);
	color: var(--ota-menu-text);
}

.ota-nav__panel[hidden],
.ota-header__account[hidden] {
	display: none;
}

.ota-nav__panel-inner {
	display: grid;
	grid-template-columns: minmax(0, 1fr) minmax(0, 24rem);
	align-items: stretch;
	max-width: 1440px;
	margin: 0 auto;
}

.ota-nav__panel-main {
	padding: 2.5rem 2rem 3rem;
}

/* The same 24px lead-in the column headings and their links now carry, so the
   panel's title lines up with the labels under it as it does in the design. */
.ota-nav__panel-head {
	display: flex;
	flex-wrap: wrap;
	align-items: baseline;
	gap: 0.5rem 1rem;
	margin-bottom: 2rem;
	padding-inline-start: 1.5rem;
}

.ota-nav__panel-title,
.ota-nav__panel-tagline,
.ota-nav__column-title {
	margin: 0;
}

.ota-nav__panel-title,
.ota-nav__column-title {
	color: var(--ota-menu-heading);
}

/*
 * Heading/H4 for the panel title, Label/Eyebrow for the column titles, both
 * from the Elementor global fonts with the Figma numbers as fallbacks.
 *
 * Neither had any type of its own before. They are `<p>` in nav-panel.php, not
 * headings, so nothing in the cascade reached them and both inherited body
 * copy: the panel title read at the same size as the links beneath it and the
 * column titles were indistinguishable from their own list.
 *
 * The `<a>` inside a column title inherits all of this; only its colour and
 * underline are set, further down.
 *
 * COLUMN TITLES ARE LABELS, NOT ROWS. Teamwork 49453523, from the client's
 * Figma comment #56: on the sandbox the column titles ("OTA", "Partner with
 * us") and the page links under them read as the same thing, 17px bold teal
 * over 16px navy in one face, and she asked for the titles to feel like
 * headings and the links like links. The design's Eyebrow at 17px is what
 * produced that, so the title keeps the Eyebrow's face, weight and tracking
 * but drops to 15px and gains a hairline under it, so it reads as the
 * column's label rather than its first row. Sentence case is kept on
 * purpose: the client has a no-uppercase requirement, so the size, the
 * tracking and the rule do the differentiating. The links keep the full
 * 16px and are now the only full-size text in the column. Nothing about
 * the links changes.
 */
.ota-nav__panel-title {
	font-size: var(--e-global-typography-h4-font-size, 1.5rem);
	font-weight: var(--e-global-typography-h4-font-weight, 400);
	line-height: var(--e-global-typography-h4-line-height, 1.08em);
	letter-spacing: var(--e-global-typography-h4-letter-spacing, -0.24px);
}

.ota-nav__column-title {
	font-size: 0.9375rem;
	font-weight: var(--e-global-typography-eyebrow-font-weight, 700);
	line-height: 1.4;
	letter-spacing: var(--e-global-typography-eyebrow-letter-spacing, 1px);
	padding-bottom: 0.625rem;
	border-bottom: 1px solid var(--ota-menu-divider);
}

.ota-nav__columns {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(11rem, 1fr));
	gap: 1.5rem 2rem;
}

/*
 * A panel that is one flat list, Membership and Communities, has a single
 * headingless column. `auto-fit` collapses the empty tracks beside it and hands
 * it the whole row, which would run the links the full width of the panel and
 * leave the hover pill stretched across empty space. Capping it keeps the rows
 * the same width they are in every other panel.
 */
.ota-nav__column--no-heading:only-child {
	max-width: 20rem;
}

/* The same lead-in as the links below it, so heading and labels line up and the
   pill sits around the text rather than shifting it. */
.ota-nav__column-title {
	margin-bottom: 1rem;
	padding-inline: 1.5rem 1rem;
}

/*
 * 8px between rows, as the design's stack of mega-lists has it. Each row then
 * carries its own 8px of padding, which is what takes the pitch to the design's
 * 52px; a gap on its own gave 37px and the columns read as one block of text.
 */
.ota-nav__links {
	display: grid;
	gap: 0.5rem;
	margin: 0;
	padding: 0;
	list-style: none;
}

/*
 * A Navigation Link from the design: a pill that only paints on hover, with a
 * badge at its trailing edge that only appears then. 24px of lead-in before the
 * label and 12px after the badge, which is the room the pill needs to sit
 * around the label rather than against it.
 */
.ota-nav__links a {
	display: flex;
	align-items: center;
	gap: 0.75rem;
	padding: 0.5rem 0.75rem 0.5rem 1.5rem;
	border-radius: 999px;
	color: var(--ota-menu-text);
	text-decoration: none;
	transition:
		background-color 0.18s ease,
		color 0.18s ease;
}

.ota-nav__link-label {
	flex: 1 1 auto;
}

.ota-nav__links a:hover,
.ota-nav__links a:focus-visible {
	background: var(--ota-menu-link-bg);
	color: var(--ota-menu-link-text);
	text-decoration: none;
}

.ota-nav__column-title a:hover {
	text-decoration: underline;
	text-underline-offset: 0.25em;
}

/*
 * THE PANEL TITLE IS THE WAY TO THE TOP LEVEL PAGE. The top level item opens
 * the panel and stays a single control, so when it has a page of its own the
 * big title inside the panel links to it, quiet until hovered like the column
 * headings. Teamwork 49688018, agreed with the client over splitting the label
 * into a link and a separate arrow.
 */
.ota-nav__panel-title a {
	color: inherit;
	text-decoration: none;
}

.ota-nav__panel-title a:hover,
.ota-nav__panel-title a:focus-visible {
	text-decoration: underline;
	text-underline-offset: 0.18em;
	text-decoration-thickness: 2px;
}

/* The same link for the mobile sheet, which hides the panel head. Desktop has
   the title, so it shows only inside the open sheet. */
.ota-nav__panel-overview {
	display: none;
	margin: 0;
}

/*
 * The badge, `ota-btn__badge` in the design file. Drawn empty at rest and the
 * arrow inside it hidden rather than absent, so the row keeps its width and the
 * labels do not shift under the pointer. Same idiom as the featured card's dot.
 */
.ota-nav__link-dot {
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	width: 1.625rem;
	height: 1.625rem;
	border-radius: 50%;
	transition:
		background-color 0.18s ease,
		color 0.18s ease;
}

.ota-nav__link-dot .ota-icon--arrow {
	width: 0.8125rem;
	height: auto;
	opacity: 0;
	transition: opacity 0.18s ease;
}

.ota-nav__links a:hover .ota-nav__link-dot,
.ota-nav__links a:focus-visible .ota-nav__link-dot {
	background: var(--ota-menu-link-text);
	color: var(--ota-menu-link-bg);
}

.ota-nav__links a:hover .ota-nav__link-dot .ota-icon--arrow,
.ota-nav__links a:focus-visible .ota-nav__link-dot .ota-icon--arrow {
	opacity: 1;
}

.ota-nav__badge {
	display: inline-flex;
	align-items: center;
	margin-left: 0.5rem;
	padding: 0.15em 0.6em;
	border-radius: 999px;
	background: var(--ota-menu-accent);
	color: var(--ota-menu-accent-text);
	text-decoration: none;
}

/*
 * The join and login buttons that pin to the bottom of the mobile sheet. On
 * desktop the utility strip already carries both, so this stays hidden rather
 * than repeating them.
 */
.ota-nav__footer {
	display: none;
}

/* --- Featured card ------------------------------------------------------ */

/*
 * Inset from the panel's top and bottom edges. Figma runs the card full bleed;
 * this is a deliberate departure, so the dark block is not hard against the
 * panel's edges. Margin rather than padding: the whitespace wanted is outside
 * the card, not inside it.
 */
/* overflow clips the image into the corners, since the image is a child rather
   than a background. */
.ota-nav__feature {
	display: flex;
	overflow: hidden;
	flex-direction: column;
	margin-block: 1.5rem;
	border-radius: var(--ota-menu-feature-radius);
	background: var(--ota-menu-feature-bg);
	color: var(--ota-menu-feature-text);
}

.ota-nav__feature-image {
	display: block;
	width: 100%;
	height: auto;
	aspect-ratio: 16 / 10;
	object-fit: cover;
}

.ota-nav__feature-body {
	display: flex;
	flex-direction: column;
	gap: 0.6rem;
	padding: 1.75rem;
}

/*
 * With an image the card reads top down and the text follows it. With no image
 * the text would otherwise float at the top of a column stretched to the
 * panel's height, so it sits on the bottom edge instead.
 */
.ota-nav__feature--no-image .ota-nav__feature-body {
	margin-top: auto;
}

.ota-nav__feature-eyebrow,
.ota-nav__feature-heading,
.ota-nav__feature-text {
	margin: 0;
}

/*
 * The card's four pieces of type, from the text styles bound in Figma, read
 * through the Elementor globals with the design's own numbers as fallbacks. Same
 * arrangement as the panel title and the column headings further up.
 *
 * All three of these are `<p>` in nav-feature.php, so nothing in the cascade
 * reached them and the card came out as three sizes of body copy: the eyebrow was
 * aqua but no smaller or bolder than the heading, and the heading did not read as
 * one at all.
 *
 *   Label/Eyebrow    17 / 24.8, Bold, 1px       eyebrow global    brand/aqua
 *   Label/Large Bold 22 / 22,   Bold            no global, below   brand/white
 *   Body/Default     17 / 28.05, Light          body global        brand/white
 *   the CTA label    17 / 17,   Bold            body global's size bar/text
 *
 * The fills are the last column, and they are two colours rather than one: the
 * heading and the copy are bound to brand/white while the label on the button is
 * bar/text, which on this card is the cream. The whole card was cream before.
 */
.ota-nav__feature-eyebrow {
	color: var(--ota-menu-feature-eyebrow);
	font-size: var(--e-global-typography-eyebrow-font-size, 1.0625rem);
	font-weight: var(--e-global-typography-eyebrow-font-weight, 700);
	line-height: var(--e-global-typography-eyebrow-line-height, 1.46em);
	letter-spacing: var(--e-global-typography-eyebrow-letter-spacing, 1px);
}

/*
 * Label/Large Bold is not one of the eleven globals: nothing in the scale is 22px
 * Bold at a 1 line height. Lead is the only 22px in it and it is Regular at 1.5,
 * which would be a different style wearing the same size, so the design's numbers
 * are carried here instead. If a global is ever added for it, this is the one
 * place to point at it. Same call as the utility bar's 14px.
 */
.ota-nav__feature-heading {
	color: var(--ota-menu-on-feature);
	font-size: 1.375rem;
	font-weight: 700;
	line-height: 1;
}

.ota-nav__feature-text {
	color: var(--ota-menu-on-feature);
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: var(--e-global-typography-body-font-weight, 300);
	line-height: var(--e-global-typography-body-line-height, 1.65em);
}

/*
 * The card's call to action is a Button in the design, not a bare link: a 48px
 * pill running the full width of the body, label on the leading edge and the dot
 * on the trailing one, with no side padding of its own so both sit flush with
 * the copy above. It is the Ghost type, which is why the border is drawn and
 * transparent rather than left out: the 1.5px is part of the 48px, and a hover
 * or focus state that wants the line later has somewhere to put it.
 *
 * Its label is the body size at Bold on a line height of 1, which is 17/17 in the
 * design. Against the card's 17px Light copy the weight is the only thing that
 * separates them, so inheriting it would lose the button.
 */
.ota-nav__feature-link {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 1rem;
	min-height: 3rem;
	margin-top: 0.5rem;
	border: 1.5px solid transparent;
	border-radius: 999px;
	color: inherit;
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: 700;
	line-height: 1;
	text-decoration: none;
}

/*
 * The rule sits on the label rather than the row, or it would stretch across
 * the gap and under the dot as well.
 */
.ota-nav__feature-link:hover .ota-nav__feature-link-label,
.ota-nav__feature-link:focus-visible .ota-nav__feature-link-label {
	text-decoration: underline;
	text-underline-offset: 0.3em;
}

/*
 * The design's hover underlines the card's heading along with the label. The
 * heading sits outside the link, so the body is asked whether the link inside it
 * is hovered rather than the heading being moved into the anchor: the whole card
 * is one link in Figma, and making it one here would put the image and the copy
 * inside an anchor for a card that also has to work with no link set at all.
 */
.ota-nav__feature-body:has(.ota-nav__feature-link:hover) .ota-nav__feature-heading,
.ota-nav__feature-body:has(.ota-nav__feature-link:focus-visible) .ota-nav__feature-heading {
	text-decoration: underline;
	text-underline-offset: 0.3em;
}

/*
 * The dot is drawn at rest but unfilled, so the arrow reads as a bare glyph
 * until hover, which is when the circle appears. Same idiom as the account
 * panel's action badge, without the resting border the design does not have.
 */
.ota-nav__feature-dot {
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	width: 1.875rem;
	height: 1.875rem;
	border-radius: 50%;
	transition: background-color 0.18s ease, color 0.18s ease;
}

.ota-nav__feature-dot .ota-icon--arrow {
	width: 0.8125rem;
	height: auto;
}

.ota-nav__feature-link:hover .ota-nav__feature-dot,
.ota-nav__feature-link:focus-visible .ota-nav__feature-dot {
	background: var(--ota-menu-feature-dot-bg);
	color: var(--ota-menu-feature-dot-icon);
}

/*
 * A touch device never hovers, so on the phone the dot would sit bare forever
 * and the CTA would never read as a button at all. Where the card is inside the
 * accordion and there is no pointer, give it the filled state at rest.
 */
@media (max-width: 1100px) and (hover: none) {
	.ota-nav.is-open .ota-nav__feature-dot {
		background: var(--ota-menu-feature-dot-bg);
		color: var(--ota-menu-feature-dot-icon);
	}
}

.ota-icon--arrow {
	flex: none;
	transition: transform 0.18s ease;
}

/* --- Account panel and notices ------------------------------------------ */

/*
 * The account dropdown. The panel positions and carries the pointer, and the
 * card inside it does the clipping: the split buttons run full bleed to the
 * rounded corners, which needs overflow hidden, and that would cut the pointer
 * off if both lived on the same element.
 */
.ota-utility__account-wrap {
	position: relative;
	z-index: 20;
	display: inline-flex;
}

.ota-header__account {
	position: absolute;
	z-index: 10;
	top: calc(100% + 0.625rem);
	right: 0;
	width: min(23.25rem, calc(100vw - 2rem));
}

/*
 * The pointer belongs to the control, not the card, so it stays centred on
 * whatever was clicked no matter how wide the card is. Decorative, so a
 * browser without :has() simply gets no pointer.
 */
.ota-utility__account-wrap:has(.ota-header__account:not([hidden]))::after {
	content: "";
	position: absolute;
	z-index: 11;
	top: calc(100% + 0.125rem);
	left: 50%;
	width: 1rem;
	height: 1rem;
	transform: translateX(-50%) rotate(45deg);
	background: var(--ota-menu-bg);
	box-shadow: -3px -3px 8px var(--ota-menu-shadow-soft);
}

.ota-account {
	position: relative;
	overflow: hidden;
	border-radius: 1.125rem;
	background: var(--ota-menu-bg);
	color: var(--ota-menu-text);
	box-shadow: 0 0.5rem 1.5rem var(--ota-menu-shadow);
}

/*
 * The card frames the base theme's own login form rather than a copy of it, so
 * everything from `.agendtheme-user-login-form` inwards is the theme's markup
 * and its Bootstrap grid classes come with it. The rules below restate the
 * design over that markup: the grid is flattened back to a single column, and
 * the rows, placeholder colour and accent focus bar are reproduced on the
 * theme's own elements.
 *
 * Keep these scoped to `.ota-account__form`. The same form renders in the
 * theme's header elsewhere on the site and must keep the theme's styling
 * there.
 */
.ota-account__form form,
.ota-account__form .agendtheme-user-login-form {
	margin: 0;
}

.ota-account__form .agendtheme-user-login-fields {
	width: auto;
	max-width: none;
	margin: 0;
	padding: 0;
	border: 0;
}

/*
 * The theme's `.row` is a Bootstrap grid row and its children carry `col-*`
 * widths. Restated as a plain wrapping flex container with explicit bases, so
 * the design's layout does not depend on the theme's grid being loaded or on
 * which `col-*` the theme happens to use.
 */
.ota-account__form .row {
	display: flex;
	flex-wrap: wrap;
	margin: 0;
}

.ota-account__form .row > * {
	flex: 0 0 100%;
	max-width: 100%;
	padding: 0;
}

.ota-account__eyebrow,
.ota-account__form .agendtheme-user-login-username,
.ota-account__form .agendtheme-user-login-password,
.ota-account__profile .agendtheme-user-identifier {
	border-bottom: 1px solid var(--ota-menu-rule);
}

.ota-account__eyebrow {
	margin: 0;
	padding: 1rem 1.375rem;
	color: var(--ota-menu-accent);
}

/*
 * The row stays full bleed and the inset lives on the input. The theme puts
 * `col-12 p-0` on these, and Bootstrap's `p-0` is `padding: 0 !important`, so
 * padding on the row is not winnable without an !important of our own. It also
 * wants to be full bleed: the focus bar below is an inset box-shadow on this
 * element and belongs against the card edge.
 */
.ota-account__form .agendtheme-user-login-username,
.ota-account__form .agendtheme-user-login-password {
	display: flex;
	align-items: center;
	gap: 0.75rem;
}

/* Visually hidden, still read out. The inputs carry placeholders only in the
   design, which is not a label. The theme labels its own fields `.sr-only`,
   which its stylesheet already hides; this covers the search field's label,
   which is ours. */
.ota-account__label {
	position: absolute;
	width: 1px;
	height: 1px;
	overflow: hidden;
	clip-path: inset(50%);
	white-space: nowrap;
}

.ota-account__form input[type="text"],
.ota-account__form input[type="email"],
.ota-account__form input[type="password"] {
	flex: 1 1 auto;
	min-width: 0;
	padding-block: 1.05rem;
	/* Carries the row's inset, since the row itself cannot: see above. The
	   right side keeps its own so the placeholder clears whatever a password
	   manager injects into the field. */
	padding-inline: 1.375rem;
	border: 0;
	border-radius: 0;
	background: none;
	color: inherit;
	font: inherit;
	box-shadow: none;
}

.ota-account__form input::placeholder {
	color: var(--ota-menu-placeholder);
	opacity: 1;
}

.ota-account__form input:focus {
	outline: none;
	box-shadow: none;
}

.ota-account__form .agendtheme-user-login-username:focus-within,
.ota-account__form .agendtheme-user-login-password:focus-within {
	box-shadow: inset 0.1875rem 0 0 var(--ota-menu-accent);
}

/* Remember me and the password reset link share one row, as in the design. */
.ota-account__form .agendtheme-user-login-remember-me,
.ota-account__form .agendtheme-user-login-forgot-password {
	display: flex;
	flex: 0 0 50%;
	max-width: 50%;
	align-items: center;
	padding-block: 0.9rem;
}

.ota-account__form .agendtheme-user-login-remember-me {
	padding-left: 1.375rem;
}

.ota-account__form .agendtheme-user-login-forgot-password {
	justify-content: flex-end;
	padding-right: 1.375rem;
}

.ota-account__form .agendtheme-user-login-remember-me label {
	display: inline-flex;
	align-items: center;
	gap: 0.6rem;
	margin: 0;
	cursor: pointer;
}

.ota-account__form .agendtheme-user-login-remember-me input {
	width: 1.1875rem;
	height: 1.1875rem;
	margin: 0;
	border: 1.5px solid var(--ota-menu-field-border);
	border-radius: 0.375rem;
	accent-color: var(--ota-menu-accent);
}

.ota-header .ota-account__form .agendtheme-user-login-form__link {
	color: var(--ota-menu-accent);
	text-decoration: none;
}

.ota-account__form .agendtheme-user-login-form__link:hover {
	text-decoration: underline;
	text-underline-offset: 0.25em;
}

/*
 * The theme's join and login controls take the same treatment as the profile
 * card's actions, so the two cards read as one component.
 */
.ota-account__form .agendtheme-user-login-form-join,
.ota-account__form .agendtheme-user-login-form-login {
	display: flex;
	flex: 0 0 50%;
	max-width: 50%;
	align-items: center;
	justify-content: space-between;
	gap: 0.75rem;
	/* Full bleed across the bottom of the card, so the theme's own pill radius
	   and spacing are cleared rather than inherited. */
	margin: 0;
	padding: 1.25rem 1.375rem;
	border: 0;
	border-radius: 0;
	font: inherit;
	text-align: left;
	cursor: pointer;
}

/*
 * Hover, focus and active are restated alongside the resting state rather than
 * left to inherit. The theme ships
 * `html body .agendtheme-label-icon-button:hover { background-color: transparent }`,
 * which out-specifies a two-class background rule of ours but not a
 * three-class colour rule, so hovering used to strip the button's fill while
 * keeping our white label: white on the card's white, and the button read as
 * empty apart from its glyph. Both halves are pinned together here so they
 * cannot come apart again.
 */
.ota-account__form .agendtheme-user-login-form-join,
.ota-account__form .agendtheme-user-login-form-join:hover,
.ota-account__form .agendtheme-user-login-form-join:focus,
.ota-account__form .agendtheme-user-login-form-join:active {
	background: var(--ota-menu-muted);
}

.ota-header .ota-account__form .agendtheme-user-login-form-join,
.ota-header .ota-account__form .agendtheme-user-login-form-join:hover,
.ota-header .ota-account__form .agendtheme-user-login-form-join:focus,
.ota-header .ota-account__form .agendtheme-user-login-form-join:active {
	color: var(--ota-menu-text);
	text-decoration: none;
}

.ota-account__form .agendtheme-user-login-form-login,
.ota-account__form .agendtheme-user-login-form-login:hover,
.ota-account__form .agendtheme-user-login-form-login:focus,
.ota-account__form .agendtheme-user-login-form-login:active {
	background: var(--ota-menu-accent);
}

.ota-header .ota-account__form .agendtheme-user-login-form-login,
.ota-header .ota-account__form .agendtheme-user-login-form-login:hover,
.ota-header .ota-account__form .agendtheme-user-login-form-login:focus,
.ota-header .ota-account__form .agendtheme-user-login-form-login:active {
	color: var(--ota-menu-accent-text);
	text-decoration: none;
}

/*
 * The glyphs are `.icon` children, and the theme colours them accent on the
 * resting state and `--at-button-text-color` on hover, neither of which knows
 * what these two buttons are sitting on. Both follow their button's own text
 * colour instead.
 */
.ota-header .ota-account__form .agendtheme-user-login-form-join > .icon,
.ota-header .ota-account__form .agendtheme-user-login-form-join:hover > .icon,
.ota-header .ota-account__form .agendtheme-user-login-form-login > .icon,
.ota-header .ota-account__form .agendtheme-user-login-form-login:hover > .icon {
	color: inherit;
	background: none;
}

/* A hover that reads without moving the fill: the design's own darkening. */
.ota-account__form .agendtheme-user-login-form-join:hover,
.ota-account__form .agendtheme-user-login-form-login:hover {
	filter: brightness(0.94);
}

/*
 * The logged in card frames the base theme's own `user-profile` template part
 * rather than a copy of it, on the same terms as the login form above:
 * everything from `.agendtheme-user-profile` inwards is the theme's markup and
 * its Bootstrap classes come with it. The rules below restate the design over
 * that markup.
 *
 * Keep these scoped to `.ota-account__profile`. The same part renders in the
 * theme's header elsewhere on the site and must keep the theme's styling
 * there.
 */
.ota-account__profile {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
}

/*
 * The theme's part is one wrapper holding the name and, below it, the controls.
 * The design puts the avatar beside the name, and the avatar cannot be a child
 * of the part without editing it. Flattening the wrapper promotes its two
 * children to items of this row instead, so the avatar and the name sit
 * together and the controls wrap under both.
 *
 * If `display: contents` is ever unavailable the card degrades to avatar above
 * the part rather than beside it, which is a layout the content survives.
 */
.ota-account__profile .agendtheme-user-profile {
	display: contents;
}

.ota-account__avatar {
	flex: none;
	padding-left: 1.375rem;
}

.ota-account__avatar img {
	display: block;
	width: 2.75rem;
	height: 2.75rem;
	border-radius: 50%;
	object-fit: cover;
}

/*
 * The name row. Bootstrap's `p-3` is a plain utility here, not an `!important`
 * one, so the design's inset simply out-specifies it; `m-0` is `!important`
 * but sets the margin this rule wants anyway.
 */
.ota-account__profile .agendtheme-user-identifier {
	flex: 1;
	min-width: 0;
	padding: 1.125rem 1.375rem;
}

/* The controls row: full width under the avatar and name. */
.ota-account__profile .agendtheme-user-profile-controls {
	flex: 0 0 100%;
	max-width: 100%;
	padding: 0;
}

/*
 * The theme's `.row` is a Bootstrap grid row and its children carry `col-6`.
 * Restated as a two column grid, so the two full bleed buttons across the
 * bottom of the card do not depend on the theme's grid being loaded or on
 * which `col-*` the theme happens to use. Same treatment as the form's rows.
 */
.ota-account__profile .row {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(0, 1fr));
	margin: 0;
}

/*
 * The theme's button mixin gives these a pill radius, which is right for a
 * button sitting in space and wrong for two that run full bleed into the
 * corners of a card. Squared off here; the card's own `overflow: hidden` and
 * radius round the two outer corners, which is the shape the design asks for.
 *
 * Order is left to the theme, which already sets `.label { order: 1 }` and
 * `.icon { order: 2 }` on this class, so both buttons read label then glyph
 * regardless of which way round the part writes them.
 */
.ota-account__profile .agendtheme-label-icon-button {
	display: flex;
	flex: auto;
	align-items: center;
	justify-content: space-between;
	gap: 0.75rem;
	max-width: none;
	padding: 1.25rem 1.375rem;
	border: 0;
	border-radius: 0;
	font: inherit;
	text-align: left;
	text-decoration: none;
	cursor: pointer;
}

/*
 * Hover, focus and active are restated alongside the resting state rather than
 * left to inherit, for the reason spelled out over the form's two buttons: the
 * theme's `html body .agendtheme-label-icon-button:hover` sets a transparent
 * background that out-specifies a two-class rule of ours but not a three-class
 * one, so the fill and the label colour have to be pinned together or the
 * button reads as empty on hover.
 */
.ota-account__profile .logout,
.ota-account__profile .logout:hover,
.ota-account__profile .logout:focus,
.ota-account__profile .logout:active {
	background: var(--ota-menu-muted);
}

.ota-header .ota-account__profile .logout,
.ota-header .ota-account__profile .logout:hover,
.ota-header .ota-account__profile .logout:focus,
.ota-header .ota-account__profile .logout:active {
	color: var(--ota-menu-text);
	text-decoration: none;
}

.ota-account__profile .dashboard,
.ota-account__profile .dashboard:hover,
.ota-account__profile .dashboard:focus,
.ota-account__profile .dashboard:active {
	background: var(--ota-menu-feature-bg);
}

.ota-header .ota-account__profile .dashboard,
.ota-header .ota-account__profile .dashboard:hover,
.ota-header .ota-account__profile .dashboard:focus,
.ota-header .ota-account__profile .dashboard:active {
	color: var(--ota-menu-on-feature);
	text-decoration: none;
}

/*
 * The glyphs are `.icon` children and the theme colours them accent, which
 * knows nothing about what these two buttons are sitting on. Both follow their
 * button's own text colour instead, as the form's do.
 */
.ota-header .ota-account__profile .agendtheme-label-icon-button > .icon,
.ota-header .ota-account__profile .agendtheme-label-icon-button:hover > .icon {
	flex: none;
	color: inherit;
	background: none;
	transition: transform 0.18s ease;
}

/*
 * Glyph sizing, and each size is stated twice on purpose. The theme's part
 * ships FontAwesome `<i>` elements and the kit's script swaps them for `<svg>`
 * once it loads, so a glyph is a font glyph first and an element second.
 * `font-size` covers the first, the explicit box covers the second, and the
 * two agree so the swap does not move the layout. Same approach as the close
 * glyph above.
 */
.ota-account__profile .agendtheme-label-icon-button > .icon {
	font-size: 1.1875rem;
	line-height: 1;
}

.ota-account__profile .agendtheme-label-icon-button > .icon svg {
	width: 1.1875rem;
	height: 1.1875rem;
}

/*
 * The dashboard glyph is the theme's circled chevron. It already carries the
 * ring the design draws, so there is no badge element to add around it, and it
 * takes the badge's diameter rather than the sign out glyph's size.
 */
.ota-account__profile .dashboard > .icon {
	font-size: 1.625rem;
}

.ota-account__profile .dashboard > .icon svg {
	width: 1.625rem;
	height: 1.625rem;
}

.ota-account__profile .dashboard:hover > .icon {
	transform: translateX(0.15rem);
}

/* A hover that reads without moving the fill: the design's own darkening. */
.ota-account__profile .agendtheme-label-icon-button:hover {
	filter: brightness(0.94);
}

/*
 * The login sheet belongs to the mobile layout and is laid out inside the
 * narrow media query. Hidden by default here so that widening the viewport
 * while it is open cannot drop an unstyled form into the desktop header: the
 * script closes it on resize, but the layout must not depend on that.
 */
.ota-sheet-login {
	display: none;
}

.ota-header__notices:empty {
	display: none;
}

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

@media (max-width: 1100px) {
	.ota-header__actions {
		display: inline-flex;
	}

	.ota-nav {
		display: none;
		margin: 0;
	}

	.ota-nav.is-open {
		display: block;
		position: absolute;
		z-index: 10;
		top: 100%;
		left: 0;
		width: 100%;
		max-height: calc(100vh - 100%);
		overflow-y: auto;
		/* Keep the scroll inside the sheet. Without this a flick past either
		   end chains to the page behind, which iOS Safari does regardless of
		   the overflow: hidden on body. */
		overscroll-behavior: contain;
		background: var(--ota-menu-bg);
		color: var(--ota-menu-text);
	}

	.ota-nav.is-open .ota-nav__list {
		flex-direction: column;
		align-items: stretch;
		gap: 0;
	}

	.ota-nav.is-open .ota-nav__item {
		flex-direction: column;
		align-items: stretch;
		border-bottom: 1px solid var(--ota-menu-divider);
	}

	.ota-nav.is-open .ota-nav__toggle,
	.ota-nav.is-open .ota-nav__link {
		justify-content: space-between;
		border-radius: 0;
	}

	/* The desktop cap does not belong in the sheet. Left on, each panel would
	   become its own scroller inside .ota-nav__list, which is already the
	   sheet's one scroller, and reaching the last link would take two scrolls.
	   Same reset as the sheet's own max-height: none below. */
	.ota-nav.is-open .ota-nav__panel {
		position: static;
		width: auto;
		max-height: none;
		overflow: visible;
	}

	.ota-nav.is-open .ota-nav__panel-inner {
		grid-template-columns: minmax(0, 1fr);
	}

	/* --- The sheet itself ------------------------------------------------ */

	/*
	 * Everything below is the Mobile Navigation component from the design: a
	 * full height panel under the bar, its list scrolling between the fixed
	 * bar and a pinned footer. It starts at the same width the nav collapses
	 * at, so the utility strip never coexists with the burger.
	 */

	/* No utility strip once collapsed: search moves into the bar, and join and
	   login move to the sheet footer. */
	.ota-utility {
		display: none;
	}

	.ota-header__search {
		display: inline-flex;
	}

	/* The strip is gone at this width, so the drawer is the only search. */
	.ota-search--bar {
		display: block;
	}

	.ota-header__inner {
		gap: 0.5rem;
	}

	.ota-nav.is-open {
		display: flex;
		flex-direction: column;
		max-height: none;
		height: calc(100vh - var(--ota-header-height, 0px) - var(--ota-admin-bar, 0px));
		height: calc(100dvh - var(--ota-header-height, 0px) - var(--ota-admin-bar, 0px));
		overflow: hidden;
	}

	/*
	 * 26px to the row edge and 10px inside it, so labels land 36px from the
	 * screen. Panel content repeats that 10px, which is what keeps a sub-link
	 * lined up under the row it belongs to instead of out at the row edge.
	 */
	.ota-nav.is-open .ota-nav__list {
		flex: 1 1 auto;
		overflow-y: auto;
		padding-inline: 1.625rem;
		-webkit-overflow-scrolling: touch;
	}

	/* min-height rather than taller padding, so the row keeps its 64px whatever
	   size the inherited type turns out to be. */
	.ota-nav.is-open .ota-nav__toggle,
	.ota-nav.is-open .ota-nav__link {
		width: 100%;
		min-height: 4rem;
		padding: 1.15rem 0.625rem;
	}

	/* 20px in the accordion rows, per the design. */
	.ota-nav.is-open .ota-icon--chevron {
		width: 1.25rem;
		height: 1.25rem;
	}

	/* An open row goes ochre rather than taking the bar's dark pill. */
	.ota-nav.is-open .ota-nav__toggle[aria-expanded="true"] {
		background: none;
		color: var(--ota-menu-accent);
	}

	/* Underlining every row fights the dividers. */
	.ota-nav.is-open .ota-nav__toggle:hover,
	.ota-nav.is-open .ota-nav__link:hover,
	.ota-nav.is-open .ota-nav__item--current > .ota-nav__toggle,
	.ota-nav.is-open .ota-nav__item--current > .ota-nav__link {
		text-decoration: none;
	}

	.ota-nav.is-open .ota-nav__panel-main {
		padding: 1rem 0.625rem;
	}

	/* The row label sits directly above, so the panel heading repeats it. */
	.ota-nav.is-open .ota-nav__panel-head {
		display: none;
	}

	/* Its link comes back as the sheet's first row, set in the panel title's
	   type so it reads as the section's own page rather than one of its links. */
	.ota-nav.is-open .ota-nav__panel-overview {
		display: block;
		margin-bottom: 0.875rem;
	}

	.ota-nav.is-open .ota-nav__panel-overview a {
		display: flex;
		align-items: center;
		min-height: 2.75rem;
		padding: 0.5rem;
		color: var(--ota-menu-heading);
		font-size: var(--e-global-typography-h4-font-size, 1.25rem);
		font-weight: var(--e-global-typography-h4-font-weight, 400);
		line-height: var(--e-global-typography-h4-line-height, 1.15em);
		letter-spacing: var(--e-global-typography-h4-letter-spacing, -0.24px);
		text-decoration: none;
	}

	.ota-nav.is-open .ota-nav__panel-overview a:hover,
	.ota-nav.is-open .ota-nav__panel-overview a:focus-visible {
		text-decoration: underline;
		text-underline-offset: 0.18em;
		text-decoration-thickness: 2px;
	}

	.ota-nav.is-open .ota-nav__columns {
		grid-template-columns: minmax(0, 1fr);
		gap: 0.875rem;
	}

	.ota-nav.is-open .ota-nav__column-title {
		margin-bottom: 0.375rem;
	}

	.ota-nav.is-open .ota-nav__links {
		gap: 0;
	}

	/* Contiguous 44px rows, indented 8px from their group heading. */
	.ota-nav.is-open .ota-nav__links a {
		display: flex;
		align-items: center;
		min-height: 2.75rem;
		padding: 0.5rem;
		border-radius: 0.5rem;
	}

	/* The heading's desktop lead-in belongs to the pill under it, and there is no
	   pill at this width. The hairline and the pad beneath it go too: the
	   accordion's rows are contiguous by design, with no dividers of their own,
	   and a rule under each group heading would be the one divider in the list.
	   The heading still reads as a label here through its size, weight and
	   tracking. Raised in review on PR #26. */
	.ota-nav.is-open .ota-nav__column-title {
		padding-inline: 0.5rem;
		padding-bottom: 0;
		border-bottom: 0;
	}

	/* No badge in the accordion either: the design's mobile rows are the label
	   alone, and 26px of circle in a 44px row beside a chevron is a busy row. */
	.ota-nav.is-open .ota-nav__link-dot {
		display: none;
	}

	/*
	 * The mobile frames in Figma stop at the link groups, so this card is the
	 * desktop one scaled down to sit at the foot of an open accordion: same
	 * order and same colours, tighter padding, shallower image and smaller type
	 * so it reads as a footnote to the section rather than competing with the
	 * links above it. Sizes are set here rather than inherited because the
	 * desktop type is built for a 384px column beside the links, not a 330px
	 * card under them.
	 */
	.ota-nav.is-open .ota-nav__feature {
		display: flex;
		margin-block: 0.875rem 0.25rem;
	}

	/* Shallower than the desktop 16:10, so the card costs less of the scroll. */
	.ota-nav.is-open .ota-nav__feature-image {
		aspect-ratio: 2 / 1;
	}

	.ota-nav.is-open .ota-nav__feature-body {
		gap: 0.35rem;
		padding: 1rem;
	}

	.ota-nav.is-open .ota-nav__feature-eyebrow {
		font-size: 0.75rem;
	}

	.ota-nav.is-open .ota-nav__feature-heading {
		font-size: 1.0625rem;
	}

	.ota-nav.is-open .ota-nav__feature-text {
		font-size: 0.9375rem;
	}

	.ota-nav.is-open .ota-nav__feature-link {
		margin-top: 0.25rem;
	}

	/* 26px against the desktop 30px, keeping the dot in proportion with the
	   smaller label beside it. */
	.ota-nav.is-open .ota-nav__feature-dot {
		width: 1.625rem;
		height: 1.625rem;
	}

	.ota-nav.is-open .ota-nav__feature-dot .ota-icon--arrow {
		width: 0.6875rem;
	}

	.ota-nav__footer {
		display: flex;
		flex: none;
		flex-direction: column;
		gap: 0.625rem;
		padding: 1rem;
		border-top: 1px solid var(--ota-bar-divider);
		background: var(--ota-bar-bg);
		color: var(--ota-bar-text);
	}

	/* The only control in the signed out footer. A button, because it opens the
	   login sheet rather than navigating. */
	.ota-nav__ghost {
		display: flex;
		align-items: center;
		justify-content: center;
		width: 100%;
		padding: 0.875rem 1rem;
		border: 1.5px solid var(--ota-bar-text);
		border-radius: 999px;
		background: none;
		font: inherit;
		text-decoration: none;
		cursor: pointer;
	}

	.ota-header .ota-nav__ghost {
		color: var(--ota-bar-text);
	}

	/* The member strip that replaces the two buttons once signed in. */
	/*
	 * Two rows: the member above, the two actions below. One row was possible
	 * only while Logout was an unlabelled glyph. With both actions labelled,
	 * as they are on the desktop card, the pair takes 272px of a 358px strip
	 * and the name is left with 12px at 390px and nothing at all at 360px.
	 * Stacking gives the name the full width and the buttons room to be read.
	 */
	.ota-nav__member {
		display: flex;
		flex-wrap: wrap;
		align-items: center;
		justify-content: space-between;
		gap: 0.75rem;
	}

	.ota-nav__member-identity {
		display: flex;
		flex: 1 0 100%;
		align-items: center;
		gap: 0.75rem;
		min-width: 0;
	}

	.ota-nav__member-avatar {
		display: inline-flex;
		flex: none;
		align-items: center;
		justify-content: center;
		width: 2.625rem;
		height: 2.625rem;
		overflow: hidden;
		border-radius: 50%;
	}

	.ota-nav__member-avatar img {
		display: block;
		width: 100%;
		height: 100%;
		object-fit: cover;
	}

	/* Only the fallback needs a fill behind it; an avatar brings its own. */
	.ota-nav__member-avatar--initials {
		background: var(--ota-bar-cta-bg);
		color: var(--ota-bar-cta-text);
	}

	/* A long display name should shorten rather than shove the dashboard
	   button off the edge. */
	.ota-nav__member-name {
		overflow: hidden;
		text-overflow: ellipsis;
		white-space: nowrap;
	}

	/*
	 * The action row. Both buttons share it evenly rather than sitting at
	 * their content widths, so the row reads as a pair and neither label has
	 * to shrink on a narrow phone.
	 */
	.ota-nav__member-actions {
		display: flex;
		flex: 1 0 100%;
		align-items: center;
		gap: 0.5rem;
	}

	/*
	 * Both actions are `.ota-btn` now, so the second button component that used
	 * to live here is gone: its border, radius, padding, paint and its two
	 * `.ota-header` colour overrides were all declared twice, it did not follow
	 * a colour theme the way every other button does, and it had no hover, no
	 * focus ring and no disabled state at all. assets/css/ota-buttons.css draws
	 * all of it instead.
	 *
	 * What is left is how the pair divides this row, which that stylesheet has
	 * no opinion about, and the shape the pair falls back to without it.
	 *
	 * `flex: 1` on both so they share it evenly rather than sitting at their
	 * content widths and leaving a ragged gap. That is also why the member's name
	 * gives way first: see `.ota-nav__member-name`, which ellipses, and the
	 * `min-width: 0` that lets it.
	 *
	 * `min-width: 0` here too. A flex item will not shrink below its content by
	 * default and the button's own inner row is `width: max-content`, so without
	 * this a long translation of either label would push the pair wider than the
	 * phone instead of the two of them sharing what there is.
	 *
	 * The rest is the switched-off state, and it is the promise
	 * `.ota-utility__join` keeps on the desktop strip. With the button design off
	 * ota-buttons.css is never enqueued at all, so this file is the only one left
	 * and the pair would be a bare row of text and glyphs. Every declaration is
	 * 0,1,0 and loses to ota-buttons.css at priority 20 when it is there, the way
	 * the note above `.ota-utility` describes, and the padding is a shorthand so
	 * the three longhands the button derives from its own height replace it
	 * whole. Logout's outline and My Dashboard's ochre follow below, each on its
	 * own, because the two pills are not the same pill.
	 */
	.ota-nav__member-logout,
	.ota-nav__member-cta {
		display: inline-flex;
		flex: 1;
		min-width: 0;
		align-items: center;
		justify-content: space-between;
		gap: var(--ob-gap, 0.5rem);
		padding: 0.5rem 0.875rem;
		border-radius: 999px;
		text-decoration: none;
	}

	/*
	 * Only Logout needs its colour said here. My Dashboard carries
	 * `ota-btn-colour--ochre`, which is the role the frame binds it to, so the
	 * button stylesheet supplies its pair already.
	 *
	 * There is no Colour modifier for "the bar's own text colour", which is what
	 * an outlined button on this strip has to draw its line and label from, so
	 * the pair is set directly. A Colour supplies exactly these two and every
	 * Type rule derives its paint from them, so this is the whole of what it
	 * takes to put a design system button on a bar-scoped surface.
	 *
	 * Not the page's CTA role, which is what an unmodified Outline would reach
	 * for. `.ota-nav__footer` above paints itself `--ota-bar-bg` on
	 * `--ota-bar-text`, and on this site `--ota-cta-bg` is #F0E7D8, the same ash
	 * the strip uses for its type: the button would have been ash on ash.
	 */
	.ota-nav__member-logout {
		/* Outline paints the line and the label from fill, and inverts to
		   on-fill against a filled pill on hover. */
		--ob-fill: var(--ota-bar-text);
		--ob-on-fill: var(--ota-bar-bg);
		/* And the line drawn for real, for the switched-off state. The same
		   colour the token above hands the Outline type, so the two cannot
		   disagree about what an outlined control on this strip looks like. */
		border: 1.5px solid var(--ota-bar-text);
	}

	/* My Dashboard's half of the same fallback, read from the role that
	   `ota-btn-colour--ochre` binds it to rather than restated as a literal. */
	.ota-nav__member-cta {
		background: var(--ota-bar-cta-bg);
	}

	/*
	 * And the label's colour has to be said again, for the same reason the logo
	 * does: `.ota-header a, .ota-header a:hover { color: inherit }` near the top
	 * of this file outranks the button component's own paint rule, so an
	 * `.ota-btn` that is also an anchor inside the header loses its text colour
	 * and inherits the strip's. The pill painted ochre and kept ash type, which
	 * is the bar's text colour rather than the ochre role's.
	 *
	 * BOTH HALVES OF THAT SELECTOR, NOT JUST THE FIRST
	 *
	 * The logo above only needs two classes because a logo has no hover colour.
	 * Here the rest state and the hover state have to be beaten separately, and
	 * they sit at different weights: `.ota-header a` is 0,1,1 and two classes
	 * clear it, but `.ota-header a:hover` is 0,2,1 and two classes tie and lose.
	 * Naming the states takes this to 0,3,0.
	 *
	 * Skipping them was not a theoretical bug: the outlined Logout filled with
	 * the bar's text colour on hover and kept the same colour for its label, so
	 * it went ash on ash and the word disappeared under the pointer.
	 *
	 * `--ob-text` rather than a role, so this stays a re-assertion rather than a
	 * second opinion: the Type rules move that token between rest and hover, and
	 * this follows them wherever they go.
	 *
	 * Which is also why the pair is two rules rather than one. With the button
	 * design off nothing defines `--ob-text`, the declaration is invalid at
	 * computed value time, and `color` falls back to inherit: the strip's ash,
	 * which is right for the outlined Logout and is ash on ochre for My
	 * Dashboard. So each names the role its own fallback wants, exactly as
	 * `.ota-utility__join` does against `.ota-utility__item` on the desktop
	 * strip.
	 */
	.ota-header .ota-nav__member-logout,
	.ota-header .ota-nav__member-logout:hover,
	.ota-header .ota-nav__member-logout:focus-visible {
		color: var(--ob-text, var(--ota-bar-text));
	}

	.ota-header .ota-nav__member-cta,
	.ota-header .ota-nav__member-cta:hover,
	.ota-header .ota-nav__member-cta:focus-visible {
		color: var(--ob-text, var(--ota-bar-cta-text));
	}

	/*
	 * The glyphs are the theme's FontAwesome, and each is sized twice so the
	 * kit's `<i>` to `<svg>` swap does not move the strip. Same pair of sizes
	 * as the desktop card: the plain sign out glyph at type size, the circled
	 * chevron at the badge's diameter.
	 */
	.ota-nav__member-logout .icon,
	.ota-nav__member-cta .icon {
		display: inline-flex;
		flex: none;
		line-height: 1;
	}

	.ota-nav__member-logout .icon {
		font-size: 1.1875rem;
	}

	.ota-nav__member-logout .icon svg {
		width: 1.1875rem;
		height: 1.1875rem;
	}

	.ota-nav__member-cta .icon {
		font-size: 1.375rem;
	}

	.ota-nav__member-cta .icon svg {
		width: 1.375rem;
		height: 1.375rem;
	}

	/*
	 * The login sheet: a card over the whole menu behind a scrim, anchored to
	 * the bottom. A sibling of the list and footer, positioned against .ota-nav.
	 */
	.ota-sheet-login {
		position: absolute;
		z-index: 20;
		inset: 0;
		display: flex;
		align-items: flex-end;
	}

	.ota-sheet-login[hidden] {
		display: none;
	}

	.ota-sheet-login__scrim {
		position: absolute;
		inset: 0;
		background: var(--ota-menu-scrim);
	}

	.ota-sheet-login__card {
		position: relative;
		width: 100%;
		max-height: 100%;
		overflow-y: auto;
		border-radius: 1.125rem 1.125rem 0 0;
		background: var(--ota-menu-bg);
		color: var(--ota-menu-text);
	}

	.ota-account__head {
		display: flex;
		align-items: center;
		justify-content: space-between;
		gap: 0.75rem;
		padding: 1rem 1.375rem;
	}

	/* The heading row carries no rule of its own here; the first field does. */
	.ota-account__head .ota-account__eyebrow {
		padding: 0;
		border: 0;
	}

	.ota-account__close {
		display: inline-flex;
		flex: none;
		align-items: center;
		justify-content: center;
		width: 1.875rem;
		height: 1.875rem;
		padding: 0;
		border: 0;
		border-radius: 50%;
		background: var(--ota-menu-muted);
		color: var(--ota-menu-text);
		cursor: pointer;
	}

	.ota-account__close .ota-icon {
		width: 0.9375rem;
		height: 0.9375rem;
	}

	/*
	 * The two fields are inset; the remember row runs full width. The inner
	 * padding keeps the placeholder off the rule ends and leaves room for the
	 * focus bar and whatever a password manager injects on the right.
	 */
	/*
	 * Inset by margin on the row, not padding: the theme's `p-0` is an
	 * !important zero and would swallow it. The input's own inset drops to
	 * match, so the total stays where the design puts it rather than stacking
	 * the desktop 1.375rem on top of the row's.
	 */
	.ota-sheet-login .ota-account__form .agendtheme-user-login-username,
	.ota-sheet-login .ota-account__form .agendtheme-user-login-password {
		/* The basis has to make room for the margin. Left at 100% the row is a
		   full width flex item that cannot shrink, so the margin pushes it off
		   the end instead of insetting it. */
		flex-basis: calc(100% - 2.75rem);
		max-width: calc(100% - 2.75rem);
		margin-inline: 1.375rem;
	}

	.ota-sheet-login .ota-account__form input[type="text"],
	.ota-sheet-login .ota-account__form input[type="email"],
	.ota-sheet-login .ota-account__form input[type="password"] {
		padding-inline: 0.75rem;
	}

	/*
	 * The sheet's two buttons follow the colour theme, unlike the surface they
	 * sit on. This artboard is the one place the design reaches for the bar
	 * roles rather than fixed values, and a button carries its own background,
	 * so its contrast holds up under any theme in a way that text on the fixed
	 * white card would not.
	 */
	.ota-sheet-login .ota-account__form .agendtheme-user-login-form-join {
		background: var(--ota-bar-join-bg);
	}

	.ota-header .ota-sheet-login .ota-account__form .agendtheme-user-login-form-join {
		color: var(--ota-bar-join-text);
	}

	.ota-sheet-login .ota-account__form .agendtheme-user-login-form-login {
		background: var(--ota-bar-cta-bg);
	}

	.ota-header .ota-sheet-login .ota-account__form .agendtheme-user-login-form-login {
		color: var(--ota-bar-cta-text);
	}

	/* The sheet covers the viewport, so the page behind it should not scroll.
	   overflow alone is not enough on iOS Safari, which still scrolls the
	   page on a touchmove that started outside the sheet's scroller, so the
	   scrim refuses touch scrolling outright and the sheet contains its own
	   (see overscroll-behavior on .ota-nav.is-open). */
	body.ota-nav-open {
		overflow: hidden;
		overscroll-behavior: none;
	}

	body.ota-nav-open .ota-sheet-login__scrim {
		touch-action: none;
	}
}

@media (prefers-reduced-motion: reduce) {
	.ota-icon--chevron,
	.ota-icon--arrow,
	.ota-search--utility,
	.ota-search--bar,
	.ota-nav__links a,
	.ota-nav__link-dot,
	.ota-nav__link-dot .ota-icon--arrow,
	.ota-nav__feature-dot {
		transition: none;
	}
}
