/* ============================================================ wcag-s0076-jackson-square.css WCAG 2.1 Level AA override for the S0076-Jackson-Square Kentico template (TemplateId 1389, DefaultCssFileName: RPcssMaster_S0076-Jackson-Square). 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. No top-bar sticky header in master CSS — sticky header comes from shared resources. ============================================================ */ /* ------------------------------------------------------------ WCAG 2.4.7 Focus Visible ------------------------------------------------------------ */ .navbar-toggle:focus-visible, .dropdown-toggle:focus-visible, .btn:focus-visible, .form-control:focus-visible, header a:focus-visible, nav a:focus-visible, #hamburgerNavMenuContainer 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 ------------------------------------------------------------ */ html { scroll-padding-top: 100px; } :focus-visible { scroll-margin-top: 100px; } /* ------------------------------------------------------------ WCAG 1.4.11 Non-text Contrast (UI components) Base failures: border-bottom:2px solid #efefef on menu hover/dividers (lines 1766, 1770, 1774) ≈ 1.18:1 — fails 3:1. border-bottom:solid 2px #ddd (line 2871) ≈ 1.59:1 — fails. ------------------------------------------------------------ */ #menuDesktop #menuElem li a:hover, #menuMobile li a:hover { border-bottom-color: #595959; } body #contactUsEnhancedContainer .form-control { border-bottom: 1px solid #595959 !important; } /* ------------------------------------------------------------ WCAG 1.4.3 Contrast Minimum (text) Base failures: #7e7e7e text-color rules ≈ 4.4:1 — fails 4.5:1. Shared footer-disclosure opacity 0.6 → 0.85. ------------------------------------------------------------ */ /* SCOPE NOTE: removed `.FloorPlansV3 .specification` / `.FloorPlansV2 .specification` color override. Verified across 53 prod + 7 SAT Jackson-Square domains (any PMC): the `.FloorPlansV2 .specification strong` color varies per property with 28+ distinct brand values, including #964c44 (Gorman default, 14 properties), #babd34 (Greystar's themckenzieapts), #40c1f1 (cyan), #03700e (green), #c2072e (red), and many others. Forcing `#595959` would replace per-property brand accents with generic gray on every site. Brand-color contrast failures belong at the property-CSS level. See per-property-base-css memory. */ .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 bleed bug) — they would underline footer nav, header nav, sidebar lists, and disclosure paragraphs unintentionally. TFS 2985969 — added `.topContent`, `.page_neighborhood` and `#contactusPrivacy`: * Neighborhood prose links (B2 Bar and Grill, Mezza Luna Pizzeria, Costco, Trader Joe's, Valley River Center) sit in `.topContent` / `.page_neighborhood`, not `.mainContent` — confirmed live on themckenzieapts.com/Neighborhood.aspx. The base even styles them explicitly (RPcssMaster_S0076-Jackson-Square.css:336 `.topContent a, .topContent a:hover, .topContent a:focus { color: RPcolor4 }`) — brand color and nothing else, i.e. colour-only distinction. * `#privacyDiv a` — the Contact-page privacy link. NOTE: the id on this template is `#privacyDiv`, NOT `#contactusPrivacy` (that id belongs to Elan/Balcony/Teracy and does not exist on Jackson-Square — measured 0 occurrences on themckenzieapts.com/Contact.aspx). The live chain is main#main-content > .page-placeholder-container > .page_contactus > … > .mainContent > .contact-us-enhanced > #contactUsEnhancedContainer > .row > .col-md-6 > #privacyDiv > label > a This file has no `.mainContent a` selector (that is Zen-Garden's), and the pre-existing homepage rule is scoped to `#homeContactCallout #privacyDiv a`, which this Contact-page instance is NOT under — so it was uncovered. `#privacyDiv a` is therefore deliberately left UNSCOPED. `#contactusPrivacy a` is kept as harmless defence-in-depth in case a template variant emits it. The wrapper's `timeout-error-contact` class is NOT a hider — it is hardcoded on the always-rendered container (ContactUsEnhanced.ascx.cs:317) and only namespaces an optional child `.timeout-message`, so this link is user-facing. Bleed check: `.page_neighborhood` is the page-content wrapper authored in S0076-Jackson-Square-Neighborhood.ascx:5 and `.topContent` is the standard content-zone wrapper. Both render inside `
` per S0076-Jackson-Square-Master.ascx:11-13, while `
`, `zoneNavBar`, `zoneHamburgerMenu` and `