/* ============================================================
wcag-s0080-copper-creek.css
WCAG 2.1 Level AA override for the S0080-Copper-Creek Kentico template.
Selectors verified against the live base CSS pulled from
https://madisononmelrose.com on 2026-05-07.
Audit findings:
- Base CSS (~27KB / 218 rules) has NO outline-suppression rules
of its own. Bootstrap still suppresses .navbar-toggle /
.dropdown-toggle / .form-control:focus etc.
- No fixed/sticky header found in this template's own CSS
(likely uses a sticky from a shared component).
- No form-control border rules in template CSS — generic input
defaults apply. Verify on a live form during deploy testing.
- Footer link color #42727f on white passes 4.5:1 (~5.3:1).
- Shared footer.min.css applies (footer-disclosure opacity:.6
fix carries over).
Specificity strategy:
Every selector is prefixed with `body #form` to lift above
widget CSS load order.
============================================================ */
/* ------------------------------------------------------------
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 .form-control: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
Sticky header height not confirmed in template CSS — 80px is
a safe default. Measure on the live site and adjust.
------------------------------------------------------------ */
html {
scroll-padding-top: 80px;
}
body #form :focus-visible {
scroll-margin-top: 80px;
}
/* ------------------------------------------------------------
WCAG 1.4.11 Non-text Contrast (form controls)
No template-specific form border rules audited. Defensive
override on generic form inputs in case any falls below 3:1.
Refine against live form CSS during deploy testing.
------------------------------------------------------------ */
body #form input.form-control,
body #form select.form-control,
body #form textarea.form-control,
body #form input[type="text"],
body #form input[type="email"],
body #form input[type="tel"],
body #form input[type="search"],
body #form input[type="number"],
body #form input[type="password"],
body #form select,
body #form textarea {
border-color: #595959;
}
/* ------------------------------------------------------------
WCAG 1.4.3 Contrast Minimum (footer disclosure)
Shared footer.min.css: .footer-widget footer .footer-disclosure
{ opacity:.6 } — bump to 0.85.
------------------------------------------------------------ */
body #form .footer-widget footer .footer-disclosure {
opacity: 0.85;
}
/* ------------------------------------------------------------
WCAG 1.4.1 Use of Color (inline links)
Defensive underline rule on common Kentico content-zone
patterns. Update with the actual content selector after
inspecting the live DOM (look for .mainContent, .content,
.main-content-text, etc.).
------------------------------------------------------------ */
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,
body #form #contactusPrivacy a,
body #form a[href$="Privacy-policy.aspx"] {
text-decoration: underline;
text-underline-offset: 2px;
}
body #form .btn,
body #form .button,
body #form .footer-btn,
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)
Copper Creek's homepage welcome blurb lives in
`#homeWelcomeSection .homeWelcomeContainer .homeWelcome
.homeWelcomeText`. The CTA grid below it is
`.homeCTAContainer > a.homeCtaItem` — every `.homeCtaItem` is
itself a CTA link (not inline content), so opted out.
------------------------------------------------------------ */
body #form #homeWelcomeSection .homeWelcomeText a,
body #form .homeWelcomeContainer .homeWelcomeText a,
body #form .homeWelcome .homeWelcomeText a {
text-decoration: underline;
text-underline-offset: 2px;
}
body #form a.homeCtaItem,
body #form .homeCtaItem,
body #form .homeCTAContainer a {
text-decoration: none;
}
/* ------------------------------------------------------------
WCAG 2.2 AA 2.5.8 Target Size (Pointer)
------------------------------------------------------------ */
/* 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. */
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: -12px; left: -12px; right: -12px; bottom: -12px;
}
#contactusPrivacy label {
line-height: 40px;
}
/* WCAG 2.1 AA 1.4.10 Reflow
.header-widget header in header.css uses width:100% on a position:fixed
element — sub-pixel rounding overflows by 1px on certain viewports. */
body #form header.header-1 {
width: calc(100% - 1px);
}
/* ------------------------------------------------------------
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 coppercreekqanew.sat-ws.realpage.com/Contact.aspx at 1280x900
(headless Chrome, border-box heights): 2 footer target(s) under 24x24.
footer .footer-property-logo a 226.7 x 16, display:inline, wraps an ![]()
footer .footer-phone-content a.footer-phone 126.3 x 19, display:inline
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, document height +0px, no horizontal overflow.
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.
------------------------------------------------------------ */
/* TFS 2987209 — WCAG 2.2 AAA 2.5.5 Target Size (Enhanced): supersedes the
two 24px (#2982346, AA) rules immediately below in place with 44px, per
plan §3.3 (44 replaces 24 on the same selector — one stanza, not two
layered ones). */
footer .footer-property-logo a {
display: inline-block;
min-height: 44px;
}
footer .footer-phone-content a.footer-phone {
display: inline-block;
min-height: 44px;
}
/* ------------------------------------------------------------
TFS 2987209 — WCAG 2.2 AAA 2.5.5 Target Size (Enhanced): header —
authored from scratch, 2026-08-20. This template never received a
header/footer/CTA/social stanza on this ticket (prod completeness
sweep: 30 sub-44 targets on the homepage alone — header phone/CTAs at
24px among them).
RPcssMaster_S0080-Copper-Creek.css carries FIVE header-1 rules
(background, sticky variant, content padding, `.header-links a` font
styling, menu-toggle) vs. ONE incidental header-6 rule (a shared
menu-toggle color, likely leftover/shared boilerplate, not evidence
this site config uses header-6) — header-1 is this template's actual
configured variant. header-1's markup (Header.ascx) puts BOTH the
phone number and both CTA links inside a single `