/* Article and resource bodies (template 2766): fixes from the Oct. 8, 2026 template design audit
   (OTX audit/02-design/2026-10-08-template-design-audit.md). Each rule names its finding ID. */

/* Load order matters here: this file prints before the theme's style.css, the kit (post-7.css),
   post-2766.css and each .otx article's own <style> block, so every rule below carries enough
   specificity to win without !important: a leading `body`, the template class .elementor-2766
   and, for template elements, Elementor's own `.elementor-element.elementor-element-<id>` pair.
   Batch 1 is scoped to .elementor-2766 (single posts and resources only). Batch 2, at the end of
   the file, also reaches the landing-page body (.otx-landing-body), the two bio widgets of the
   profile template 348 and phone links and stacked related lists in any .otx-content block. No
   rule reaches menus, the footer, cards or pillars. Since 1.1.20 one set at the end of the file
   (Daniel's check 15) reaches the logo links of Learn About the Unification (page 4115). */

/* ART-01: one reading column for the whole body. 720 px is about 90-95 characters at the legacy
   18 px body; the gutter is shared by the body container and the .otx intro so both align. */
.elementor-2766 {
	--otx-read-width: 720px;
	--otx-read-gutter: 24px;
}

/* ART-01: container 82c4d08 boxed to the reading width, with 60 px above and below (legacy text
   sat 10 px under the hero and 10-25 px above the footer) and a 24 px side gutter. Only when it
   holds a widget, so an empty body (Medication Policy, on the D34 hold) keeps its current strip. */
body .elementor-2766 .elementor-element.elementor-element-82c4d08:has(.elementor-widget) {
	--content-width: min(100%, var(--otx-read-width));
	--padding-top: 60px;
	--padding-bottom: 60px;
	--padding-left: var(--otx-read-gutter);
	--padding-right: var(--otx-read-gutter);
}

/* ART-01: the .otx intro keeps its full-width halftone band, but its text column now matches
   the body column (it was 1080 px wide at x 204 while the body ran from x 45 to 1395).
   Behind the same :has() support test as the body rule above, so a browser without :has()
   (Firefox before 121, Safari before 15.4) keeps both at their old widths instead of narrowing
   only the intro and misaligning the two the other way round. */
@supports selector(:has(a)) {
	body .elementor-2766 .otx-content .otx-intro-inner {
		max-width: calc(var(--otx-read-width) + 2 * var(--otx-read-gutter));
		padding-left: var(--otx-read-gutter);
		padding-right: var(--otx-read-gutter);
	}
}

/* ART-01: the View the PDF button (d53rlnk) carried a 60 px bottom margin on top of the
   container padding; the container's 60 px now does that job. */
body .elementor-2766 .elementor-element.elementor-element-82c4d08 .elementor-element.elementor-element-d53rlnk {
	margin-bottom: 0;
}
/* ART-01: on a PDF-only resource the button is the only widget, so its 20 px top margin would
   sit on top of the 60 px padding (80 above, 60 below). */
body .elementor-2766 .elementor-element.elementor-element-82c4d08 .elementor-element.elementor-element-d53rlnk:first-child {
	margin-top: 0;
}

/* ART-03: fixed hero image height with a cover crop, so a panorama no longer becomes a 201 px
   strip and a portrait no longer pushes the text 1,200 px down. Width 100% fills the column.
   Known trade-off: a featured image smaller than the 595x400 box is now enlarged (32 of 364
   records at 1440; two at 1.5x or more, the Dr. Schwartz Super Doctors logo at 1.94x). CSS cannot
   avoid that without giving up the fixed height; the fix is a larger source image. */
body .elementor-2766 .elementor-element.elementor-element-461fade img {
	width: 100%;
	height: 400px;
	object-fit: cover;
}

/* ART-05: space after a list, so the next paragraph no longer reads as another bullet
   (it sat at 0 px). The 40 px list indent is left alone. */
body .elementor-2766 .elementor-widget-theme-post-content > :is(ul, ol),
body .elementor-2766 .elementor-widget-theme-post-content > .otx-content > :is(ul, ol) {
	margin-block-end: 1em;
}

/* ART-R3: a little space between list items, so a wrapped line does not look like a new item. */
body .elementor-2766 .elementor-widget-theme-post-content > :is(ul, ol) > li + li,
body .elementor-2766 .elementor-widget-theme-post-content > .otx-content > :is(ul, ol) > li + li {
	margin-block-start: 0.4em;
}

