@charset "UTF-8";
/**
 * Gravity Forms — the THEME-LEVEL skin for directly-embedded forms.
 *
 * Source for `assets/css/gravity-forms.css`. This is a thin ENTRY, not a
 * second skin: every rule it emits comes from the shared engine at
 * `src/blocks/_shared/_gravity-forms.scss`, which is a partial and therefore
 * only compiled when something `@use`s it. Until this file existed the only
 * consumers were meant to be form BLOCKS — so a form dropped straight onto a
 * page (the `wp:gravityforms/form` block, the `[gravityform]` shortcode, a
 * `gravity_form()` call in a template) rendered with GF's stock styles and
 * nothing of ours.
 *
 * MEASURED on https://saconnects.local/design-system/ (form 1, 22 field types),
 * so the scope of the job is not guesswork: GF's own CSS IS delivered and
 * healthy there — `gform_basic` (50,413 chars, 404 `.gravity-theme` selectors)
 * and `gform_theme` (32,375 chars, 315) are both inlined into <head> — and the
 * controls were STILL at browser defaults, because the lean gravity-theme
 * simply does not paint them: the text input carried the UA's
 * `2px rgb(118,118,118)` border, `border-radius: 0`, `padding: 8px`,
 * `font-size: 15px`, the checkbox and radio were the UA's 13×13 squares, and
 * the submit was Chrome's UA button verbatim (`#F0F0F0` / `padding: 1px 6px` /
 * `13.3333px` / weight 400). We are layering on top of GF's base, not
 * replacing it, and the geometry is entirely ours.
 *
 * WHY THE LEAN THEME AT ALL: functions.php forces
 * `gform_form_theme_slug` → `gravity-theme` (CLAUDE.md §Third-party
 * integrations — Orbital injects GF-blue custom properties). So our markup is
 * `.gform_wrapper.gravity-theme`, never `.gform-theme--framework`. The GF
 * block also prints an inline `<style>` at `#gform_wrapper_1[data-form-index]`
 * setting `--gf-color-primary` &c.; nothing here reads a `--gf-*` property, so
 * that ID-specificity block is irrelevant to us by construction rather than by
 * out-specifying it.
 *
 * LABELS ARE SHOWN. `engine($labels: visible)` — a directly-embedded form is
 * a multi-field form, and the placeholder-only skin is reserved for
 * single-field ones (block-conventions.md §Forms: a placeholder is not an
 * accessible name, and a seven-field form on that skin ships seven unnamed
 * inputs).
 *
 * FOCUS adds nothing new. functions.php prints the site-wide 3px #4144FF
 * `:focus-visible` ring plus the pointer-modality suppression for text
 * inputs; the engine only RECLAIMS that ring where the plugin sets
 * `outline: 0` at a specificity the generic restatement loses to.
 *
 * Enqueue: `framework-gravity-forms` on `wp_enqueue_scripts` at priority 999,
 * gated on GF's own stylesheets actually being enqueued, with `path` data so
 * the inliner embeds it — see functions.php. It loads AFTER `gform_basic` /
 * `gform_theme`, which is what settles the handful of exact specificity ties
 * with the plugin (e.g. our `.gform_wrapper.gravity-theme input[type=text]`
 * vs its own, both (0,3,1)). Everything the DESIGN depends on is written to
 * win on specificity instead, because §Performance playbook allows GF's CSS
 * to be loaded async on pages where the form is below the fold — which would
 * flip every tie.
 *
 * Build: `npm run build:css` (see package.json).
 */
/**
 * Shared Gravity Forms skin — "the GF engine".
 *
 * Harvested from ASRI (extracted from its newsletter-form on 2026-07-29 when
 * its contact-form was built, so two GF shells could not drift apart), then
 * re-measured against the SAConnects Figma Design System §Forms on 2026-08-20
 * (nodes 14459:8820 field · :8883 controls · :8914 submit row · :8959
 * confirmation · :8877 states). Where the ported ASRI values and the Figma
 * disagreed, the Figma won — every such correction is marked "Figma 2026-08-20"
 * below so the next reader can tell a measurement from a guess.
 *
 * Everything here is keyed on GF's STRUCTURAL markup (.gform_wrapper, .gfield,
 * .gform_footer, input types) rather than on any theme's visual classes, and
 * pinned with `.gravity-theme` so it out-specifies the plugin's own (0,2,x)
 * rules. functions.php forces the lean gravity-theme framework (Orbital injects
 * GF-blue custom properties).
 *
 * SURFACE CONTRACT — the consuming block sets these on its root; nothing below
 * ever names a raw colour, so one block can paint a form on the dark footer
 * band and another a light page panel from the same rules:
 *
 *   --saconnects-gf-input-bg        input / select / textarea fill
 *                                   (the Figma field is transparent on its
 *                                   surface; the footer fields too)
 *   --saconnects-gf-input-ink       input text — the Figma "Filled" state
 *                                   (placeholders are the MUTED body colour,
 *                                   see the `placeholder` mixin)
 *   --saconnects-gf-body            body copy: descriptions/helper text, the
 *                                   sub-labels, the textarea counter
 *   --saconnects-gf-label           field-label ink AND the checkbox/radio
 *                                   option labels (Figma draws those in
 *                                   `contrast`, not in the body grey)
 *   --saconnects-gf-btn-bg / -ink / -bg-hover   the submit pill. Light
 *                                   surface: primary / white / primary-hover
 *                                   (the theme pill). Dark surface: white /
 *                                   contrast / gold-light (the inverse pill).
 *   --saconnects-gf-choice-accent   `accent-color` for the native controls this
 *                                   skin does NOT redraw (multi-select option
 *                                   highlight, range, progress). The checkbox,
 *                                   radio and toggle are drawn from the
 *                                   `custom.input.*` tokens — see the controls
 *                                   block — so accent-color no longer reaches
 *                                   them; the property is kept because it is
 *                                   part of the published contract and still
 *                                   does real work on the rest.
 *
 * Field bounds, states and focus are NOT part of the contract: they are the
 * theme's `custom.input.*` tokens (bounds / active / focus / warning /
 * warning-fill / disabled / disabled-fill / disabled-label), identical on
 * every surface in the Figma Design System.
 *
 * Usage:
 *   @use '../_shared/gravity-forms' as gf;
 *   .wp-block-saconnects-x {
 *     --saconnects-gf-input-bg: …;            // the whole contract
 *     .gform_wrapper.gravity-theme { @include gf.engine($labels: visible); }
 *     .gform_confirmation_wrapper.gravity-theme .gform_confirmation_message {
 *       @include gf.confirmation;             // see the note below — NOT in engine()
 *     }
 *   }
 *
 * THE CONFIRMATION IS NOT INSIDE `.gform_wrapper` — measured on the installed
 * plugin, not assumed. `includes/form-display/block-styles/views/
 * class-confirmation-view.php` builds the lean-theme confirmation as
 * `gform_confirmation_wrapper gravity-theme gform-theme--no-framework` (no
 * `gform_wrapper` class), and the AJAX transport's own inline script runs
 * `jQuery('#gform_wrapper_N').replaceWith(confirmation_content)` — the wrapper
 * is DELETED, not filled. So `.gform_wrapper.gravity-theme .gform_confirmation_message`
 * matches nothing on either transport, and `engine()` (which is emitted inside
 * the wrapper by contract) can never carry the confirmation. That is why the
 * card lives in its own `confirmation` mixin the consumer applies to
 * `.gform_confirmation_wrapper.gravity-theme` — and why the surface-contract
 * custom properties must be set on BOTH wrappers.
 *
 * ARTWORK IS ALWAYS A DATA-URI, never `url('../icons/x.svg')`. This stylesheet
 * is INLINED into <head> by wp_maybe_inline_styles, and a relative url() in
 * inlined CSS resolves against the PAGE, not against the stylesheet, so every
 * file reference would 404 (CLAUDE.md §Performance playbook). The canonical
 * source files for the glyphs drawn below live in `assets/icons/`
 * (chevron-16.svg, search-16.svg, checkbox-selected.svg). A `var()` cannot
 * live inside a data-URI, so every glyph that changes with the surface takes
 * its colour as a URL-ENCODED literal argument and each one names the token
 * it mirrors.
 */
/**
 * Hides a label from sight while KEEPING it in the accessibility tree. Never
 * display:none / visibility:hidden — those delete the accessible name, which is
 * the whole reason the label exists (a placeholder is not a name).
 */
/**
 * The SAConnects input skin (Figma Forms/field 14459:8820; block-conventions.md
 * → Forms): 1px bounds ring, 5px radius, 12px padding, 16px/1.45 text, and the
 * design's states — Active (pointer over: ink ring), Focus (the 1.5px
 * focus-blue ring), Warning (1.5px warning ring + pale fill) and Disabled
 * (Figma 2026-08-20: a FILLED `input.disabled` plate, not just a greyed ring,
 * with `input.disabled-label` text). The ring is a real `border`, declared
 * HERE, so the engine below can restyle GF's invalid state instead of letting
 * GF's own brick-red 1px ring through (that ring is the plugin's, not the
 * design's). Consumers that print their own fallback inputs include this and
 * get the same states for free.
 *
 * Focus paints on `:focus` (any modality) because it is the FIELD's look, not
 * the keyboard indicator — the global 3px :focus-visible ring (functions.php)
 * is the indicator and stays untouched.
 */
/**
 * Placeholders.
 *
 * Figma 2026-08-20: the field's Default state draws its placeholder in the
 * MUTED body colour (#4F4F4F) and the Filled state draws typed text in ink —
 * which is exactly the split between `--saconnects-gf-body` here and
 * `--saconnects-gf-input-ink` on the control itself. (This supersedes the ASRI
 * note that "the design draws ink placeholders at full strength": that was
 * true of ASRI's mockups, not of this Design System.) `opacity: 1` still has
 * to be said — browsers dim placeholders by default and would take the muted
 * grey down another step.
 */
/**
 * The system pill (block-conventions.md → Buttons; theme.json elements.button):
 * Momo Trust Sans 600 · 16px · line-height 1.1 · −1% tracking · 21px 23px ·
 * pill radius. Resting fill, ink and hover fill come from the surface's custom
 * properties, so a dark band gets the INVERSE pill (white, gold-light hover)
 * and a light surface gets the primary pill — one rule, no duplicated art.
 *
 * PADDING, DELIBERATELY 21px 23px AND NOT THE FIGMA FORMS FRAME'S 21px 20px.
 * The Forms frame (14459:8914) measures the submit at 21/20; block-conventions
 * .md §Buttons carries a standing RULING that the global button variants win
 * over per-section mockup button sizes, because "buttons are a site-wide
 * system, not per-section art" — and the whole point of that ruling is cases
 * exactly like this 3px. Flagged to the coordinator; it is one number here if
 * the ruling is reversed for forms.
 *
 * Hover = background swap ONLY — the design has no shadows and no lift (ASRI's
 * client ordered every hover glow removed in QA, 2026-08-05; SAConnects never
 * had one — every `custom.shadow.*` token is pinned to none). Focus is NOT a
 * hover clone either: the resting fill stays and the global 3px #4144FF ring
 * (functions.php) carries the state. No :focus-visible is paired with the
 * background swap.
 *
 * NOTE this is a raw `<input type=submit>` / `<button>` that GF prints — it can
 * never carry `wp-element-button`, so the system's values are restated here.
 * That is the documented divergence, not drift.
 */
