/* ============================================================
   wcag-s0075-zen-garden.css
   WCAG 2.1 Level AA override for the S0075-Zen-Garden Kentico template
   (TemplateId 1387).

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

   This template does NOT use a template-namespace prefix — base
   selectors are global. Bootstrap is loaded separately and
   suppresses outlines on .navbar-toggle / .dropdown-toggle as
   usual.

   Specificity strategy:
   Every selector is prefixed with `body #form` (ASP.NET WebForms
   page-level form ID) to lift specificity above widget CSS that
   loads after our override.
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   The Zen-Garden CSS itself has no outline-suppression rules,
   but Bootstrap removes outlines on .navbar-toggle, .dropdown-
   toggle, .form-control:focus, etc. Restore visible focus rings
   via :focus-visible.
   .footer-widget footer a:focus { outline:none } also lives in
   the shared footer.min.css — covered here too.
   ------------------------------------------------------------ */
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 input.form-control:focus-visible,
body #form select.form-control:focus-visible,
body #form textarea.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
   Base: #topHeaderBar { position:fixed; top:0; padding:15px 0;
                         font-size:18px; ... } ≈ 50px tall.
   Reserve scroll space below the sticky bar.
   ------------------------------------------------------------ */
html {
  scroll-padding-top: 80px;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.11 Non-text Contrast (form controls)
   Base: input.form-control, select.form-control, textarea.form-control
         { border:none; border-bottom: solid 1px #c1c1c1; ... }
   #c1c1c1 on white ≈ 1.85:1 — fails 3:1.
   ------------------------------------------------------------ */
body #form input.form-control,
body #form select.form-control,
body #form textarea.form-control {
  border-bottom-color: #595959;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.1 Use of Color (inline links)
   Base inline content links:
     .mainContent a, .contentPrivacy a, .content404 a,
     .thankyoublurb a, .readmoreWrapper a
       { color:#799c0b; font-size:24px; }
   No underline → fails 1.4.1 (color-only distinction).
   We add underline ONLY (no color change). Reasons:
     1. The 24px font-size qualifies as WCAG large text — only
        3:1 contrast required. #799c0b on white ≈ 3.5:1 PASSES
        large-text contrast, so 1.4.3 is not technically failed.
     2. Brand colors vary per property. A blanket color override
        in this template-level injection would clash with any
        property whose brand replaces the default green.
   If Silktide flags 1.4.3 anyway on a specific property, fix it
   at that property's site-CSS level, not here.
   ------------------------------------------------------------ */
body #form .mainContent a,
body #form .contentPrivacy a,
body #form .content404 a,
body #form .thankyoublurb a,
body #form .readmoreWrapper a {
  text-decoration: underline;
  text-underline-offset: 2px;
}


/* ------------------------------------------------------------
   WCAG 1.4.3 (footer disclosure opacity)
   Shared footer.min.css: .footer-widget footer .footer-disclosure
     { opacity:.6 }  — bump so 4.5:1 passes comfortably.
   ------------------------------------------------------------ */
body #form .footer-widget footer .footer-disclosure {
  opacity: 0.85;
}


/* ------------------------------------------------------------
   Footer link / nav / button opt-outs
   These are distinguishable by container or shape, so they do
   NOT need underline.
   ------------------------------------------------------------ */
body #form .btn,
body #form .button,
body #form header a,
body #form nav a,
body #form .navbar a,
body #form .cta-header-btn,
body #form .header-CTA-button,
body #form .footer-CTA-Button,
body #form .footer-widget footer a,
body #form a.more-link,
body #form a.less-link {
  text-decoration: none;
}

/* ------------------------------------------------------------
   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;
}

/* WCAG 2.2 AA 2.5.8 Target Size (Pointer) — real fix (native checkbox can't be padded;
   appearance:none + explicit 24px sizing; :checked::after re-draws the check so consent UX is preserved) */
body .contact-mobile-form input[type="checkbox"],
#contactusPrivacy input[type="checkbox"],
#privacyDiv input[type="checkbox"],
#contactUsV1Privacy input[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 {
    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 {
    outline: 2px solid; outline-offset: 2px;
}