/* ============================================================
   wcag-c0067-gs-insta.css
   WCAG 2.1 Level AA override for the C0067-GS-Insta Kentico template
   (TemplateId 1369, DefaultCssFileName: RPcssMaster_C0067-GS-Insta).

   Selectors verified against the live base CSS pulled from
   livesommery.com (cross-fetched) on 2026-05-12.

   This template namespaces all base rules under .template-insta.
   Several base focus suppressors use !important on outline:none,
   so focus rules below also use !important to win.
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   Base suppresses outlines on:
     .template-insta a:hover { outline:0 }
     .template-insta a:hover, .template-insta a:focus
       { outline-color:transparent; outline-style:none }
     .template-insta .btn-primary.focus / :active / .active
       { outline:none !important }
     .template-insta .btn-default.active / .contact-us-enhanced
       .sumbit-button button.active { outline:none !important }
     .template-insta .FloorPlansV2 select { outline:0 }
   ------------------------------------------------------------ */
.template-insta a:focus-visible,
.template-insta button:focus-visible,
.template-insta .btn:focus-visible,
.template-insta .btn-primary:focus-visible,
.template-insta .btn-default:focus-visible,
.template-insta .navbar-toggle:focus-visible,
.template-insta .dropdown-toggle:focus-visible,
.template-insta .contact-us-enhanced .form-control:focus-visible,
.template-insta .contact-us-enhanced .sumbit-button button:focus-visible,
.template-insta .FloorPlansV2 select:focus-visible,
.template-insta input:focus-visible,
.template-insta select:focus-visible,
.template-insta textarea:focus-visible,
.template-insta [tabindex]:focus-visible,
.template-insta [role="button"]:focus-visible,
.footer-widget footer a:focus-visible {
  /* Webkit-style two-ring halo: blue inner ring + white outer ring
     gives focus visibility on both light AND dark backgrounds.
     The `outline` declaration is intentionally omitted — outline
     paints on top of box-shadow and would cover the white ring. */
  outline-offset: 2px !important;
  box-shadow: 0 0 0 2px #005fcc, 0 0 0 3px #fff !important;
}


/* ------------------------------------------------------------
   WCAG 2.4.11 Focus Not Obscured
   Multiple position:fixed elements in the base (header,
   stacked-amenities overlay, mobile menu). Header height not
   declared in master — use 100px scroll padding.
   ------------------------------------------------------------ */
html {
  scroll-padding-top: 100px;
}

.template-insta :focus-visible {
  scroll-margin-top: 100px;
}


/* ------------------------------------------------------------
   WCAG 1.4.11 Non-text Contrast (UI components)
   Base failures:
     .template-insta .FloorPlansV2 select { border:1px solid #ccc }
       ≈ 2.40:1 — fails 3:1.
     .template-insta ... { border:solid 1px #ddd } (line 2373)
       ≈ 1.60:1 — fails.
     .template-insta .FloorPlansV2 .fp-switch-tabs
       { border:1px solid #e7e7e7 } ≈ 1.18:1 — fails.
     ... { border-bottom:1px solid #ccc8c5 } (line 2231)
       ≈ 2.39:1 — fails.
   ------------------------------------------------------------ */
.template-insta .FloorPlansV2 select,
.template-insta .FloorPlansV2 .fp-switch-tabs {
  border-color: #595959;
}

body #contactUsEnhancedContainer .form-control {
  border-bottom: 1px solid #595959 !important;
}


/* ------------------------------------------------------------
   WCAG 1.4.3 Contrast Minimum (text)
   Base failure:
     #b4b4b4 (line 1368) ≈ 2.60:1 — clearly fails wherever
     used as text. Scoped to confirmed selectors only —
     brand hover color #717171 (≈ 4.20:1) is preserved as it's
     the property's accent. The 1.4.1 underline below carries
     the distinguishability requirement without recoloring.
     Shared footer-disclosure opacity 0.6 → 0.85.
   ------------------------------------------------------------ */