/**
 * The select chevron, drawn HERE instead of borrowed from the plugin.
 *
 * The lean gravity-theme ships NO arrow for `select` at all (only the
 * datepicker header's own) — it leaves the browser's native control glyph,
 * which is a different shape, size and colour on every OS. `appearance: none`
 * deletes that glyph, so the replacement is not decoration: without it the
 * control loses its only affordance.
 *
 * Figma 2026-08-20 (14459:8820 "Select"): the glyph is the 16px filled chevron
 * from `assets/icons/chevron-16.svg`, inset by the field's own 12px padding
 * with a 4px gap to the text lane (12 + 16 + 4 = the 32px end padding below).
 * The previous 10×6 stroked chevron was the ASRI port and is superseded.
 *
 * $fill is a URL-ENCODED literal because a `var()` cannot live inside a
 * data-URI. %23989799 mirrors `--wp--preset--color--meta` (the Figma field
 * glyph colour); %23FBF9F8 mirrors `--wp--preset--color--white` for a dark
 * surface.
 */
/**
 * The search field's magnifier (Figma Forms/field 14459:8820 "Search").
 *
 * The glyph sits at the START of the field — 12px in (the field's own padding)
 * with a 12px gap to the text lane, so the text starts at 40px — and it is
 * RED. That is the design, not an export accident: the Design System draws the
 * search icon in `accent/01` #EF3E42 while every other field glyph is the grey
 * `meta`. Source file: `assets/icons/search-16.svg`.
 *
 * GF has no search field type, so nothing in the sample form matches this; the
 * rule exists for `input[type=search]` printed by a consuming block's own
 * fallback markup (the `input` mixin is documented as reusable that way) and
 * for any GF add-on that emits one.
 *
 * $fill is a URL-ENCODED literal: %23EF3E42 mirrors
 * `--wp--preset--color--accent`, %23FBF9F8 `--wp--preset--color--white`.
 */
/**
 * The CHECKBOX (Figma Forms/controls 14459:8883).
 *
 * 24×24, radius 7, and four states: Default (1px bounds), Active (1px
 * `input.active` — the pointer-over ring), Selected (`input.focus` fill AND
 * border with a white tick, stroke-width 2 — `assets/icons/checkbox-selected
 * .svg`), Disabled (`input.disabled` plate, bounds ring, `input.disabled-label`
 * ink).
 *
 * WHY NOT `accent-color` (which is what this file shipped until 2026-08-20):
 * `accent-color` recolours the UA control and nothing else. It cannot give the
 * box a 7px radius, cannot draw the Active ring (UA controls have no border to
 * colour at rest), cannot produce the radio's two-tone Selected state (ink
 * fill + focus-blue ring), and leaves the box at the UA's 13×13 — measured on
 * the served design-system form — against a design that specifies 24×24.
 *
 * WHY NOT "hidden input + a styled sibling box": nothing is hidden here at
 * all. The native input keeps its box, its focusability, its role, its label
 * association and the global `:focus-visible` ring; `appearance: none` only
 * removes the UA's PAINT, and everything drawn below is drawn on the input
 * itself. Forced-colors mode is the one case where the paint is thrown away
 * (see the media query in `engine`).
 */
/**
 * The RADIO (Figma Forms/controls 14459:8883).
 *
 * Same 24×24 box, full radius, and the design's own state split: Active is the
 * FOCUS blue here (the checkbox's is `input.active`), and Selected is
 * two-tone — a `contrast` fill inside a 1px `input.focus` ring with a 10px
 * white centre dot. That two-tone state is the single clearest reason
 * `accent-color` could not serve: it paints fill and mark from ONE colour.
 */
/**
 * The TOGGLE (Figma Forms/controls 14459:8883): a 42×24 track, radius 24, with
 * an 18px white indicator inset 3px — OFF on the `input.disabled` track, ON on
 * `input.focus`.
 *
 * GF HAS NO TOGGLE FIELD TYPE, so this is opt-in and never fires by itself:
 * give the checkbox field a Custom CSS Class of `saconnects-toggle` in the GF
 * form editor (Appearance → Custom CSS Class) and the field's checkbox renders
 * as the design's switch. It stays a real `<input type=checkbox>` — same
 * label, same role, same focus ring — which is what an accessible switch is;
 * only the paint changes.
 *
 * The knob is a background-image rather than a pseudo-element on purpose: an
 * `<input>` is a replaced element and ::before/::after on it are not
 * guaranteed. `background-position` animates, so the knob still slides.
 */
/**
 * The List field's add / remove row buttons.
 *
 * PORTED RATIONALE (WBL QA #24, adapted — their symptom, our mechanism): GF
 * draws these as a glyph that takes a theme colour with the sign knocked out
 * of it, and on the wrong surface the sign disappears. Ours is not a font
 * glyph but two black `images/list-*.svg` files painted at `opacity: .5` in a
 * 16×16 box — same failure on an ink band (black at 50% on #132230 is
 * invisible) plus a target well under the 24×24 floor. So: our own circle
 * glyph in a token colour, full opacity, and a real 28px hit area.
 *
 * $circle / $sign are URL-encoded literals (see select-chevron above).
 */
/**
 * The confirmation as a DESIGNED CARD (Figma Forms/thanks-message 14459:8959).
 *
 * Emit it on `.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message`,
 * never inside `engine()` — see the file header for why the wrapper is gone by
 * the time this renders.
 *
 * Figma 2026-08-20 REPLACES the invented card this file used to draw (a `tint`
 * plate at card radius with a 32px inset): the real one is an INK plate —
 * `contrast` background, white text, 2px radius, 30px padding — with a 16px
 * body line and a 25px/800 display line 5px under it. The plate is
 * self-contained on purpose: the same markup is what a visitor lands on after
 * submitting the FOOTER form, on an ink band, so it cannot inherit the surface.
 *
 * 2px and 30px are raw lengths because neither is in the token map (`radius`
 * stops at the 5px input; `spacing` steps 24 → 32 around 30). Flagged to the
 * coordinator for consolidation rather than rounded silently to 32 —
 * block-conventions.md logs consolidations, it does not invent them.
 */
/**
 * The engine. Emit it INSIDE a `.gform_wrapper.gravity-theme` selector.
 *
 * @param $labels  `hidden`  — a placeholder-only skin (single-field forms).
 *                            EVERY FIELD IN THE GF ADMIN MUST THEN CARRY A
 *                            PLACEHOLDER: an empty placeholder plus a hidden
 *                            label is a naked input.
 *                 `visible` — real labels above the control, which is what
 *                            block-conventions requires of MULTI-FIELD forms
 *                            (the footer newsletter shows its labels too).
 */
/**
 * GF on dark — the brick-red contrast overrides.
 *
 * gravity-theme hardcodes #c02b0a (~2.4:1 on an ink band) across ~15 rules. The
 * ones that paint red ON a dark surface are pinned here. The ones that paint red
 * on GF's OWN light plates are deliberately left alone — `.gform_validation_errors`
 * ships `background: #fff9f9`, where GF's red clears AA, and the standing ruling
 * is "on light surfaces GF's red passes AA — leave it". Emit INSIDE a
 * `.gform_wrapper.gravity-theme` selector on the dark-surface variant only.
 */
/**
 * THE LIGHT-SURFACE CONTRACT.
 *
 * Set on BOTH wrappers. `.gform_confirmation_wrapper` is not a descendant of
 * `.gform_wrapper` and does not carry its class — GF's AJAX transport runs
 * `jQuery('#gform_wrapper_N').replaceWith(confirmation_content)`, and the
 * non-AJAX path prints the confirmation instead of the form — so a contract
 * declared on the form wrapper alone would leave the confirmation card
 * resolving every custom property to nothing.
 *
 * Field bounds, states and focus are deliberately NOT here: they are the
 * theme's `custom.input.*` tokens, identical on every surface in the Figma
 * Design System. So are the drawn checkbox / radio / toggle.
 */
:is(.gform_wrapper, .gform_confirmation_wrapper).gravity-theme {
  --saconnects-gf-input-bg: transparent;
  --saconnects-gf-input-ink: var(--wp--preset--color--contrast);
  --saconnects-gf-body: var(--wp--preset--color--muted);
  --saconnects-gf-label: var(--wp--preset--color--contrast);
  --saconnects-gf-btn-bg: var(--wp--preset--color--primary);
  --saconnects-gf-btn-ink: var(--wp--preset--color--white);
  --saconnects-gf-btn-bg-hover: var(--wp--preset--color--primary-hover);
  --saconnects-gf-choice-accent: var(--wp--preset--color--primary);
}