/* ART-R1: headings sit nearer their own section than the text above (they were 8-14 px under
   the previous block and 16 px over their own). Direct children only, so the guide box,
   related box and CTA headings keep their own margins. */
body .elementor-2766 .elementor-widget-theme-post-content > h2:not(:first-child),
body .elementor-2766 .elementor-widget-theme-post-content > .otx-content > h2:not(:first-child) {
	margin-block-start: 1.6em;
}
body .elementor-2766 .elementor-widget-theme-post-content > h3:not(:first-child),
body .elementor-2766 .elementor-widget-theme-post-content > .otx-content > h3:not(:first-child) {
	margin-block-start: 1.25em;
}
/* ART-R1, extended to H4 (13 bodies: 11 legacy, 2 .otx): the kit draws H4 larger than H3 (32 px desktop,
   24 px tablet and phone, against 22 px), so with only H2 and H3 spaced, an H4 sat 14 px under
   the text above while a smaller H3 sat 28 px under it. Same 1.25em as H3, but not when the H4
   comes straight after another heading (pediatric foot doctor: an H3 label, then H4 items), so a
   heading and its first subheading stay together. Drop this rule if the finding is to stay
   limited to H2 and H3. */
body .elementor-2766 .elementor-widget-theme-post-content > h4:not(:first-child):not(:is(h2, h3, h4) + *),
body .elementor-2766 .elementor-widget-theme-post-content > .otx-content > h4:not(:first-child):not(:is(h2, h3, h4) + *) {
	margin-block-start: 1.25em;
}

/* ART-06 (weight rule only): legacy H2s wrapped in <strong> rendered at 900 beside 600
   neighbors. Bold inside a heading takes the heading's weight. The one-type-style change is a
   client decision and is not made here. */
body .elementor-2766 .elementor-widget-theme-post-content :is(h2, h3, h4) :is(strong, b) {
	font-weight: inherit;
}

/* ART-07: guide-box and related links were #0A7CC4 (4.13:1 on the guide tint, 4.47:1 on white).
   #086AA8 keeps the .otx hue and passes AA: 5.33:1 on #F0F7FB, 5.77:1 on white. The sup and
   reference links on the three .otx articles with citations have the same #0A7CC4-on-white defect. */
body .elementor-2766 .otx-content .otx-anchor-nav-columns ul li a,
body .elementor-2766 .otx-content .otx-related-columns ul li a,
body .elementor-2766 .otx-content .otx-related-hub a,
body .elementor-2766 .otx-content sup a,
body .elementor-2766 .otx-content .otx-references a {
	color: #086AA8;
}

/* ART-07: white on #0A7CC4 was 4.47:1. The plain CTA block (seven .otx articles; the banner
   variant uses a white button and is unaffected) and .otx table headers move to #086AA8
   (5.77:1). Hover steps to the darker .otx blue #075D9B so it still shows a change. No published
   body has a table today; the header rule only covers future ones. */
body .elementor-2766 .otx-content .otx-cta-block:not(.otx-cta-banner) .otx-cta-button {
	background: #086AA8;
}
body .elementor-2766 .otx-content .otx-cta-block:not(.otx-cta-banner) .otx-cta-button:hover {
	background: #075D9B;
}
body .elementor-2766 .otx-content .otx-table thead th {
	background: #086AA8;
}

/* Found while verifying ART-01, not an audit finding: a bare URL in the references list cannot
   wrap, so the hand-fractures article scrolled sideways on phones (397 px page at 390 before
   these fixes, 407 px with the wider gutter). Let long reference URLs break. */
body .elementor-2766 .otx-content .otx-references a {
	overflow-wrap: anywhere;
}

/* GLB-08 (also ART-R2): in-paragraph links were marked by color alone (#2D68C4 inside #222E3F
   text is 2.54:1, under the 3:1 needed). Underline links in body paragraphs and list items,
   including the .otx intro, CTA text, FAQ answers and references. Not the guide box or related
   lists (link lists), not the CTA button, and nothing outside the post-content widget. */
body .elementor-2766 .elementor-widget-theme-post-content :is(p, li) a:not(.otx-cta-button):not(.otx-anchor-nav *):not(.otx-related *) {
	text-decoration: underline;
}

