/* ============================================================
   wcag-c0053-gs-teracy.css
   WCAG 2.1 Level AA override for the C0053-GS-Teracy Kentico template
   (TemplateId 1373, DefaultCssFileName: RPcssMaster_C0053-GS-Teracy).

   Selectors verified against the live base CSS pulled from
   https://www.1000jeffersonapts.com on 2026-05-12.

   This template does NOT use a .template-* wrapper.
   Header is confirmed sticky:
     header { position:fixed; height:80px; top:0; z-index:100 }
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   Base: body .FloorPlansV2 #sidebar .button a { outline:none }
   plus Bootstrap's standard .navbar-toggle / .dropdown-toggle
   suppressions.
   ------------------------------------------------------------ */
.navbar-toggle:focus-visible,
.dropdown-toggle:focus-visible,
.btn:focus-visible,
.form-control:focus-visible,
.FloorPlansV2 #sidebar .button a:focus-visible,
header a:focus-visible,
#innerNav a:focus-visible,
#innerNav #menuElem li 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 { position:fixed; height:80px; top:0 }
   Reserve scroll space matching the measured header + 20px buffer.
   ------------------------------------------------------------ */
html {
  scroll-padding-top: 100px;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.11 Non-text Contrast (UI components)
   Base failures:
     .fp2-left-panel-header { border-color:#cfcfcf !important }
     body .fp2-show-available { border-color:#cfcfcf !important }
   #cfcfcf on white ≈ 1.50:1 — fails 3:1 for UI component
   boundaries. Override matches with !important to win.
   ------------------------------------------------------------ */
.fp2-left-panel-header,
.fp2-show-available {
  border-color: #595959 !important;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.3 Contrast Minimum (text)
   The Teracy master CSS has no failing text-color rules of its
   own (the #d1d1d1 usages are light text on a dark #4a4a4a
   inner-nav background ≈ 8:1, which passes).
   Shared footer-disclosure opacity 0.6 → 0.85.
   ------------------------------------------------------------ */
.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). */
.inner-page-main a,
.inner-page-master a,
.main-content-text a,
.main-content-wrapper a,
#contactusPrivacy a,
a[href$="Privacy-policy.aspx"] {
  text-decoration: underline;
  text-underline-offset: 2px;
}

a.btn,
a.button,
a.cta-button,
.btn,
.btn-primary,
header a,
#innerNav a,
#innerNav #menuElem li 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)
   Teracy's homepage uses `#homeMain` (`.container`) wrapping
   `#homeMainTop > .home-right > .cta > .cta-content` for the
   welcome/intro prose, and `#homeMainBottom > .home-neighborhood-
   content` for the around-town blurb. Inline prose anchors land
   in either block. Verified against 1000jeffersonapts.com (welcome
   "Strikingly Modern Apts" blurb + Around Town neighborhood blurb).
   The Schedule-A-Visit CTA (`a.cta-button`) is already opted out
   above.

   CORRECTION (TFS 2985969) — this block previously claimed:
     "The header `.topCallout > a` ("Click Here") sits outside
      `#homeMain`, in the header zone — already covered by the
      `header a` opt-out."
   That premise is FALSE and left a live 1.4.1 failure in place.
   See the TFS 2985969 block below for the evidence and the fix.
   Do not re-derive the old conclusion.
   ------------------------------------------------------------ */
#homeMain .cta-content a,
#homeMain .home-neighborhood-content a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

#homeMain .cta-content a.cta-button,
#homeMain .cta-content a.btn,
#homeMain .cta-content a.button,
#homeMain .home-neighborhood-content a.btn,
#homeMain .home-neighborhood-content a.button {
  text-decoration: none;
}

/* ------------------------------------------------------------
   TFS 2985969 — WCAG 1.4.1: `.topCallout a` ("Click Here")
   Reported failing on live https://www.1000jeffersonapts.com/
   (Silktide/axe `link-in-text-block`, at
    /html/body/form/div[5]/div/div/div/div/div/div/div/a).

   Root cause — the TFS 2870264 comment above assumed this anchor
   was inside the header zone and therefore already covered by the
   `header a` opt-out. It is NOT. Verified against the live DOM:
     form#form > div.container-fluid.page-container > div.row
       > div#homeMenu.container > div.row > div.menu-container.container
         > div.row > div#homeNav.nav-menu.shadow > div.topCallout > a
   Every ancestor is a plain `div` — the anchor has NO <header>,
   <nav> or <footer> ancestor, and the page's single <header>
   element does not contain `.topCallout`. So `header a` never
   matched it, no underline selector reached it, and the base
   leaves it colour-only in EVERY state
   (RPcssMaster_C0053-GS-Teracy.css:429-436):
     .topCallout a       { text-decoration: none; color: RPcolor3; }
     .topCallout a:hover { text-decoration: none; color: RPcolor3,l1.1; }
   i.e. hover changes only the colour — no non-colour cue at rest
   or on interaction. `.topCallout` is a template-level component,
   not per-site content (base styles it at :423 with responsive
   rules at :468/:478/:485), so this applies fleet-wide on Teracy.

   `body #form .topCallout a` is (1,1,2), which beats the base
   (0,1,1) at rest and (0,2,1) on hover outright. The base uses no
   `!important` on these rules, so no `!important` counter is
   needed — a plain declaration holds through hover/focus/active.

   NOTE: this also disproves the "Teracy is clean" conclusion in
   the 2985969 plan (§9.4). That sweep checked interior-page prose
   links and missed this homepage nav-adjacent callout.
   ------------------------------------------------------------ */
body #form .topCallout a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

/* Container-scoped opt-out: the underline rule above (1,1,2)
   out-specifies the bare shape opt-outs near the top of this file
   (`a.btn` / `a.button` / `a.cta-button` at (0,1,1), `.btn-primary`
   at (0,1,0)), so re-assert them at `.topCallout` scope (1,2,2) to
   keep button/CTA-shaped links un-underlined. */
body #form .topCallout a.btn,
body #form .topCallout a.button,
body #form .topCallout a.btn-primary,
body #form .topCallout a.cta-button,
body #form .topCallout a.cta-header-btn,
body #form .topCallout a.header-CTA-button,
body #form .topCallout a.footer-CTA-Button,
body #form .topCallout a.more-link,
body #form .topCallout a.less-link {
  text-decoration: none;
}

/* ------------------------------------------------------------
   TFS 2985969 — Google Maps bleed opt-out (measured live on sibling templates)
   The Maps JS API injects its own colour-only anchors ("Terms",
   "Report a map error", "Open this area in Google Maps") into
   `.gm-style` INSIDE our content containers, so a container-scoped
   underline rule reaches them. Confirmed live on Elan /About.aspx,
   themckenzieapts.com home, and both Balcony homepages (see
   sibling override files) — not independently re-verified on this
   Teracy template, but the same Maps JS API behavior applies
   wherever the widget renders inside a covered container, so this
   opt-out is applied defensively here too. These are third-party
   map chrome, not site prose — never underline them.

   `!important` and the `body #form` prefix are both required so
   this beats the content-container counters in this file family,
   including the `underline !important` interaction-state counters
   on Jackson-Square and Zen-Garden. States are listed explicitly
   because those counters are state-scoped.
   ------------------------------------------------------------ */
body #form .gm-style a,
body #form .gm-style a:hover,
body #form .gm-style a:focus,
body #form .gm-style a:active,
body #form .google-map-container a,
body #form .google-map-container a:hover,
body #form .google-map-container a:focus,
body #form .google-map-container a:active,
body #form .gm-style-cc a,
body #form a[href*="maps.google.com/maps?ll="],
body #form a[href^="https://www.google.com/maps/@"] {
  text-decoration: none !important;
}

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