/**
 * OTA styling for Elementor's own widgets on the content page.
 *
 * Figma: the content page frames, "Ash Content - Desktop" 241:14477 and "Teal
 * Content - Desktop" 220:39887, in the OTA Design file iJIMvo6qjZanmK5Iza7bUs.
 * FAQ list 2278:17550 / 241:14322, tab row 2278:17584 / 241:14359, check list
 * 241:14295, quote block 241:14308, media rows 2001:18702 and 2001:18719.
 *
 * TWO KINDS OF RULE LIVE IN HERE, AND THE DIFFERENCE IS THE POINT
 *
 * The Accordion and the Tabs are skinned unconditionally: an FAQ list and a tab
 * row are that design wherever they appear, so no editor has to opt in.
 *
 * The check list, the quote block and the content images are NOT. They are
 * ordinary Icon List, Text Editor and Image widgets, used all over the site for
 * things that have nothing to do with this page, so styling them globally would
 * repaint work nobody asked to change. They are opt-in instead: the editor puts
 * a class in Elementor's Advanced > CSS Classes field and gets the design.
 *
 *   ota-check-list   Icon List, the check mark list.
 *   ota-quote        Text Editor, the ochre bar pull quote.
 *   ota-media        Image, the 14px radius the frame draws.
 *
 * Chosen with Bryce on 17 Aug 2026 over a global skin, so a stock Icon List
 * somewhere else on the site keeps its own spacing.
 *
 * WHY THIS STYLES SOMEBODY ELSE'S WIDGET INSTEAD OF ADDING OURS
 *
 * The design's FAQ and tab row are ordinary accordions and tabs. Elementor
 * already ships both, they already carry the keyboard handling, the ARIA wiring
 * and the FAQ schema, and an editor already knows where to find them. Building
 * `ota_faq` and `ota_tabs` would mean reimplementing all of that to change
 * colours and spacing. So this is a skin, not a widget, and it sits beside
 * `ota-theme-buttons.css` which does the same job for the theme's buttons.
 *
 * The nested Accordion and nested Tabs would have expressed most of this through
 * their own controls, but the `nested-elements` experiment is off on this site
 * and turning it on would rewrite every existing widget's markup contract.
 *
 * NOTHING HERE IS A COLOUR ROLE, AND THAT IS DELIBERATE
 *
 * Every other block in this plugin binds `--ota-*` and follows the page's
 * colour theme. These two do not, and the evidence is direct: the Ash and Teal
 * content frames were diffed and the FAQ card and the tab row are identical in
 * both, down to the card's white fill, the 14% navy hairline, the Mint
 * indicator and the ochre underline. They are fixed brand furniture sitting on
 * the white body of the page, not part of the themed chrome. Held as literals in
 * one token block so there is a single place to change them, and written down
 * here so nobody "fixes" them onto roles later and makes the FAQ disappear on
 * the Ochre theme.
 *
 * SPECIFICITY IS ONE STEP ABOVE ELEMENTOR'S, ON PURPOSE
 *
 * Elementor's widget stylesheets are enqueued while the widget renders, so their
 * position relative to this file is not something a priority on
 * `wp_enqueue_scripts` can settle. Every selector below therefore carries the
 * `.elementor-widget-*` wrapper to sit one class above the rule it replaces,
 * which wins on specificity whichever way round they load.
 *
 * THE THEME IS NOT TO BE EDITED, SO IT GETS OUTRANKED FROM HERE
 *
 * `wordpress-theme-agend` is the shared Agend product every client site runs, so
 * an OTA change there lands on sites that never asked for it. Six rules in it
 * conflict with this file. All six are answered from the plugin, and the note
 * against each records where the cause lives so it is findable the day the theme
 * is worked on for its own reasons. The fifth and sixth, the Posts skin's title
 * colour and the Icon Box's linked title, are documented against their own rules
 * near the bottom of this file.
 *
 * Three of the four are the same shape: a selector written for editor prose,
 * anchored on `main#agendtheme-content`, reaching into a widget it predates.
 * The id is what makes them unanswerable by an ordinary class, so each counter
 * rule below carries its specificity arithmetic. Get that wrong and nothing
 * breaks loudly: the page just keeps the theme's value.
 *
 * The tabs are two of them. `src/scss/modules/_elementor.scss:324` opens
 * `#agendtheme-content .elementor-widget-tabs` and does two things inside it
 * that no number of classes can outrank. Both are bugs against Elementor 4's
 * markup rather than decisions, and they are answered two different ways below:
 *
 * 1. It zeroes the tab title's padding and moves it onto an inner `<a>` that
 *    Elementor 4 no longer renders: the title is a bare `<div role="tab">` now,
 *    so the `a` rule matches nothing and the four labels butt together. Answered
 *    by not using padding at all. The metrics below are `min-block-size` plus an
 *    absolutely positioned `::after`, so the theme's dead rule is irrelevant and
 *    nothing here changes on the day it is deleted.
 *
 * 2. It forces `display: flex` on the tab row with no media query, which
 *    overrides Elementor's own rule hiding that row below 768 and leaves the
 *    widget showing its navigation twice on a phone: the desktop row and the
 *    mobile titles together. That one predates this file and is visible on any
 *    tabs widget on the site. `display` has no second property to reach for, so
 *    the media query at the bottom is the one place here that answers the id
 *    with an id, and it doubles a class so it wins outright rather than relying
 *    on load order.
 *
 * 3. `src/scss/modules/_content.scss:264` sets `img { border-radius: var(--at-
 *    border-radius) }` nested under `main#agendtheme-content`, which resolves to
 *    4px. Its id beats the rule Elementor writes for its own Image widget radius
 *    control, so ANY radius an editor sets on ANY image on this site is silently
 *    thrown away and has been all along: the widget saves 14, the page paints 4.
 *    `.ota-media` answers it below, and the arithmetic is written out there
 *    because getting it wrong just loses again, quietly.
 *
 * 4. `_content.scss` also gives `ul li + li` a `margin-top: 0.5rem`, prose
 *    spacing for an editor's bullet list, which lands on the check list and
 *    adds itself to that list's `gap`. Answered in the `.ota-check-list` block.
 */