@media (max-width: 1024px) {
	/* ART-03: tablet hero image height. */
	body .elementor-2766 .elementor-element.elementor-element-461fade img {
		height: 300px;
	}

	/* ART-04: the article H1 stayed 48 px on tablets; 36 px matches the kit's tablet H1. */
	body .elementor-2766 .elementor-element.elementor-element-6b69ebb .elementor-heading-title {
		font-size: 36px;
	}
}

@media (max-width: 767px) {
	/* ART-01: 20 px phone gutter (the body text sat 10 px from the screen edge) and 40 px above
	   and below the body. */
	.elementor-2766 {
		--otx-read-gutter: 20px;
	}
	body .elementor-2766 .elementor-element.elementor-element-82c4d08:has(.elementor-widget) {
		--padding-top: 40px;
		--padding-bottom: 40px;
	}

	/* ART-03: phone hero image height. */
	body .elementor-2766 .elementor-element.elementor-element-461fade img {
		height: 220px;
	}

	/* ART-04: 32 px H1 on phones (matches template 7099) and less navy padding in the hero
	   (100 px top and bottom from the theme's .container-padding rule). */
	body .elementor-2766 .elementor-element.elementor-element-6b69ebb .elementor-heading-title {
		font-size: 32px;
	}
	body .elementor-2766 .elementor-element.elementor-element-fb4e7fe.container-padding > .e-con-inner {
		padding-top: 48px;
		padding-bottom: 40px;
	}

	/* ART-10: floated images in legacy bodies squeezed the text into a one-word column beside
	   them (Dr. Brian Fuller's welcome post). On phones they sit on their own line, centered. */
	body .elementor-2766 .elementor-widget-theme-post-content :is(.alignleft, .alignright) {
		float: none;
		display: block;
		margin: 0 auto 16px;
		max-width: 100%;
	}
}

/* ART-01: on .otx articles the intro's own halftone band supplies the top space, so the body
   container starts flush under the hero, at every width (placed after the phone block so the
   40 px phone value does not override it). */
body .elementor-2766 .elementor-element.elementor-element-82c4d08:has(.otx-intro-section) {
	--padding-top: 0px;
}

/* ==============================================================================================
   Batch 2 (Oct. 8, 2026, articles builder): ART-02, ART-11, GLB-11, GLB-R2 and the rest of GLB-08.
   Same rules of the road as batch 1: every selector is scoped to a template (.elementor-2766,
   .elementor-348), to the landing-page body (.otx-landing-body, pages 7319 to 7322) or to an
   .otx-content component, so nothing reaches menus, footers, card lists or pillars.
   ============================================================================================== */

/* ART-02: PDF-only resources (no body, a View the PDF button: 462 and 3475 today, 3477 once its
   D34 hold lifts). tools/staged/r-article-pdf.php moved the button d53rlnk from the body container
   82c4d08 into the hero's text column 8cab51f, after the H1, so the two batch-1 d53rlnk rules
   above (scoped to 82c4d08) no longer match. They are kept, and every ART-02 rule below tests that
   the button sits in 8cab51f, so a template where the script has not run (or was rolled back)
   still renders as batch 1 left it. */

/* ART-02: the excerpt 2dbb192 is hidden on every device in the template. Show it under the H1 when
   the resource has no body and the button is in the hero. It already renders in Gibson 18/27
   white: the template's Roboto 20 setting is inert (its typography switch is off), so only display
   changes. Without :has() support it stays hidden, as before. */
body .elementor-2766:has(.elementor-element-8cab51f > .elementor-element-d53rlnk):not(:has(.elementor-widget-theme-post-content)) .elementor-element.elementor-element-2dbb192 {
	display: block;
}

/* ART-02: in the hero the button keeps its 20 px top margin (with the column's 20 px gap it sits
   40 px under the text, as Find Your Doctor does in the landing-page hero) but drops the 60 px
   bottom margin it carried at the end of the body: in a vertically centered column that margin
   lifted the title block 30 px off center. */
body .elementor-2766 .elementor-element.elementor-element-8cab51f > .elementor-element.elementor-element-d53rlnk {
	margin-bottom: 0;
}

/* ART-02: say what the button opens. The note "(PDF, opens in new tab)" is real markup, printed by
   includes/article-pdf-note.php after the link (which it also names in the link's
   aria-describedby), only when the link is a PDF that opens in a new tab. It sits beside the
   button (under it when the column is too narrow) and outside the orange link, so the approved
   button is unchanged. White in the navy hero; anywhere else (the button back in the white body
   after a rollback) it keeps the inherited body text color, so it never goes white on white. */
