/* ============================================================
   wcag-s0063-au-courant.css
   WCAG 2.1 Level AA override for the S0063-Au-Courant Kentico template
   (TemplateId 1338, DefaultCssFileName: RPcssMaster_S0063-Au-Courant).

   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. No
   position:fixed in master CSS — sticky header comes from
   shared resources.
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   ------------------------------------------------------------ */
.navbar-toggle:focus-visible,
.dropdown-toggle:focus-visible,
.btn:focus-visible,
.form-control:focus-visible,
header a:focus-visible,
nav 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)
   #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;
}


/* ------------------------------------------------------------
   TFS 2871246 — WCAG 1.4.11 (homepage "Ready to Tour?" form)
   The homepage uses the ContactUsFloating widget (separate from
   the /Contact.aspx #contactUsEnhancedContainer form handled
   above). Markup: `<footer class="footerContact"> ... .contact-
   mobile-form .contactus-float-input-div input/select`.
   Inputs render white with no visible border on the template's
   orange/peach hero band — fails 3:1 against the surroundings.
   Full border (not just bottom) so the control is defined on
   any background.
   ------------------------------------------------------------ */
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,
body .contact-mobile-form input.body-txt1,
body .contact-mobile-form select.body-txt1 {
  border: 1px solid #595959 !important;
}

body .contact-mobile-form input::placeholder,
body .contact-mobile-form textarea::placeholder {
  color: #595959;
  opacity: 1;
}


/* ------------------------------------------------------------
   WCAG 1.4.3 Contrast Minimum (text)
   Base failures:
     #7e7e7e in 6+ rules ≈ 4.4:1 — fails 4.5:1.
     #999 (line 226) ≈ 2.85:1 — clearly fails.
     Shared footer-disclosure opacity 0.6 → 0.85.
   ------------------------------------------------------------ */
.FloorPlansV3 .specification,
.FloorPlansV2 .specification {
  color: #595959;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.1 Use of Color (inline links)
   ------------------------------------------------------------ */
/* 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 {
  text-decoration: underline;
  text-underline-offset: 2px;
}

a.btn,
a.button,
.btn,
.btn-primary,
header a,
nav 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)
   Au-Courant's homepage uses `.slider` rows with
   `.cta2Content` / `.cta3Content` / `.cta4Content` content
   columns; inline prose sits in `.leftCol` / `.rightCol`
   under each. Verified against 24merrimackstreet.com (inline
   link "View our amenities." inside `.cta2Content .leftCol`).
   ------------------------------------------------------------ */
.slider .cta2Content a,
.slider .cta3Content a,
.slider .cta4Content a,
.cta2Content .leftCol a,
.cta2Content .rightCol a,
.cta3Content .leftCol a,
.cta3Content .rightCol a,
.cta4Content .leftCol a,
.cta4Content .rightCol a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

.cta2Content a.btn,
.cta2Content a.button,
.cta3Content a.btn,
.cta3Content a.button,
.cta4Content a.btn,
.cta4Content a.button {
  text-decoration: none;
}