/* ============================================================
   wcag-s0071-aurora.css
   WCAG 2.1 Level AA override for the S0071-Aurora Kentico template
   (TemplateId 1372, DefaultCssFileName: RPcssMaster_S0071-Aurora).

   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:
     .header-contents { position:fixed; top:0 }
     .top-spacer { height:185px }  ← actual reserved space
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   No outline:none in Aurora's master CSS, but Bootstrap
   suppresses outlines on .navbar-toggle / .dropdown-toggle / .btn.
   ------------------------------------------------------------ */
.navbar-toggle:focus-visible,
.dropdown-toggle:focus-visible,
.btn:focus-visible,
.cta-button:focus-visible,
a.home-cta-button:focus-visible,
.form-control:focus-visible,
.header-contents a:focus-visible,
.header-main a:focus-visible,
.main-menu-container 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
   Base: .header-contents { position:fixed; top:0 } with
   .top-spacer { height:185px }. 200px scroll padding covers
   the reserved space plus a small buffer.
   ------------------------------------------------------------ */
html {
  scroll-padding-top: 200px;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.11 Non-text Contrast (form controls)
   #contactUsEnhancedContainer .form-control failure comes from
   shared webpart CSS. Specificity strategy matches Ron's Haute.
   ------------------------------------------------------------ */
body #contactUsEnhancedContainer .form-control {
  border-bottom: 1px solid #595959 !important;
}


/* ------------------------------------------------------------
   WCAG 1.4.3 Contrast Minimum (text)
   Base failures:
     1. body a, body a:hover { color:#7e7e7e } ≈ 4.4:1 — fails
        4.5:1 by a hair. NB: this is a GLOBAL link color rule.
        Scoping the override to content zones avoids clobbering
        any per-property branded link color in nav/CTA/footer.
     2. .cta-button, a.home-cta-button, .header-main a em/i, and
        floorplan specs use the same #7e7e7e on white. Bump only
        the content-area inheritors here; CTA/header retain
        whatever brand color the property sets.
     3. 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 because bare element
   selectors bleed into nav/footer/sidebar — Manila's intent was to
   scope to content zones (per the comment above) but the bare
   selectors defeat that. Verified against Aurora base CSS:
     header #menuElem li a       → #29292e (would be downgraded)
     .tabs-panel ul li a         → #29292e
     #leftPanelTabs .tabList li a:hover/active → #fff (on dark bg)
                                  → INVISIBLE if forced to #595959
     .social_media .footer-social li a → #008080 (brand teal)
   Also dropped `.FloorPlansV3 .specification` / `.FloorPlansV2
   .specification` — same per-property brand color pattern as
   Grids' .FloorPlansV3 a (4 different colors across 4 properties).
   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,
a.cta-button,
a.home-cta-button,
.btn,
.btn-primary,
.header-contents a,
.header-main a,
.main-menu-container a,
.cta-header-btn,
.header-CTA-button,
.footer-CTA-Button,
a.more-link,
a.less-link,
.footer-widget footer a {
  text-decoration: none;
}

/* ------------------------------------------------------------
   TFS 2870264 — WCAG 1.4.1 (homepage inline links)
   Defensive — Aurora's homepage stacks six numbered section
   wrappers (`.home-section1` through `.home-section6`)
   plus `.home-banner-text` and `.home-section-overlay`.
   1600boulder.com showed no inline prose anchors in those
   today (CTAs use `.home-cta-button` / `.cta-button` —
   already opted out above), but the wrappers exist and
   would need underline coverage if a property's content
   editor adds an inline link inside the section copy.
   ------------------------------------------------------------ */
.home-section1 a,
.home-section2 a,
.home-section3 a,
.home-section4 a,
.home-section5 a,
.home-section6 a,
.home-banner-text a,
.home-section-overlay a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

.home-section1 a.btn,
.home-section1 a.button,
.home-section2 a.btn,
.home-section2 a.button,
.home-section3 a.btn,
.home-section3 a.button,
.home-section4 a.btn,
.home-section4 a.button,
.home-section5 a.btn,
.home-section5 a.button,
.home-section6 a.btn,
.home-section6 a.button,
.home-cta-button,
.home-cta-group a,
.home-cta-text a,
a.home-cta2 {
  text-decoration: none;
}


/* ------------------------------------------------------------
   WCAG 2.2 AA 2.5.8 Target Size (Pointer)
   ------------------------------------------------------------ */
.footer-info-menu li a {
    line-height: 24px;
}