/**
 * Forminator forms, dressed in the VIM design system.
 *
 * Forminator ships its own theme ("forminator-design--default"), which does not
 * know about this site's tokens: the submit button was a small flat rectangle
 * in the plugin's blue, labels were the wrong size, and inputs had none of the
 * site's border or focus treatment.
 *
 * Everything below is scoped to `.forminator-ui` so nothing leaks into the rest
 * of the site, and every colour and size comes from a token — no literal hexes,
 * per the house rules.
 *
 * @package generatepress_child
 */

/* ---------------------------------------------------------------------------
 * The form as a whole
 *
 * Constrained rather than filling the 1400px measure. A single column of inputs
 * stretched across the full width is hard to scan and looks broken; forms read
 * better at roughly the width of the answers people type into them. Widen this
 * one value if a form ever wants to run full width.
 * ------------------------------------------------------------------------- */

.forminator-ui.forminator-custom-form {
	max-width: 48rem;
	margin-inline: 0;
}

/*
 * `vim-form-full` releases that cap — the form fills its container instead
 * (Tom, 2026-08-25, of the contact form: "it should be 100%"). Put the class on
 * the section's inner wrapper, not on the form: the shortcode's own output is
 * Forminator's and we do not control its classes.
 *
 * ⚠️ Three classes, so it outranks the two-class rule above. It has to beat the
 * default rather than merely follow it — source order alone would break if
 * forms.css were ever reordered or split.
 *
 * ⚠️ NOT done by widening the 48rem for everyone. Every other form on the site
 * sits inside a `.vim-form-accordion`, which already releases the cap its own
 * way; changing the default would silently restyle the newsletter overlay,
 * where the modal is the constraint and 48rem is doing no harm.
 */
.vim-form-full .forminator-ui.forminator-custom-form {
	max-width: none;
}

/* ---------- labels ---------- */

.forminator-ui.forminator-custom-form .forminator-label {
	color: var(--teal-900);
	font-size: var(--fs-body, 1rem);
	font-weight: 700;
	margin-bottom: 0.35rem;
}

/*
 * Required fields say so in words.
 *
 * Forminator marks them with a bare asterisk, which is exactly what the forms
 * spec said not to inherit from the live site — an asterisk alone is easy to
 * miss and means nothing to someone who has not been told the convention. The
 * asterisk is collapsed to zero and replaced with the word, which screen
 * readers announce as part of the label.
 */
.forminator-ui.forminator-custom-form .forminator-required {
	font-size: 0;
	color: inherit;
}

.forminator-ui.forminator-custom-form .forminator-required::after {
	content: " (required)";
	font-size: var(--fs-small, 0.875rem);
	font-weight: 400;
	color: var(--body-alt);
}

/* ---------- inputs ---------- */

.forminator-ui.forminator-custom-form .forminator-input,
.forminator-ui.forminator-custom-form .forminator-textarea,
.forminator-ui.forminator-custom-form select {
	width: 100%;
	font-family: inherit;
	font-size: var(--fs-body, 1rem);
	color: var(--body);
	background-color: var(--white);
	border: 1px solid color-mix(in srgb, var(--teal-900) 34%, transparent);
	border-radius: 0.25rem;
	padding: 0.65rem 0.85rem;
	line-height: 1.4;
}

.forminator-ui.forminator-custom-form .forminator-textarea {
	min-height: 9rem;
	resize: vertical;
}

.forminator-ui.forminator-custom-form .forminator-input:hover,
.forminator-ui.forminator-custom-form .forminator-textarea:hover,
.forminator-ui.forminator-custom-form select:hover {
	border-color: var(--teal-700);
}

/*
 * A visible focus ring on the field itself, not just a colour shift — keyboard
 * users need to see where they are.
 */
.forminator-ui.forminator-custom-form .forminator-input:focus,
.forminator-ui.forminator-custom-form .forminator-textarea:focus,
.forminator-ui.forminator-custom-form select:focus,
.forminator-ui.forminator-custom-form input:focus-visible {
	outline: 3px solid var(--accent);
	outline-offset: 1px;
	border-color: var(--teal-900);
}

/* ---------- checkboxes and radios ---------- */

/*
 * With Forminator's own design off, its checkbox and radio rows fall back to
 * `display: inline` — which ran the option text straight into the group's
 * label with no gap. Each option is its own row again, with the box and its
 * text properly separated.
 */
