/* Homepage wireframe additions (Website Layout Version 1) */

/* Anchor-scroll offset: the fixed header (~90px once scrolled) otherwise
   covers the top of whatever section a nav link jumps to. */
section[id] {
  scroll-margin-top: 100px;
}

.icon-circle {
  width: 70px;
  height: 70px;
  border-radius: 50%;
  display: flex;
  align-items: center;
  justify-content: center;
  background-color: var(--primary-color);
  flex-shrink: 0;
}

.icon-circle i {
  color: var(--secondary-color);
  font-size: 26px;
}

.icon-circle.sm {
  width: 52px;
  height: 52px;
}

.icon-circle.sm i {
  font-size: 20px;
}

.hover-card {
  transition: transform 0.3s ease, box-shadow 0.3s ease;
}

.hover-card:hover {
  transform: translateY(-6px);
  box-shadow: 0 20px 40px rgba(25, 25, 25, 0.12);
}

/* How It Works - connected step flow */
.steps-flow {
  position: relative;
  display: flex;
  flex-wrap: wrap;
  gap: 28px 20px;
  list-style: none;
  margin: 0;
  padding: 0;
}

.steps-flow::before {
  content: "";
  position: absolute;
  top: 32px;
  left: 10%;
  right: 10%;
  height: 2px;
  background-color: var(--primary-color);
  opacity: 0.25;
  z-index: 0;
}

.step-item {
  position: relative;
  z-index: 1;
  flex: 1 1 180px;
  text-align: center;
  background-color: #fff;
  border-radius: 10px;
  box-shadow: 0 4px 24px rgba(25, 25, 25, 0.07);
  padding: 32px 20px 28px;
  transition: transform 0.3s ease, box-shadow 0.3s ease;
}

.step-item:hover {
  transform: translateY(-6px);
  box-shadow: 0 20px 40px rgba(25, 25, 25, 0.12);
}

.step-icon-wrap {
  position: relative;
  width: 64px;
  height: 64px;
  margin: 0 auto 20px;
}

.step-icon-circle {
  width: 100%;
  height: 100%;
  border-radius: 50%;
  background-color: var(--primary-color);
  display: flex;
  align-items: center;
  justify-content: center;
}

.step-icon-circle i {
  color: var(--secondary-color);
  font-size: 24px;
}

.step-number-badge {
  position: absolute;
  top: -4px;
  right: -4px;
  width: 26px;
  height: 26px;
  border-radius: 50%;
  background-color: var(--secondary-color);
  color: #fff;
  font-size: 12px;
  font-weight: 700;
  display: flex;
  align-items: center;
  justify-content: center;
  border: 2px solid #fff;
}

.step-title {
  margin-bottom: 8px;
}

.step-desc {
  margin-bottom: 0;
  color: rgba(25, 25, 25, 0.7);
}

@media (max-width: 1199.98px) {
  .steps-flow {
    flex-direction: column;
  }

  .steps-flow::before {
    display: none;
  }

  .step-item {
    flex: 1 1 auto;
  }
}

/* Buttons: vendor default is white text on vibrant orange (2.35:1, fails AA)
   -- keep the requested vibrant orange fill but swap to dark text instead of
   darkening the fill. Restore white text on hover/active/focus, since the
   vendor's hover state expands a dark circle behind the button, and dark
   text would otherwise disappear against it. */
.btn-style01:not(.white):not(.secondary) {
  background-color: var(--primary-color);
  color: var(--secondary-color) !important;
}

.btn-style01:not(.white):not(.secondary):hover,
.btn-style01:not(.white):not(.secondary):active,
.btn-style01:not(.white):not(.secondary):focus {
  color: #fff !important;
}

/* Client has prohibited any darkened/muted orange variant and has already
   accepted this version of the site -- these are now plain --primary-color,
   full stop, matching exactly what was asked for and nothing more. Note:
   this reintroduces a real WCAG AA contrast shortfall (vibrant orange text/
   glyphs directly on white measure ~2.35:1, below the 4.5:1/3:1 minimums)
   -- a known, client-directed tradeoff, not an oversight. */
