/* ============================================================
   wcag-s0084-ascension.css
   WCAG 2.1 Level AA override for the S0084-Ascension Kentico template
   (TemplateId 1398).

   Selectors verified against the live base CSS pulled from
   https://livesommery.com on 2026-05-12
   (CMSPages/GetResource.ashx?stylesheetname=RPcssMaster_S0084-Ascension).

   This template does NOT use a .template-* wrapper. Overrides
   target the same selectors the base uses (often with `body`
   prefixes in the base, which we drop here — source order wins
   at equal specificity).
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   The Ascension master CSS has no outline:none rules, but
   Bootstrap suppresses outlines on .navbar-toggle / .dropdown-
   toggle / .btn / .form-control. Restore visible focus rings.
   ------------------------------------------------------------ */
.navbar-toggle:focus-visible,
.dropdown-toggle:focus-visible,
.btn:focus-visible,
.form-control:focus-visible,
.header-widget header a:focus-visible,
.header-widget .header-button.menu-toggle:focus-visible,
.menu-drawer .menu-nav ul li a:focus-visible,
.contactus-float-input-div input:focus-visible,
.contactus-float-input-div select:focus-visible,
.contactus-float-input-div textarea:focus-visible,
#homeContactSection input:focus-visible,
#homeContactSection select:focus-visible,
#homeContactSection textarea:focus-visible,
a:focus-visible,
button:focus-visible,
input:focus-visible,
select:focus-visible,
textarea:focus-visible,
[tabindex]:focus-visible,
[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;
  box-shadow: 0 0 0 2px #005fcc, 0 0 0 3px #fff;
}


/* ------------------------------------------------------------
   WCAG 2.4.11 Focus Not Obscured
   Base: #specialsContainer { position:fixed; top:0; width:100% }
   — promo banner overlaying the top of the page when specials
   are active. The Bootstrap-driven header can also occupy the
   top area. 100px scroll padding covers typical specials
   banner + header height.
   ------------------------------------------------------------ */
html {
  scroll-padding-top: 100px;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.11 Non-text Contrast (form controls)
   Two distinct contact form patterns on this template:

   1. /Contact.aspx dedicated form:
      #contactUsEnhancedContainer .form-control failure comes
      from shared webpart CSS (per the Haute pattern).
      Specificity: body + ID matches widget's (1,1,1); !important
      handles the base's `border-bottom:none` (no color to override).

   2. Home page / floating mini contact form (#homeContactSection):
      Base rule:
        body .contactus-float-input-div select,
        body .contact-mobile-form .contactus-float-input-div input
          { border-bottom: 1.5px solid #a3a3a3 }
      #a3a3a3 on white page bg ≈ 2.5:1 — fails 3:1. Same pattern
      as GS-Elan's mobile contact form. Specificity matches base;
      source order wins from location 2 (ExternalResources_Header).
   ------------------------------------------------------------ */
body #contactUsEnhancedContainer .form-control {
  border-bottom: 1px solid #595959 !important;
}

body .contact-mobile-form .contactus-float-input-div input,
body .contact-mobile-form .contactus-float-input-div select,
body .contact-mobile-form .contactus-float-input-div textarea,
body .contactus-float-input-div input,
body .contactus-float-input-div select,
body .contactus-float-input-div textarea {
  border-bottom-color: #595959;
}


/* ------------------------------------------------------------
   WCAG 1.4.3 Contrast Minimum (text)
   Real failures in the base:
     #7e7e7e on white ≈ 4.4:1 — fails 4.5:1. Used across nav,
     menu drawer, header button, floorplan specs, and form
     placeholders. Override those specific selectors to #595959.
     .footer-widget footer .footer-disclosure { opacity:.6 }
     from shared footer.min.css — bump to 0.85.
   ------------------------------------------------------------ */
/* SCOPE NOTE: the previous selector list also covered .header-widget,
   .menu-drawer, .contactus-float-input-div select, and .FloorPlansV2/V3
   .specification. Those have `color: #be9142` (gold) on livesommery.com
   but use entirely different brand palettes on other Greystar Ascension
   properties. Forcing `#595959` would make text practically invisible
   on dark-branded properties (e.g., livelexctrcity.com white-on-dark
   header). Brand-color contrast failures must be fixed at the property
   level, not in shared template injection. See per-property-base-css
   memory. Only #homeContactSection placeholders kept here — the input
   background (`#ededed`) is non-brand neutral across properties. */
body #homeContactSection input::placeholder,
body #homeContactSection textarea::placeholder,
body #homeContactSection select::placeholder {
  color: #595959;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.1 Use of Color (inline links)
   Underline inline content links so they are distinguishable
   without color. Header / nav / footer / CTA / button-styled
   links opt out — distinguishable by container or shape.
   Brand link color preserved.
   ------------------------------------------------------------ */
/* Scope: content containers only. Bare `p a` / `li a` / `dd a` selectors were dropped (same Balcony/Aurora/Bliss/Jackson-Square bleed bug — they would underline footer nav, header items, sidebar lists). */
.main-content-text a,
.inner-page-main a,
.main-content-wrapper a,
#contact-main-wrapper a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

a.btn,
a.button,
.btn,
.btn-primary,
.header-widget header a,
.header-widget nav a,
.menu-drawer a,
.cta-header-btn,
.header-CTA-button,
.footer-CTA-Button,
a.more-link,
a.less-link,
.header-button.menu-toggle,
.footer-widget footer a {
  text-decoration: none;
}

/** ------------------------------------------------------------
   WCAG 2.2 AA 2.5.8 Target Size (Pointer)
   ------------------------------------------------------------ */
.footer-widget footer .footer-nav>ul>li a,
.footer-widget footer.footer-1 a {
    line-height: 24px;
}
.footer-widget footer #link-rp {
    margin-bottom: 15px;
}