.forminator-ui.forminator-custom-form .forminator-field-checkbox .forminator-label,
.forminator-ui.forminator-custom-form .forminator-field-radio .forminator-label {
	display: block;
	margin-bottom: 0.5rem;
}

.forminator-ui.forminator-custom-form .forminator-checkbox,
.forminator-ui.forminator-custom-form .forminator-radio {
	display: flex;
	align-items: flex-start;
	gap: 0.55rem;
	font-size: var(--fs-body, 1rem);
	color: var(--body);
	margin-bottom: 0.45rem;
	line-height: 1.45;
}

.forminator-ui.forminator-custom-form .forminator-checkbox input,
.forminator-ui.forminator-custom-form .forminator-radio input {
	flex: 0 0 auto;
	margin-top: 0.25em;
}

/* ---------------------------------------------------------------------------
 * The column grid
 *
 * Forminator lays fields out with its own `forminator-col-md-*` classes, but
 * the widths for those live in the design CSS we switched off — so without
 * this every column stacked full width, including the two halves of a split
 * name field. This is the grid, rebuilt in the theme.
 * ------------------------------------------------------------------------- */

/*
 * 🚨 `gap` here is ROW then COLUMN, and the row half was 0 — which is why every
 * field sat flush against the one above it with no breathing room at all
 * (Tom, 2026-08-25: "forms are still too tight"). Measured: 0px between every
 * pair of stacked fields.
 *
 * ⚠️ The vertical spacing HAS to live here rather than as a margin on the
 * fields, because Forminator does not give each field its own row — the whole
 * form body is one `.forminator-row` and every field is a `.forminator-col`
 * inside it. That is also why `.forminator-row + .forminator-row` rules never
 * matched anything: there is only ever one row.
 */
.forminator-ui.forminator-custom-form .forminator-row {
	display: flex;
	flex-wrap: wrap;
	gap: 1.75rem 1rem;
}

.forminator-ui.forminator-custom-form .forminator-row > .forminator-col {
	flex: 1 1 100%;
	min-width: 0;
}

/*
 * 🚨 Page-break markers must be taken OUT of the flex flow, not merely left
 * empty. Forminator emits one `.forminator-field-page-break` per step boundary
 * — genuinely empty: no children, no content, zero height. But it is still a
 * flex item, so it collected a full `row-gap` on each side and every section
 * heading sat 76px below the previous field instead of the intended 48.
 *
 * Measured, not inferred: 28 (gap) + 28 (gap either side of the empty marker)
 * + 20 (the heading's own margin) = 76.
 *
 * ⚠️ `display: none` does not hide these from JavaScript — they stay in the DOM
 * and in `querySelectorAll`, so Forminator's pagination script still finds
 * them. They have no visual role to lose.
 */
.forminator-ui.forminator-custom-form .forminator-row > .forminator-field-page-break {
	display: none;
}

@media (min-width: 640px) {

	.forminator-ui.forminator-custom-form .forminator-row > .forminator-col-md-6 {
		flex: 1 1 calc(50% - 0.5rem);
	}

	.forminator-ui.forminator-custom-form .forminator-row > .forminator-col-md-4 {
		flex: 1 1 calc(33.333% - 0.67rem);
	}

	.forminator-ui.forminator-custom-form .forminator-row > .forminator-col-md-3 {
		flex: 1 1 calc(25% - 0.75rem);
	}
}

/* Rows of fields need breathing room between them. */
.forminator-ui.forminator-custom-form .forminator-row + .forminator-row {
	margin-top: 1.1rem;
}

.forminator-ui.forminator-custom-form .forminator-field-name .forminator-row.forminator-no-margin {
	margin-top: 0;
}

.forminator-ui.forminator-custom-form .forminator-checkbox input:focus-visible + span,
.forminator-ui.forminator-custom-form .forminator-radio input:focus-visible + span {
	outline: 3px solid var(--accent);
	outline-offset: 2px;
}

/* ---------- the submit button ---------- */

/*
 * The same two tokens as .gbp-button--primary, so a form's call to action reads
 * as the same control as every other button on the site. The rule is duplicated
 * rather than the class applied, because the button is Forminator's markup and
 * we do not control what classes it carries.
 */
