/* ============================================================ wcag-s0077-harmony.css WCAG 2.1 Level AA override for the S0077-Harmony Kentico template (TemplateId 1395, DefaultCssFileName: RPcssMaster_S0077-Harmony). 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. Header is confirmed sticky: #header-wrapper { height:110px; position:fixed; top:0 } ============================================================ */ /* ------------------------------------------------------------ WCAG 2.4.7 Focus Visible ------------------------------------------------------------ */ .navbar-toggle:focus-visible, .dropdown-toggle:focus-visible, .btn:focus-visible, .form-control:focus-visible, #header-wrapper a:focus-visible, #header-cta-wrapper a:focus-visible, header 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-wrapper { height:110px; position:fixed; top:0 } ------------------------------------------------------------ */ html { scroll-padding-top: 130px; } :focus-visible { scroll-margin-top: 130px; } /* ------------------------------------------------------------ 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; } /* ------------------------------------------------------------ WCAG 1.4.3 Contrast Minimum (text) Base failures: #7e7e7e in 6+ rules ≈ 4.4:1 — fails 4.5:1. 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-wrapper a, #header-cta-wrapper a, header 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) Defensive — Harmony shares Avana's BEM-style `.homepage__about-*` widget; the homepage wraps welcome text in `.homepage__about-container > .homepage__about- content`. broadstonewoodmillcreek.com showed no inline anchors in the block today, but the wrapper exists; cover it for future content-editor-added links. ------------------------------------------------------------ */ .homepage__about-container a, .homepage__about-content a, .homepage__about-content--link { text-decoration: underline; text-underline-offset: 2px; } .homepage__about-button, .homepage__about-buttons a, .homepage__about-content a.btn, .homepage__about-content a.button { text-decoration: none; } /* ------------------------------------------------------------ WCAG 2.2 AA 2.5.8 Target Size (Pointer) ------------------------------------------------------------ */ .footer-links ul li a, body .header-contents .header-widget .header-2 .header-links li a, body .header-contents .menu-drawer .header-links li a, body .header-contents .menu-drawer .header-links li a { line-height: 24px; min-height: 25px; margin: 5px 0; } /* ------------------------------------------------------------ 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 2982346 - WCAG 2.2 AA 2.5.8 Target Size (Pointer): footer links Live-measured on testwinharmonysat100623.sat-ws.realpage.com/Contact.aspx at 1280x900 (headless Chrome, border-box heights): 4 footer target(s) under 24x24. footer .footer-links li.footer-site-map-link a 57.5 x 19, display:inline footer #ada-hud-links a#link-ada / a#link-hud 20 x 30 - fails on WIDTH only footer .footer-logo.footer-pmclogo a 140 x 19, display:inline, wraps an These are display:inline, where `line-height` cannot help - it does not change an inline element's border-box height. inline-block is what makes min-height apply. No padding and no negative-margin cancel is used: each target sits in a line box already at or above 24px, so the box grows into existing leading. Verified by injecting these rules into the live SAT page: 0 targets remaining and no horizontal overflow. Document height +0px at 1280px; +8px at 390px, where the PMC logo and sitemap link sit in tighter line boxes and genuinely gain height rather than consuming leading. SCOPE PREFIX: scoped on the `footer` element. On THIS template `.footer-widget footer` also matches, so either prefix would work - the bare `footer` is used for consistency across the 18 template files in this ticket, three of which genuinely need it (Zen-Garden and Au-Courant nest `footer > .footer-widget`, reversed; Jackson-Square has no `.footer-widget` element at all). `footer` is a superset of both nestings. Verified against the live SAT DOM per template - not assumed. ------------------------------------------------------------ */ footer .footer-links li.footer-privacy-link a, footer .footer-links li.footer-site-map-link a { display: inline-block; min-height: 24px; } /* ADA/HUD icons already clear 24px on HEIGHT (30px here) and fail only on WIDTH: the anchor is inline-block wrapping a 20px SVG. min-width is the whole fix - do NOT add min-height, which would stretch the row for nothing. */ footer #ada-hud-links a#link-ada, footer #ada-hud-links a#link-hud { min-width: 24px; } footer .footer-logo.footer-pmclogo a { display: inline-block; min-height: 24px; }