body .elementor-2766 .elementor-element.elementor-element-d53rlnk:has(> .otx-pdf-note) {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	column-gap: 16px;
	row-gap: 8px;
}
body .elementor-2766 .elementor-element.elementor-element-d53rlnk > .otx-pdf-note {
	font-size: 16px;
	line-height: 1.4;
}
body .elementor-2766 .elementor-element.elementor-element-8cab51f > .elementor-element.elementor-element-d53rlnk > .otx-pdf-note {
	color: #FFFFFF;
}

/* ART-02: with the button in the hero, a PDF-only resource's body container 82c4d08 is empty and
   shrank to the template's 10 px + 10 px padding: a 20 px white sliver between the navy hero and
   the navy footer that read as a rendering glitch. It becomes a deliberate 60 px white band
   (40 px on phones, under the 767 px block below), so the page keeps the template's navy hero,
   white body and navy footer. Hiding it instead was tried and rejected: the hero then runs
   straight into the footer, and the footer logo reads as part of the hero. Medication Policy
   (3477, D34 hold) shows no button, so this does not match there and its strip is unchanged. */
body .elementor-2766:has(.elementor-element-8cab51f > .elementor-element-d53rlnk) .elementor-element.elementor-element-82c4d08:not(:has(.elementor-widget)) {
	--padding-top: 30px;
	--padding-bottom: 30px;
}

/* ART-11: a phone link inside .otx-content (the CTA banner's (972) 492-1334 on 70 bodies) no
   longer breaks across lines on phones. Every such link is the bare number, so it cannot overflow. */
body .otx-content a[href^="tel:"] {
	white-space: nowrap;
}

/* GLB-08 (rest; batch 1 did article bodies): underline in-paragraph links in provider bios, the
   biography excerpt 074f50a and the full biography 12bd1c0 on template 348. No published bio has
   a link on Oct. 8, so this changes nothing visible today; it covers links added later. Only the
   two bio text widgets: not the sub-nav, specialty buttons, location phones or cards. */
body .elementor-348 .elementor-element.elementor-element-074f50a :is(p, li) a,
body .elementor-348 .elementor-element.elementor-element-12bd1c0 :is(p, li) a {
	text-decoration: underline;
}

/* GLB-08 (rest): underline in-paragraph links in the landing-page body (Dr. Jay Pond on the AOA
   page; the CTA banner's own link is already underlined by otx-content.css). Not the name and
   office lists (.otx-related-columns), not the CTA button. */
body .otx-landing-body .otx-content :is(p, li) a:not(.otx-cta-button):not(.otx-related-columns *):not(.otx-anchor-nav *):not(.otx-related *) {
	text-decoration: underline;
}

/* GLB-R2: landing body paragraphs ran about 175 characters a line at 16 px across the 1290 px
   column. They now use the kit's 18 px body text (otx-content.css sets 16 px with !important, so
   this has to as well) and stop at 720 px, the ART-01 article reading column, still on the page's
   left edge under the hero title. The audit's literal 75ch was tried first and missed the intent:
   1ch is the width of a Gibson "0" (about 11.3 px at 18 px), wider than the average letter, so
   75ch came to 848 px and the longest lines to 108-113 characters. 720 px holds about 90-95, as
   in the articles. The 960 px whole-column cap was rejected: it wrapped the NTO "Find Your ...
   Doctor" H2 onto a second line. Running paragraphs only: headings, the name and office lists and
   the CTA banner keep their widths and sizes. */
body .otx-landing-body .otx-content > p {
	max-width: 720px;
	font-size: 18px !important;
}

@media (max-width: 768px) {
	/* GLB-11 (also ART-11): where a two-list .otx-related-columns stacks (768 px and below, the
	   otx-content.css breakpoint), the first list's last row keeps its divider, so the stacked
	   list no longer looks split in two (99 article Related boxes, the landing-page name lists). */
	body .otx-content .otx-related-columns > ul:not(:last-child) > li:last-child {
		border-bottom: 1px solid #eef5f9;
	}
}

@media (max-width: 767px) {
	/* ART-02: the empty body band on a PDF-only resource is 40 px on phones (20 + 20), the phone
	   step ART-01 uses for the body padding. Same selector as the desktop rule above. */
	body .elementor-2766:has(.elementor-element-8cab51f > .elementor-element-d53rlnk) .elementor-element.elementor-element-82c4d08:not(:has(.elementor-widget)) {
		--padding-top: 20px;
		--padding-bottom: 20px;
	}
}