.forminator-ui.forminator-custom-form button[type="submit"],
.forminator-ui.forminator-custom-form .forminator-button-submit,
.forminator-ui.forminator-custom-form .forminator-pagination-submit {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	background-color: var(--accent);
	color: var(--ink);
	font-family: inherit;
	font-size: var(--fs-body, 1rem);
	font-weight: 800;
	letter-spacing: 0.02em;
	line-height: 1;
	text-transform: uppercase;
	text-decoration: none;
	border: 0;
	border-radius: 999px;
	padding: 0.875rem 1.75rem;
	cursor: pointer;
	transition: background-color 0.25s ease, color 0.25s ease;
}

.forminator-ui.forminator-custom-form button[type="submit"]:is(:hover, :focus),
.forminator-ui.forminator-custom-form .forminator-button-submit:is(:hover, :focus),
.forminator-ui.forminator-custom-form .forminator-pagination-submit:is(:hover, :focus) {
	background-color: var(--accent-dark);
	color: var(--ink);
}

.forminator-ui.forminator-custom-form button[type="submit"]:focus-visible,
.forminator-ui.forminator-custom-form .forminator-pagination-submit:focus-visible {
	outline: 3px solid var(--ink);
	outline-offset: 2px;
}

/*
 * Space the submit button away from the last field (Tom, 2026-08-25: "pad
 * button away from form on all forms it is touching").
 *
 * ⚠️ The `.forminator-row + .forminator-row` rule above does NOT cover this.
 * The submit row's previous sibling is not always another .forminator-row —
 * on the donation form it is an unclassed div — so the adjacent-sibling
 * selector silently misses and the button ends up flush against the field
 * above it. Targeting the row itself is what makes this hold on every form.
 *
 * Specificity ties with the `+` rule (four classes each), so this must stay
 * BELOW it in the file to win and normalise the gap to one value everywhere.
 */
.forminator-ui.forminator-custom-form .forminator-row.forminator-row-last,
.forminator-ui.forminator-custom-form .forminator-pagination-footer {
	margin-top: 1.75rem;
}

/* ---------- multi-step navigation (the volunteer form) ---------- */

/*
 * The step indicator across the top of a paginated form.
 *
 * With `form-style: none` Forminator ships no styling for this at all, so the
 * steps rendered as full-width stacked blocks — a stack of teal slabs above the
 * first question that read as broken buttons rather than as progress.
 *
 * Laid out as a single wrapping row: dot, label, dot, label. The current step
 * takes the approved accent/ink pair rather than white-on-teal, and the row
 * carries a rule beneath it so it reads as a header for what follows.
 */
.forminator-ui.forminator-custom-form .forminator-pagination-steps {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 0.4rem 0.75rem;
	margin-bottom: 1.75rem;
	padding-bottom: 1rem;
	border-bottom: 1px solid color-mix(in srgb, var(--teal-900) 20%, transparent);
}

.forminator-ui.forminator-custom-form .forminator-step {
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
	width: auto;
	margin: 0;
	padding: 0.4rem 0.9rem;
	border: 0;
	border-radius: 999px;
	background-color: transparent;
	color: var(--body-alt);
	font-size: var(--fs-small, 0.875rem);
	font-weight: 700;
	line-height: 1.2;
	cursor: pointer;
}

.forminator-ui.forminator-custom-form .forminator-step:is(:hover, :focus) {
	background-color: color-mix(in srgb, var(--teal-900) 10%, transparent);
	color: var(--teal-900);
}

.forminator-ui.forminator-custom-form .forminator-step:focus-visible {
	outline: 3px solid var(--teal-900);
	outline-offset: 2px;
}

.forminator-ui.forminator-custom-form .forminator-current {
	background-color: var(--accent);
	color: var(--ink);
}

/*
 * The dot is the only thing distinguishing a completed step from a pending one
 * for someone who is not reading the labels, so it takes the current text
 * colour rather than a fixed one.
 */
.forminator-ui.forminator-custom-form .forminator-step-dot {
	/* Forminator prints the dot after its label; leading it reads as a marker
	   for the step rather than as punctuation trailing the words. */
	order: -1;
	width: 0.55rem;
	height: 0.55rem;
	border-radius: 50%;
	background-color: currentColor;
	flex: 0 0 auto;
}

.forminator-ui.forminator-custom-form .forminator-pagination-footer {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 0.75rem;
	margin-top: 1.75rem;
}