.elementor-widget-accordion,
.elementor-widget-tabs,
.ota-check-list,
.ota-quote,
.ota-media {
	/* The palette, resolved. See the note above on why these are not roles. */
	--oew-card: #ffffff;
	--oew-line: rgba(0, 48, 56, 0.14);
	--oew-text: #003038;
	--oew-indicator: #d4f0d9;
	--oew-underline: #f04c3a;
	/* The inactive tab label. Not in the palette, read off the frame. */
	--oew-muted: #5a6b6e;

	/* `radius/md`. */
	--oew-radius: 14px;
}

/* -------------------------------------------------------------------------
 * Accordion, the FAQ list.
 * ---------------------------------------------------------------------- */

/*
 * SEPARATE CARDS, WHICH IS THE WHOLE REASON THIS FILE EXISTS. Elementor stacks
 * the items into one block and takes the top border off every item after the
 * first, so the group reads as a single bordered table. The frame draws four
 * cards 14px apart. `gap` on a flex column undoes the join; the `border-block-
 * start: none` on adjacent items has to be put back explicitly or the second
 * card onwards loses its top edge.
 */
.elementor-widget-accordion .elementor-accordion {
	display: flex;
	flex-direction: column;
	gap: 14px;
}

.elementor-widget-accordion .elementor-accordion .elementor-accordion-item,
.elementor-widget-accordion .elementor-accordion .elementor-accordion-item + .elementor-accordion-item {
	border: 1px solid var(--oew-line);
	border-radius: var(--oew-radius);
	background-color: var(--oew-card);

	/*
	 * `clip` rather than `hidden`: the card never scrolls, and `hidden` makes a
	 * scroll container that clips the focus ring on the title inside it. Same
	 * reasoning as the hero band.
	 */
	overflow: clip;
}

/*
 * The question row. A flex row rather than Elementor's floated icon, because a
 * float cannot vertically centre the indicator against a title that has wrapped
 * to two lines, which real questions do at this width.
 */
.elementor-widget-accordion .elementor-accordion .elementor-tab-title {
	display: flex;
	gap: 16px;
	align-items: center;
	justify-content: space-between;
	min-block-size: 80px;
	margin: 0;
	padding: 22px 26px;
	border: 0;
	background: none;
	cursor: pointer;
}

/*
 * KEYBOARD FOCUS, WHICH ELEMENTOR NEVER GAVE THIS WIDGET. Its shipped
 * `widget-accordion.min.css` puts an unconditional `outline: none` on the
 * title, with no `:focus-visible` rule and no border fallback like the tabs
 * widget carries, so a keyboard user tabbing an FAQ list gets nothing at all
 * (WCAG 2.4.7). This file owns the accordion's whole look, so it owns the gap
 * too. Same treatment as the tab titles below, at the same one level above
 * Elementor's rule. Raised in review on PR #5.
 *
 * The offset is NEGATIVE, unlike the tabs': the title fills its card
 * edge-to-edge and the card is `overflow: clip` (see above), so a ring drawn
 * outside the title's box would be cut off at all four sides. Drawn inside,
 * it follows the card's rounded corners and loses nothing.
 */
