/* Common Accounting — late overrides (legibility pass, colour rules).
   These intentionally come LAST. Load AFTER page-specific CSS. */

/* Moved here from core-base.css: page-specific CSS re-declares .about-grid
   unconditionally (no media query), and since it loads after core-base.css,
   it always won at equal specificity, silently cancelling this collapse.
   Living here, after page-specific CSS, guarantees it always wins instead. */
@media(max-width:900px){.about-grid{grid-template-columns:1fr;gap:36px}}

/* Moved here from core-base.css: src/_css/canadian-tax-tips-blog.css redeclares
   .feature unconditionally (no media query), and since page CSS loads after
   core-base.css, it always won at equal specificity, silently cancelling this
   collapse. Living here, after page-specific CSS, guarantees it always wins. */
@media(max-width:820px){.feature{grid-template-columns:1fr}.feature .thumb{min-height:200px}
  .feature .body{padding:24px}.feature h3{font-size:1.35rem}}

/* Moved here from core-base.css: src/_css/canadian-tax-tips-blog.css redeclares
   .postgrid unconditionally (no media query), and since page CSS loads after
   core-base.css, it always won at equal specificity, silently cancelling this
   collapse. Living here, after page-specific CSS, guarantees it always wins. */
@media(max-width:960px){.postgrid{grid-template-columns:1fr 1fr}}
@media(max-width:640px){.postgrid{grid-template-columns:1fr}}

/* Moved here from core-base.css: src/_css/index.css redeclares .steps
   unconditionally (no media query), and since page CSS loads after
   core-base.css, it always won at equal specificity, silently cancelling this
   collapse. Living here, after page-specific CSS, guarantees it always wins. */
@media(max-width:820px){.steps{grid-template-columns:1fr 1fr;gap:26px 0}
  .step:nth-child(3){padding-left:0;border-left:0}}
@media(max-width:520px){.steps{grid-template-columns:1fr;gap:22px}
  .step{padding-left:0;border-left:0}}

/* Moved here from core-base.css: same cascade-collision as above, on the
   tablet-range rule (was inside @media(min-width:641px) and
   (max-width:1000px){...} alongside .wrap/.section/.hero/.stats-strip,
   which is why it was missed when the <=820px/<=520px .steps rules were
   moved). src/_css/index.css's unconditional .steps rule cancelled this
   one too, so .steps stayed at 4 columns for 821-1000px widths. */
@media(min-width:641px) and (max-width:1000px){
  .steps{grid-template-columns:1fr 1fr;gap:30px 0}
}

/* Moved here from core-base.css: src/_css/tools.css redeclares .tool-grid
   unconditionally (no media query), and since page CSS loads after
   core-base.css, it always won at equal specificity, silently cancelling this
   collapse. Living here, after page-specific CSS, guarantees it always wins. */
@media(max-width:820px){.tool-grid{grid-template-columns:1fr}}

/* Moved here from core-base.css: 11 of 22 page CSS files redeclare
   .logo .mark unconditionally (no media query), and since page CSS loads
   after core-base.css, it always won at equal specificity, silently
   cancelling this collapse. Living here, after page-specific CSS,
   guarantees it always wins. */
@media (max-width:900px){
  .logo .mark,.logo .mark img{height:28px}
}

/* Moved here from core-base.css: every page CSS file redeclares
   .navlinks a unconditionally (no media query), and since page CSS loads
   after core-base.css, it always won at equal specificity, silently
   cancelling both the <=1040px mobile-panel sizing and the sitewide
   font-weight:600 the original applies to nav links and dropdown
   buttons. Living here, after page-specific CSS, guarantees both win.
   Desktop values (base rule, core-base.css:94/98) are untouched. */
.navlinks a,.dd>button{font-weight:600}
@media(max-width:1040px){
  .navlinks a,.dd>button{font-size:1rem;padding:12px 14px}
}

/* Moved here from core-base.css: src/_css/index.css has an unconditional
   .hero .wrap{grid-template-columns:1.05fr .95fr;...}, and since page CSS
   loads after core-base.css, it always won at equal specificity, silently
   cancelling the <=900px collapse to a single column. That squeezed the
   hero portrait image into a ~48px-wide second grid column instead of
   letting it fill the row. Living here, after page-specific CSS,
   guarantees the collapse wins. */
@media(max-width:900px){
  .hero .wrap{grid-template-columns:1fr;gap:40px}.hero{padding:38px 0 26px}.portrait{order:-1}
}

/* Moved here from core-base.css: src/_css/index.css has an unconditional
   .portrait{width:min(100%,400px)}, and since page CSS loads after
   core-base.css, it always won at equal specificity, silently cancelling
   the <=900px cap of min(100%,340px). Living here, after page-specific
   CSS, guarantees the narrower mobile cap wins. */