.forminator-ui.forminator-custom-form .forminator-button-back {
	background-color: transparent;
	color: var(--teal-900);
	border: 2px solid var(--teal-900);
	border-radius: 999px;
	font-weight: 800;
	text-transform: uppercase;
	padding: 0.75rem 1.5rem;
	cursor: pointer;
}

.forminator-ui.forminator-custom-form .forminator-button-next {
	background-color: var(--teal-900);
	color: var(--white);
	border: 0;
	border-radius: 999px;
	font-weight: 800;
	text-transform: uppercase;
	padding: 0.875rem 1.75rem;
	cursor: pointer;
}

.forminator-ui.forminator-custom-form .forminator-button-next:is(:hover, :focus) {
	background-color: var(--teal-700);
}

/* ---------- file upload ---------- */

.forminator-ui.forminator-custom-form .forminator-button-upload {
	background-color: var(--sand);
	color: var(--teal-900);
	border: 1px solid color-mix(in srgb, var(--teal-900) 34%, transparent);
	border-radius: 0.25rem;
	font-weight: 700;
	padding: 0.6rem 1rem;
	cursor: pointer;
}

/* ---------- section headings inside a form ---------- */

/*
 * A section heading belongs to what FOLLOWS it, so it needs air above and very
 * little below (Tom, 2026-08-25: "the headers need space at the top and less
 * below"). Left alone it had the opposite: no top margin at all, so
 * "How you would like to help" sat hard against the field above it, then 24px
 * plus a rule plus 40px before the first checkbox — the heading read as the tail
 * of the previous section rather than the start of the next.
 *
 * The space goes on the SECTION WRAPPER, not the h2. Forminator wraps each
 * section in `.forminator-field-section`, and putting the top margin there
 * separates the whole block — heading, rule and all — from the field above.
 */
/*
 * ⚠️ 1.25rem, not 3rem — this ADDS to the row's 1.75rem `row-gap` rather than
 * replacing it, so the space above a heading is 20 + 28 = 48px, which is the
 * figure that was signed off. Flex gaps and margins do not collapse. Change the
 * row-gap and this needs re-deriving.
 */
.forminator-ui.forminator-custom-form .forminator-field-section {
	margin-top: 1.25rem;
}

/*
 * ⚠️ Except the first one. A form that opens with a section heading would
 * otherwise start with dead space above its own first line — most visible
 * inside an accordion, where the panel's top edge is right there.
 *
 * 🚨 Anchored to the SECTION, not to its row, and the difference is the whole
 * bug. Forminator does NOT put each field in its own row: the entire form body
 * is ONE `.forminator-row`, and every field and section heading is a
 * `.forminator-col` inside it. Measured on the volunteer form, the four
 * sections sit at child indices 0, 7, 10 and 16.
 *
 * So a rule hung off `.forminator-row:first-child` matches that single shared
 * row and cascades to all four headings, silently zeroing every one — which is
 * exactly what happened before this was measured. Only
 * `.forminator-field-section:first-child` picks out the one at index 0, which
 * is the form's opening heading and the only one that should have no space
 * above it.
 */
.forminator-ui.forminator-custom-form .forminator-field-section:first-child {
	margin-top: 0;
}

.forminator-ui.forminator-custom-form .forminator-title {
	color: var(--teal-900);
	font-size: var(--fs-heading, 1.625rem);
	font-weight: 600;
	margin-bottom: 0.4rem;
}

/*
 * The rule under a section heading. Forminator ships it as its own element, and
 * with the heading's margin reduced it needs its own tightening or the gap
 * simply moves from above the rule to below it.
 */
.forminator-ui.forminator-custom-form .forminator-border {
	margin-top: 0;
	margin-bottom: 1.25rem;
}

/* ---------- messages ---------- */

/*
 * Errors and the success message carry text, an icon and a colour — never
 * colour alone, which is the requirement the forms spec set out.
 */
.forminator-ui.forminator-custom-form .forminator-error-message {
	color: var(--plum);
	font-size: var(--fs-small, 0.875rem);
	font-weight: 700;
	margin-top: 0.3rem;
}

.forminator-ui.forminator-custom-form .forminator-response-message {
	font-size: var(--fs-body, 1rem);
	padding: 0.9rem 1.1rem;
	border-radius: 0.25rem;
}

/*
 * The response area is printed empty on page load, waiting to be filled after a
 * submission. Given padding it showed as a blank grey bar above every form, so
 * it stays out of the flow until it actually has something to announce.
 */
