/* ============================================================
   wcag-s0078-bliss.css
   WCAG 2.1 Level AA override for the S0078-Bliss Kentico template
   (TemplateId 1408, DefaultCssFileName: RPcssMaster_S0078-Bliss).

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

   This template does NOT use a .template-* wrapper.
   Header is confirmed sticky:
     body .header-widget header.header-sticky { position:fixed }
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   ------------------------------------------------------------ */
.navbar-toggle:focus-visible,
.dropdown-toggle:focus-visible,
.btn:focus-visible,
.form-control:focus-visible,
.header-widget header a:focus-visible,
.menu-drawer a:focus-visible,
.contact-us-enhanced .form-control: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
   ------------------------------------------------------------ */
html {
  scroll-padding-top: 100px;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.11 Non-text Contrast (form controls)
   Base failures:
     1. .homeContactFormHolder .contact-mobile-form
          .contactus-float-input-div input/select/textarea
          { border-bottom:1px solid #cfcecb } ≈ 1.62:1 — fails 3:1.
     2. #contactUsEnhancedContainer .form-control comes from
        shared webpart CSS; per Ron's Haute pattern, override
        with body #contactUsEnhancedContainer prefix to lift
        above widget CSS load order.

   The .l-title / .hero__text rules using #d5d5d5 borders are
   decorative title frames — 1.4.11 excludes purely decorative
   borders. Left alone.

   Specificity strategy:
   The base rules carry `body ...` prefixes, so we match with
   `body ...` here. The #contactUsEnhancedContainer fix keeps
   !important because typical widget CSS sets
   `border-bottom:none` (no color value to override).
   ------------------------------------------------------------ */
body .homeContactFormHolder .contact-mobile-form .contactus-float-input-div input,
body .homeContactFormHolder .contact-mobile-form .contactus-float-input-div select,
body .homeContactFormHolder .contact-mobile-form .contactus-float-input-div textarea {
  border-bottom-color: #595959;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.3 Contrast Minimum (text)
   Base failures:
     body a, body a:hover { color:#bea67e } ≈ 3.31:1 — fails 4.5:1.
     NB: this is a GLOBAL link color. Scoped to content zones
     to avoid clobbering per-property branded link colors in
     nav/CTA/footer.
     #7e7e7e in 5+ rules ≈ 4.4:1 — borderline.
     Shared footer-disclosure opacity 0.6 → 0.85.
   ------------------------------------------------------------ */
/* SCOPE NOTE: dropped `p a`, `li a`, `dd a` from both the 1.4.3
   color rule and the 1.4.1 underline rule (bare element selectors
   bleed into nav/header/footer). Manila's comment above states
   the intent was to scope to content zones; the bare selectors
   defeat that. Verified against Bliss base CSS (cpwaterfront.com
   prod vs blissandro SAT) — multiple per-property brand colors
   on nav li>a:
       #headerNav2 li a:hover       prod=#e3983b  SAT=#b3a67e
       header nav.header-nav li a   prod=#538fab  SAT=#6d6d6d
       header-sticky nav li a:hover prod=#e3983b  SAT=#b3a67e
       header-4 nav li a            #fff (would be downgraded to
                                    gray-on-dark = invisible)
   Also dropped `.FloorPlansV3 .specification` / `.FloorPlansV2
   .specification` — same per-property brand pattern as Grids
   (4 different colors across 4 properties) and Aurora.
   See per-property-base-css memory. Brand-color contrast failures
   must be fixed at the property-CSS level. */
.main-content-text a,
.inner-page-main a,
.main-content-wrapper a {
  color: #595959;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.1 Use of Color (inline links)
   Scope matches the 1.4.3 rule above — content containers only,
   no bare `p a` / `li a` / `dd a`.
   ------------------------------------------------------------ */
.main-content-text a,
.inner-page-main a,
.main-content-wrapper a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

a.btn,
a.button,
.btn,
.btn-primary,
.header-widget header a,
.menu-drawer a,
.cta-header-btn,
.header-CTA-button,
.footer-CTA-Button,
a.more-link,
a.less-link,
.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,
#privacyDiv label {
    line-height: 30px;
}
input[type="checkbox"] {
    padding: 20px;
    margin: 4px;
}
.footer-widget footer #link-rp {
    margin-bottom: 15px;
}