.template-insta .FloorPlansV3 .specification,
.template-insta .FloorPlansV2 .specification {
  color: #595959;
}

.footer-widget footer .footer-disclosure {
  opacity: 0.85;
}


/* ------------------------------------------------------------
   WCAG 1.4.1 Use of Color (inline links)
   ------------------------------------------------------------ */
.template-insta .main-content-text a,
.template-insta .inner-page-main a,
.template-insta .inner-page-main-content a,
.template-insta .main-content-wrapper a,
.template-insta .container-fluid.main a,
.template-insta .callout a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

.template-insta a.btn,
.template-insta a.button,
.template-insta .btn,
.template-insta .btn-primary,
.template-insta .btn-default,
.template-insta header a,
.template-insta nav a,
.template-insta .cta-header-btn,
.template-insta .header-CTA-button,
.template-insta .footer-CTA-Button,
.template-insta a.more-link,
.template-insta a.less-link,
.template-insta .contact-us-enhanced .sumbit-button button,
.footer-widget footer a {
  text-decoration: none;
}

/* ------------------------------------------------------------
   TFS 2870264 — WCAG 1.4.1 (homepage inline links)
   Insta's homepage uses `.home-intro` rows with
   `.home-intro-content` holding the welcome blurb. Verified
   against academyapts.com (inline link "GET STARTED WITH
   AirBnB" inside `.home-intro-content`).
   ------------------------------------------------------------ */
.template-insta .home-intro a,
.template-insta .home-intro-content a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

.template-insta .home-intro a.btn,
.template-insta .home-intro a.button,
.template-insta .home-intro-content a.btn,
.template-insta .home-intro-content a.button {
  text-decoration: none;
}


/** ------------------------------------------------------------
   WCAG 2.2 AA 2.5.8 Target Size (Pointer)
   ------------------------------------------------------------ */
.template-insta .navbar .header-contact .seo-number {
    line-height: 24px;
}
/* ------------------------------------------------------------
   TFS 2905632 - WCAG 1.4.1 Use of Color (selected state)
   The Floor Plans bed/bath filter and view-switch tabs mark the
   selected item with a brand-color background + #fff text only
   (base rule sets border-color:transparent, no weight/underline).
   Add an underline so the selection is perceivable in greyscale
   and for color-blind users. `body #form` prefix keeps specificity
   above the rpWebpartCss_Floorplan* base bundles. No color changed.
   ------------------------------------------------------------ */
body #form .fp2-bed-bath ul li.active > a,
body #form .FloorPlansV2 .fp-switch-tabs .btn-default.active,
body #form .FloorPlansV3 .fp-switch-tabs .btn-default.active {
  text-decoration: underline;
  text-underline-offset: 3px;
}

/* ------------------------------------------------------------
   TFS 2905631 - WCAG 1.4.11 Non-text Contrast (form controls)
   The full-width Neighborhood search input has no perceivable
   resting border: base CSS (rpWebpartCss_NeighborhoodFullWidth.css)
   sets `border:none; background:none; color:#fff` on a dark
   rgba(0,0,0,.83) search overlay. Add a light 1px boundary at
   #cfcfcf (~9.6:1 on that dark surface; matches the widget's
   existing placeholder color). All 21 priority templates use this
   dark default - none override it to a light surface.
   ------------------------------------------------------------ */
body #form .neighborhood-widget .neighborhood-widget__search .form-group .form-control {
  border: 1px solid #cfcfcf;
}

/* ------------------------------------------------------------
   TFS 2924975 - WCAG 1.4.3 Contrast (Minimum)
   The interior-page banner body copy renders #807e7d on the cream
   page background #f2eeea (3.50:1, fails AA 4.5:1). Base rule:
   RPcssMaster_C0067-GS-Insta.css `.template-insta .banner .content p`
   sets color:#807e7d; body.ContentBody sets background:#f2eeea.
   Darken to #595959 (~7:1 on #f2eeea). `body #form` prefix keeps
   specificity above the master sheet - no !important needed.
   (Home page is unaffected: it has no .banner .content p.)
   ------------------------------------------------------------ */