.gform_wrapper.gravity-theme {
  margin: 0;
  /*
   * The native controls this skin does NOT redraw — the multi-select's
   * selected-option highlight, and any range/progress a GF add-on prints.
   * The checkbox, radio and toggle are drawn from `custom.input.*` below, so
   * this no longer reaches them (they are `appearance: none`); it is kept
   * because it is a published contract property and still does real work
   * here.
   */
  accent-color: var(--saconnects-gf-choice-accent);
}
.gform_wrapper.gravity-theme .gform_fields {
  /*
   * THE LIST RESET. `.gform_fields` is a <ul> and every field is an <li>,
   * so without this the browser's UA `list-style: disc` paints a BULLET
   * beside every input. Reported on the footer newsletter, 2026-08-20.
   *
   * It is our job because gravity-theme does not do it: grepping the
   * installed plugin's theme.min.css for `list-style` returns NOTHING —
   * the lean theme has no list rules at all. The only reset GF ships is
   * `body .gform_wrapper.gf_reset_wrapper li/ol/ul { list-style: none }`
   * in basic.min.css, and `gf_reset_wrapper` is a LEGACY-markup class
   * that this wrapper never carries (measured on the served page: the
   * wrapper is `gform_wrapper gravity-theme gform-theme--no-framework …`).
   * So the reset never matched, on any surface, for any form.
   *
   * Declared here rather than on a bare `ul` selector so it can only ever
   * touch GF's own field list — a list the AUTHOR writes inside a form
   * description keeps its markers.
   */
  list-style: none;
  margin: 0;
  padding: 0;
  column-gap: var(--wp--preset--spacing--20);
  row-gap: var(--wp--preset--spacing--20);
}
.gform_wrapper.gravity-theme .gfield {
  margin: 0;
  position: relative;
}
.gform_wrapper.gravity-theme .gform_heading {
  margin: 0;
}
.gform_wrapper.gravity-theme {
  /*
   * Visible labels. `.gfield_label` covers both the <label> of a simple
   * field and the <legend> of a complex one (name, checkbox group); the
   * `--type-sub` variant is GF's sub-label ("First Name" under "Your
   * Name"), which sits a tier down. Choice-option labels
   * (`--type-inline`) are NOT labels in the design sense and are styled as
   * control copy in the .gchoice row below.
   *
   * Tier: Figma Forms/field label — 14px / 700 / 20px line, 8px to the
   * control.
   *
   * TRACKING: the Figma Forms frame measures 0.14px here, while the label
   * token is 0.07em (0.98px). block-conventions.md §Consolidation rulings
   * already adjudicated exactly this pair — "label tracking 1px/0.14px
   * @14px → 0.07em" — so the token stands and the 0.84px difference is a
   * recorded consolidation, not drift. Flagged to the coordinator; it is
   * one declaration here if the ruling is reversed.
   */
}
.gform_wrapper.gravity-theme .gfield_label {
  display: block;
  margin: 0 0 var(--wp--preset--spacing--10);
  padding: 0;
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--eyebrow);
  font-weight: 700;
  line-height: 20px;
  letter-spacing: var(--wp--custom--tracking--eyebrow);
  color: var(--saconnects-gf-label);
}
.gform_wrapper.gravity-theme {
  /*
   * Figma Forms/field "State: Disabled" greys the label with the control.
   *
   * `.gchoice_other_control` is excluded because it is NOT a disabled
   * field — it is GF's "Other" free-text box, which ships `disabled`
   * until its radio is selected and is re-enabled by GF's own script.
   * MEASURED on the served design-system form: a bare `:has(:disabled)`
   * greyed the whole radio group's label (#A49FB1) purely because one
   * unselected option carried that box, so a fully interactive field
   * read as switched off. Any choice field offering "Other" hits this.
   */
}
.gform_wrapper.gravity-theme .gfield:has(:disabled:not(.gchoice_other_control)) > .gfield_label {
  color: var(--wp--custom--input--disabled-label);
}
.gform_wrapper.gravity-theme .gform-field-label--type-sub {
  display: block;
  margin: 0 0 var(--wp--preset--spacing--10);
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--small);
  font-weight: 400;
  line-height: 1.6;
  letter-spacing: normal;
  color: var(--saconnects-gf-body);
}
.gform_wrapper.gravity-theme {
  /*
   * "(Required)".
   *
   * Figma 2026-08-20: it is NOT a lesser tier and NOT italic — it takes
   * the label's own properties exactly (14 / 700 / 20px line / label
   * ink), reading as part of the label. GF disagrees in two rules that
   * both out-specify a flat class here, which is why the selectors are
   * written long:
   *
   *   .gform_wrapper.gravity-theme .gfield_required               (0,3,0)
   *       → #c02b0a, 13.008px
   *   .gform_wrapper.gravity-theme .gfield_required .gfield_required_text
   *                                                              (0,4,0)
   *       → font-style: italic, font-weight: 400
   *
   * A bare `.gfield_required_text` lands at (0,3,0) and loses the italic
   * outright; the pairs below are (0,4,0) and (0,5,0), so both win on
   * specificity rather than on load order (this stylesheet is enqueued
   * last today, but the performance playbook allows GF's CSS to be
   * loaded async on pages where the form is below the fold, which would
   * flip a tie).
   *
   * GF's own `padding-inline-start: 0.125em` is deliberately left alone —
   * it is the word space between the label and "(Required)".
   */
}
.gform_wrapper.gravity-theme .gfield_label .gfield_required,
.gform_wrapper.gravity-theme .gform_required_legend .gfield_required {
  font-size: inherit;
  color: inherit;
}
.gform_wrapper.gravity-theme .gfield_label .gfield_required .gfield_required_text,
.gform_wrapper.gravity-theme .gform_required_legend .gfield_required .gfield_required_text {
  font-style: normal;
  font-weight: inherit;
}
.gform_wrapper.gravity-theme .gform_required_legend {
  margin: 0 0 var(--wp--preset--spacing--30);
  font-size: var(--wp--preset--font-size--small);
  line-height: 1.6;
  color: var(--saconnects-gf-body);
}
.gform_wrapper.gravity-theme input[type=text],
.gform_wrapper.gravity-theme input[type=email],
.gform_wrapper.gravity-theme input[type=tel],
.gform_wrapper.gravity-theme input[type=url],
.gform_wrapper.gravity-theme input[type=number],
.gform_wrapper.gravity-theme input[type=password],
.gform_wrapper.gravity-theme input[type=search],
.gform_wrapper.gravity-theme input[type=date],
.gform_wrapper.gravity-theme input[type=time],
.gform_wrapper.gravity-theme select,
.gform_wrapper.gravity-theme textarea {
  width: 100%;
  height: 48px;
  border: 1px solid var(--wp--custom--input--bounds);
  border-radius: var(--wp--custom--radius--input);
  background: var(--saconnects-gf-input-bg);
  padding: 12px;
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--base);
  font-weight: 400;
  line-height: 1.45;
  letter-spacing: normal;
  color: var(--saconnects-gf-input-ink);
}
.gform_wrapper.gravity-theme input[type=text]:hover,
.gform_wrapper.gravity-theme input[type=email]:hover,
.gform_wrapper.gravity-theme input[type=tel]:hover,
.gform_wrapper.gravity-theme input[type=url]:hover,
.gform_wrapper.gravity-theme input[type=number]:hover,
.gform_wrapper.gravity-theme input[type=password]:hover,
.gform_wrapper.gravity-theme input[type=search]:hover,
.gform_wrapper.gravity-theme input[type=date]:hover,
.gform_wrapper.gravity-theme input[type=time]:hover,
.gform_wrapper.gravity-theme select:hover,
.gform_wrapper.gravity-theme textarea:hover {
  border-color: var(--wp--custom--input--active);
}
.gform_wrapper.gravity-theme input[type=text]:focus,
.gform_wrapper.gravity-theme input[type=email]:focus,
.gform_wrapper.gravity-theme input[type=tel]:focus,
.gform_wrapper.gravity-theme input[type=url]:focus,
.gform_wrapper.gravity-theme input[type=number]:focus,
.gform_wrapper.gravity-theme input[type=password]:focus,
.gform_wrapper.gravity-theme input[type=search]:focus,
.gform_wrapper.gravity-theme input[type=date]:focus,
.gform_wrapper.gravity-theme input[type=time]:focus,
.gform_wrapper.gravity-theme select:focus,
.gform_wrapper.gravity-theme textarea:focus {
  border-width: 1.5px;
  border-color: var(--wp--custom--input--focus);
}
.gform_wrapper.gravity-theme input[type=text],
.gform_wrapper.gravity-theme input[type=email],
.gform_wrapper.gravity-theme input[type=tel],
.gform_wrapper.gravity-theme input[type=url],
.gform_wrapper.gravity-theme input[type=number],
.gform_wrapper.gravity-theme input[type=password],
.gform_wrapper.gravity-theme input[type=search],
.gform_wrapper.gravity-theme input[type=date],
.gform_wrapper.gravity-theme input[type=time],
.gform_wrapper.gravity-theme select,
.gform_wrapper.gravity-theme textarea {
  /*
   * `background-color`, never the `background` SHORTHAND: the shorthand also
   * resets background-image, and the select/search fields below carry their
   * glyph there — an invalid select would lose its arrow the moment it turned
   * red.
   */
}
.gform_wrapper.gravity-theme input[type=text][aria-invalid=true],
.gform_wrapper.gravity-theme input[type=email][aria-invalid=true],
.gform_wrapper.gravity-theme input[type=tel][aria-invalid=true],
.gform_wrapper.gravity-theme input[type=url][aria-invalid=true],
.gform_wrapper.gravity-theme input[type=number][aria-invalid=true],
.gform_wrapper.gravity-theme input[type=password][aria-invalid=true],
.gform_wrapper.gravity-theme input[type=search][aria-invalid=true],
.gform_wrapper.gravity-theme input[type=date][aria-invalid=true],
.gform_wrapper.gravity-theme input[type=time][aria-invalid=true],
.gform_wrapper.gravity-theme select[aria-invalid=true],
.gform_wrapper.gravity-theme textarea[aria-invalid=true] {
  border-width: 1.5px;
  border-color: var(--wp--custom--input--warning);
  background-color: var(--wp--custom--input--warning-fill);
}
.gform_wrapper.gravity-theme input[type=text],
.gform_wrapper.gravity-theme input[type=email],
.gform_wrapper.gravity-theme input[type=tel],
.gform_wrapper.gravity-theme input[type=url],
.gform_wrapper.gravity-theme input[type=number],
.gform_wrapper.gravity-theme input[type=password],
.gform_wrapper.gravity-theme input[type=search],
.gform_wrapper.gravity-theme input[type=date],
.gform_wrapper.gravity-theme input[type=time],
.gform_wrapper.gravity-theme select,
.gform_wrapper.gravity-theme textarea {
  /*
   * Figma 2026-08-20 "State: Disabled": the plate is `input.disabled`
   * (#E5E5EB) and the text is `input.disabled-label` (#A49FB1). The previous
   * value here (`disabled-fill` #BDB9C6 text on a transparent field) was the
   * ASRI port and is superseded.
   */
}
.gform_wrapper.gravity-theme input[type=text]:disabled,
.gform_wrapper.gravity-theme input[type=email]:disabled,
.gform_wrapper.gravity-theme input[type=tel]:disabled,
.gform_wrapper.gravity-theme input[type=url]:disabled,
.gform_wrapper.gravity-theme input[type=number]:disabled,
.gform_wrapper.gravity-theme input[type=password]:disabled,
.gform_wrapper.gravity-theme input[type=search]:disabled,
.gform_wrapper.gravity-theme input[type=date]:disabled,
.gform_wrapper.gravity-theme input[type=time]:disabled,
.gform_wrapper.gravity-theme select:disabled,
.gform_wrapper.gravity-theme textarea:disabled {
  border-color: var(--wp--custom--input--bounds);
  background-color: var(--wp--custom--input--disabled);
  color: var(--wp--custom--input--disabled-label);
}
.gform_wrapper.gravity-theme input[type=text]:disabled::placeholder,
.gform_wrapper.gravity-theme input[type=email]:disabled::placeholder,
.gform_wrapper.gravity-theme input[type=tel]:disabled::placeholder,
.gform_wrapper.gravity-theme input[type=url]:disabled::placeholder,
.gform_wrapper.gravity-theme input[type=number]:disabled::placeholder,
.gform_wrapper.gravity-theme input[type=password]:disabled::placeholder,
.gform_wrapper.gravity-theme input[type=search]:disabled::placeholder,
.gform_wrapper.gravity-theme input[type=date]:disabled::placeholder,
.gform_wrapper.gravity-theme input[type=time]:disabled::placeholder,
.gform_wrapper.gravity-theme select:disabled::placeholder,
.gform_wrapper.gravity-theme textarea:disabled::placeholder {
  color: var(--wp--custom--input--disabled-label);
}
.gform_wrapper.gravity-theme {
  /*
   * TEXTAREA — Figma Forms/field: 12px 15px padding, ~170px tall, and the
   * counter line right-aligned under it.
   *
   * The height needs the long selector. GF sizes textareas by the class it
   * stamps from the field's admin setting:
   *
   *   .gform_wrapper.gravity-theme .gfield textarea.large   (0,4,1) → 288px
   *
   * against which the shared `textarea` arm above is (0,2,1) — MEASURED on
   * the served design-system form, the textarea was 288px tall, not the
   * design's 170. `.gform_fields .gfield textarea:is(…)` is (0,5,1) and
   * takes it outright for all three size classes; the bare `textarea` rule
   * after it covers a textarea with no size class at all.
   *
   * `height`, not `min-height` alone: GF also prints `rows='10'` on the
   * control, and an auto-height textarea sizes to its ROWS attribute — 257.9px
   * here, measured, with min-height:170 satisfied and doing nothing. The
   * min-height stays as the floor for a user drag (the resize handle is left
   * alone deliberately: shrinking a comment box is the visitor's business).
   */
}
.gform_wrapper.gravity-theme .gform_fields .gfield textarea:is(.small, .medium, .large),
.gform_wrapper.gravity-theme textarea {
  height: 170px;
  min-height: 170px;
  padding: 12px 15px;
  line-height: 1.45;
}
.gform_wrapper.gravity-theme {
  /*
   * GF's ≤641px line-height override, undone.
   *
   *   @media only screen and (max-width: 641px)
   *     .gform_wrapper.gravity-theme input:not([type=radio]):not([type=checkbox])
   *       :not([type=image]):not([type=file]) { line-height: 2; min-height: 32px }
   *
   * lands at (0,6,1) — two classes plus four `:not()` arguments — and so
   * beats both the field arm (0,3,1) and the pill's (0,4,1). MEASURED at
   * 390px: the submit's line box went 17.6px → 32px and the pill grew to
   * 74px tall beside its 60px arrow disc, while every text field carried a
   * 32px line box inside a 24px content box.
   *
   * Mirroring GF's four `:not()`s under `.gform_fields` / `.gform_footer`
   * lands at (0,7,1) / (0,8,1) — so this wins on specificity at every
   * viewport rather than needing a media query of its own (a media query
   * adds no specificity, and the desktop values are these values). GF's
   * `min-height: 32px` needs no answer: every field here is taller.
   */
}
.gform_wrapper.gravity-theme .gform_fields input:not([type=radio]):not([type=checkbox]):not([type=image]):not([type=file]) {
  line-height: 1.45;
}
.gform_wrapper.gravity-theme .gform_footer input[type=submit]:not([type=radio]):not([type=checkbox]):not([type=image]):not([type=file]) {
  line-height: 1.1;
}
.gform_wrapper.gravity-theme {
  /*
   * The character counter GF prints under a textarea with a maximum
   * ("You have N characters left" / the design's "Max. 2000 characters").
   * Figma: right-aligned, 14px, body grey. It carries `.gfield_description`
   * too, so it would otherwise inherit the 12px helper tier below;
   * `.gfield .ginput_counter` is (0,4,0) against GF's own (0,3,0).
   */
}
.gform_wrapper.gravity-theme .gfield .ginput_counter {
  text-align: end;
  font-size: var(--wp--preset--font-size--small);
  line-height: 1.5;
  color: var(--saconnects-gf-body);
}
.gform_wrapper.gravity-theme {
  /*
   * Invalid fields: the skin's own Warning state (in `input` above) replaces
   * GF's brick-red 1px ring on the INPUT — the design specifies that ring
   * (1.5px warning + pale fill).
   *
   * MEASURED, and it is NOT a clean win everywhere — the arithmetic below is
   * why the block after this one exists. GF's ring is
   * `.gform_wrapper.gravity-theme .gfield_error [aria-invalid=true]` = 3
   * classes + 1 attribute = (0,4,0). The `input` mixin's own arm lands at:
   *
   *   input[type='text'][aria-invalid='true']   (0,4,1)  — beats it
   *   select[aria-invalid='true']               (0,3,1)  — LOSES
   *   textarea[aria-invalid='true']             (0,3,1)  — LOSES
   *
   * so an invalid select or textarea kept GF's 1px brick ring and no pale
   * fill while every text input turned to the design's. Hence the explicit
   * error group below, which also covers the fields GF marks on the FIELD
   * and not on the control.
   */
  /*
   * Per-field error states (ported from the WBL GF override, re-targeted and
   * compressed). Two arms, because GF marks errors two different ways:
   *
   *   1. simple controls carry `aria-invalid` themselves;
   *   2. COMPLEX fields (name, address, time, date, fileupload) put
   *      `.gfield_error` on the container and leave the sub-inputs unmarked
   *      — the reason WBL's list needed rows without an aria-invalid step.
   *
   * Arm 2 is deliberately limited to those text-ish composites: `.gfield_error`
   * also lands on checkbox/radio/consent groups, and a 1.5px ring plus a pale
   * fill on a 24px checkbox is not a state, it is damage.
   */
}
.gform_wrapper.gravity-theme .gfield.gfield_error :is(input, select, textarea)[aria-invalid=true],
.gform_wrapper.gravity-theme .gfield:is(.gfield--type-name,
.gfield--type-address,
.gfield--type-time,
.gfield--type-date,
.gfield--type-fileupload).gfield_error :is(input, select) {
  border: 1.5px solid var(--wp--custom--input--warning);
  background-color: var(--wp--custom--input--warning-fill);
}
.gform_wrapper.gravity-theme {
  /*
   * The per-field ERROR MESSAGE (Figma Forms/states 14459:8877): 12px, a
   * small round warning icon before it, and NO plate. GF ships it as a
   * bordered `#fff9f9` card at 14.992px with 24px of padding, which is a
   * different component entirely.
   *
   * COLOUR — READ BEFORE CHANGING. The Figma error text is
   * `input.warning` #FF0500, which measures **3.80:1** on the `base`
   * #FBF9F8 page (and 3.81:1 on GF's own #fff9f9) — under the 4.5:1 that
   * WCAG 1.4.3 requires of 12px text, and CLAUDE.md §Accessibility makes
   * that a hard requirement, not a preference. The palette's own dark red
   * `highlight` #970305 measures **8.59:1** and is what ships here. The
   * ICON keeps the design's #FF0500 — it is a graphic, and 3.80:1 clears
   * 1.4.11's 3:1 threshold.
   *
   * This is the one place the Figma did not win, and it is a one-token
   * change (`--wp--preset--color--highlight` →
   * `--wp--custom--input--warning`) if the PM accepts 3.80:1. Note that
   * "just leave GF's own #c02b0a" (5.57:1) is NOT available: our
   * `.gfield_description` rule ties GF's colour rule at (0,3,0) and wins on
   * load order, so the message renders in the BODY GREY unless a colour is
   * declared here — measured on the served form before this rule existed.
   *
   * `:not(:empty)` is load-bearing: GF prints an empty live-validation div
   * on every file field and hides it with
   * `.validation_message--hidden-on-empty:empty{display:none}` (0,3,0). A
   * flat `display: flex` here is (0,4,0) and would beat that hide, planting
   * a bare red icon under every upload field.
   */
}
.gform_wrapper.gravity-theme .gfield :is(.gfield_validation_message, .validation_message):not(:empty) {
  display: flex;
  align-items: flex-start;
  column-gap: var(--wp--preset--spacing--10);
  border: 0;
  background: none;
  margin-block-start: var(--wp--preset--spacing--10);
  padding: 0;
  font-size: var(--wp--preset--font-size--helper);
  line-height: 18px;
  color: var(--wp--preset--color--highlight);
}
.gform_wrapper.gravity-theme .gfield :is(.gfield_validation_message, .validation_message):not(:empty)::before {
  content: "";
  flex: 0 0 auto;
  width: 16px;
  height: 16px;
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 16 16' fill='none'%3E%3Ccircle cx='8' cy='8' r='8' fill='%23FF0500'/%3E%3Cpath d='M8 3.75V9' stroke='%23FBF9F8' stroke-width='1.75' stroke-linecap='round'/%3E%3Ccircle cx='8' cy='11.75' r='1' fill='%23FBF9F8'/%3E%3C/svg%3E");
  background-position: center;
  background-repeat: no-repeat;
  background-size: contain;
  margin-block-start: 1px;
}
.gform_wrapper.gravity-theme input::placeholder,
.gform_wrapper.gravity-theme textarea::placeholder {
  color: var(--saconnects-gf-body);
  opacity: 1;
}
.gform_wrapper.gravity-theme {
  /*
   * Selects. `:not([multiple])` is not decoration — it lifts the rule to
   * (0,3,1), over the shared `select` rule above (0,2,1) whose `background`
   * SHORTHAND would otherwise blank the chevron, and it keeps the multi-select
   * list box (which has no closed state and therefore no arrow) out of it.
   */
}
.gform_wrapper.gravity-theme select:not([multiple]) {
  appearance: none;
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 16 16' fill='none'%3E%3Cpath d='M11.7166 5.23204C11.858 5.08339 12.049 5 12.248 5C12.4471 5 12.6381 5.08339 12.7795 5.23204C12.8493 5.30503 12.9048 5.39204 12.9427 5.48799C12.9805 5.58395 13 5.68694 13 5.79097C13 5.895 12.9805 5.99799 12.9427 6.09395C12.9048 6.18991 12.8493 6.27691 12.7795 6.34991L8.53202 10.7683C8.39026 10.9168 8.19913 11 8 11C7.80086 11 7.60974 10.9168 7.46798 10.7683L3.22049 6.34991C3.15065 6.27691 3.0952 6.18991 3.05735 6.09395C3.01949 5.99799 3 5.895 3 5.79097C3 5.68694 3.01949 5.58395 3.05735 5.48799C3.0952 5.39204 3.15065 5.30503 3.22049 5.23204C3.36192 5.08339 3.55292 5 3.75197 5C3.95101 5 4.14201 5.08339 4.28345 5.23204L8.00163 8.8556L11.7166 5.23204Z' fill='%23989799'/%3E%3C/svg%3E");
  background-position: calc(100% - 12px) 50%;
  background-repeat: no-repeat;
  background-size: 16px 16px;
  padding-inline-end: 32px;
}
.gform_wrapper.gravity-theme select[multiple] {
  height: auto;
  min-height: 48px;
}
.gform_wrapper.gravity-theme {
  /*
   * Search. GF prints no search field, so nothing in the sample form matches;
   * this is for a consuming block's own fallback markup and for add-ons.
   * `:not([type='text'])` is impossible on an attribute selector, so the
   * specificity here is the plain (0,3,1) of the type attribute — the same
   * tier as the shared input arm, later in source, which is all it needs.
   */
}
.gform_wrapper.gravity-theme input[type=search] {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 16 16' fill='none'%3E%3Cpath d='M15.7125 14.8637L11.8882 11.0171C12.8362 9.85469 13.4075 8.36571 13.4075 6.74286C13.4075 3.02041 10.4046 0 6.70377 0C2.99965 0 0 3.02041 0 6.74286C0 10.4653 2.99965 13.4857 6.70377 13.4857C8.31722 13.4857 9.79432 12.9143 10.95 11.9608L14.7743 15.8041C15.034 16.0653 15.4528 16.0653 15.7125 15.8041C15.9722 15.5461 15.9722 15.1216 15.7125 14.8637ZM6.70377 12.1437C3.73983 12.1437 1.33101 9.72082 1.33101 6.74286C1.33101 3.7649 3.73983 1.33878 6.70377 1.33878C9.66446 1.33878 12.0765 3.7649 12.0765 6.74286C12.0765 9.72082 9.66446 12.1437 6.70377 12.1437Z' fill='%23EF3E42'/%3E%3C/svg%3E");
  background-position: 12px 50%;
  background-repeat: no-repeat;
  background-size: 16px 16px;
  padding-inline-start: 40px;
}
.gform_wrapper.gravity-theme {
  /*
   * File upload.
   *
   * The FIELD is the same bounded box as its siblings, but at 6px of vertical
   * padding rather than 12: the "Choose File" control has to live INSIDE the
   * 48px field. The arithmetic is exact and both halves are load-bearing —
   * 6 + 33.4 + 6 + 2 borders = 47.4px, which the 48px min-height rounds up to
   * the sibling fields' height; at GF's own 12px the same button pushed the
   * box to 57px, and at this file's previous 12px/no-button it measured 51px
   * (both out of the column, measured on the served form).
   *
   * The BUTTON is the primary CTA shrunk to fit (Figma has no file frame; the
   * brief's ruling, 2026-08-20, is "the primary CTA, small enough that it
   * never exceeds the input's height"): pill radius, ink fill, white ink, the
   * 14px tier, and 9px/16px padding for a 33.4px control — inside the 32–36px
   * the ruling asks for. It is `::file-selector-button` only —
   * Chrome/Firefox/Safari 15.4+ — and the fallback in an older engine is the
   * UA's own button, which is exactly what shipped here before.
   */
}
.gform_wrapper.gravity-theme input[type=file] {
  width: 100%;
  min-height: 48px;
  border: 1px solid var(--wp--custom--input--bounds);
  border-radius: var(--wp--custom--radius--input);
  background: var(--saconnects-gf-input-bg);
  padding: 6px 12px;
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--base);
  line-height: 1.45;
  color: var(--saconnects-gf-input-ink);
}
.gform_wrapper.gravity-theme input[type=file]::file-selector-button {
  appearance: none;
  border: 0;
  cursor: pointer;
  border-radius: var(--wp--custom--radius--pill);
  background: var(--saconnects-gf-btn-bg);
  margin-inline-end: var(--wp--preset--spacing--20);
  padding: 9px 16px;
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--small);
  font-weight: 600;
  line-height: 1.1;
  letter-spacing: var(--wp--custom--tracking--button);
  color: var(--saconnects-gf-btn-ink);
  transition: background-color 0.2s;
}
.gform_wrapper.gravity-theme input[type=file]::file-selector-button:hover {
  background: var(--saconnects-gf-btn-bg-hover);
}
.gform_wrapper.gravity-theme input:focus-visible,
.gform_wrapper.gravity-theme select:focus-visible,
.gform_wrapper.gravity-theme textarea:focus-visible,
.gform_wrapper.gravity-theme button:focus-visible,
.gform_wrapper.gravity-theme a:focus-visible {
  outline: var(--wp--custom--focus--width) solid var(--wp--custom--focus--ring);
  outline-offset: 2px;
}
.gform_wrapper.gravity-theme {
  /*
   * …and the three places where that restatement is NOT enough. The rule
   * above lands at (0,2,1); each of these plugin suppressions is (0,3,1) and
   * wins it, so the control had NO visible focus indicator at all (2.4.7):
   *
   *   basic.min.css  .gfield_list_icons button:focus     { outline: 0 }
   *   basic.min.css  .gform_show_password:focus          { outline: 0 }
   *   theme.min.css  .gfield_repeater_buttons …:focus    { outline: 0 }
   *
   * Same ring, same values — this is a specificity repair, not a second
   * indicator. (The `.add_list_item`/`.delete_list_item` step also takes the
   * list buttons to (0,4,1), clear of a tie.)
   */
}
.gform_wrapper.gravity-theme .gfield_list_icons button.add_list_item:focus-visible,
.gform_wrapper.gravity-theme .gfield_list_icons button.delete_list_item:focus-visible,
.gform_wrapper.gravity-theme .gform_show_password:focus-visible,
.gform_wrapper.gravity-theme .gfield_repeater_buttons :is(button, a):focus-visible {
  outline: var(--wp--custom--focus--width) solid var(--wp--custom--focus--ring);
  outline-offset: 2px;
}
.gform_wrapper.gravity-theme {
  /*
   * THE SUBMIT ROW: the plain pill, and NOTHING beside it.
   *
   * THE HISTORY MATTERS, because the arrow this row used to carry has now
   * been four things, and the fourth is "gone":
   *   1. SHIPPED AS DECORATION: a 60px disc on `.gform_footer::after`,
   *      pointer-events none. QA 2026-08-28 (#6): "parece otro boton
   *      clickeable" — ornament drawn at control size in control colour,
   *      and every click it invited did nothing.
   *   2. WITHDRAWN INTO THE PILL (a 12px glyph after the label). Rejected
   *      2026-08-31: "si la flecha se integra en el submit no cumple el
   *      diseño" — the Figma submit row (14459:8914) draws the disc
   *      SEPARATE.
   *   3. THE COMPOSITE: pill + 5px + 60px disc drawn as two surfaces
   *      (::before / ::after) of the ONE `<button>`, with the AJAX loader
   *      parked on the disc and the arrow glyph stepping aside for it.
   *   4. REMOVED (Pastel 2026-09-03, #72 — pin on the disc beside "Sign Me
   *      Up": "esta flecha esta de mas"). The newest instruction wins over
   *      the 2026-08-31 ruling and over the comp's separate disc: the submit
   *      is the `pill` mixin verbatim — one surface, one tab stop, the focus
   *      ring hugging the pill — and no arrow anywhere on it. The engine is
   *      shared, so this is EVERY GF form on the site (the footer
   *      newsletter, the /about/ contact form, the design-system form), not
   *      the footer alone. block-conventions.md §Buttons carries the ruling.
   *
   * Known need (CLAUDE.md): GF's footer margin/padding breaks the stack
   * rhythm, and its `align-self: flex-end` pushes the pill right. GF's own
   * `.gform_footer input { margin-bottom: 8px }` is zeroed with the pill's
   * `margin: 0` below, which is what keeps the row one line tall.
   */
}
.gform_wrapper.gravity-theme .gform_footer {
  margin: var(--wp--preset--spacing--30) 0 0;
  padding: 0;
  align-items: flex-start;
  justify-content: flex-start;
  gap: 5px;
}
.gform_wrapper.gravity-theme .gform_footer input[type=submit],
.gform_wrapper.gravity-theme .gform_footer button[type=submit],
.gform_wrapper.gravity-theme .gform_footer .gform_button {
  display: inline-flex;
  align-items: center;
  align-self: flex-start;
  /*
   * `appearance: none` and an explicit border/padding because GF does not
   * style its submit AT ALL on the lean theme — measured on the served page,
   * the control is Chrome's UA button verbatim (background #F0F0F0, colour
   * #000, `padding: 1px 6px`, `font-size: 13.3333px`, weight 400). Every
   * value below is therefore load-bearing, not a nudge; the UA padding in
   * particular has shrunk a control here before (block-conventions →
   * Carousels, the 18px SVG in a 6px box).
   */
  appearance: none;
  border: 0;
  cursor: pointer;
  border-radius: var(--wp--custom--radius--pill);
  background: var(--saconnects-gf-btn-bg);
  padding: 21px 23px;
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--base);
  font-weight: 600;
  line-height: 1.1;
  letter-spacing: var(--wp--custom--tracking--button);
  color: var(--saconnects-gf-btn-ink);
  text-decoration: none;
  transition: background-color 0.2s;
}
.gform_wrapper.gravity-theme .gform_footer input[type=submit]:hover,
.gform_wrapper.gravity-theme .gform_footer button[type=submit]:hover,
.gform_wrapper.gravity-theme .gform_footer .gform_button:hover {
  background: var(--saconnects-gf-btn-bg-hover);
}
.gform_wrapper.gravity-theme .gform_footer input[type=submit],
.gform_wrapper.gravity-theme .gform_footer button[type=submit],
.gform_wrapper.gravity-theme .gform_footer .gform_button {
  margin: 0;
  align-self: flex-start;
}
.gform_wrapper.gravity-theme .gform_footer {
  /*
   * THE AJAX LOADER (client, 2026-08-31: "ajusta el spinner porque
   * ahora se pisa con el mismo cta"). GF 2.9 injects
   * `<span class="gform-loader">` INSIDE the button, right after the
   * label's text node, and stamps `gform-has-spinner` on the button —
   * measured mid-submit on /01-design-system/. Left in flow it is a
   * flex item wedged against the label, and the circle sat on the copy.
   * With the disc gone (history, above) there is no lane to park it in
   * any more, so the button opens one FOR THE DURATION OF THE SUBMIT
   * ONLY: `gform-has-spinner` widens the end padding by 32px (24px
   * circle + 8px breath) and the loader is absolutely centred in that
   * lane — 16px from the pill's end edge, 15px clear of the label's
   * last glyph — so the two can never meet. The pill grows 32px for the
   * second the request takes; that is the trade: a resting pill that is
   * exactly the button system's, and a spinner that never covers the
   * label. GF's own state class gates it, so there is no :has() and no
   * script of ours.
   *
   * Scoped to a `<button>` on purpose: an `<input type=submit>` (if a
   * filter ever reverts GF's button) cannot hold children, so the
   * loader can never land inside it — it stays the plain pill.
   */
}
.gform_wrapper.gravity-theme .gform_footer button[type=submit] {
  position: relative;
}
.gform_wrapper.gravity-theme .gform_footer button[type=submit] .gform-loader {
  position: absolute;
  inset-inline-start: auto;
  inset-inline-end: 16px;
  inset-block-start: 50%;
  translate: 0 -50%;
  margin: 0;
  width: 24px;
  height: 24px;
}
.gform_wrapper.gravity-theme .gform_footer button[type=submit].gform-has-spinner {
  padding-inline-end: 55px;
}
.gform_wrapper.gravity-theme {
  /*
   * The validation SUMMARY box — the icon laid out in FLOW, not absolutely.
   *
   * Known need (CLAUDE.md): gravity-theme absolutely positions the summary's
   * error icon in a left inset —
   *   .gform_validation_errors > h2 .gform-icon {
   *       position: absolute; inset-inline-start: 12px; inset-block-start: 0;
   *       height: 100%; font-size: 28px;
   *   }
   * — and reserves room for it with `padding-inline-start: 48px` on the box.
   * That reservation is the ONLY thing keeping the icon off the text, which
   * is exactly the arrangement WBL's client filed as QA #23: once the heading
   * wrapped, the absolutely-positioned icon sat on top of it. This previously
   * PINNED GF's 48px inset; pinning a workaround is weaker than removing the
   * need for it, so the icon is now a flex ITEM and cannot overlap anything.
   *
   * The glyph itself becomes an inline-SVG data-URI (the WBL pattern): GF
   * draws it from the `gform-icons-theme` icon FONT, so a blocked or
   * late-loading font file leaves the summary with a blank square or a
   * tofu box. Drawn here it is part of the stylesheet.
   *
   * The box keeps GF's own `#fff9f9` plate and red text — the standing
   * ruling is "on light surfaces GF's red passes AA — leave it" (5.57:1
   * measured) — but loses its box-shadow: every `custom.shadow.*` token in
   * this theme is pinned to `none` and the design has no shadows at all.
   */
}
.gform_wrapper.gravity-theme .gform_validation_errors {
  border-radius: var(--wp--custom--radius--input);
  padding-inline-start: 16px;
  box-shadow: var(--wp--custom--shadow--card);
}
.gform_wrapper.gravity-theme .gform_validation_errors > h2 {
  display: flex;
  align-items: flex-start;
  column-gap: var(--wp--preset--spacing--10);
  /*
   * Class-doubled on purpose. GF's rule is
   * `.gform_wrapper.gravity-theme .gform_validation_errors > h2 .gform-icon`
   * = (0,4,1); a single `.gform-icon` here ties it and would be decided
   * by load order alone. Doubling makes it (0,5,1) and the reset is
   * load-order-independent — this one has to hold, an un-reset absolute
   * icon lands ON the text.
   */
}
.gform_wrapper.gravity-theme .gform_validation_errors > h2 .gform-icon.gform-icon {
  position: static;
  inset: auto;
  flex: 0 0 auto;
  width: 16px;
  height: 16px;
  margin: 0;
  font-size: 0;
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 16 16' fill='none'%3E%3Ccircle cx='8' cy='8' r='8' fill='%23FF0500'/%3E%3Cpath d='M5.75 5.75L10.25 10.25M10.25 5.75L5.75 10.25' stroke='%23FBF9F8' stroke-width='1.5' stroke-linecap='round'/%3E%3C/svg%3E");
  background-position: center;
  background-repeat: no-repeat;
  background-size: contain;
}
.gform_wrapper.gravity-theme .gform_validation_errors > h2 .gform-icon.gform-icon::before {
  content: none;
}
.gform_wrapper.gravity-theme {
  /*
   * The List field's row buttons — see the `list-icons` mixin header for the
   * ported rationale (WBL QA #24). This half is the geometry, which is the
   * same on every surface; the glyph colours arrive per surface.
   *
   * 28px: GF ships a 16×16 button, under the 24×24 target floor
   * (block-conventions → Accessibility, WCAG 2.5.8). The box grows, the
   * artwork does not — background-size pins the glyph at 20px.
   */
  /*
   * THE LIST FIELD'S ICON CELL needs air. GF puts the add/delete buttons in a
   * <td> hard against the input's cell, so the round + sat flush on the input
   * border — reported 2026-08-20 — and the 28px target below made the collision
   * worse, not better, because the box grew toward the input.
   *
   * Padding on the CELL, not a margin on the buttons: the cell is what abuts
   * the input, and padding keeps both buttons inside one hit region instead of
   * opening a dead gap between them.
   */
}
.gform_wrapper.gravity-theme .gfield_list_icons {
  padding-inline-start: var(--wp--preset--spacing--20);
  white-space: nowrap;
}
.gform_wrapper.gravity-theme {
  /*
   * THE TIME FIELD's inputs were UA-narrow. GF gives hour and minute a bare
   * <input type="number"> and the AM/PM a <select>, none of them sized, so the
   * browser's default width left "HH" and "MM" clipped behind their own
   * spinners — reported 2026-08-20.
   *
   * min-width, not width: these sit in GF's own flex row and must still be
   * able to grow. The values clear the two-digit text plus the UA spinner at
   * the design's 16px input type, and the select clears "AM" plus its chevron.
   */
}
.gform_wrapper.gravity-theme .gfield--type-time .ginput_container_time input[type=number],
.gform_wrapper.gravity-theme .gfield--type-time .ginput_container_time input[type=text] {
  min-width: 64px;
}
.gform_wrapper.gravity-theme .gfield--type-time .ginput_container_time select {
  min-width: 78px;
}
.gform_wrapper.gravity-theme .gfield_list_icons button.add_list_item,
.gform_wrapper.gravity-theme .gfield_list_icons button.delete_list_item {
  flex: 0 0 auto;
  width: 28px;
  height: 28px;
  background-color: transparent;
  background-position: center;
  background-repeat: no-repeat;
  background-size: 20px 20px;
  opacity: 1;
}
.gform_wrapper.gravity-theme .gfield_list_icons button.add_list_item {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='20' height='20' viewBox='0 0 20 20' fill='none'%3E%3Ccircle cx='10' cy='10' r='10' fill='%23132230'/%3E%3Cpath d='M10 5.5V14.5M5.5 10H14.5' stroke='%23FBF9F8' stroke-width='1.75' stroke-linecap='round'/%3E%3C/svg%3E");
}
.gform_wrapper.gravity-theme .gfield_list_icons button.delete_list_item {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='20' height='20' viewBox='0 0 20 20' fill='none'%3E%3Ccircle cx='10' cy='10' r='10' fill='%23132230'/%3E%3Cpath d='M5.5 10H14.5' stroke='%23FBF9F8' stroke-width='1.75' stroke-linecap='round'/%3E%3C/svg%3E");
}
.gform_wrapper.gravity-theme {
  /*
   * CHOICE ROWS.
   *
   * GF gives choice-option labels the SAME `.gform-field-label` class as field
   * labels; without a flex row the box stacks above its text
   * (block-conventions.md → Forms).
   *
   * Figma 2026-08-20 (14459:8883): the row gap is 10px and the option label
   * is 16px / **500** / 1.4 in the LABEL ink, not the body grey — control
   * copy sits a tier above description copy in this design. `max-width: none`
   * undoes GF's `.gfield-choice-input + label { max-width: calc(100% - 32px) }`,
   * which reserved room for a UA checkbox that no longer exists.
   */
  /*
   * THE ROW RHYTHM between choices, which nothing was setting.
   *
   * `.gchoice` below lays out ONE row (control beside label). The stack of
   * rows had no gap at all: gravity-theme leaves `.gfield_radio` /
   * `.gfield_checkbox` unstyled, and the rows are plain block children, so
   * three choices rendered flush against each other (reported 2026-08-20).
   *
   * A flex column with a gap, not `margin-bottom` on `.gchoice`: a margin
   * would also hang off the LAST row and push the next field out of the
   * grid's own row-gap rhythm.
   *
   * 10px mirrors the measured control→label gap on the same rows — the
   * design's one spacing step at this scale. Worth confirming against Figma
   * if the choice groups turn out to carry their own value.
   */
}
.gform_wrapper.gravity-theme .gfield_radio,
.gform_wrapper.gravity-theme .gfield_checkbox {
  display: flex;
  flex-direction: column;
  gap: 10px;
}
.gform_wrapper.gravity-theme .gchoice,
.gform_wrapper.gravity-theme .ginput_container_consent {
  display: flex;
  flex-direction: row;
  align-items: center;
  gap: 10px;
}
.gform_wrapper.gravity-theme .gchoice label,
.gform_wrapper.gravity-theme .ginput_container_consent label {
  margin: 0;
  max-width: none;
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--base);
  font-weight: 500;
  line-height: 1.4;
  color: var(--saconnects-gf-label);
}
.gform_wrapper.gravity-theme .gchoice input[type=checkbox],
.gform_wrapper.gravity-theme .ginput_container_consent input[type=checkbox] {
  appearance: none;
  flex: 0 0 auto;
  width: 24px;
  height: 24px;
  margin: 0;
  padding: 0;
  border: 1px solid var(--wp--custom--input--bounds);
  border-radius: 7px;
  background-color: transparent;
  background-position: center;
  background-repeat: no-repeat;
  background-size: 24px 24px;
  cursor: pointer;
}
.gform_wrapper.gravity-theme .gchoice input[type=checkbox]:hover:not(:disabled),
.gform_wrapper.gravity-theme .ginput_container_consent input[type=checkbox]:hover:not(:disabled) {
  border-color: var(--wp--custom--input--active);
}
.gform_wrapper.gravity-theme .gchoice input[type=checkbox]:checked,
.gform_wrapper.gravity-theme .ginput_container_consent input[type=checkbox]:checked {
  border-color: var(--wp--custom--input--focus);
  background-color: var(--wp--custom--input--focus);
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='24' height='24' viewBox='0 0 24 24' fill='none'%3E%3Cpath d='M6 12.7598L9.79814 16L17 8' stroke='%23FBF9F8' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E");
}
.gform_wrapper.gravity-theme .gchoice input[type=checkbox]:disabled,
.gform_wrapper.gravity-theme .ginput_container_consent input[type=checkbox]:disabled {
  border-color: var(--wp--custom--input--bounds);
  background-color: var(--wp--custom--input--disabled);
  cursor: default;
}
.gform_wrapper.gravity-theme .gchoice input[type=checkbox]:disabled:checked,
.gform_wrapper.gravity-theme .ginput_container_consent input[type=checkbox]:disabled:checked {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='24' height='24' viewBox='0 0 24 24' fill='none'%3E%3Cpath d='M6 12.7598L9.79814 16L17 8' stroke='%23A49FB1' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E");
}
.gform_wrapper.gravity-theme .gchoice input[type=radio],
.gform_wrapper.gravity-theme .ginput_container_consent input[type=radio] {
  appearance: none;
  flex: 0 0 auto;
  width: 24px;
  height: 24px;
  margin: 0;
  padding: 0;
  border: 1px solid var(--wp--custom--input--bounds);
  border-radius: 50%;
  background-color: transparent;
  background-position: center;
  background-repeat: no-repeat;
  background-size: 24px 24px;
  cursor: pointer;
}
.gform_wrapper.gravity-theme .gchoice input[type=radio]:hover:not(:disabled),
.gform_wrapper.gravity-theme .ginput_container_consent input[type=radio]:hover:not(:disabled) {
  border-color: var(--wp--custom--input--focus);
}
.gform_wrapper.gravity-theme .gchoice input[type=radio]:checked,
.gform_wrapper.gravity-theme .ginput_container_consent input[type=radio]:checked {
  border-color: var(--wp--custom--input--focus);
  background-color: var(--wp--preset--color--contrast);
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='24' height='24' viewBox='0 0 24 24' fill='none'%3E%3Ccircle cx='12' cy='12' r='5' fill='%23FBF9F8'/%3E%3C/svg%3E");
}
.gform_wrapper.gravity-theme .gchoice input[type=radio]:disabled,
.gform_wrapper.gravity-theme .ginput_container_consent input[type=radio]:disabled {
  border-color: var(--wp--custom--input--bounds);
  background-color: var(--wp--custom--input--disabled);
  cursor: default;
}
.gform_wrapper.gravity-theme .gchoice input[type=radio]:disabled:checked,
.gform_wrapper.gravity-theme .ginput_container_consent input[type=radio]:disabled:checked {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='24' height='24' viewBox='0 0 24 24' fill='none'%3E%3Ccircle cx='12' cy='12' r='5' fill='%23A49FB1'/%3E%3C/svg%3E");
}
.gform_wrapper.gravity-theme .gchoice,
.gform_wrapper.gravity-theme .ginput_container_consent {
  /*
   * GF greys a disabled option's label itself
   * (`.gfield-choice-input:disabled + label { color: #757575 }`, (0,3,0));
   * this is the same idea in the design's token, one class heavier.
   */
}
.gform_wrapper.gravity-theme .gchoice input:disabled + label,
.gform_wrapper.gravity-theme .ginput_container_consent input:disabled + label {
  color: var(--wp--custom--input--disabled-label);
}
.gform_wrapper.gravity-theme {
  /*
   * The TOGGLE, opt-in. GF has no toggle field type — give a checkbox field
   * the Custom CSS Class `saconnects-toggle` in the form editor and its
   * control renders as the design's 42×24 switch. (0,5,1) against the
   * checkbox rule's (0,3,1), so it wins wherever both match.
   */
}
.gform_wrapper.gravity-theme .gfield.saconnects-toggle :is(.gchoice, .ginput_container_consent) input[type=checkbox] {
  appearance: none;
  flex: 0 0 auto;
  width: 42px;
  height: 24px;
  margin: 0;
  padding: 0;
  border: 0;
  border-radius: 24px;
  background-color: var(--wp--custom--input--disabled);
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='18' height='18' viewBox='0 0 18 18' fill='none'%3E%3Ccircle cx='9' cy='9' r='9' fill='%23FBF9F8'/%3E%3C/svg%3E");
  background-position: 3px 50%;
  background-repeat: no-repeat;
  background-size: 18px 18px;
  cursor: pointer;
  transition: background-color 0.2s;
}
@media (prefers-reduced-motion: no-preference) {
  .gform_wrapper.gravity-theme .gfield.saconnects-toggle :is(.gchoice, .ginput_container_consent) input[type=checkbox] {
    transition: background-color 0.2s, background-position 0.2s;
  }
}
.gform_wrapper.gravity-theme .gfield.saconnects-toggle :is(.gchoice, .ginput_container_consent) input[type=checkbox]:checked {
  background-color: var(--wp--custom--input--focus);
  background-position: calc(100% - 3px) 50%;
}
.gform_wrapper.gravity-theme .gfield.saconnects-toggle :is(.gchoice, .ginput_container_consent) input[type=checkbox]:disabled {
  background-color: var(--wp--custom--input--disabled);
  cursor: default;
  opacity: 0.6;
}
.gform_wrapper.gravity-theme {
  /*
   * FORCED COLORS. `appearance: none` throws away the UA's checkbox and radio
   * paint, and a forced-colors context overrides the background-color our
   * tick/dot/track sits on — which would leave an empty square, or a 42×24
   * bar with a floating knob, and no readable checked state at all. Hand
   * those controls back to the UA there; everything else in this skin
   * degrades to system colours on its own.
   *
   * The toggle needs its own arm: its rule is (0,5,1) and would otherwise
   * out-specify the (0,3,1) reset beside it. A switch reverting to a system
   * checkbox is the right degradation — same element, same semantics, only
   * the paint changes.
   */
}
@media (forced-colors: active) {
  .gform_wrapper.gravity-theme .gchoice input[type=checkbox],
  .gform_wrapper.gravity-theme .gchoice input[type=radio],
  .gform_wrapper.gravity-theme .ginput_container_consent input[type=checkbox],
  .gform_wrapper.gravity-theme .ginput_container_consent input[type=radio] {
    appearance: auto;
    width: auto;
    height: auto;
  }
  .gform_wrapper.gravity-theme .gfield.saconnects-toggle :is(.gchoice, .ginput_container_consent) input[type=checkbox] {
    appearance: auto;
    width: auto;
    height: auto;
    background-image: none;
  }
}
.gform_wrapper.gravity-theme .gfield_description {
  padding-top: var(--wp--preset--spacing--10);
  font-size: var(--wp--preset--font-size--helper);
  line-height: 1.5;
  color: var(--saconnects-gf-body);
}