.forminator-ui.forminator-custom-form .forminator-response-message:empty {
	display: none;
	padding: 0;
}

.forminator-ui.forminator-custom-form .forminator-response-message.forminator-success {
	background-color: color-mix(in srgb, var(--accent) 22%, transparent);
	color: var(--ink);
}

.forminator-ui.forminator-custom-form .forminator-response-message.forminator-error {
	background-color: color-mix(in srgb, var(--plum) 14%, transparent);
	color: var(--plum);
}

/* ---------------------------------------------------------------------------
 * Long option lists wrap into columns
 *
 * Forminator stacks every radio and checkbox one per line. That is right for a
 * short list, and wrong for the donation form's nine amounts or the volunteer
 * application's sixteen roles — nine dollar figures in a single column at
 * 1273px is a screenful of almost entirely empty page, and it pushes the rest
 * of the form below the fold for no reason.
 *
 * 🚨 THE `:nth-of-type(4)` GATE IS LOAD-BEARING, not a flourish. Several groups
 * on this site are a SINGLE option carrying a 45–53 character sentence — the
 * newsletter opt-in, the Heritage Society statements. Dropped into a column
 * grid those get squeezed to one narrow track and wrap into a ragged block, so
 * only groups of four or more options are gridded. Every group that stays
 * stacked (n = 1, 2 or 3) is either long-form prose or three short words, and
 * both read better in a column.
 *
 * The options are siblings of the label inside `.forminator-field`, so the
 * label is forced onto its own full-width line rather than becoming a column
 * of its own.
 *
 * `:has()` is the gate; where it is unsupported the whole rule is skipped and
 * the lists simply stay stacked, which is today's layout — a safe fallback
 * rather than a broken one.
 *
 * 🚨 **THIS IS FLEX, NOT GRID, AND IT MUST STAY FLEX.** Grid is the obvious
 * reach for "columns" and it was tried twice, and both attempts were wrong in
 * the same way:
 *
 *   1. `repeat(auto-fill, minmax(X, 1fr))` divides the row equally, so every
 *      option sits glued to the left of a track far wider than it needs —
 *      "$5,000" marooned in a 16rem column. The group reads as scattered
 *      rather than as a list.
 *   2. `repeat(auto-fill, minmax(X, max-content))` looks like the fix and is a
 *      trap. **`auto-fill` computes the NUMBER of tracks from the MINIMUM**,
 *      then those tracks cannot all grow to `max-content`, so they settle near
 *      the minimum and the long labels WRAP. At a 5rem floor the volunteer
 *      application's "Clinical Support" was breaking across two lines inside
 *      an 82px track. Nothing about the rule looks wrong; you only catch it by
 *      measuring option HEIGHTS and comparing `scrollWidth` to `clientWidth`.
 *      And `minmax(max-content, …)` is not a way out — `auto-fill` requires a
 *      definite minimum, so that declaration is simply dropped.
 *
 * Flex has neither problem: each option is sized by its own content, is never
 * squeezed below it, and wraps when the row runs out. The cost is that columns
 * do not line up between rows, which for a wrapping list of options is not
 * something anyone reads down anyway.
 *
 * 🚨 **The longest label in a group still matters — it is just no longer
 * contagious.** Under grid, one long option widened every track, which is why
 * the donation amounts would not close up while the last one read "Another
 * amount". Shortening it to "Other" (what the live site says anyway) fixed
 * that, and is worth keeping regardless: look at the longest label first when
 * a group refuses to tighten.
 *
 * ⚠️ **`column-gap` is now the ONLY thing separating one option from the next**
 * (Tom, 2026-08-25: *"the gift frequency bullets are too close — space them a
 * little more"*). Under grid, short labels got the gap plus their track's
 * trailing slack, so the amounts read as comfortably spaced while the gift
 * frequencies — whose labels filled their tracks — got the gap and nothing
 * else. With content-sized flex items every group gets exactly this value, so
 * tune it against a group of SHORT labels; that is the tightest case.
 */
.forminator-ui.forminator-custom-form .forminator-field:has(> label.forminator-radio:nth-of-type(4)),
.forminator-ui.forminator-custom-form .forminator-field:has(> label.forminator-checkbox:nth-of-type(4)) {
	display: flex;
	flex-wrap: wrap;
	align-items: baseline;
	column-gap: 2.25rem;
	row-gap: 0.55rem;
}