/* ==============================================================================================
   Batch 3 (Oct. 9, 2026, articles builder): A1, Blake's ruling on GLB-06 (the CTA half).
   Scoped to .otx-landing-body (pages 7319 to 7322) only. The 108 published article bodies that use
   the same .otx-cta-banner (104 posts, 4 resources) keep the blue photo banner, and nothing here
   reaches menus, footers or cards.
   ============================================================================================== */

/* A1 (GLB-06): the four practice landing pages ended on the article CTA banner, a blue photo panel
   boxed in the content column, where every pillar page (template 7099) ends on the site's navy
   Request an Appointment band. Blake chose option (a) on Oct. 9: keep each page's own closing line
   ("Schedule an appointment with your North Texas Orthopedics & Spine Center doctor or another
   OrthoTexas specialist ...") and draw it as that navy band. CSS only: the words, the link and the
   button text are the page's own and are unchanged.
   The band copies the measured pillar band: kit navy #041E42 (the secondary global color) edge to
   edge, 100 px above and below its content (80 at 1024 px and below, 60 on phones), centered white
   text no wider than 820 px and a pill button in the kit's shape, sitting flush on the navy footer.
   The box stays in the content column and a navy border-image, outset 100vmax to the sides only,
   paints the rest of the row. An outset is drawn but takes no space, so the band reaches both
   screen edges without the 100vw-plus-scrollbar sideways scroll a negative-margin breakout would
   cause. (A box-shadow clipped with clip-path was tried first: its clipped edge left a faint
   light seam on the side strips where the band meets the footer.) These pages carry no heading in the
   band, so the closing line is set larger (22 px) than the pillar's 18 px subline to lead it. */