/*
 * A form dropped straight into a page takes the SECTION TEXT MEASURE.
 *
 * Every saconnects/* section caps its content at `measure--wide` via its own
 * `__inner` (text-block/style.scss:86), but a bare `wp:gravityforms/form` has
 * no inner of its own: as a direct child of the constrained post-content it
 * fills the full 1320 container instead. On /about/ that put the form 35px
 * wider on EACH side than the "Get in touch" copy sitting immediately above
 * it — measured 1162px starting at x=51, against the section's 1094px at
 * x=86 — so the two halves of one section visibly disagreed.
 *
 * Scoped to a DIRECT child of post-content on purpose: a form nested inside a
 * column or a block's own shell (the footer newsletter) is already inside
 * something that owns its width, and must not be re-capped here.
 *
 * The confirmation wrapper is included because a non-AJAX submit REPLACES the
 * form wrapper with it — without this the page would snap 68px wider at
 * exactly the moment the visitor is reading the thank-you message.
 *
 * Nothing vertical is touched: GF zeroes its own top margin, so the form
 * stays flush under the section's copy the way it renders today.
 */
.wp-block-post-content > :is(.gform_wrapper, .gform_confirmation_wrapper).gravity-theme {
  max-width: var(--wp--custom--measure--wide);
  margin-inline: auto;
}