.elementor-widget-accordion .elementor-accordion .elementor-tab-title:focus-visible {
	outline: 2px solid var(--oew-text);
	outline-offset: -2px;
}

/*
 * 18px Bold at 23.4 is off the registered scale, which has Body/Default at 17
 * and jumps to Body/Lead at 22. Held literal rather than bent onto a token that
 * is not it. If an 18px step is ever added to the scale, this is the one place
 * that changes.
 */
.elementor-widget-accordion .elementor-accordion .elementor-accordion-title {
	font-size: 18px;
	font-weight: 700;
	line-height: 23.4px;
	color: var(--oew-text);
	text-decoration: none;
	order: 1;
	flex: 1 1 auto;
}

/*
 * The indicator. Elementor draws a bare glyph floated right in a 1.5em box; the
 * frame draws a 36px Mint disc with an 18px mark centred in it. `order` puts it
 * after the title in the visual row while leaving it first in the DOM, which is
 * where Elementor prints it and where it should stay: the icon is decoration and
 * a screen reader should reach the question text first.
 */
.elementor-widget-accordion .elementor-accordion .elementor-tab-title .elementor-accordion-icon {
	display: grid;
	place-items: center;
	flex: 0 0 auto;
	order: 2;
	inline-size: 36px;
	block-size: 36px;
	border-radius: 999px;
	background-color: var(--oew-indicator);
	color: var(--oew-text);
	float: none;
	text-align: center;

	/*
	 * `line-height: 0` IS WHAT ACTUALLY CENTRES THE MARK, and without it the
	 * grid above only looks like it does. Elementor wraps the glyph in a pair
	 * of spans, `-closed` and `-opened`, and shows one at a time. That span is
	 * a block containing an inline SVG, so it gets a text line box: measured at
	 * 38px tall inside this 36px circle, with the 18px mark sitting on the
	 * baseline rather than in the middle of it.
	 *
	 * The grid dutifully centres the 38px span, and the mark inside it came out
	 * 7.75px low. Bryce reported it as the accordions looking broken on
	 * 17 Aug 2026, and 7.75px off centre in a 36px disc is exactly that.
	 *
	 * Collapsing the line box makes the span hug the mark, so the grid is then
	 * centring the mark itself. The `i` rule below restores a line height for
	 * the font icon case, which needs one to have any height at all.
	 */
	line-height: 0;
}

.elementor-widget-accordion .elementor-accordion .elementor-tab-title .elementor-accordion-icon i {
	font-size: 18px;
	line-height: 1;
}

/* Whichever way the icon library renders, a glyph or an inline SVG. */
.elementor-widget-accordion .elementor-accordion .elementor-tab-title .elementor-accordion-icon svg {
	inline-size: 18px;
	block-size: 18px;
	fill: currentcolor;
}

/*
 * The answer. Elementor puts a hairline above it and 15px of padding; the frame
 * carries the card's own border and nothing else, so the rule comes off.
 *
 * The left inset matches the question's 26px rather than the frame's 33px. That
 * 7px is a nudge in the artboard, not a decision: nothing else on the card is
 * indented past the question, and aligning the two is what the card looks like
 * it is doing.
 */
.elementor-widget-accordion .elementor-accordion .elementor-tab-content {
	padding: 0 26px 26px;
	border: 0;
	background: none;
	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);
	color: var(--oew-text);
}

.elementor-widget-accordion .elementor-accordion .elementor-tab-content > :first-child {
	margin-block-start: 0;
}

.elementor-widget-accordion .elementor-accordion .elementor-tab-content > :last-child {
	margin-block-end: 0;
}

/* -------------------------------------------------------------------------
 * Tabs.
 * ---------------------------------------------------------------------- */