@media(max-width:900px){
  .portrait{width:min(100%,340px)}
}

/* Moved here from core-base.css: 11 page CSS files redeclare .navlinks a
   unconditionally, and since .dd-menu is nested inside .navlinks, that
   descendant selector also matches .dd-menu a at equal specificity. Page
   CSS loading after core-base.css meant it always won, silently
   overwriting the dropdown item's own radius/padding. Living here, after
   page-specific CSS, guarantees .dd-menu a wins again. */
.dd-menu a{display:block;padding:9px 12px;border-radius:9px;font-size:.97rem;opacity:1;
  color:var(--ink);text-decoration:none}
.dd-menu a:hover{background:var(--royal-soft)}
.dd-menu a small{display:block;color:var(--muted);font-size:.95rem;font-weight:400}

/* Moved here from core-base.css: after the .dd-menu a base rule above was
   moved into this file, the <=1040px mobile-panel padding override for
   .dd-menu a (previously in core-base.css) started loading before it
   instead of after, so it stopped winning at <=1040px. Living here, after
   the base rule, guarantees the mobile padding wins again. */
@media(max-width:1040px){
  .dd-menu a{padding:11px 14px}
}

/* Moved here from core-base.css: src/_css/index.css and 5 other page CSS
   files redeclare .hero, .stats-strip .wrap, .stat .n, .hero h1 and
   .post .body unconditionally, and since page CSS loads after
   core-base.css, those always won at equal specificity, silently
   cancelling the 640px stat-grid collapse, the 641-1000px tablet padding
   for .hero/.stats-strip .wrap/.stat .n, the >=1600px large-desktop
   .hero h1 size, and the <=380px .post .body padding. Living here, after
   page-specific CSS, guarantees all five win again. */
@media(max-width:640px){.stats-strip .wrap{grid-template-columns:1fr 1fr;gap:18px 0}}
@media(min-width:641px) and (max-width:1000px){
  .hero{padding:36px 0 24px}
  .stats-strip .wrap{padding:22px}
  .stat .n{font-size:1.65rem}
}
@media(max-width:380px){
  .post .body{padding:18px}
}
@media(min-width:1600px){
  .hero h1{font-size:4rem}
}

/* Any remaining mid-tone used for text on a light surface. The rule from the
   client is absolute: on white, text is black. */