/*
 * …EXCEPT under bare article copy. The engine's `margin: 0` (0,2,0) beats the
 * constrained layout's `:where(.is-layout-constrained) > *` 24px gap, which is
 * right under a section block (that owns its own bottom padding — /about/) but
 * glued "Name (Required)" to the paragraph above it in a migrated magazine
 * article (unsung-heroes-25-years-later, QA 2026-09-17: gap measured 0px vs
 * 24px between every other block). Restore the layout's own gap there only.
 */
.wp-block-post-content > :is(p, h2, h3, h4, h5, h6, ul, ol) + :is(.gform_wrapper, .gform_confirmation_wrapper).gravity-theme {
  margin-block-start: var(--wp--style--block-gap, var(--wp--preset--spacing--30));
}

/**
 * PLACEHOLDER-ONLY FIELDS — the footer newsletter (form 2), opted in with the
 * form's own `sac-form--newsletter` class.
 *
 * WHY THIS EXISTS INSTEAD OF GF's `hidden_label` (client instruction,
 * 2026-08-20). GF's option is not itself inaccessible: measured in the
 * installed plugin, `.gform_wrapper.gravity-theme .hidden_label .gfield_label`
 * (basic.min.css) is the standard clip pattern, so the <label> keeps its place
 * in the accessibility tree. The problem is DELIVERY. This file's own header
 * already states it: "§Performance playbook allows GF's CSS to be loaded async
 * on pages where the form is below the fold — which would flip every tie." A
 * footer form IS below the fold. The moment `gform_basic` goes async, a label
 * hidden by GF's stylesheet is VISIBLE until that sheet lands — three labels
 * the design does not have, flashing on every page, and permanently visible if
 * the async load ever fails. This rule ships inlined with the theme, so it can
 * never arrive late, and it survives a GF update or a change of theme slug.
 *
 * SELECTOR — GF renders the form's cssClass in two different shapes and only
 * one of them is the raw class (measured in the served markup):
 *     <div class='gform_wrapper gravity-theme … sac-form--newsletter_wrapper'>
 *       <div class='gform_heading'>…</div>
 *       <form  class='sac-form--newsletter …'>
 * GF appends `_wrapper` on the wrapper div. So this hooks the <form>, which is
 * also where the fields live. (0,4,0) — a class above the engine's own
 * `$labels: visible` arm at (0,3,0), so it wins on specificity, not order.
 *
 * The placeholder is what carries the field's meaning visually, and it is set
 * on all three fields — an empty placeholder here would ship naked inputs.
 */