/*
 * The row. One hairline under the whole row, drawn here rather than with
 * Elementor's trick of hanging a 999em border off the active tab's `::before`
 * and `::after`. That trick exists to make the active tab look cut out of a
 * bordered strip, which is not what the frame draws, and it costs both
 * pseudo elements on the element that needs one for its underline.
 *
 * The tabs hug their labels 28px apart. Elementor's own alignment control could
 * spread them instead, and must not be set to `stretch` in the widget: that
 * gives four equal quarters and the design draws a left aligned cluster.
 *
 * BEHIND A MIN-WIDTH, WHICH IT WAS NOT. Unconditional, this `display: flex`
 * scores three classes and outranks Elementor's own two-class rule hiding the
 * row on mobile, so the row stayed visible on a phone. The media query at the
 * bottom of this file put it back, but only for tabs inside
 * `#agendtheme-content`: a tabs widget in an Elementor popup or a theme builder
 * part showed the desktop row and the mobile titles at once, which is the same
 * double navigation this file's header note blames the theme for. Found by
 * Nathan in review on PR #5.
 *
 * 768 matches this site's configured Elementor mobile breakpoint rather than
 * Elementor's stock 767. See the note on the media query at the bottom.
 */
@media (min-width: 769px) {
	.elementor-widget-tabs .elementor-tabs .elementor-tabs-wrapper {
		display: flex;
		flex-wrap: wrap;
		gap: 28px;
		overflow: visible;
	}
}

.elementor-widget-tabs .elementor-tabs .elementor-tabs-wrapper {
	border-block-end: 1.5px solid var(--oew-line);
}

/*
 * NO PADDING ANYWHERE IN HERE, WHICH IS LOAD BEARING. The 32px box and the
 * bottom anchored underline reproduce the frame's 18px label with an 11px gap
 * under it without ever asking for padding back. The `padding: 0` below is
 * this file's own: Elementor ships 20px/25px on this element unconditionally,
 * and relying on the theme's id-scoped zero left the row 72px tall in exactly
 * the popup and theme-builder contexts the media-query fix was written for.
 * Raised in review on PR #5.
 */
.elementor-widget-tabs .elementor-tabs .elementor-tab-desktop-title {
	position: relative;
	display: flex;
	align-items: flex-start;
	min-block-size: 32px;
	padding: 0;
	border: 0;
	background: none;
	font-size: 17px;
	/*
	 * Weight 500. The scale carries 17px only at Light 300 and no global carries
	 * Medium at all, the same gap already open on the top level nav link and the
	 * utility bar. Literal until a UI label weight is registered.
	 */
	font-weight: 500;
	line-height: 1;
	color: var(--oew-muted);
	cursor: pointer;
}

.elementor-widget-tabs .elementor-tabs .elementor-tab-desktop-title.elementor-active {
	border: 0;
	background: none;
	font-weight: 700;
	color: var(--oew-text);
}

/*
 * KEYBOARD FOCUS, WHICH THE `border: 0` ABOVE WAS CANCELLING. Elementor's own
 * focus indicator on a tab title is a border (`:focus-visible` at three
 * classes) and its outline is `var(--focus-outline, none)`, so whenever this
 * file loads after Elementor's, the reset above tied that rule and won on
 * source order, leaving a keyboard user nothing at all (WCAG 2.4.7). Raised in
 * review on PR #5.
 *
 * One level above Elementor's rule, same as everything else in this file, so
 * the answer does not depend on which file loaded last. An outline rather than
 * putting the border back: the resting state above carries no border, so a
 * border appearing on focus would grow the box and nudge the row, where an
 * outline paints outside it and moves nothing.
 */
.elementor-widget-tabs .elementor-tabs .elementor-tab-desktop-title:focus-visible {
	/*
	 * `border: 0` here too, because the reset above ties Elementor's own
	 * 1px-black focus border at equal specificity and loses on source order:
	 * the outline made focus visible either way, but a load-order flip would
	 * have added the black border back and nudged the row, the exact jitter
	 * the outline was chosen to avoid. Raised in review on PR #5.
	 */
	border: 0;
	outline: 2px solid var(--oew-text);
	outline-offset: 2px;
}

/*
 * Elementor's cut out border, off. Both pseudo elements are claimed on the
 * active tab at four classes, so this has to reach five to answer them, and
 * `::after` is then free to be the underline.
 */
.elementor-widget-tabs.elementor-tabs-view-horizontal .elementor-tabs .elementor-tab-desktop-title.elementor-active::before {
	content: none;
}

/*
 * The underline. A pseudo element rather than `border-block-end`, because the
 * frame rounds it to a 999px pill and a border cannot be rounded on one edge.
 * Sits on the row's hairline rather than above it, which is what the frame
 * draws: the pill covers the hairline for the width of the active label.
 */
.elementor-widget-tabs.elementor-tabs-view-horizontal .elementor-tabs .elementor-tab-desktop-title.elementor-active::after {
	content: "";
	display: block;
	position: absolute;
	inset-inline: 0;
	inset-block-end: -1.5px;
	block-size: 3px;
	inline-size: auto;
	border: 0;
	border-radius: 999px;
	background-color: var(--oew-underline);
}