#problem h2 .text-primary,
#outcomes h2 .text-primary,
#how-it-works h2 .text-primary,
#why-tl h2 .text-primary,
#outcomes .list-style01 li::before,
#why-tl .list-style01 li::before {
  color: var(--primary-color);
}

.accordion-style .btn-link .text-primary {
  color: var(--primary-color) !important;
}

/* Brand-color correction: css/plugins/default.css hardcodes the vendored
   template's original near-black (#191919) for all headings, independent of
   the --secondary-color variable, so every h1-h6 never picked up the navy
   rebrand. Override here rather than editing the vendored plugin file. */
h1, h2, h3, h4, h5, h6,
.h1, .h2, .h3, .h4, .h5, .h6,
h1 a, h2 a, h3 a, h4 a, h5 a, h6 a,
.h1 a, .h2 a, .h3 a, .h4 a, .h5 a, .h6 a {
  color: var(--secondary-color);
}

/* Same bug, scoped to the nav link color used ONLY after the header goes
   solid-white on scroll (css/plugins/nav-menu.css sets a white header
   background there, so dark text is correct -- unlike the transparent,
   over-photo header state at the top of the page, which is intentionally
   white text and must NOT be touched here, or it becomes unreadable). */
.header-style1.scrollHeader .navbar-nav > li > a,
.header-style1.scrollHeader .attr-nav > ul > li > a,
.menu_area-light.scrollHeader .navbar-nav > li > a {
  color: var(--secondary-color);
}

/* Keyboard access: mirror the existing :hover dropdown reveal for :focus-within,
   so tabbing into a submenu link shows the menu instead of leaving it rendered
   off-screen (css/plugins/nav-menu.css positions it at left:-9999px by default). */
.navbar-nav li:focus-within > ul {
  left: auto;
}

.navbar-nav > li.has-sub:focus-within > ul {
  margin-top: 0;
  opacity: 1;
}

/* Visible keyboard focus. css/plugins/default.css blanket-suppresses the native
   outline on every link/button/.btn with no replacement (a common old fix for
   "focus rings on mouse click" that :focus-visible makes unnecessary -- it only
   matches keyboard/programmatic focus, never a mouse click). Double-ring so it
   reads on both light and dark/photo sections. */
a:focus-visible,
button:focus-visible,
.btn:focus-visible,
.btn-style01:focus-visible,
input:focus-visible,
textarea:focus-visible,
[tabindex]:focus-visible {
  outline: 2px solid #fff;
  outline-offset: 2px;
  box-shadow: 0 0 0 4px var(--secondary-color);
  border-radius: 2px;
}

/* Native button reset for controls converted from <div>/<span> to <button> for
   keyboard operability, so they keep the theme's existing visual appearance. */
button.navbar-toggler,
button.input-group-addon,
button.scroll-top-percentage {
  border: 0;
  appearance: none;
  -webkit-appearance: none;
  cursor: pointer;
}

/* Skip-to-content link: visually hidden until it receives keyboard focus. */
.skip-link {
  position: absolute;
  top: 0;
  left: 0;
  transform: translateY(-120%);
  z-index: 100000;
  background-color: var(--secondary-color);
  color: #fff;
  padding: 12px 24px;
  border-radius: 0 0 6px 0;
  font-weight: 600;
  transition: transform 0.2s ease;
}

.skip-link:focus-visible {
  transform: translateY(0);
}

/* About page intro: about-08.jpg (259x450 native) and about-housing.jpg
   (a landscape aerial photo) sit in two equal-width columns and are expected
   to render at matching sizes. Neither <img> has width:100% by default, so
   each one caps at its own natural pixel size regardless of column width --
   at any viewport wider than ~259px per column, about-housing.jpg (with this
   class) stretches to fill the column while about-08.jpg (without it) stayed
   pinned small, producing a visibly mismatched pair. Apply this class to both
   images so they scale together at every breakpoint; about-08.jpg is already
   259:450 natively, so object-fit:cover never crops it. */
