/* ============================================================ wcag-s0088-haute.css WCAG 2.1 Level AA override for the S0088-Haute Kentico template. Selectors verified against the live base CSS pulled from https://ascendatelevon.com on 2026-05-07. Audit findings: - Base CSS (~52KB / 572 rules). No outline-suppression in template CSS; Bootstrap still removes them. - Form controls — TWO real failures: 1. .neighborhood-widget .form-control { border:1px solid #999 } #999 ≈ 2.85:1 — fails 3:1. 2. #contactUsEnhancedContainer .form-control { background:#f1f1f1; border-bottom:none } No visible border at all. Visual cue absent. - Sticky elements: .header-menu and #menu-screen-overlay are position:fixed; height not declared in those rules. - Footer link hover: ul.footer-links li a:hover { color:#999 } If footer is dark, that's fine; if light, fails. Verify. Specificity strategy: Every selector is prefixed with `body #form` to lift above widget CSS load order. The form-control fix for #contactUsEnhancedContainer keeps its !important because the base rule explicitly sets `border-bottom:none` (without a color value to override). ============================================================ */ /* ------------------------------------------------------------ WCAG 2.4.7 Focus Visible Bootstrap suppressors plus general fallback. ------------------------------------------------------------ */ body #form .navbar-toggle:focus-visible, body #form .dropdown-toggle:focus-visible, body #form .btn:focus-visible, body #form .btn-primary:focus-visible, body #form .form-control:focus-visible, body #form .header-menu: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.13 AAA (Focus Appearance) — PME-507688 rework (Will Sharp, manual scan 2026-08-24): the shared blue+white ring above doesn't reliably clear 3:1 against every property's footer background (footers commonly run darker/branded compared to the form fields and buttons this shared rule also covers). Override just the footer link ring with a white+black double ring — one leg always clears 3:1 against any single backdrop, the same treatment already used for the Floor Plans V4 focus rings. Scoped narrowly to `.footer-widget footer a` so the inputs/selects/tabindex/role=button elements above, which were not flagged, keep their existing ring. */ body #form .footer-widget footer a:focus-visible { box-shadow: 0 0 0 2px #fff, 0 0 0 4px #000 !important; } /* ------------------------------------------------------------ WCAG 2.4.11 Focus Not Obscured .header-menu is position:fixed. Default 80px scroll-padding; adjust after measuring on the live site. ------------------------------------------------------------ */ html { scroll-padding-top: 80px; } body #form :focus-visible { scroll-margin-top: 80px; } /* ------------------------------------------------------------ WCAG 1.4.11 Non-text Contrast (form controls) Two confirmed failures from base CSS. ------------------------------------------------------------ */ body #form .neighborhood-widget .neighborhood-widget__search .form-group .form-control { border-color: #595959; } body #form #contactUsEnhancedContainer .form-control { border-bottom: 1px solid #595959 !important; } body #form input.form-control, body #form select.form-control, body #form textarea.form-control { border-color: #595959; } body #form input::placeholder, body #form textarea::placeholder { color: #595959; opacity: 1; } /* ------------------------------------------------------------ WCAG 1.4.3 Contrast Minimum (footer disclosure) ------------------------------------------------------------ */ body #form .footer-widget footer .footer-disclosure { opacity: 0.85; } /* ------------------------------------------------------------ WCAG 1.4.1 Use of Color (inline links) ------------------------------------------------------------ */ body #form .main-content-text a, body #form .inner-page-main-content a, body #form .mainContent a, body #form main p a, body #form article p a, body #form .content p a { text-decoration: underline; text-underline-offset: 2px; } body #form .btn, body #form .button, body #form header a, body #form nav a, body #form .navbar a, body #form footer a, body #form .footer-widget footer a, body #form .footer-CTA-Button, body #form .header-CTA-button, body #form a.more-link, body #form a.less-link { text-decoration: none; } /* ------------------------------------------------------------ TFS 2870264 — WCAG 1.4.1 (homepage inline links) Haute's homepage is `
` containing `.content-home .content-row` and a series of `.home-main-content-wrapper` rows. Each row's text content lives in `.home-content-sub-content` and `.home-column`. The hero/welcome blurb sits in `.content-right.home-column` and `.content-left.home-column`. Background captions use `.bg-caption`. Homepage CTA buttons use `.button.cta1` / `.button.cta2` — opted out. ------------------------------------------------------------ */ body #form #home .content-home a, body #form #home .home-main-content-wrapper a, body #form #home .home-content-sub-content a, body #form #home .home-column a, body #form #home .bg-caption a { text-decoration: underline; text-underline-offset: 2px; } body #form #home a.button, body #form #home a.cta1, body #form #home a.cta2, body #form #home .button.cta1, body #form #home .button.cta2, body #form #home .header-ctas a, body #form #home .homeNav a { text-decoration: none; } /** ------------------------------------------------------------ WCAG 2.2 AA 2.5.8 Target Size (Pointer) ------------------------------------------------------------ */ body #form header .header-social a { width: 24px; line-height: 24px; margin: 0 5px; } /* 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; } /* TFS 2987209 — WCAG 2.2 AAA 2.5.5 Target Size (Enhanced): expand the consent checkbox's pointer hit-area to 44×44 without changing anything visually (Option B, plan §4.4/§0.5 J — live-prototyped pixel-identical to today). The painted box stays 24×24 (position:relative already set above); this adds a transparent ::before centred over the box that only widens the clickable/tappable region. Do not touch :checked::after or :focus-visible above, and do not remove min-width/min-height:24px on the box rule above — on ContactUsFloating templates that min-width is the only reason the box is 24px wide at all (rpWebpartCss_ContactUsFloating.css sets width:auto !important, §0.4 D). Uses symmetric inset offsets, not left/top:50%+transform: live click-testing found percentage-based centering lands ~1-2px off-centre (asymmetric vs. the border-box), which stole clicks from an adjacent control (Submit button / privacy-policy link) on 3 of 16 templates — insets centre reliably regardless of border width. FIX (TFS 2987209, fleet rescan 2026-08): the checkbox rule above renders box-sizing:border-box (confirmed live via computed style on all 8 templates carrying this exact block), so the CSS containing block for this ::before (the padding box) is only 24px - 2*2px border = 20x20, not 24x24. The original -12px inset was sized against the 24x24 assumption, so it actually produced a 20+2*12=44x44 overlay - exactly at the SC 2.5.5 floor with zero cushion, which is why it measured as a genuine misclick onto the adjacent privacy-policy link on Ascension/Aurora/Bliss (live elementFromPoint hit-test, 2026-08-19) and as a 1-6px shortfall elsewhere once combined with per-template line-height jitter. Bumping each inset by 2px (one border-width) restores the intended 48x48 cushion (20 + 2*14) regardless of box-sizing - re-verified live: elementFromPoint at every point in the overlay, including the corner nearest the link, now resolves to the checkbox with no measured encroachment onto the link/label. */ body .contact-mobile-form input[type="checkbox"]::before, #contactusPrivacy input[type="checkbox"]::before, #privacyDiv input[type="checkbox"]::before, #contactUsV1Privacy input[type="checkbox"]::before { content: ""; position: absolute; top: -14px; left: -14px; right: -14px; bottom: -14px; } /* ------------------------------------------------------------ TFS 2987209 — WCAG 2.2 AAA 2.5.5 Target Size (Enhanced) S0088-Haute / Ascend footer (plan §4.3b, Family 1b). This template renders