/*
 * The panel. Elementor borders it on three sides and pads it 20px; the frame
 * draws neither, just air between the row and the copy.
 */
.elementor-widget-tabs .elementor-tabs .elementor-tabs-content-wrapper {
	border: 0;
	background: none;
}

.elementor-widget-tabs .elementor-tabs .elementor-tab-content {
	padding: 32px 0 0;
	border: 0;
	background: none;
	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);
	color: var(--oew-text);
}

.elementor-widget-tabs .elementor-tabs .elementor-tab-content > :first-child {
	margin-block-start: 0;
}

.elementor-widget-tabs .elementor-tabs .elementor-tab-content > :last-child {
	margin-block-end: 0;
}

/*
 * Below Elementor's own 768 breakpoint the desktop row is hidden and the widget
 * turns into a stack of accordion style rows, each title sitting above its own
 * panel. No mobile frame was drawn for either of these components, so what
 * follows is invented to match the desktop reading rather than measured, and
 * needs designing before client sign off. Same caveat as the news block.
 */
@media (max-width: 768.98px) {
	/*
	 * THE ONE ID SELECTOR IN THIS FILE. See point 2 of the header note: the theme
	 * forces `display: flex` on this row from `#agendtheme-content` with no media
	 * query, which cancels Elementor's own rule hiding it below 768 and shows the
	 * widget's navigation twice on a phone. An id can only be answered by an id,
	 * and the repeated `.elementor-widget-tabs` takes this to one class above the
	 * theme so it wins on specificity rather than on which file loaded last.
	 *
	 * This rule can go the day `_elementor.scss:324` is fixed, but check the
	 * desktop title's `padding: 0` first: it was added precisely so a theme
	 * cleanup here cannot quietly hand the row back Elementor's 20px/25px.
	 *
	 * 768 AND NOT 767, WHICH IS SITE SPECIFIC AND WORTH KNOWING. Elementor's
	 * shipped `widget-tabs.min.css` splits at 767/768, and reading that file
	 * alone says this should be `max-width: 767px`. This site overrides the
	 * mobile breakpoint to 768 in the Elementor kit, so Elementor regenerates its
	 * own rules at 768/769 and the mobile titles are visible AT 768. Changing
	 * this to 767 would leave the desktop row and the mobile titles both showing
	 * at exactly 768, which is the defect this rule exists to prevent: measured,
	 * not reasoned. Raised in review on PR #5 and checked at 766, 767, 768, 769
	 * and 1024.
	 *
	 * If anyone changes the kit's mobile breakpoint, this number and the
	 * `min-width` further up have to move with it.
	 *
	 * .98 AND NOT A WHOLE NUMBER: width media features compare the actual,
	 * possibly fractional CSS-px viewport, and browser zoom routinely produces
	 * one. A plain 768 against the desktop rules' 769 left the open interval
	 * (768, 769) where neither block applied and only the theme's unconditional
	 * flex stood, so at 768.4px the double navigation came back. The .98 closes
	 * it the way Bootstrap's boundaries do. Raised in review on PR #5.
	 */
	#agendtheme-content .elementor-widget-tabs.elementor-widget-tabs .elementor-tabs .elementor-tabs-wrapper {
		display: none;
	}

	.elementor-widget-tabs .elementor-tabs .elementor-tab-mobile-title {
		padding: 18px 0;
		border: 0;
		border-block-start: 1px solid var(--oew-line);
		font-size: 17px;
		font-weight: 700;
		line-height: 1.2;
		color: var(--oew-text);
		cursor: pointer;
	}

	/*
	 * THE OPEN TITLE STAYS IN INK, WITH AN OCHRE BAR ABOVE IT. The first pass
	 * flipped the active label to `--oew-underline`, and that ochre computes
	 * 3.62:1 against the white body: at 17px/700 the label sits under the
	 * large-text threshold, so WCAG 1.4.3 asks 4.5:1 and it fails. The bar is
	 * the desktop underline's 3px, painted as an inset shadow rather than a
	 * border so activating a row does not grow it and nudge the stack. Still
	 * invented pending the mobile design pass, like everything in this block.
	 * Raised in review on PR #5.
	 */
	.elementor-widget-tabs .elementor-tabs .elementor-tab-mobile-title.elementor-active {
		box-shadow: inset 0 3px 0 0 var(--oew-underline);
		color: var(--oew-text);
	}

	.elementor-widget-tabs .elementor-tabs .elementor-tab-content {
		padding: 0 0 18px;
	}

	.elementor-widget-tabs .elementor-tabs .elementor-tabs-content-wrapper {
		border-block-end: 1px solid var(--oew-line);
	}
}