.about-photo-portrait {
  width: 100%;
  aspect-ratio: 259 / 450;
  object-fit: cover;
}

/* Honeypot spam trap (contact.html): off-screen rather than display:none/
   visibility:hidden, since bots increasingly check for and skip those. */
.quform-honeypot {
  position: absolute;
  left: -9999px;
  top: -9999px;
}

/* Contact page: photo fills the stretched row height next to the form. */
.contact-photo {
  width: 100%;
  height: 100%;
  min-height: 320px;
  object-fit: cover;
}

/* Footer divider: the original template's border-bottom sat on a row inside
   .container, so it stopped short of the section's own full-bleed background
   on both sides instead of reading as a real divider. Break it out to span
   the full viewport width instead. */
footer {
  overflow-x: hidden;
}

.footer-divider {
  position: relative;
}

.footer-divider::after {
  content: "";
  position: absolute;
  left: 50%;
  right: 50%;
  bottom: 0;
  width: 100vw;
  margin-left: -50vw;
  margin-right: -50vw;
  border-bottom: 1px solid rgba(255, 255, 255, 0.1);
}

/* Quform success/error messages: the vendor default is a raster checkmark/X
   icon on a stock neon-green/pink background (quform/images/success.png,
   error.png) -- off-brand, and both real usages of this form (contact.html,
   search.html's newsletter widget) sit on the dark --secondary-color form
   background, so a plain white card reads as a foreign popup rather than
   part of the form. Use a subtle tinted-dark treatment instead: a soft
   accent-colored wash over the form's own dark background, a left accent
   border, and Font Awesome icons (already loaded site-wide) instead of a
   raster image. */
.quform-success-message,
.quform-outer-no-js .quform-success-message {
  background: rgba(224, 155, 64, 0.12);
  background-image: none;
  border: none;
  border-left: 3px solid var(--primary-color);
  border-radius: 4px;
  color: #fff;
  padding: 12px 16px 12px 42px;
  position: relative;
}

.quform-success-message::before {
  content: "\f00c";
  font-family: "Font Awesome 6 Free";
  font-weight: 900;
  color: var(--primary-color);
  position: absolute;
  left: 16px;
  top: 50%;
  transform: translateY(-50%);
}

/* Top-of-form "There was a problem" summary box (Quform's
   .quform-error-message, built by quform/js/plugins.js' self.errorMessage()
   for AJAX/server-level failures) -- sits on the dark form background like
   .quform-success-message above, so the same translucent-wash treatment
   applies here. */
.quform-error-message,
.quform-outer-no-js .quform-error-message {
  background: rgba(217, 83, 79, 0.15);
  background-image: none;
  border: none;
  border-left: 3px solid #d9534f;
  border-radius: 4px;
  color: #fff;
  padding: 12px 16px 12px 42px;
  position: relative;
}

.quform-error-message::before {
  content: "\f06a";
  font-family: "Font Awesome 6 Free";
  font-weight: 900;
  color: #ff8a84;
  position: absolute;
  left: 16px;
  top: 50%;
  transform: translateY(-50%);
}

.quform-error-title {
  color: #ff8a84;
}

/* Per-field "this field is required" badges (Quform's .quform-error --
   plugins.js absolutely-positions these over the top-right corner of each
   invalid input via .quform-errors-wrap in base.css). Unlike the summary
   box above, these render on top of the white input fields rather than the
   dark form background, so they must stay opaque -- the translucent
   treatment washed them out to near-illegible white-on-white. */
.quform-errors > .quform-error,
.quform-outer-no-js .quform-error {
  background: #d9534f;
  background-image: none;
  border: none;
  border-radius: 4px;
  color: #fff;
  padding: 6px 12px 6px 32px;
  position: relative;
}

.quform-errors > .quform-error::before,
.quform-outer-no-js .quform-error::before {
  content: "\f06a";
  font-family: "Font Awesome 6 Free";
  font-weight: 900;
  color: #fff;
  position: absolute;
  left: 10px;
  top: 50%;
  transform: translateY(-50%);
}