body #form .template-insta .banner .content p {
  color: #595959;
}

/* ------------------------------------------------------------
   TFS 2941965 / 2924977 - WCAG 2.2 AA 2.5.8 Target Size (Pointer)
   Privacy consent checkbox (Contact-Us enhanced + V1 + floating
   widgets). This template was missed in the original 2924977 rollout
   (block landed in 16 of 22 override files), so the native checkbox
   rendered <24px. Size it to 24x24 via appearance:none; :checked::after
   redraws the check so the consent UX is preserved. min-width/min-height
   hold the 24px floor against rpWebpartCss_ContactUsFloating's
   `width:auto !important` on the floating popup. input.privacy-check
   covers every widget variant (enhanced #privacyDiv, V1
   #contactUsV1Privacy, floating #contactusPrivacy/.contact-mobile-form,
   corporate #corporateContactPrivacy).
   ------------------------------------------------------------ */
body .contact-mobile-form input[type="checkbox"],
#contactusPrivacy input[type="checkbox"],
#privacyDiv input[type="checkbox"],
#contactUsV1Privacy input[type="checkbox"],
input.privacy-check[type="checkbox"] {
    -webkit-appearance: none;
    appearance: none;
    width: 24px; height: 24px;
    min-width: 24px; min-height: 24px;
    margin: 4px; padding: 0;
    border: 2px solid currentColor; border-radius: 3px;
    background: #fff; cursor: pointer; position: relative;
    vertical-align: middle; flex: 0 0 auto;
}
body .contact-mobile-form input[type="checkbox"]:checked::after,
#contactusPrivacy input[type="checkbox"]:checked::after,
#privacyDiv input[type="checkbox"]:checked::after,
#contactUsV1Privacy input[type="checkbox"]:checked::after,
input.privacy-check[type="checkbox"]:checked::after {
    content: ""; position: absolute; left: 7px; top: 3px;
    width: 6px; height: 11px;
    border: solid #1a1a1a; border-width: 0 2px 2px 0;
    transform: rotate(45deg);
}
body .contact-mobile-form input[type="checkbox"]:focus-visible,
#contactusPrivacy input[type="checkbox"]:focus-visible,
#privacyDiv input[type="checkbox"]:focus-visible,
#contactUsV1Privacy input[type="checkbox"]:focus-visible,
input.privacy-check[type="checkbox"]:focus-visible {
    outline: 2px solid; outline-offset: 2px;
}

/* ------------------------------------------------------------
   TFS 2924977 - WCAG 2.2 AA 2.5.8 Target Size (Pointer)
   Banner carousel paging dots. The global flexslider.css hit-box fix
   (.flex-control-paging li a -> 24px) is outranked by the master rule
   .template-insta .slides-banner-wrapper .flex-control-nav li a
   (specificity 0,3,2), so width/height stayed 14px. Grow the <a>
   itself to a 26px target (specificity 1,3,3, no !important) and
   redraw the 14px visible dot on ::before, so the master's outer glow
   hugs the dot instead of floating out from the enlarged border-box
   (padding + background-clip can't constrain box-shadow).
   ------------------------------------------------------------ */
body #form .template-insta .slides-banner-wrapper .flex-control-nav li a {
  box-sizing: border-box;
  width: 26px;
  height: 26px;
  padding: 0;
  background: transparent;
  box-shadow: none;
  position: relative;
}
body #form .template-insta .slides-banner-wrapper .flex-control-nav li a::before {
  content: "";
  position: absolute;
  top: 50%;
  left: 50%;
  width: 14px;
  height: 14px;
  margin: -7px 0 0 -7px;
  border-radius: 50%;
  background: rgba(255, 255, 255, 0.5);
  box-shadow: 0 0 5px rgba(0, 0, 0, 0.5);
}
body #form .template-insta .slides-banner-wrapper .flex-control-nav li a.flex-active::before {
  background: #fff;
}