/* -------------------------------------------------------------------------
 * `ota-check-list`, an Icon List. Node 241:14295.
 * ---------------------------------------------------------------------- */

/*
 * OPT IN, SO NOTHING HERE MAY ASSUME A CHECK MARK. Every rule is geometry. The
 * glyph, its colour and the label text all stay on the widget's own controls,
 * where an editor can still reach them, and the type is already right from the
 * Body/Default global. What the controls could not get right is the size and
 * the rhythm, because Elementor drives both through variables that also feed a
 * margin, so setting one moves the other.
 *
 * A flex column with a real `gap` rather than Elementor's `space_between`, which
 * splits its value across a bottom margin and a bottom padding on every item.
 * That inflates the item box, so the row pitch stops matching the number in the
 * control: 12 in the field measured 8 between the boxes on this page.
 */
.ota-check-list .elementor-icon-list-items {
	display: flex;
	flex-direction: column;
	gap: 12px;
}

/*
 * `flex-start`, not Elementor's centre. On one line the two are identical, and
 * the frame only ever draws one line. Real copy wraps at narrow widths, and a
 * centred mark on a two line item floats into the gap between the lines instead
 * of sitting against the first, which is where a check mark means anything.
 */
.ota-check-list .elementor-icon-list-item {
	align-items: flex-start;
	gap: 12px;
}

/*
 * 22px, from the frame, against the 16 the control was set to.
 *
 * `--e-icon-list-icon-size` is Elementor's own variable and setting it here is
 * what makes the glyph honour the size whichever way the icon library renders,
 * an inline SVG or a font glyph. It is not enough on its own though: the same
 * variable also feeds a right margin of a quarter of itself on the SVG, so
 * raising the size to 22 would silently push the label 5.5px further out. The
 * margin is zeroed and the 12px stands on its own as the row's `gap`, which is
 * the 34px the frame measures from the mark's left edge to the text.
 */
.ota-check-list .elementor-icon-list-icon {
	--e-icon-list-icon-size: 22px;

	flex: 0 0 22px;
	inline-size: 22px;
	block-size: 22px;

	/*
	 * The frame puts the mark 2px down from the top of a 27.2px row. Against the
	 * 28.05px line box the label actually occupies, dead centring the 22px mark
	 * would be 3.02px, so the frame's 2 and the arithmetic agree to within a
	 * pixel. Taking the frame's number.
	 */
	margin-block-start: 2px;
}

/*
 * THE MARK IS THE FRAME'S OWN FILE, NOT AN ICON FROM THE LIBRARY, and this is
 * the one place in this file that overrules a control an editor can see.
 *
 * The frame draws a stroked tick: a three point path at 2.2 weight with round
 * caps, no fill. Font Awesome's `fa-check` is a solid glyph, a filled wedge, and
 * FA Free ships it in that one weight, so there is no lighter variant to pick in
 * the widget. At 16px nobody noticed; at the frame's 22px the difference is the
 * first thing you see. Asked for by Bryce on 17 Aug 2026.
 *
 * So the glyph is hidden and the slot is painted with the file through a mask,
 * exactly as the footer and hero brand marks are, which is why it sits beside
 * them in `assets/img/` rather than being redrawn as a path here. The file is
 * the one Bryce supplied on 17 Aug 2026, not a Figma export: same geometry, but
 * without the `preserveAspectRatio="none"` an export carries, which would
 * distort the tick the day this slot stops being square.
 *
 * THE TRADE, WRITTEN DOWN BECAUSE IT IS INVISIBLE FROM THE EDITOR: the widget's
 * own Icon and Icon Color controls stop having any effect on a list carrying
 * this class. There is no glyph left for them to reach. The tick takes
 * `currentColor` instead, so it follows the list's text colour, which is the
 * same navy the icon colour global was already resolving to: nothing moves on
 * this page, and the two can no longer drift apart. The frame actually strokes
 * it teal `#005361` rather than navy, and that difference is left alone here
 * rather than hardcoded, since it is a palette question and not this one.
 */
.ota-check-list .elementor-icon-list-icon {
	color: inherit;
	background-color: currentcolor;
	-webkit-mask: url("../img/ota-check.svg") no-repeat center / contain;
	mask: url("../img/ota-check.svg") no-repeat center / contain;
}

.ota-check-list .elementor-icon-list-icon svg,
.ota-check-list .elementor-icon-list-icon i {
	display: none;
}

