/* ============================================================
   wcag-s0092-emerald.css
   WCAG 2.1 Level AA override for the S0092-Emerald Kentico template.
   Owner of TFS 2849882 (1.4.11 form control contrast).

   Selectors verified against the live base CSS pulled from
   https://affinityatkendrick.com on 2026-05-07.

   Audit findings:
   - Base CSS (~25KB / 313 rules). No outline-suppression in
     template CSS; Bootstrap still removes them.
   - Form: #contactUsEnhancedContainer .form-control
       { border-color:#000; border-width:0 0 1px 0 }
     Black border passes 3:1 trivially. The TFS 2849882 form-
     contrast failure must be on a DIFFERENT form element on
     the live page (Silktide flagged something specific).
     Refine this file at deploy time after identifying the
     actual failing form control.
   - Footer link colors look correct (#fff, #efefef on dark).

   Specificity strategy:
   Every selector is prefixed with `body #form` to lift above
   widget CSS load order.
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   Bootstrap suppressors plus general fallback.
   ------------------------------------------------------------ */
body #form .navbar-toggle:focus-visible,
body #form .dropdown-toggle:focus-visible,
body #form .btn:focus-visible,
body #form .form-control:focus-visible,
body #form a:focus-visible,
body #form button:focus-visible,
body #form input:focus-visible,
body #form select:focus-visible,
body #form textarea:focus-visible,
body #form [tabindex]:focus-visible,
body #form [role="button"]:focus-visible,
body #form .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
   Default 80px scroll-padding; verify and adjust on live site.
   ------------------------------------------------------------ */
html {
  scroll-padding-top: 80px;
}

body #form :focus-visible {
  scroll-margin-top: 80px;
}


/* ------------------------------------------------------------
   WCAG 1.4.11 Non-text Contrast (TFS 2849882 form control)
   #contactUsEnhancedContainer .form-control already has
   border-color:#000 (passes). The flagged element is likely
   ELSEWHERE — possibly the contactus-floating widget, search
   bar inputs, or a different form. PLACEHOLDER override below
   covers the generic input case; refine after identifying the
   exact failing element via Silktide on the deployed page.
   ------------------------------------------------------------ */
body #form input.form-control,
body #form select.form-control,
body #form textarea.form-control,
body #form .contactus-float-input-div input,
body #form .contactus-float-input-div textarea,
body #form input[type="text"],
body #form input[type="email"],
body #form input[type="tel"],
body #form input[type="search"],
body #form select,
body #form textarea {
  border-color: #595959;
}

body #form input::placeholder,
body #form textarea::placeholder {
  color: #595959;
  opacity: 1;
}


/* ------------------------------------------------------------
   WCAG 1.4.3 Contrast Minimum (footer disclosure)
   ------------------------------------------------------------ */
body #form .footer-widget footer .footer-disclosure {
  opacity: 0.85;
}


/* ------------------------------------------------------------
   WCAG 1.4.1 Use of Color (inline links)
   ------------------------------------------------------------ */
body #form .main-content-text a,
body #form .inner-page-main-content a,
body #form .inner-page-main a,
body #form .mainContent a,
body #form main p a,
body #form article p a,
body #form .content p a,
body #form a[href$="Privacy-policy.aspx"] {
  text-decoration: underline;
  text-underline-offset: 2px;
}

body #form .btn,
body #form .button,
body #form header a,
body #form nav a,
body #form .navbar a,
body #form footer a,
body #form .footer-widget footer a,
body #form .footer-CTA-Button,
body #form .header-CTA-button,
body #form a.more-link,
body #form a.less-link {
  text-decoration: none;
}


/* ------------------------------------------------------------
   TFS 2870264 — WCAG 1.4.1 (homepage inline links)
   Emerald's homepage welcome zone is
   `<div id="welcome" class="main-row">` containing
   `.contentTable > .contentCell.welcomeCell.welcomeText` for
   the inline-text content (sibling `.welcomeImages` holds
   images). The `#connect` row beneath is utility info (office
   address, phone) — those links are wrapped CTAs, not inline
   prose, so opted out.
   ------------------------------------------------------------ */
body #form #welcome .welcomeText a,
body #form .welcomeCell.welcomeText a,
body #form .contentCell.welcomeText a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

body #form #connect a,
body #form .connectInfoWrapper a,
body #form .connectOffice a,
body #form a.seo-number {
  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 .footer-content #link-rp {
    margin-bottom: 15px;
}
/* ------------------------------------------------------------
   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 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;
}