body .otx-landing-body .otx-content .otx-cta-block.otx-cta-banner {
	--otx-band-navy: var(--e-global-color-secondary, #041E42);
	flex-direction: column;
	justify-content: center;
	gap: 28px;
	margin: 100px 0 0;
	padding: 100px 0;
	border: 0;
	border-radius: 0;
	background: var(--otx-band-navy);
	text-align: center;
	border-image: linear-gradient(var(--otx-band-navy), var(--otx-band-navy)) fill 0 / 0 / 0 100vmax;
}
body .otx-landing-body .otx-content .otx-cta-banner .otx-cta-content {
	flex: 0 1 auto;
	width: 100%;
	max-width: 820px;
}
/* A1: otx-content.css sets every .otx-content paragraph to 16 px with !important, so this has to
   be !important as well (as GLB-R2 is above). Color and the link underline already come from the
   banner rules in otx-content.css (white, underlined). */
body .otx-landing-body .otx-content .otx-cta-banner .otx-cta-content p {
	font-size: 22px !important;
	line-height: 1.5;
}
body .otx-landing-body .otx-content .otx-cta-banner .otx-cta-content p a {
	text-underline-offset: 3px;
}
/* A1 (GLB-06), with GLB-07 pending: the button takes the kit button's shape and size (Site Settings >
   Buttons, as on the pillar band: 2 px border, 100 px radius, 20 px semibold) but keeps the colors
   this button had before A1 (otx-content.css: white fill, #075D9B text, #F0F7FB on hover), 6.9:1
   and 6.4:1. The kit's orange button carries white text at 2.32:1, below the 3:1 large-text
   minimum (GLB-07, UMP's call, recommended fix the week of Oct. 19), so taking the kit's colors
   here would have added a failing button where there was a passing one.
   GLB-07 BUILD CHECKLIST: when UMP rules on GLB-07, switch this rule to the kit's orange fill with
   the ruled text color (option a: navy #041E42 on #FE8C42, 7.1:1), and its hover and focus to
   the GLB-R1 ruling. Until then, keyboard focus keeps the browser's own focus ring. */
body .otx-landing-body .otx-content .otx-cta-banner .otx-cta-button {
	padding: 15px 26px;
	border: 2px solid #FFFFFF;
	border-radius: 100px;
	background: #FFFFFF;
	color: #075D9B !important;
	font-size: 20px;
	font-weight: 600;
	line-height: 1;
	transition: background-color 0.3s, border-color 0.3s;
}
body .otx-landing-body .otx-content .otx-cta-banner .otx-cta-button:is(:hover, :focus-visible) {
	border-color: #F0F7FB;
	background: #F0F7FB;
	color: #075D9B !important;
}
/* A1: the band sits flush on the footer, as the pillar band does. The theme's .container-padding
   rule gives the landing body 100 px under its last element; it goes only when the body ends on
   the banner. Without :has() support the 100 px white strip stays between band and footer. */
body .otx-landing-body.container-padding > .e-con-inner:has(.otx-content > .otx-cta-banner:last-child) {
	padding-bottom: 0;
}

@media (max-width: 1024px) {
	/* A1: the pillar band's tablet step (80 px). */
	body .otx-landing-body .otx-content .otx-cta-block.otx-cta-banner {
		margin-top: 80px;
		padding: 80px 0;
	}
	body .otx-landing-body .otx-content .otx-cta-banner .otx-cta-content p {
		font-size: 20px !important;
	}
}

@media (max-width: 767px) {
	/* A1: the pillar band's phone step (60 px), and the kit's 18 px body size for the line. */
	body .otx-landing-body .otx-content .otx-cta-block.otx-cta-banner {
		gap: 24px;
		margin-top: 60px;
		padding: 60px 0;
	}
	body .otx-landing-body .otx-content .otx-cta-banner .otx-cta-content p {
		font-size: 18px !important;
	}
}

/* C8 (ART-09, with ART-R1's spacing): tools/staged/s-legacy-headings.php turned the bold paragraphs
   of 100 legacy posts into H2s and H3s. The ART-R1 rules above space headings that are direct
   children of the post-content widget, which covers 98 of those bodies. Two (6243, the 3D printed
   titanium cages Q&A, and 6247, the osteoporosis Q&A) hold text pasted from the block editor,
   still wrapped in its div.block-editor-block-list__block, so their new headings sat 14 px under
   the text above them and 16 px over their own. The same 1.6em and 1.25em reach a heading inside
   one of those wrappers when it is not the wrapper's first child, or when the wrapper itself has
   something before it (another wrapper, or a plain paragraph or list: 6247's "Risk Factors of
   Osteoporosis?" follows a paragraph). A wrapper at the very top of a body gets nothing, as the
   first heading of a body does not. Only that class pairing matches: nothing else on the site
   carries it. */
body .elementor-2766 .elementor-widget-theme-post-content .block-editor-block-list__block > h2:not(:first-child),
body .elementor-2766 .elementor-widget-theme-post-content .block-editor-block-list__block:not(:first-child) > h2:first-child {
	margin-block-start: 1.6em;
}
body .elementor-2766 .elementor-widget-theme-post-content .block-editor-block-list__block > h3:not(:first-child),
body .elementor-2766 .elementor-widget-theme-post-content .block-editor-block-list__block:not(:first-child) > h3:first-child {
	margin-block-start: 1.25em;
}

/* Daniel's check 15 (Oct. 12, 2026; Blake, Oct. 14: "build all of it according to your
   recommendation"): on Learn About the Unification (page 4115) the four legacy-practice logos in
   grid 84f279c link to their landing pages (images 85169b0, 79cdd67, 39091d2 and f62461e; the
   OrthoTexas logo e008e17 is not a link), but nothing showed that on hover, and keyboard focus
   got only the browser's thin default ring around an image on a grey (#DEE2E6) card. Styles only,
   scoped to that grid's image links; no markup or template change.
   - Hover: a 2 px blue (#2D68C4) ring, 4.15:1 against the card.
   - Keyboard focus (:focus-visible): a 3 px navy (#041E42) ring, 12.7:1 against the card, so
     it stays distinct from hover. Outlines, not shadows, so both survive forced-colors mode.
   - The ring sits 6 px out, inside the widget's 20 px padding, and follows a 6 px radius;
     line-height 0 drops the line gap under the logo so the ring is even on all four sides. */
body .elementor-4115 .elementor-element.elementor-element-84f279c .elementor-widget-image a {
	line-height: 0;
	border-radius: 6px;
}
body .elementor-4115 .elementor-element.elementor-element-84f279c .elementor-widget-image a:hover {
	outline: 2px solid #2D68C4;
	outline-offset: 6px;
}
body .elementor-4115 .elementor-element.elementor-element-84f279c .elementor-widget-image a:focus-visible {
	outline: 3px solid #041E42;
	outline-offset: 6px;
}