/* ============================================================
   wcag-s0069-gs-grids.css
   WCAG 2.1 Level AA override for the S0069-Grids Kentico template
   (TemplateId 1363, DefaultCssFileName: RPcssMaster_S0069-GS-Grids).

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

   This template namespaces all base rules under .template-grids.
   Brand palette is gold #ddb563 + terracotta #c67e65 — both
   fail 4.5:1 on white as link/text colors.

   First flagged by Ron in TFS 2845711 (The Hill /
   thehillapts.com) as outside the current 8-template
   remediation scope. This file brings it in.
   ============================================================ */


/* ------------------------------------------------------------
   WCAG 2.4.7 Focus Visible
   Base suppresses outlines on:
     .template-grids a:hover { outline:0 }
     .template-grids a:hover, .template-grids a:focus
       { outline-color:transparent; outline-style:none }
     .template-grids .contact-widget .sumbitbutton input.active
       { outline:none !important }
     .template-grids .floorplan-search-bar .floorplan-search-moveindate:focus
       { outline:none }
   Plus Bootstrap's .navbar-toggle:focus, .dropdown-toggle:focus.
   The base's !important on submit-button outline forces ours to
   use !important for that selector class.
   ------------------------------------------------------------ */
.template-grids a:focus-visible,
.template-grids button:focus-visible,
.template-grids .btn:focus-visible,
.template-grids .btn-primary:focus-visible,
.template-grids .navbar-toggle:focus-visible,
.template-grids .dropdown-toggle:focus-visible,
.template-grids .top-bar a:focus-visible,
.template-grids .contact-widget input:focus-visible,
.template-grids .contact-us-enhanced .form-control:focus-visible,
.template-grids .floorplan-search-bar .floorplan-search-moveindate:focus-visible,
.template-grids .FloorPlansV3 a:focus-visible,
.template-grids input:focus-visible,
.template-grids select:focus-visible,
.template-grids textarea:focus-visible,
.template-grids [tabindex]:focus-visible,
.template-grids [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;
}

.template-grids .contact-widget .sumbitbutton input: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 !important;
  box-shadow: 0 0 0 2px #005fcc, 0 0 0 3px #fff !important;
}


/* ------------------------------------------------------------
   WCAG 2.4.11 Focus Not Obscured
   Header height not declared in master CSS (shared header
   resources). Use 100px scroll padding (Balcony default).
   ------------------------------------------------------------ */
html {
  scroll-padding-top: 100px;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.11 Non-text Contrast (form controls)
   Base: .template-grids .contact-us-enhanced .form-group .form-control
         { border:1px solid #ebe9e9 }
   #ebe9e9 on white ≈ 1.18:1 — fails 3:1. Bump to #595959.
   ------------------------------------------------------------ */
.template-grids .contact-us-enhanced .form-group .form-control {
  border-color: #595959;
}

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


/* ------------------------------------------------------------
   WCAG 1.4.3 Contrast Minimum (text)
   Base failures:
     1. .template-grids .FloorPlansV3 a { color:#c67e65 } ≈ 3.41:1
        — fails 4.5:1 for normal text.
     2. .template-grids a:hover, .template-grids a:focus
          { color:#ddb563 } ≈ 1.97:1 — link hover/focus is
        unreadable. Use darker gold #8a6b34 (~4.6:1) to keep
        the brand cue.
     3. Shared footer-disclosure opacity 0.6 → 0.85.
   ------------------------------------------------------------ */
/* SCOPE NOTE: two previous color overrides were removed from this
   block because both targeted brand colors that vary per property:

   (a) `.template-grids .FloorPlansV3 a { color: #595959 }` was
   replacing the floor-plans link color. Verified across 4 Greystar
   Grids properties — every property has a different FloorPlansV3
   link color (highbridge #6f8490, thejuneapts #212721,
   lindenhighlands #292421, lumenabq #477a7b). 3 of 4 already passed
   4.5:1 contrast; only highbridge's #6f8490 (~3.7:1) fails. Forcing
   gray on every property strips brand without fixing anything for
   the 3 that already passed.

   (b) Inline-link :hover/:focus color to #8a6b34 (dark brown),
   claiming it fixed `.template-grids a:hover { color:#ddb563 }`
   ≈ 1.97:1 on white. The base hover color is per-property
   (highbridge #5890b0, thejuneapts #d1ccbd, etc.). #8a6b34 isn't
   in any property's brand palette and could make hover text
   unreadable on dark-branded properties.
   Brand-color contrast failures must be fixed at the property level,
   not in shared template injection. See per-property-base-css memory.
   Also: the bare `p a:hover` / `li a:hover` selectors would bleed
   into nav/footer (same Balcony bug). Block removed entirely. */

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


/* ------------------------------------------------------------
   WCAG 1.4.1 Use of Color (inline links)
   ------------------------------------------------------------ */
.template-grids .container-fluid.main a,
.template-grids .col-sm-12.content a,
.template-grids .main-content-text a,
.template-grids .inner-page-main-content a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

.template-grids a.btn,
.template-grids a.button,
.template-grids .btn,
.template-grids .btn-primary,
.template-grids .top-bar a,
.template-grids .navbar-grids a,
.template-grids .cta-header-btn,
.template-grids .header-CTA-button,
.template-grids .footer-CTA-Button,
.template-grids a.more-link,
.template-grids a.less-link,
.template-grids .floorplan-search-bar a,
.template-grids .contact-widget .sumbitbutton input,
.footer-widget footer a {
  text-decoration: none;
}

/* ------------------------------------------------------------
   TFS 2870264 — WCAG 1.4.1 (homepage inline links)
   Grids' homepage uses `.special-home-message` for the
   welcome blurb (same wrapper used by Dakota/Elan/Emerald/
   Slate Phase 1 fixes). Verified against averydallas.com
   (4 inline links inside `.special-home-message`).
   ------------------------------------------------------------ */
.template-grids .special-home-message a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

.template-grids .special-home-message a.btn,
.template-grids .special-home-message a.button,
.template-grids .special-home-message a.more-btn,
.template-grids .special-home-message .more-btn {
  text-decoration: none;
}