.form,.dot,.sigrole,.stat .l,.microtrust span,.points .tx span,
.svc-sub,.rl,.since,.step p,.faq p,.sec-head p,.go,.plogos .lab,
.partners .lab,.result-card .lbl,#tool-t4 .field label,#tool-t4 .checkbox-row,
.pcalc-row .desc,.pcalc-sec,.pcalc-qty label,.bring-col li,.cats span{
  color:#000000}
/* ---- no grey body text ----
   Rule from the client: text on a light background is near-black, never grey.
   --muted keeps its name so every existing rule picks this up, but it is no
   longer a mid-tone. Light text survives only on the navy footer, where the
   background is dark and light text is the legible choice.
   Contrast on white: 16.1:1, well past WCAG AAA. */
:root{
  --muted:#000000;
  /* --ink deliberately NOT overridden: .topbar, footer.site and the CTA band
     gradient all use it as a background-color. Forcing it black turned those
     navy surfaces black. Text colour is handled by explicit rules below. */
}
/* the greys introduced earlier in this build, all pulled to the same near-black */
.lede,.sec-text,.hint,.note,.casl-note,.price-note,.pcalc-foot,
.svc-seo p,.legal-doc p,.legal-doc li,.prose p,.prose li,
.persona p,.scard p,.pg-step p,.price-card p,.bring-col li,.col-block li,
.plogos .efile-txt span,#tool-t4 .disclaimer,.legal-meta,.updated,
figcaption,.prose .post-fig figcaption,.result-card .lbl,
table.cmp td,.prose table.cmp td,.pmeta,.svc-why li{
  color:#000}
/* ---- legibility pass ----
   Body copy reads heavier and looser than the original design; small print in
   particular was the specific complaint. */
body{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale;
  font-family:"Inter",system-ui,-apple-system,"Segoe UI",sans-serif}
/* Inter replaces Hanken Grotesk for body text. Measured x-height is 54.6% of
   the em against Hanken's 49.3%, so lowercase letters are about 11% physically
   larger at the same font-size. That is what "the font looks small" meant.
   Sept 2026: headings, logo and display numerals all moved to Inter as well —
   the old display serif read as too informal for a tax practice. Weights were
   raised 100 wherever it was replaced, because Inter's stems are lighter at
   the same numeric weight. Inter is now the only typeface in the project. */
.logo,.sig,.big,.amt,.val,.pcalc-head,.pcalc-total .sum,
.result-card .val,table.cmp thead th,.efile-txt b{
  font-family:"Inter",system-ui,sans-serif}
input,select,textarea,button{font-family:"Inter",system-ui,sans-serif}
/* muted body text: slightly heavier and looser, which does more for perceived
   size than raising the size alone */
p,li,dd,figcaption,label,small,.note,.sec-text,.hint{
  font-variation-settings:"wght" 450;
  line-height:1.68}
.lede{font-size:1.18rem;line-height:1.62;color:#000}
/* the smallest labels keep their size but gain weight and tracking so they
   stay legible rather than becoming decorative */
.eyebrow,.pmeta,.casl-note,.legal-meta,.updated{
  font-variation-settings:"wght" 600}
/* cards and list copy */
.persona p,.scard p,.bring-col li,.col-block li,.pg-step p,.price-card p,
.svc-why li,.svc-seo p,.prose p,.prose li,.legal-doc p,.legal-doc li{
  line-height:1.7}
/* footer sits on navy, where light text needs more contrast, not less */
footer.site,footer.site p,footer.site a,footer.site li{color:#D6DEF5}
footer.site .nap,footer.site small,footer.site .casl-note{color:#C3CFEC}
/* ---- story-section portrait ----
   The circular override was added when the hero used a pre-cropped circular
   headshot. On a standing portrait it reads as a mistake: a square photo
   floating on a circle that belongs to nothing. This restores the treatment
   used in the hero, which is the one that works: rounded frame, offset accent
   border, real shadow. */
.aside-photo{aspect-ratio:auto!important;border-radius:0!important;background:none!important;
  position:relative;width:min(100%,420px)}
.aside-photo .frame{aspect-ratio:4/5!important;border-radius:20px!important;
  overflow:hidden;background:var(--paper);box-shadow:var(--shadow);position:relative;z-index:2}
.aside-photo .frame img{width:100%;height:100%;object-fit:cover;object-position:center 12%;display:block}
.aside-photo::after{content:"";position:absolute;
  inset:20px -20px -20px 20px;border:2px solid var(--royal);border-radius:20px;
  z-index:1;pointer-events:none}
@media (max-width:900px){
  .aside-photo{width:min(100%,340px);margin:0 auto}
  .aside-photo::after{inset:12px -12px -12px 12px}
}
/* ---- blog card thumbnails ----
   The photo sits on top of a branded plate. If the file is missing the plate
   shows the mark instead of an empty navy rectangle, so a missing asset reads
   as deliberate rather than broken. */
.thumb{
  background-image:url("/icons/mark-white-96.webp"),
    linear-gradient(150deg,#26377f,#141f52);
  background-repeat:no-repeat,no-repeat;
  background-position:center center,center center;
  background-size:82px auto,cover}
.thumb img{position:relative;z-index:1}
/* ---- the rule: no grey text on light backgrounds ----
   A blanket declaration, so any rule added later inherits black rather than
   needing to be found and patched. The dark bands are excepted immediately
   below, because light text on navy is the legible choice there. */
body,p,li,dd,dt,td,th,span,small,label,figcaption,summary,blockquote,
.note,.hint,.sec-text,.lede,.pmeta,.casl-note,.legal-meta,.updated,
.persona p,.scard p,.bring-col li,.col-block li,.pg-step p,.price-card p,
.prose p,.prose li,.legal-doc p,.legal-doc li,.svc-seo p,.svc-why li,
.result-card .lbl,#tool-t4 .field label,#tool-t4 .checkbox-row,
#tool-t4 .exempt-note,.plogos .efile-txt span{color:#000}
/* ---- dark surfaces ----
   These backgrounds are navy, so their text is light. Stated explicitly and
   last, so the blanket black rule above cannot reach inside them. */
.topbar{background:var(--ink)}
footer.site{background:var(--ink)}
.topbar,.topbar *,.topbar a,.topbar span,.topbar small{color:#FFFFFF!important}
.topbar .stars,.topbar span[style*="--gold"]{color:#FFC844!important}
footer.site,footer.site *{color:#EEF2FE!important}
footer.site h3,footer.site h4,footer.site strong,footer.site b,
footer.site .logo{color:#FFFFFF!important}
footer.site input,footer.site input::placeholder{color:#1a1a1a!important}
footer.site button.primary{color:#FFFFFF!important}
footer.site a:hover{color:#FFFFFF;text-decoration:underline}
footer.site .efile{color:#EEF2FE;background:rgba(255,255,255,.10);
  border-color:rgba(255,255,255,.22)}
.band,.band *{color:#FFFFFF!important}
/* .artcta is the dark CTA panel at the foot of each blog post. It was missing
   from this list, so the blanket "text on light is black" rule above caught its
   paragraph and rendered it near-black on navy — the same failure mode as the
   .band gradient. Declared here, last, so nothing can reach inside it. */
.artcta,.artcta *,.cta-panel,.cta-panel *{color:#EEF2FE!important}
.artcta h3,.artcta h4,.artcta strong,.artcta b,
.cta-panel h3,.cta-panel h4,.cta-panel strong,.cta-panel b{color:#FFFFFF!important}
.artcta .btn-primary,.artcta .btn-primary *,
.cta-panel .btn-primary,.cta-panel .btn-primary *{color:#FFFFFF!important}
.artcta .btn-ghost,.artcta .btn-ghost *,
.cta-panel .btn-ghost,.cta-panel .btn-ghost *{color:#FFFFFF!important;border-color:rgba(255,255,255,.5)!important}
.band .btn-ghost{color:#FFFFFF!important;border-color:rgba(255,255,255,.5)!important}
.pcalc-head,.pcalc-total,.pcalc-total *{color:#FFFFFF!important}
.thumb,.thumb *{color:#FFFFFF!important}
.sidecard.dark,.sidecard.dark *{color:#EEF2FE!important}
/* ---- sticky mobile action bar ----
   This sits on a near-white background, so its text must be dark. It was
   previously grouped with the dark surfaces (.band, footer, calculator header)
   and inherited white-on-white, which made the "Call" button unreadable. */
.mobar{background:rgba(255,255,255,.97)!important;
  border-top:1px solid var(--line);box-shadow:0 -6px 20px rgba(14,26,60,.10)}
.mobar,.mobar *{color:#000000!important}
.mobar .btn-primary{background-color:#2C4BE0!important;border-color:#2C4BE0!important}
.mobar .btn-primary,.mobar .btn-primary *{color:#FFFFFF!important}
.mobar .btn-ghost{background-color:#FFFFFF!important;border:1.5px solid #1B2A6B!important}
.mobar .btn-ghost,.mobar .btn-ghost *{color:#000000!important;font-weight:700}
/* form helper text was the least readable thing on the site */
.hint,.pcalc-foot,#tool-t4 .disclaimer,.price-note{font-size:1.1rem;color:#000}
/* Stars and menu icon drawn as SVG rather than text characters: those glyphs are not
   in Inter, so machines without a fallback font rendered them as empty boxes. */
.starsvg{height:.95em;width:auto;display:inline-block;vertical-align:-.1em;fill:currentColor}
/* .topbar * forces #fff !important on descendants, which would catch the SVG. */
.topbar .stars .starsvg{fill:#FFC844}
/* Blog articles ran full-width, 94-126 characters per line at desktop widths.
   Cap the body content (not the surrounding section background) so lines
   stay readable, same 44em cap used for the FAQ answer text. */
.artfull .prose>p,.artfull .prose>h2,.artfull .prose>h3,.artfull .prose>ul,
.artfull .prose>ol,.artfull .prose>blockquote{max-width:44em;margin-left:auto;margin-right:auto}

/* Header wordmark: uppercase, same dark blue as the hero title (all pages) */
nav.bar .logo{color:#1B2A6B;letter-spacing:.02em}

/* Sticky header fix: body overflow-x:hidden (plus html) turned body into a scroll container,
   so position:sticky on nav.bar never stuck. clip hides sideways overflow without that side effect. */
body,body.nav-open{overflow:visible}
html{overflow-x:hidden}
html:has(body.nav-open){overflow:hidden}
html{scroll-padding-top:84px}
nav.bar{box-shadow:0 1px 0 rgba(14,26,60,.08)}

/* Phones: top bar shows just the call line (the bottom action bar already has Call + Book) */
@media(max-width:760px){
  .topbar .rgt{gap:0;flex-wrap:nowrap}
  .topbar .rgt>span{display:none}
  .topbar .wrap{justify-content:center;padding:8px 18px}
}

/* Tablets (761-1000px): show the sticky Call + Book bar here too, centred, not edge-to-edge */
@media(min-width:761px) and (max-width:1000px){
  .mobar{display:flex;justify-content:center}
  .mobar .btn{flex:0 1 320px}
  body{padding-bottom:76px}
}
/* Call / Book bar: centre the label when it wraps to two lines */
.mobar .btn{text-align:center;line-height:1.2}