/* Elementor's default 5px, and whatever the indent control wrote, off. The
 * row's `gap` is the only thing setting this distance now. */
.ota-check-list .elementor-icon-list-icon + .elementor-icon-list-text {
	align-self: auto;
	padding-inline-start: 0;
}

/*
 * THE `gap` ABOVE IS NOT THE ONLY THING SPACING THESE ROWS, which is worth an
 * explanation because the symptom is so quiet: the rows come out 8px looser
 * than the frame and every number in the control panel still reads correct.
 *
 * `_content.scss` gives every list in the content area
 *
 *   main#agendtheme-content .agendtheme-content-inner:not(...)
 *     ul:not(...) li + li            { margin-top: 0.5rem }
 *
 * which is prose styling for an editor's bullet list and has no idea this ul is
 * a widget. It lands on the second row onwards and adds to the `gap`, so the
 * first row sits 12px below its heading and the rest 20px apart. Reading the
 * margin off row one, which is the row that has none, says everything is fine.
 *
 * One id, three classes, four elements, because both `:not()`s count their
 * argument. Beating it needs to beat the classes, so the two list classes are
 * named in full: one id, four classes, no elements. Element counts stop
 * mattering once the class count is ahead.
 */
#agendtheme-content .ota-check-list .elementor-icon-list-items .elementor-icon-list-item + .elementor-icon-list-item {
	margin-block-start: 0;
}

/* -------------------------------------------------------------------------
 * `ota-quote`, a Text Editor. Node 241:14308.
 * ---------------------------------------------------------------------- */

/*
 * The ochre bar. `border-inline-start` rather than `border-left` so it moves to
 * the other side under an RTL locale, which is the one thing the per-widget
 * border control could not have expressed: Elementor writes physical sides.
 *
 * The copy is Body/Lead at 22/33 and stays on the widget's global, same as the
 * check list. Only the bar and its inset are design that an editor should not
 * have to re-key.
 */
.ota-quote .elementor-widget-container {
	border-inline-start: 4px solid var(--oew-underline);

	/*
	 * 36 is the frame's 39.79 from the block edge to the text, less the 4 the
	 * bar itself occupies. The 10 top and bottom is the frame's 74px block
	 * around two 33px lines, near enough that the extra half pixel is not worth
	 * a fractional padding.
	 */
	padding: 10px 0 10px 36px;
}

/*
 * The attribution, which the news detail draws under the quote (417:19199 on
 * frame 404:9883) at 14px in the muted colour where the quote itself is Body/
 * Lead. It is the editor's own trailing line inside the same Text Editor,
 * marked up as a `cite`, so the widget gains no settings and a quote with no
 * attribution simply has no `cite` in it.
 *
 * `font-style: normal` is load-bearing: every browser italicises `cite` by
 * default and the frame draws it upright.
 */
.ota-quote cite {
	display: block;
	margin-block-start: 8px;
	font-size: 0.875rem;
	font-style: normal;
	font-weight: 300;
	line-height: 1.65;
	color: var(--oew-muted);
}

/* -------------------------------------------------------------------------
 * `ota-media`, an Image. Nodes 2001:18708, 2001:18725 and 2001:18720.
 * ---------------------------------------------------------------------- */

/*
 * THE ARITHMETIC, because this rule looks needlessly heavy and is not. Point 3
 * of the header note: the theme paints every content image at 4px from
 *
 *   main#agendtheme-content .agendtheme-content-inner:not(...) img
 *
 * which scores one id, two classes and two elements. Beating it needs at least
 * that, and CSS compares the three counts in order, so more classes is the only
 * lever that does not need a second id:
 *
 *   #agendtheme-content .elementor-widget-image.ota-media
 *     .elementor-widget-container img          1 id, 3 classes, 1 element
 *
 * Three classes beats two whatever the element counts are, so this wins on
 * specificity rather than on which stylesheet happened to load last. Dropping
 * any one of the three classes loses, silently and only for images: everything
 * still renders, at the theme's 4px.
 *
 * The radius is on the `img` and not the wrapper because the wrapper has no
 * background to clip, and `overflow` on it would trap the focus ring when the
 * image is inside a link.
 */
#agendtheme-content .elementor-widget-image.ota-media .elementor-widget-container img {
	border-radius: var(--oew-radius);
}