.gform_wrapper.gravity-theme .sac-form--newsletter .gfield_label,
.gform_wrapper.gravity-theme .sac-form--newsletter .gform_required_legend {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  border: 0;
  clip: rect(0 0 0 0);
  clip-path: inset(50%);
  white-space: nowrap;
}

/**
 * The newsletter's lead line.
 *
 * This sentence used to be a `.site-footer__lead` paragraph in parts/footer.html
 * and is now the FORM'S description, which is what the design requires: GF's
 * AJAX transport runs `replaceWith` on `#gform_wrapper_N`, and `.gform_heading`
 * sits INSIDE that wrapper (measured: offset 6483 vs the wrapper's 1612), so
 * anything in the heading disappears when the confirmation arrives — exactly
 * what the comp shows. A paragraph left in the template part would instead
 * still be promising a subscription underneath the thank-you card.
 *
 * Note the `_wrapper` suffix: GF puts the form's cssClass raw on the <form> but
 * appends `_wrapper` to it on the wrapper div, and `.gform_description` lives in
 * the wrapper, OUTSIDE the form. The rule above hooks the <form>; this one
 * cannot.
 *
 * Values are the ones the footer paragraph carried, so nothing about the design
 * changed — only which element owns it.
 */
.gform_wrapper.gravity-theme.sac-form--newsletter_wrapper .gform_description {
  display: block;
  padding: 0;
  font-size: var(--wp--preset--font-size--sub-lead);
  font-weight: 700;
  line-height: 1.4;
  letter-spacing: var(--wp--custom--tracking--heading-small);
}