/*
 * Each option keeps its own width and never shrinks — `flex: 0 0 auto` is what
 * stops flexbox reintroducing the squeeze that grid caused.
 */
.forminator-ui.forminator-custom-form .forminator-field:has(> label.forminator-radio:nth-of-type(4)) > label,
.forminator-ui.forminator-custom-form .forminator-field:has(> label.forminator-checkbox:nth-of-type(4)) > label {
	flex: 0 0 auto;
	max-width: 100%;
}

.forminator-ui.forminator-custom-form .forminator-field:has(> label.forminator-radio:nth-of-type(4)) > .forminator-label,
.forminator-ui.forminator-custom-form .forminator-field:has(> label.forminator-checkbox:nth-of-type(4)) > .forminator-label {
	flex: 0 0 100%;
}

/*
 * The stacked lists get their spacing from the label's own bottom margin; in a
 * grid that margin fights `row-gap` and doubles the first row's offset.
 */
.forminator-ui.forminator-custom-form .forminator-field:has(> label.forminator-radio:nth-of-type(4)) > label,
.forminator-ui.forminator-custom-form .forminator-field:has(> label.forminator-checkbox:nth-of-type(4)) > label {
	margin-bottom: 0;
}

/* ---------------------------------------------------------------------------
 * Long forms in an accordion
 *
 * A thirty-field application dominating a page is the thing people bounce off,
 * so the long forms sit behind a labelled toggle (Tom, 2026-08-24).
 *
 * ⚠️ The accordion's own appearance is NOT here — it lives in interior.css as
 * `.vim-accordion`, because FAQs use the same component and this stylesheet is
 * only enqueued when Forminator is active. What remains below is the handful of
 * rules that are genuinely about a form sitting inside a panel.
 * ------------------------------------------------------------------------- */

/*
 * wpautop wraps a shortcode block in paragraph tags and leaves an empty <p> on
 * each side of the form it renders. Those inherit the panel padding above plus
 * GeneratePress's paragraph margin, which put 44px of nothing between the
 * accordion header and the first field, and the same again under the submit
 * button.
 */
.vim-form-accordion .gb-accordion__content > p:empty {
	display: none;
}

/*
 * Forms inside an accordion panel run the full measure (Tom, 2026-08-25:
 * "make form full width"). The earlier 56rem cap was there because a
 * single-column input at 1400px is a very long empty box — the two-up rows in
 * .forminator-row above are what keep that readable now, so the cap goes.
 *
 * 🚨 Two traps here, both found by measuring rather than by reading the CSS.
 *
 * 1. Forminator emits per-form CSS keyed to
 *    `#forminator-module-<id>:not(.select2-dropdown){padding:0}`. That is an ID
 *    selector, so it outranks any class rule in this file. `max-width` on our
 *    rule applies while `padding` on the SAME rule is silently discarded, which
 *    makes the rule look like it worked. `!important` is the only way to beat an
 *    id rule from a class selector, and there is no Forminator setting for this
 *    padding once `form-style: none` is on. That is why it is used here — it is
 *    a targeted override of one hard-coded declaration, not a general habit.
 *
 * 2. The padding must sit on the FORM, not on `.gb-accordion__content`. A closed
 *    GB Pro panel collapses with `max-height: 0; overflow: hidden`, which clips
 *    children but does NOT remove the panel's own padding — putting it there
 *    left every closed accordion showing a 56px empty white band under its
 *    toggle. On the form it is inside the clipped area, so a closed panel stays
 *    at zero height.
 */
.vim-form-accordion .forminator-ui.forminator-custom-form {
	max-width: none;
}

.vim-form-accordion .gb-accordion__content > * {
	padding: 1.5rem 1.75rem 2rem !important;
}

@media (max-width: 640px) {

	.vim-form-accordion .gb-accordion__content > * {
		padding: 1.25rem 1.1rem 1.5rem !important;
	}
}

/* On a --teal-900 band the labels and helper text have to invert. */
.vim-section--teal .forminator-ui.forminator-custom-form .forminator-label,
.vim-section--teal .forminator-ui.forminator-custom-form .forminator-checkbox,
.vim-section--teal .forminator-ui.forminator-custom-form .forminator-radio {
	color: var(--white);
}