/*
 * POSTS WIDGET, THEME SKIN: THE TITLE TAKES THE COLOUR THE EDITOR SET
 *
 * Teamwork 49460453. On a page with a page-level colour theme, the titles in an
 * Elementor Pro Posts widget painted in that theme's text colour, which on the
 * teal theme is Ash: cream text on the cream content area. Two rules meet to
 * produce that, neither of them in this plugin's widgets:
 *
 * 1. The theme's Posts skin, `src/scss/modules/elementor/widgets/_posts.scss`
 *    around line 271 ("Ensure the titles match the headings. Client request."),
 *    forces `.elementor-post__title` to `var(--at-color-text-heading)` and the
 *    `<a>` inside it to `var(--at-color-text-header-link)`, both `!important`.
 *    That beats the rule Elementor writes for the widget's own Title Colour
 *    control, so the control has never worked on this site.
 *
 * 2. Colour_Themes::get_chrome_map() maps `--at-color-text-header-link` to the
 *    page theme's `text` role, which is correct for the header it was named for
 *    and wrong for a post title in the content area below it. The title is the
 *    `<a>`, so that is the colour a reader sees.
 *
 * The answer is the id, as everywhere else in this file. The theme's selectors
 * score (0,3,0) for the title and (0,3,1) for its link; the ones below add
 * `#agendtheme-content` for (1,3,0), (1,3,1) and (1,4,1) on the hover, so with
 * both sides `!important` this wins on specificity rather than load order.
 *
 * THE VALUE IS THE CONTROL'S. Elementor_Widgets::pipe_control_colours()
 * teaches the Title Colour control to write its value into `--oew-posts-title`
 * on the same elements, so an editor's global or hex still decides. The
 * fallback is Elementor Pro's own default for that control, the Secondary
 * global, which is Navy on this kit and matches the headings around it. The
 * hover is pinned to the same colour because the theme's hover rule would
 * otherwise flash the header link colour back in.
 *
 * Scoped to the `agendtheme` skin, which is the only one the theme rules touch.
 */
#agendtheme-content .elementor-widget-posts[data-agend-widget-variant-name="agendtheme"] .elementor-post__title,
#agendtheme-content .elementor-widget-posts[data-agend-widget-variant-name="agendtheme"] .elementor-post__title a,
#agendtheme-content .elementor-widget-posts[data-agend-widget-variant-name="agendtheme"] .elementor-post__title a:hover {
	color: var(--oew-posts-title, var(--e-global-color-secondary)) !important;
}

/*
 * ICON BOX: A LINKED TITLE TAKES THE COLOUR THE EDITOR SET
 *
 * Same fault as the Posts title above, found while auditing for it. The theme's
 * `src/scss/modules/_elementor.scss` around line 246 forces the `<a>` inside
 * `.elementor-icon-box-title` to the body text colour, and its hover to the
 * accent link colour, both `!important`. Elementor's Title Colour control paints
 * the heading itself, so an unlinked title honours it and a linked one silently
 * does not: same widget, same control, different result depending on whether a
 * link was added. Thirteen Icon Boxes on the site as of Sep 2026.
 *
 * Theme selectors score (0,3,1) and (0,4,1) on hover; adding the id gives
 * (1,3,1) and (1,4,1), so with both sides `!important` this wins on specificity.
 *
 * The property is written on the heading by both the Title Colour control and
 * its Hover twin (see Elementor_Widgets::PIPED_CONTROLS), and custom properties
 * inherit, so the link reads whichever state the heading is in. The fallback is
 * `currentColor`, which on `color` means the heading's own colour: Elementor
 * only writes the control when the editor has touched it, so an untouched Icon
 * Box keeps painting its linked title exactly as its unlinked title, rather
 * than jumping to the control's nominal default (the Primary global, Ochre
 * here) the moment a link is added.
 */
#agendtheme-content .elementor-widget-icon-box .elementor-icon-box-content .elementor-icon-box-title a,
#agendtheme-content .elementor-widget-icon-box .elementor-icon-box-content .elementor-icon-box-title a:hover {
	color: var(--oew-icon-box-title, currentColor) !important;
}

@media (max-width: 600px) {
	/*
	 * The card tightens but the indicator does not shrink: it is the touch
	 * target, and 36px is already under the 44px the AAA audit asks for, so
	 * taking it smaller would fail a criterion the type scale was built to pass.
	 */
	.elementor-widget-accordion .elementor-accordion .elementor-tab-title {
		gap: 12px;
		min-block-size: 68px;
		padding: 16px 20px;
	}

	.elementor-widget-accordion .elementor-accordion .elementor-accordion-title {
		font-size: 17px;
		line-height: 22px;
	}

	.elementor-widget-accordion .elementor-accordion .elementor-tab-content {
		padding: 0 20px 20px;
	}
}