/**
 * The confirmation card. Applied OUTSIDE the engine because the form wrapper
 * is gone by the time this markup exists (see the contract note above and the
 * engine file's header) — a rule nested under `.gform_wrapper` would match
 * nothing on either transport.
 */
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message {
  margin: 0;
  border: 0;
  border-radius: 2px;
  background: var(--wp--preset--color--contrast);
  padding: 30px;
  font-family: var(--wp--preset--font-family--body);
  font-size: var(--wp--preset--font-size--base);
  font-weight: 400;
  line-height: 1.6;
  color: var(--wp--preset--color--white);
}
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message > * {
  margin: 0;
}
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message > * + * {
  margin-block-start: 5px;
}
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message {
  /*
   * The display line. It is a HEADING in the design; `p:has(> strong)` is
   * here because the GF confirmation editor is a plain rich-text box and
   * authors reach for bold before they reach for a heading level — without
   * it the second line silently stays at 16px. The `strong` inside has to be
   * told to inherit: the UA gives it `bolder`, which resolves off 800.
   */
}
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message :is(h1, h2, h3, h4, h5, h6),
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message p:has(> strong:only-child) {
  font-family: var(--wp--preset--font-family--heading);
  font-size: var(--wp--preset--font-size--heading-6);
  font-weight: 800;
  line-height: 1.2;
  letter-spacing: var(--wp--custom--tracking--heading-small);
  color: var(--wp--preset--color--white);
}
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message :is(h1, h2, h3, h4, h5, h6) > strong,
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message p:has(> strong:only-child) > strong {
  font-weight: inherit;
}
.gform_confirmation_wrapper.gravity-theme .gform_confirmation_message a {
  color: var(--wp--custom--on-dark--link);
  text-decoration: underline;
  text-underline-offset: auto;
  text-underline-position: from-font;
}

/**
 * ON DARK.
 *
 * A directly-embedded form can land on an ink band — the footer is the
 * obvious one, and it is where CLAUDE.md says forms usually live. Gated on
 * the same two ancestors the rest of the theme uses for this
 * (`assets/css/navigation.css` → footer link colours): `.footer--dark` is the
 * explicit opt-in class the footer part carries, `.has-contrast-background-color`
 * is the preset class core stamps on any group given the contrast background.
 * A LIGHT surface must never match, so there is no bare `footer` arm.
 *
 * The dark contract is (0,3,0) against the light one's (0,2,0), so it wins by
 * specificity rather than by source order.
 */
:is(.footer--dark, .has-contrast-background-color) :is(.gform_wrapper, .gform_confirmation_wrapper).gravity-theme {
  --saconnects-gf-input-bg: var(--wp--custom--on-dark--fill);
  --saconnects-gf-input-ink: var(--wp--preset--color--white);
  --saconnects-gf-body: var(--wp--custom--on-dark--text);
  --saconnects-gf-label: var(--wp--preset--color--white);
  --saconnects-gf-btn-bg: var(--wp--preset--color--white);
  --saconnects-gf-btn-ink: var(--wp--preset--color--contrast);
  --saconnects-gf-btn-bg-hover: var(--wp--preset--color--gold-light);
  --saconnects-gf-choice-accent: var(--wp--preset--color--white);
}

:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield_required {
  color: var(--wp--custom--on-dark--text);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield_error label,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield_error legend,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield_error .gfield_repeater_cell label,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme [aria-invalid=true] + label {
  color: var(--wp--custom--on-dark--text);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme {
  /*
   * …but `label + [aria-invalid='true']` is the INPUT itself, which sits on
   * the input fill, not on the band — it keeps the surface's input ink
   * instead of the on-dark one.
   */
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme label + [aria-invalid=true] {
  color: var(--saconnects-gf-input-ink);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme {
  /*
   * The per-field error message no longer has GF's pale plate under it (the
   * engine strips it to match Figma), so on an ink band its text lands
   * straight on #132230 — where the light surface's `highlight` #970305
   * measures 1.6:1. The on-dark equivalent is the band's own text colour;
   * the red disc before it stays, and clears 1.4.11 at 4.06:1 on ink.
   */
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield :is(.gfield_validation_message, .validation_message):not(:empty) {
  color: var(--wp--custom--on-dark--text);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme {
  /*
   * The field skin's light-surface states do not survive an ink band: the
   * Warning state's pale fill would put the on-dark input ink on a
   * near-white plate (white on #FBEFEF), and the Active / Focus rings are
   * ink and focus-blue — ~1:1 and ~1.3:1 on the band. Keep the warning RING
   * (red clears 3:1 on ink) and drop its fill; step the hover/focus rings up
   * to the on-dark text colour. The Figma Design System draws its field
   * states on light only, so these are the on-dark equivalents, not copies.
   */
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield [aria-invalid=true] {
  background: var(--saconnects-gf-input-bg);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield :is(input, select, textarea):enabled:not([aria-invalid=true]):hover,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield :is(input, select, textarea):enabled:not([aria-invalid=true]):focus {
  border-color: var(--wp--custom--on-dark--text);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme {
  /*
   * The drawn CONTROLS on an ink band. Their tokens are surface-independent
   * by design, and two of them stop working here: an unchecked box's
   * `input.bounds` ring is a 50%-alpha grey that all but vanishes on
   * #132230, and the checkbox's Selected fill #07327A is itself a dark navy
   * — box and band read as one shape. The ring moves to the on-dark border
   * token at rest and to on-dark text when the control is on, which is the
   * same move the fields above make. The white tick and the white dot need
   * no change.
   *
   * (0,5,1) here — the dark ancestor's own class is already counted by the
   * consumer's selector, so this only has to clear the engine's (0,3,1).)
   */
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gchoice input[type=checkbox],
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gchoice input[type=radio],
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .ginput_container_consent input[type=checkbox],
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .ginput_container_consent input[type=radio] {
  border-color: var(--wp--custom--on-dark--border);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gchoice input[type=checkbox]:checked,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gchoice input[type=radio]:checked,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .ginput_container_consent input[type=checkbox]:checked,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .ginput_container_consent input[type=radio]:checked {
  border-color: var(--wp--custom--on-dark--text);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .validation_error {
  color: var(--wp--custom--on-dark--text);
  border-block-color: var(--wp--custom--on-dark--border);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gform_validation_errors:focus,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gform_validation_errors:focus-visible,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gform_validation_errors > ol a:focus,
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gform_validation_errors > ol a:focus-visible {
  outline: var(--wp--custom--focus--width) solid var(--wp--custom--focus--ring);
  outline-offset: 2px;
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield_error .ginput_container_image_choice .gfield-choice-image-wrapper::before {
  border-color: var(--wp--custom--on-dark--text);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield_creditcard_warning .gfield_creditcard_warning_message {
  color: var(--wp--custom--on-dark--text);
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme {
  /*
   * The pieces of ARTWORK the light engine draws for a light surface. A
   * data-URI cannot read a custom property, so a hex baked for a light
   * surface stays baked — the chevron, the search glyph and the list icons
   * are redrawn here rather than recoloured. Same shapes, inverted palette.
   *
   * The submit is NOT in this list: since the disc was removed (Pastel
   * 2026-09-03 #72 — see the submit-row note in `engine`) the pill carries
   * no baked artwork at all, and its fill and ink are the contract's custom
   * properties, which the dark contract already re-points.
   */
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme select:not([multiple]) {
  appearance: none;
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 16 16' fill='none'%3E%3Cpath d='M11.7166 5.23204C11.858 5.08339 12.049 5 12.248 5C12.4471 5 12.6381 5.08339 12.7795 5.23204C12.8493 5.30503 12.9048 5.39204 12.9427 5.48799C12.9805 5.58395 13 5.68694 13 5.79097C13 5.895 12.9805 5.99799 12.9427 6.09395C12.9048 6.18991 12.8493 6.27691 12.7795 6.34991L8.53202 10.7683C8.39026 10.9168 8.19913 11 8 11C7.80086 11 7.60974 10.9168 7.46798 10.7683L3.22049 6.34991C3.15065 6.27691 3.0952 6.18991 3.05735 6.09395C3.01949 5.99799 3 5.895 3 5.79097C3 5.68694 3.01949 5.58395 3.05735 5.48799C3.0952 5.39204 3.15065 5.30503 3.22049 5.23204C3.36192 5.08339 3.55292 5 3.75197 5C3.95101 5 4.14201 5.08339 4.28345 5.23204L8.00163 8.8556L11.7166 5.23204Z' fill='%23FBF9F8'/%3E%3C/svg%3E");
  background-position: calc(100% - 12px) 50%;
  background-repeat: no-repeat;
  background-size: 16px 16px;
  padding-inline-end: 32px;
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme input[type=search] {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 16 16' fill='none'%3E%3Cpath d='M15.7125 14.8637L11.8882 11.0171C12.8362 9.85469 13.4075 8.36571 13.4075 6.74286C13.4075 3.02041 10.4046 0 6.70377 0C2.99965 0 0 3.02041 0 6.74286C0 10.4653 2.99965 13.4857 6.70377 13.4857C8.31722 13.4857 9.79432 12.9143 10.95 11.9608L14.7743 15.8041C15.034 16.0653 15.4528 16.0653 15.7125 15.8041C15.9722 15.5461 15.9722 15.1216 15.7125 14.8637ZM6.70377 12.1437C3.73983 12.1437 1.33101 9.72082 1.33101 6.74286C1.33101 3.7649 3.73983 1.33878 6.70377 1.33878C9.66446 1.33878 12.0765 3.7649 12.0765 6.74286C12.0765 9.72082 9.66446 12.1437 6.70377 12.1437Z' fill='%23FBF9F8'/%3E%3C/svg%3E");
  background-position: 12px 50%;
  background-repeat: no-repeat;
  background-size: 16px 16px;
  padding-inline-start: 40px;
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield_list_icons button.add_list_item {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='20' height='20' viewBox='0 0 20 20' fill='none'%3E%3Ccircle cx='10' cy='10' r='10' fill='%23FBF9F8'/%3E%3Cpath d='M10 5.5V14.5M5.5 10H14.5' stroke='%23132230' stroke-width='1.75' stroke-linecap='round'/%3E%3C/svg%3E");
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme .gfield_list_icons button.delete_list_item {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='20' height='20' viewBox='0 0 20 20' fill='none'%3E%3Ccircle cx='10' cy='10' r='10' fill='%23FBF9F8'/%3E%3Cpath d='M5.5 10H14.5' stroke='%23132230' stroke-width='1.75' stroke-linecap='round'/%3E%3C/svg%3E");
}
:is(.footer--dark, .has-contrast-background-color) .gform_wrapper.gravity-theme {
  /*
   * The validation SUMMARY keeps GF's own red on GF's own `#fff9f9` plate
   * (the standing ruling above), and so does the circle-cross icon the engine
   * draws — it sits on that same plate, not on the band. Nothing to invert.
   */
}

/**
 * The confirmation card ON DARK.
 *
 * Figma draws the thanks-message as an INK plate (`contrast`, white text) — on
 * the light page that is a strong, self-contained card, but on the footer's
 * ink band it is the band's own colour and the card's edges disappear. The
 * plate and the type stay exactly as designed; a hairline in the on-dark
 * border token is the minimum that gives it back its shape.
 */
:is(.footer--dark, .has-contrast-background-color) .gform_confirmation_wrapper.gravity-theme .gform_confirmation_message {
  border: 1px solid var(--wp--custom--on-dark--border);
}
