/* Finsightic Bangladesh (/bd) - shared stylesheet.
 *
 * The rest of finsightic.com inlines its CSS per page, which suits pages that
 * each look different. This section is one design across seven pages, so
 * inlining would mean seven copies of this file kept in step by hand - and the
 * eighth page would quietly drift. One request, cached after the first page.
 */
:root{
  /* The interactive blue is the US site's action blue, not the logo's.
     The logo's own #1D89E4 puts white text at 3.7:1, under the 4.5:1 floor,
     so buttons set in it fail plain-text contrast; #1C5FCC carries white at
     5.9:1. The mark keeps its lighter blue, as a logo may; the UI does not. */
  --blue:#1C5FCC; --blue-d:#1550B0; --blue-l:#EAEEF8; --blue-xl:#F5F7FC;
  --ink:#0A1F44; --ink-2:#39456E; --grey:#55618C; --line:#DCE3F2;
  --green:#12A06A; --green-l:#E8F7F0;
  --bn:"Hind Siliguri","Noto Sans Bengali","Kalpurush","SolaimanLipi","Nirmala UI",system-ui,sans-serif;
  --en:"Plus Jakarta Sans",system-ui,sans-serif;
}
*{box-sizing:border-box;}
html{scroll-behavior:smooth;scroll-padding-top:120px;}
body{margin:0;background:#fff;color:var(--ink);font-family:var(--bn);font-size:18px;line-height:1.85;-webkit-font-smoothing:antialiased;}
body.lang-en{font-family:var(--en);line-height:1.7;}
img{max-width:100%;display:block;}
a{color:inherit;}
.wrap{max-width:1080px;margin:0 auto;padding:0 20px;}h1,h2,h3,h4,.hsub{margin:0;font-weight:600;line-height:1.4;}
body.lang-en h1,body.lang-en h2{letter-spacing:-.02em;line-height:1.18;}
h1{font-size:clamp(1.95rem,5.2vw,3rem);}
h2{font-size:clamp(1.5rem,3.8vw,2.2rem);}h3,.hsub{font-size:1.14rem;}
p{margin:0;}
section{padding:70px 0;}
.soft{background:var(--blue-xl);}
.sec-top{max-width:660px;margin:0 auto 40px;text-align:center;}
.sec-top p{color:var(--grey);margin-top:12px;font-size:1.02rem;}
/* Matched to the US site's label badge (.lb): small caps-height uppercase
   with wide tracking, quiet padding. Bangla has no case and does not track,
   so Bangla mode keeps natural spacing at a size that reads. */
.kicker{display:inline-block;background:var(--blue-l);color:var(--blue-d);font-size:.75rem;font-weight:700;text-transform:uppercase;letter-spacing:.1em;padding:5px 13px;border-radius:999px;margin-bottom:14px;}
body.lang-bn .kicker{font-size:.86rem;letter-spacing:0;font-weight:600;}
.muted{color:var(--grey);}
.center{text-align:center;}

.btn{display:inline-flex;align-items:center;justify-content:center;gap:9px;font-weight:600;font-size:1rem;padding:15px 24px;border-radius:12px;text-decoration:none;border:1.5px solid transparent;cursor:pointer;transition:.18s;min-height:52px;font-family:inherit;}
.btn:focus-visible{outline:3px solid var(--blue);outline-offset:2px;}
.btn-b{background:var(--blue);color:#fff;}
.btn-b:hover{background:var(--blue-d);}
.btn-o{background:#fff;border-color:var(--line);color:var(--ink);}
.btn-o:hover{border-color:var(--blue);color:var(--blue-d);}
.btn-g{background:var(--green);color:#fff;}
.btn-sm{padding:10px 16px;min-height:44px;font-size:.94rem;}

/* top bar */

/* header */
/* Opaque, like the US nav. The logo files are palette PNGs with no alpha,
   so at 97% opacity the logo's own white background showed as a distinct
   white box wherever a tinted section scrolled behind the header. */
.hdr{position:sticky;top:0;z-index:60;background:#fff;border-bottom:1px solid var(--line);}
.hdr-in{display:flex;align-items:center;justify-content:space-between;gap:14px;height:70px;}
.logo img{height:30px;width:auto;}
.nav{display:flex;gap:22px;align-items:center;}
.nav a{text-decoration:none;font-size:.97rem;font-weight:500;color:var(--ink-2);}
.nav a:hover{color:var(--blue-d);}
.hdr-r{display:flex;align-items:center;gap:9px;}
.lang{display:inline-flex;align-items:center;background:var(--blue-xl);border:1px solid var(--line);border-radius:999px;padding:3px;gap:2px;}
.lang button{background:transparent;border:0;padding:5px 12px;border-radius:999px;font-size:.8rem;font-weight:700;cursor:pointer;color:var(--grey);font-family:var(--bn);line-height:1.4;}
.lang button.on{background:var(--blue);color:#fff;}
.burger{display:none;background:none;border:none;padding:4px;cursor:pointer;flex-direction:column;align-items:center;justify-content:center;gap:0;}
.burger span{width:20px;height:2px;background:var(--ink-2);display:block;margin:4px 0;border-radius:2px;transition:transform .2s ease, opacity .2s ease;}
.burger.on span:nth-child(1){transform:translateY(10px) rotate(45deg);}
.burger.on span:nth-child(2){opacity:0;}
.burger.on span:nth-child(3){transform:translateY(-10px) rotate(-45deg);}
.mnav{display:none;background:#fff;border-top:1px solid var(--line);}
.mnav.open{display:block;}
.mnav a{display:block;padding:15px 20px;border-bottom:1px solid var(--line);text-decoration:none;font-weight:500;}
.cmp-mobile{display:block;max-width:720px;margin:0 auto;}

/* hero */
.hero{padding:52px 0 60px;background:linear-gradient(180deg,var(--blue-xl),#fff);}
.hero-grid{display:grid;grid-template-columns:1.05fr .95fr;gap:46px;align-items:center;}
/* Home hero: content left, the find-your-fit card right, the US hero's
   layout localized. The card holds the six situations that used to be a
   section of their own further down. */
.hero h1 em{font-style:normal;color:var(--blue);}
.hero .acts .btn{flex:0 0 auto;padding:13px 20px;min-height:48px;font-size:.96rem;}
.hero .ticks.two{display:flex;flex-wrap:wrap;gap:6px 18px;margin-top:18px!important;}
.hero .ticks.two li{margin:0;padding-left:24px;font-size:.9rem;color:var(--ink-2);}
.hero .ticks.two li::before{width:16px;height:16px;top:.22em;}
.hero .ticks.two li::after{left:4px;top:calc(.22em + 5px);width:7px;height:3.5px;}
.fitcard{background:#F5F7FC;border:1px solid var(--line);border-radius:18px;padding:24px;}
.fitcard .eyebrow{display:flex;align-items:center;gap:8px;font-size:.75rem;font-weight:700;letter-spacing:.12em;text-transform:uppercase;color:var(--blue-d);}
.fitcard .eyebrow::before{content:"";width:6px;height:6px;border-radius:50%;background:var(--blue);flex:none;}
body.lang-bn .fitcard .eyebrow{letter-spacing:0;font-size:.86rem;}.fitcard h3,.fitcard .hsub{margin-top:10px;font-size:1.05rem;}
.fitcard .chips{display:flex;flex-wrap:wrap;gap:8px;margin-top:14px;}
.fitcard .chip{display:inline-flex;align-items:center;gap:8px;background:#fff;border:1px solid var(--line);border-radius:10px;padding:9px 14px;font-size:.92rem;font-weight:600;color:var(--ink);text-decoration:none;transition:.15s;}
.fitcard .chip::after{content:"\203A";color:var(--blue-d);font-weight:700;}
.fitcard .chip:hover{border-color:var(--blue);color:var(--blue-d);}
.hero h1{max-width:16ch;}
.hero .sub{margin-top:16px;font-size:1.1rem;color:var(--ink-2);max-width:46ch;}
.acts{display:flex;gap:12px;margin-top:26px;flex-wrap:wrap;}
.acts .btn{flex:1 1 210px;}
.freelist{display:flex;flex-wrap:wrap;gap:8px 18px;margin-top:22px;}
.freelist span{display:inline-flex;align-items:center;gap:8px;font-size:.96rem;color:var(--ink-2);}
.tick{width:19px;height:19px;border-radius:50%;background:var(--green-l);position:relative;flex:none;}
.tick::after{content:"";position:absolute;left:5px;top:6px;width:8px;height:4px;border-left:2px solid var(--green);border-bottom:2px solid var(--green);transform:rotate(-45deg);}

/* A CHECKED LIST. The design shipped .tick as a standalone dot used inside
   hand-built flex rows, so every <ul class="ticks"> written since - the
   service pages, the new home page - was falling back to browser bullets and
   nobody noticed because a bullet list still looks like a list. Defining the
   class once fixes every page that already asked for it. */
.ticks{list-style:none;padding:0;margin:0;}
.ticks li{position:relative;padding-left:29px;margin:8px 0;}
.ticks li::before{content:"";position:absolute;left:0;top:.35em;width:19px;height:19px;border-radius:50%;background:var(--green-l);}
.ticks li::after{content:"";position:absolute;left:5px;top:calc(.35em + 6px);width:8px;height:4px;border-left:2px solid var(--green);border-bottom:2px solid var(--green);transform:rotate(-45deg);}
/* Two even columns where the content is short enough to pair up. CSS columns
   balance by line, which put three items left and one right. */
.ticks.two{display:grid;grid-template-columns:1fr 1fr;gap:0 22px;}
@media (max-width:640px){.ticks.two{grid-template-columns:1fr;}}

/* report card */
.rep{background:#fff;border:1px solid var(--line);border-radius:16px;padding:22px;box-shadow:0 22px 54px -34px rgba(15,22,38,.4);}
.rep h4{font-size:1.02rem;}
.rep .date{font-size:.85rem;color:var(--grey);}
.rep .r{display:flex;justify-content:space-between;padding:11px 0;border-bottom:1px solid var(--line);font-size:.98rem;}
.rep .r:last-of-type{border-bottom:0;}
.rep .r span{color:var(--ink-2);}
.rep .r b{font-weight:600;}
.rep .good{color:var(--green);}
.rep .note{margin-top:12px;background:var(--green-l);color:#0B6B47;border-radius:10px;padding:11px 14px;font-size:.9rem;}

/* cards */
/* Service groups on the home page: a one-line lead under each group name,
   then rows of service + what it covers, so the four cards carry the same
   weight and every row says something before you click it. */
.svcs .lead{color:var(--grey);font-size:.94rem;margin-top:6px;}
.svcs ul{list-style:none;padding:0;margin:14px 0 0;}
.svcs .srow{display:flex;justify-content:space-between;align-items:center;gap:12px;padding:11px 0;border-top:1px solid var(--line);text-decoration:none;color:var(--ink);}
.svcs .srow b{display:block;font-weight:600;line-height:1.35;}
.svcs .srow small{display:block;font-size:.85rem;color:var(--grey);line-height:1.45;margin-top:2px;}
.svcs .srow-arr{color:var(--blue-d);font-weight:700;font-size:1.2rem;flex:none;}
.svcs .srow:hover b{color:var(--blue-d);}
.grid{display:grid;gap:18px;}
.g2{grid-template-columns:repeat(2,1fr);}
.g3{grid-template-columns:repeat(3,1fr);}
.g4{grid-template-columns:repeat(4,1fr);}
.card{background:#fff;border:1px solid var(--line);border-radius:16px;padding:26px 24px;}.card h3,.card .hsub{margin-bottom:8px;}
.card p{color:var(--grey);font-size:.99rem;}
.icon{width:46px;height:46px;border-radius:13px;background:var(--blue-l);display:flex;align-items:center;justify-content:center;font-size:1.3rem;margin-bottom:15px;}
.card.big{padding:30px 28px;}
.card.big ul{list-style:none;margin:16px 0 0;padding:0;}
.card.big ul li{position:relative;padding:6px 0 6px 26px;font-size:.98rem;color:var(--ink-2);}
.card.big ul li::before{content:"";position:absolute;left:3px;top:1em;width:9px;height:5px;border-left:2px solid var(--green);border-bottom:2px solid var(--green);transform:rotate(-45deg);}
.card .from{margin-top:16px;padding-top:14px;border-top:1px dashed var(--line);font-size:.96rem;color:var(--grey);}
.card .from b{color:var(--ink);font-size:1.25rem;font-weight:700;}

/* calculator */
.calc{background:#fff;border:1px solid var(--line);border-top:3px solid var(--blue);border-radius:20px;padding:30px 28px;box-shadow:0 24px 50px -30px rgba(15,22,38,.16);}
.calc .q{margin-bottom:20px;}
.calc .q > label{display:block;font-weight:600;margin-bottom:10px;font-size:1rem;}
.opts{display:grid;grid-template-columns:repeat(3,1fr);gap:8px;}
.opts.two{grid-template-columns:repeat(2,1fr);}
.opt{position:relative;}
.opt input{position:absolute;opacity:0;width:0;height:0;}
.opt span{display:flex;align-items:center;justify-content:center;text-align:center;min-height:52px;padding:9px 12px;border:1px solid var(--line);border-radius:12px;cursor:pointer;font-size:.95rem;font-weight:500;line-height:1.35;transition:.15s;background:#FBFCFE;}
.opt:hover span{border-color:var(--blue);box-shadow:0 2px 10px rgba(28,95,204,.10);}
.opt input:checked + span{border-color:var(--blue);background:var(--blue-l);color:var(--blue-d);font-weight:600;}
.opt input:focus-visible + span{outline:3px solid var(--blue);outline-offset:2px;}
.opt.rec span::after{content:"recommended";font-size:.68rem;font-weight:700;color:var(--blue);margin-left:7px;letter-spacing:.02em;white-space:nowrap;}
body.lang-bn .opt.rec span::after{content:"পরামর্শ";}
.result{margin-top:24px;background:var(--blue-xl);border-radius:16px;padding:22px;}
.result .lbl{font-size:.95rem;color:var(--grey);}
.result .amt{font-size:2.1rem;font-weight:700;line-height:1.25;margin:4px 0 2px;}
.result .fine{font-size:.9rem;color:var(--grey);margin-top:12px;}
.result .btn{margin-top:16px;width:100%;}

/* pricing */
.toggle{display:inline-flex;background:#fff;border:1.5px solid var(--line);border-radius:12px;padding:4px;gap:4px;margin:0 auto 30px;}
.toggle button{border:0;background:transparent;padding:10px 18px;border-radius:9px;font-family:inherit;font-size:.95rem;font-weight:600;cursor:pointer;color:var(--grey);}
.toggle button.on{background:var(--blue);color:#fff;}
.plan{background:#fff;border:1.5px solid var(--line);border-radius:18px;padding:28px 24px;display:flex;flex-direction:column;position:relative;}
.plan.pick{border-color:var(--blue);box-shadow:0 22px 54px -38px rgba(29,137,228,.8);}
.plan .badge{position:absolute;top:-14px;left:50%;transform:translateX(-50%);background:var(--blue);color:#fff;font-size:.82rem;font-weight:600;padding:5px 15px;border-radius:999px;white-space:nowrap;}.plan h3,.plan .hsub{font-size:1.24rem;}
.plan .fit{color:var(--grey);font-size:.95rem;margin-top:4px;}
.plan .p{font-size:2rem;font-weight:700;margin:16px 0 0;line-height:1.2;}
.plan .p small{font-size:.95rem;font-weight:500;color:var(--grey);}
.plan .save{color:var(--green);font-size:.9rem;font-weight:600;min-height:22px;}
.plan .lim{background:var(--blue-xl);border-radius:10px;padding:10px 14px;font-size:.94rem;margin:14px 0 4px;color:var(--ink-2);}
.plan ul{list-style:none;margin:12px 0 20px;padding:0;flex:1;}
.plan ul li{position:relative;padding:7px 0 7px 26px;font-size:.97rem;border-bottom:1px dashed var(--line);}
.plan ul li:last-child{border-bottom:0;}
.plan ul li::before{content:"";position:absolute;left:3px;top:1.05em;width:9px;height:5px;border-left:2px solid var(--green);border-bottom:2px solid var(--green);transform:rotate(-45deg);}
.paybar{display:flex;gap:10px;flex-wrap:wrap;justify-content:center;align-items:center;margin-top:26px;color:var(--grey);font-size:.94rem;}
.paybar b{background:#fff;border:1px solid var(--line);border-radius:8px;padding:7px 14px;color:var(--ink-2);font-weight:600;}

/* services accordion */
.svc{background:#fff;border:1px solid var(--line);border-radius:14px;margin-bottom:10px;overflow:hidden;}
.svc summary{list-style:none;cursor:pointer;display:flex;gap:14px;align-items:flex-start;padding:18px 20px;}
.svc summary::-webkit-details-marker{display:none;}
.svc summary:focus-visible{outline:3px solid var(--blue);outline-offset:-3px;}
.svc .n{width:32px;height:32px;flex:none;border-radius:9px;background:var(--blue-l);color:var(--blue-d);font-weight:700;font-size:.92rem;display:flex;align-items:center;justify-content:center;}
.svc .h{flex:1;}
.svc .h b{display:block;font-weight:600;font-size:1.05rem;line-height:1.5;}
.svc .cmp-when{display:block;font-weight:400;font-size:.86rem;color:var(--grey);margin-top:2px;}
.svc .h span{display:block;color:var(--grey);font-size:.95rem;}
.svc .pl{width:20px;height:20px;flex:none;position:relative;margin-top:7px;}
.svc .pl::before,.svc .pl::after{content:"";position:absolute;background:var(--blue-d);transition:.22s;}
.svc .pl::before{top:9px;left:0;width:20px;height:2px;}
.svc .pl::after{left:9px;top:0;width:2px;height:20px;}
.svc[open] .pl::after{transform:rotate(90deg);}
.svc .body{padding:0 20px 22px 66px;}
.svc ul{list-style:none;margin:0;padding:0;columns:2;column-gap:28px;}
.svc ul li{break-inside:avoid;position:relative;padding:5px 0 5px 24px;font-size:.97rem;color:var(--ink-2);}
.svc ul li::before{content:"";position:absolute;left:2px;top:.95em;width:9px;height:5px;border-left:2px solid var(--green);border-bottom:2px solid var(--green);transform:rotate(-45deg);}

/* steps */
.steps{display:grid;gap:16px;grid-template-columns:repeat(4,1fr);}
.stp{background:#fff;border:1px solid var(--line);border-radius:16px;padding:24px 22px;}
.stp .num{width:38px;height:38px;border-radius:50%;background:var(--blue);color:#fff;display:flex;align-items:center;justify-content:center;font-weight:700;margin-bottom:14px;}
.stp p{color:var(--grey);font-size:.96rem;}

/* trust strip */
.tstrip{display:grid;grid-template-columns:repeat(4,1fr);gap:1px;background:var(--line);border:1px solid var(--line);border-radius:16px;overflow:hidden;}
.tstrip > div{background:#fff;padding:22px 20px;text-align:center;}
.tstrip .k{display:block;font-weight:700;color:var(--blue-d);font-size:1.05rem;}
.tstrip .v{display:block;color:var(--grey);font-size:.92rem;margin-top:4px;}

/* review */
.rev{background:#fff;border:1px solid var(--line);border-radius:16px;padding:24px;}
.rev .stars{color:#F5A623;letter-spacing:2px;}
.rev p{margin-top:10px;font-size:1.02rem;}
.rev .who{margin-top:14px;color:var(--grey);font-size:.94rem;}

/* faq */
.faq{border:1px solid var(--line);border-radius:16px;overflow:hidden;background:#fff;}
.faq details{border-bottom:1px solid var(--line);}
.faq details:last-child{border-bottom:0;}
.faq summary{list-style:none;cursor:pointer;display:flex;justify-content:space-between;gap:16px;align-items:flex-start;padding:18px 22px;font-weight:600;font-size:1.03rem;}
.faq summary::-webkit-details-marker{display:none;}
.faq summary:focus-visible{outline:3px solid var(--blue);outline-offset:-3px;}
.faq p{padding:0 22px 20px;color:var(--grey);font-size:.99rem;}
.faq .pl{width:20px;height:20px;flex:none;position:relative;margin-top:7px;}
.faq .pl::before,.faq .pl::after{content:"";position:absolute;background:var(--blue-d);transition:.22s;}
.faq .pl::before{top:9px;left:0;width:20px;height:2px;}
.faq .pl::after{left:9px;top:0;width:2px;height:20px;}
.faq details[open] .pl::after{transform:rotate(90deg);}

/* contact */
.cgrid{display:grid;grid-template-columns:1fr 1fr;gap:34px;align-items:start;}
/* Until the calculator has a result to show, its hidden result panel
   left an empty half-grid on desktop; centre the input card instead. */
.cgrid:has(> [hidden]){grid-template-columns:1fr;max-width:640px;margin:0 auto;}
.way{display:flex;align-items:center;gap:14px;background:#fff;border:1px solid var(--line);border-radius:13px;padding:15px 18px;text-decoration:none;margin-bottom:11px;}
.way:hover{border-color:var(--blue);}
.way .ic{width:44px;height:44px;border-radius:12px;background:var(--blue-l);display:flex;align-items:center;justify-content:center;font-size:1.2rem;flex:none;}
.way b{display:block;}
.way span{display:block;color:var(--grey);font-size:.93rem;}
.form{background:#fff;border:1px solid var(--line);border-radius:16px;padding:26px 24px;}
.field{margin-bottom:15px;}
.field label{display:block;font-size:.95rem;font-weight:600;margin-bottom:7px;}
.field input,.field select,.field textarea{width:100%;padding:14px 15px;border:1.5px solid var(--line);border-radius:12px;font-family:inherit;font-size:1rem;background:#fff;color:var(--ink);}
.field input:focus,.field select:focus,.field textarea:focus{outline:0;border-color:var(--blue);}
.field textarea{min-height:100px;resize:vertical;}
.fnote{font-size:.92rem;color:var(--grey);margin-top:12px;}

/* FOOTER, MATCHED TO THE US SITE.
   It had drifted into a different design: a darker ground, headings set large
   and white in sentence case, and body-sized links, against the US footer's
   small uppercase blue labels and quiet 12px list. Two footers on one domain
   should not look like two companies, so these are the US values.

   The logo was the worse half. It reused the dark header mark and forced it
   light with filter:brightness(0) invert(1), which flattens every pixel to the
   same white, so the symbol and the wordmark merged into one solid rectangle.
   The US footer has always shipped a real light logo file; use that, drop the
   filter. */
footer{background:#0A1F44;color:rgba(255,255,255,.9);padding:54px 0 24px;}
footer .logo img{height:28px;width:auto;display:block;}
footer p{font-size:12.5px;color:rgba(255,255,255,.72);margin-top:14px;max-width:34ch;}
footer h2{color:#74A9FF;font-size:11px;font-weight:800;text-transform:uppercase;letter-spacing:.14em;margin-bottom:14px;}
footer ul{list-style:none;margin:0;padding:0;}
footer li{margin-bottom:0;font-size:12.5px;}
footer li span{font-size:12.5px;color:rgba(255,255,255,.95);display:block;padding:3px 0;}
footer a{text-decoration:none;display:block;font-size:12.5px;color:rgba(255,255,255,.95);padding:3px 0;}
footer a:hover{color:#C0D8F8;}
.fbar{margin-top:32px;border-top:1px solid rgba(255,255,255,.12);padding-top:14px;font-size:11px;color:rgba(255,255,255,.65);display:flex;justify-content:space-between;gap:10px;flex-wrap:wrap;}

.callbar{position:fixed;left:0;right:0;bottom:0;z-index:70;display:none;gap:10px;padding:10px 14px calc(10px + env(safe-area-inset-bottom));background:rgba(255,255,255,.98);border-top:1px solid var(--line);transform:translateY(110%);transition:transform .25s ease;}
.callbar.cb-show{transform:translateY(0);}
@media (prefers-reduced-motion:reduce){.callbar{transition:none;}}
.callbar .btn{flex:1;}

.rise{opacity:0;transform:translateY(14px);transition:.5s;}
.rise.in{opacity:1;transform:none;}
@media (prefers-reduced-motion:reduce){.rise{opacity:1;transform:none;transition:none;}html{scroll-behavior:auto;}}

@media (max-width:960px){
  .hero-grid,.cgrid{grid-template-columns:1fr;gap:34px;}
  .g3,.g4,.steps,.tstrip{grid-template-columns:repeat(2,1fr);}
  .nav{display:none;}
  .burger{display:flex;}
}
@media (max-width:640px){
  .cmp-desktop{display:none;}
  .cmp-mobile{display:block;}
  /* Long-scroll relief: the desktop rhythm read as empty highway on a
     phone. Sections, section heads and form questions all tighten. */
  section{padding:42px 0;}
  .sec-top{margin-bottom:24px;}
  .calc .q{margin-bottom:13px;}
  .opt span{min-height:44px;padding:7px 8px;font-size:.9rem;}
  body{font-size:17px;}
  .hero{padding:34px 0 42px;}
  .g2,.g3,.g4,.steps,.tstrip{grid-template-columns:1fr;}
  .opts{grid-template-columns:1fr;}
  .svc ul{columns:1;}
  .svc .body{padding:0 18px 20px;}
  .callbar{display:flex;}
  .acts .btn{flex:1 1 100%;}
  .calc{padding:24px 20px;}

  /* HEADER CROWDING ON PHONES. Logo, language toggle, "Free consult" and the
     burger competed for one 390px row, and the loser was the Bangla label:
     "বাংলা" rendered clipped to "বাংল" - the toggle a Bangladeshi visitor is
     most likely to want, mangled on the device most of them will arrive on.

     The toggle was lost in the home-page rebuild and has been restored, so
     the crowding is back and something has to give. It is the CTA again,
     and this time it genuinely costs nothing: the sticky bar pinned to the
     bottom of every phone screen carries the same action, closer to the
     thumb. The language switch has no second home; the button has two. */
  .hdr-r .btn{display:none;}
  .lang button{padding:5px 10px;}
  .hdr-in{gap:10px;height:64px;}

  /* HOME HERO ON PHONES. The USA home was tuned to a centred, compact
     hero; this one still read as a left-hung column of oversized text.
     Same treatment here: centre the kicker, headline and copy, take the
     sub line down a step, and fold the four assurances into one centred
     chip row instead of a tall tick list. The !important overrides are
     against inline styles baked into the hero markup. */
  /* SITE-WIDE PHONE TYPE SCALE. The USA pages were hand-tuned for
     phones; these inherited the desktop clamp minimums, which left a
     31px h1 wrapping four lines over a seven-line sub on every page.
     One step down across the board, and English text loses the tall
     Bengali-friendly line-height it never needed. */
  h1{font-size:1.82rem;letter-spacing:-.01em;}
  h2{font-size:1.42rem;}
  .sec-top p{font-size:.98rem;line-height:1.65;}
  body.lang-en{line-height:1.7;}

  .hero-grid > div:first-child{text-align:center;}
  .fitcard{padding:18px 16px;}
  .fitcard .chips{justify-content:center;}
  .hero h1{max-width:none;}

  /* Founder card on the about page: side-by-side photo and name read
     as left-hung against the centred stats below. On phones the head
     stacks and centres, and the three stats hold one row. */
  .fhead{flex-direction:column;text-align:center;}
  .grid.fstats{grid-template-columns:repeat(3,1fr);}
  .fstats .muted{font-size:.78rem !important;}
  .hero-grid > div:first-child > p.muted{font-size:.98rem!important;line-height:1.65;margin-top:12px!important;}
  .hero .acts{margin-top:20px!important;}
  .hero .ticks.two{display:flex;flex-wrap:wrap;justify-content:center;gap:7px 16px;margin-top:16px!important;}
  .hero .ticks.two li{margin:0;padding-left:24px;font-size:.85rem;color:var(--grey);white-space:nowrap;}
  .hero .ticks.two li::before{width:16px;height:16px;top:.18em;}
  .hero .ticks.two li::after{left:4px;top:calc(.18em + 5px);width:7px;height:3.5px;}
}

/* Narrow Androids (360px and below) are still common in Bangladesh, so the
   toggle has to survive there too rather than only on a 390px iPhone. */
@media (max-width:380px){
  .lang button{padding:4px 8px;font-size:.76rem;}
  .hdr-in{gap:8px;}
}

/* DOWNLOAD TILES LINE UP ACROSS A ROW. The descriptions are different lengths,
   so a button placed straight after the text sat at a different height in
   every card of the row and the grid stopped reading as a grid. Pushing the
   button to the bottom of the card is what makes three tiles look like one
   row rather than three unrelated boxes. */
.card.dl{display:flex;flex-direction:column;}
.card.dl p{margin-bottom:18px;}
.card.dl > .btn{margin-top:auto;align-self:flex-start;}

/* CASE STUDIES FROM THE US PRACTICE.
   These are real engagements of the American practice, not Bangladesh
   clients, and the section header says so on every page that carries one.
   Styled deliberately unlike a testimonial: no faces, no quote marks, no
   stars - a problem, the work, and what changed. The outcome block is the
   only tinted thing, because it is the only part a buyer is scanning for. */
.cs{background:#fff;border:1px solid var(--line);border-radius:16px;padding:26px 24px;display:flex;flex-direction:column;gap:15px;}
.cs .tagp{align-self:flex-start;background:var(--blue-xl);color:var(--blue-d);font-size:.75rem;font-weight:700;letter-spacing:.05em;padding:5px 12px;border-radius:999px;}.cs h3,.cs .hsub{font-size:1.1rem;margin:0;line-height:1.35;}
.cs .lab{font-size:.72rem;font-weight:700;text-transform:uppercase;letter-spacing:.09em;color:var(--grey);margin-bottom:6px;}
.cs .blk{border-top:1px solid var(--line);padding-top:13px;}
.cs .blk:first-of-type{border-top:0;padding-top:0;}
.cs p{margin:0;font-size:.94rem;color:var(--ink-2);line-height:1.65;}
.cs .out{background:var(--blue-xl);border-radius:12px;padding:14px 16px;margin-top:auto;}
.cs .out .lab{color:var(--blue-d);}
.cs .out p{color:var(--ink);font-weight:500;}
/* The standing disclaimer that keeps the section honest. */
.uspx{max-width:660px;margin:0 auto 26px;text-align:center;font-size:.94rem;color:var(--grey);}

/* PLATFORM LOGOS, rendered as masks like the US site.
   A silhouette rather than the full-colour mark: it keeps a row of nine
   brands from turning into a colour clash, and it goes full colour on hover
   for anyone who wants to check what they are looking at. */
.tlogo{display:block;height:calc(var(--h,15px) * var(--ls,1));width:calc(var(--h,15px) * var(--ls,1) * var(--ar,3));background:#6B7699;-webkit-mask:var(--mask) center/contain no-repeat;mask:var(--mask) center/contain no-repeat;opacity:.85;transition:opacity .2s ease;}
.tlogo:hover{opacity:1;background:var(--mask) center/contain no-repeat;-webkit-mask:none;mask:none;}
/* A PNG mask has no transparency to key off, so it stays a silhouette and
   only darkens on hover. */
.tlogo.tlogo-mono:hover{opacity:1;background:var(--ink);-webkit-mask:var(--mask) center/contain no-repeat;mask:var(--mask) center/contain no-repeat;}
.logos{display:flex;flex-wrap:wrap;align-items:center;justify-content:center;gap:26px 40px;padding:4px 0;}
.logos-note{text-align:center;color:var(--grey);font-size:.92rem;margin-top:18px;}
/* On phones the four-logo tool strips were one logo too wide and wrapped
   3+1, which read as cut off. Scale the marks down together so the strip
   holds one balanced row down to the narrowest common screens. */
@media (max-width:640px){ .logos{gap:14px 10px;--ls:.8;} }
@media (max-width:379px){ .logos{gap:12px 8px;--ls:.7;} }

/* Client logo row: real marks, greyed so ten brands read as one row. */
.logos img{filter:grayscale(1);opacity:.72;width:auto;transition:opacity .2s ease,filter .2s ease;}
.logos img:hover{filter:none;opacity:1;}

/* THE COST BAR ON THE LANDING PAGE.
   Emphasis form, not categorical: one accent for us, de-emphasis grey for the
   thing we are measured against. Colours were run through a CVD validator
   rather than eyeballed - the brand blue against #55618C gives deutan dE 19.3 and
   normal-vision 20.3, both well clear of the floor. The grey deliberately
   "reads grey"; that is what de-emphasis means.
   Single theme on purpose: the rest of /bd is light-only, so a chart that
   flipped to dark on its own would sit dark on a white page. Every colour is
   painted explicitly rather than inherited. */
.cb-rail{background:var(--blue-xl);border-radius:8px;}
/* Salary against everything else. Two shades of ONE grey, which is the
   allowed treatment for parts of a single quantity, with the 2px surface gap
   the stacked-bar spec asks for. The first version used a white marker line
   and it read as a gap in the bar rather than a boundary, which is the sort
   of thing only looking at the render catches.
   The lighter step sits at 2.83:1 against the surface, under the 3:1 line, so
   the validator asks for relief: both segments carry a visible label. */
@media (max-width:640px){
  /* The narrow segment is about 87px on a 390px screen, which clipped
     "Everything else" mid-word. Drop the wording, keep the figure: the note
     under the bar already says what the two parts are. */
}

/* Article pages. The section had no blog at all, so this is the first
   long-form typography on /bd. Measure kept near 68 characters. */
.art{max-width:720px;margin:0 auto;}
.art .meta{color:var(--grey);font-size:.92rem;margin-bottom:6px;}
.art h1{margin-bottom:14px;}
.art .dek{font-size:1.12rem;color:var(--ink-2);line-height:1.65;margin:0 0 8px;}
.art h2{font-size:1.32rem;margin:34px 0 12px;}.art h3,.art .hsub{font-size:1.06rem;margin:26px 0 8px;}
.art p{margin:0 0 15px;line-height:1.75;}
.art ul,.art ol{margin:0 0 15px;padding-left:22px;}
.art li{margin:8px 0;line-height:1.7;}
.art a{color:var(--blue-d);}
.art .pull{background:var(--blue-xl);border-left:3px solid var(--blue);border-radius:0 10px 10px 0;padding:16px 20px;margin:22px 0;}
.art .pull p{margin:0;}
.art .srcs{border-top:1px solid var(--line);margin-top:34px;padding-top:16px;font-size:.9rem;color:var(--grey);}
.art .srcs li{margin:5px 0;}
.art .asof{background:var(--blue-l);border-radius:10px;padding:14px 17px;font-size:.92rem;color:var(--ink-2);margin:26px 0 0;}
.plist{display:grid;gap:16px;}
.pcard{background:#fff;border:1px solid var(--line);border-radius:14px;padding:22px 24px;display:block;text-decoration:none;color:inherit;}
.pcard:hover{border-color:var(--blue);}
.pcard .d{color:var(--grey);font-size:.87rem;}.pcard h3,.pcard .hsub{margin:5px 0 7px;font-size:1.12rem;}
.pcard p{margin:0;color:var(--grey);font-size:.95rem;line-height:1.6;}


/* The home page comparison table is five columns of prose. Below 760px it
   stops behaving as a table and becomes one block per question, each
   alternative labelled from its column header, because a horizontal
   scrollbar hides four of the five answers on a phone. */
@media (max-width:760px){
  #compare .card{overflow-x:visible;padding:0;border:0;background:none;box-shadow:none}
  #compare table{min-width:0;display:block}
  #compare thead{display:none}
  #compare tbody,#compare tbody tr,#compare tbody th,#compare tbody td{display:block}
  #compare tbody tr{background:#fff;border:1px solid var(--line);border-radius:14px;padding:4px 16px 14px;margin-bottom:14px}
  #compare tbody th[scope="row"]{border-top:0;padding:14px 0 4px;font-size:1.02rem;font-weight:700;color:var(--ink)}
  #compare tbody td{border-top:1px solid var(--line);padding:10px 0 0;margin-top:10px}
  #compare tbody td::before{content:attr(data-label);display:block;font-size:.72rem;font-weight:700;text-transform:uppercase;letter-spacing:.04em;color:var(--ink-2);margin-bottom:3px}
  #compare tbody td:last-child::before{color:var(--blue-d)}
}

/* Wide enough that five prose columns stay readable on a desktop; the
   scroller on .card handles anything narrower down to the 760px breakpoint
   above, where the table stops being a table. */
#compare table{min-width:900px}
@media (max-width:760px){#compare table{min-width:0}}

/* The generic rule collapses every .g4 to one column on a phone, which made
   the footer a single column about two screens tall. The US footer goes to two
   columns at this width, so the footer opts out. */
@media (max-width:640px){
  footer .grid.g4{grid-template-columns:1fr 1fr;gap:26px 18px;}
  /* Brand and Contact span the full width; Services and Information pair up
     as the two columns - no short column leaving a void. */
  footer .grid.g4 > div:first-child{grid-column:1 / -1;}
  footer .grid.g4 > div:last-child{grid-column:1 / -1;}
}

/* The Bangladesh line under the wordmark. A sub-brand lockup, not a badge:
   the mark stays the one brand, the line under it says which side of the
   site this is, and it follows the language toggle. The left offset clears
   the logo mark so the word sits under the wordmark, where a lockup belongs. */
.logo{display:inline-block;text-decoration:none;line-height:1;}
.logo img{display:block;}
.logo-bd{display:block;font-family:var(--en);font-size:.54rem;font-weight:800;letter-spacing:.18em;text-transform:uppercase;color:var(--blue-d);margin:3px 0 0 38px;white-space:nowrap;text-decoration:none;}
body.lang-bn .logo-bd{letter-spacing:.04em;font-size:.74rem;font-weight:600;}
/* BANGLADESH sits flush with the logo's left edge in the footer - the
   36px header indent had nothing to align with at this scale and read as a
   stray tab (Abu, 1 Sep: "text are still not aligning professionally"). */
footer .logo-bd{color:#8AC6F5;margin-left:0;}

/* Columns live here, not inline: an inline grid-template-columns outranks
   every media query, the exact bug the US e-commerce page had. */

/* Numbered flow, ported from the USA practice's process visual. Vertical
   timeline: gradient number discs joined by a dashed rail, which reads
   better on phones than a horizontal band. */
.flow{max-width:680px;margin:0 auto;}
.fstep{position:relative;padding:0 0 30px 60px;}
.fstep::before{content:"";position:absolute;left:20px;top:50px;bottom:8px;border-left:2px dashed rgba(28,95,204,.32);}
.fstep:last-child{padding-bottom:0;}
.fstep:last-child::before{display:none;}
.fnum{position:absolute;left:0;top:0;width:42px;height:42px;border-radius:50%;background:linear-gradient(135deg,var(--blue),var(--blue-d));color:#fff;display:flex;align-items:center;justify-content:center;font-weight:800;font-size:17px;box-shadow:0 6px 20px rgba(28,95,204,.28),0 0 0 4px rgba(28,95,204,.08);}.fstep h3,.fstep .hsub{margin:0;padding-top:8px;font-size:1.05rem;}
.fstep p{margin-top:6px;}
/* Icon chip on cards, ported from the USA service cards. */
.ico{width:42px;height:42px;border-radius:11px;display:flex;align-items:center;justify-content:center;background:var(--blue-xl);color:var(--blue);margin-bottom:12px;}
.ico svg{width:22px;height:22px;}

/* Motion ported from the USA site, kept subtle. Cards lift on hover where a
   pointer exists; scroll-reveal uses the existing .rise machinery, which
   bd.js now applies to card grids automatically with a small stagger. */
@media (hover:hover){
.grid .card{transition:transform .3s ease, box-shadow .3s ease, border-color .3s ease;}
.grid .card:hover{transform:translateY(-3px);box-shadow:0 14px 36px rgba(10,31,68,.07);border-color:rgba(28,95,204,.2);}
}
/* Horizontal snap rows on phones: browsing collections (templates, related
   services, casework, reading) swipe sideways instead of stacking three
   screens tall. Desktop keeps the grid. */
@media (max-width:640px){
.grid.hs{display:grid;grid-template-columns:none;grid-auto-flow:column;grid-auto-columns:80%;overflow-x:auto;scroll-snap-type:x mandatory;padding:2px 2px 10px;-webkit-overflow-scrolling:touch;scrollbar-width:thin;}
.grid.hs > *{scroll-snap-align:start;margin:0;}
}

/* Keyframe vocabulary, ported from the USA site. Sections fade in, values
   pulse when they change, swipe hints bob. Everything that moves attaches
   only under no-preference. */
@keyframes fadeUp{from{opacity:0;transform:translateY(18px)}to{opacity:1;transform:translateY(0)}}
@keyframes fadeIn{from{opacity:0}to{opacity:1}}
@keyframes shBob{0%,100%{transform:translateX(0)}50%{transform:translateX(4px)}}
@keyframes pricePulse{50%{transform:scale(1.06)}100%{transform:scale(1)}}
@media (prefers-reduced-motion:no-preference){
section{animation:fadeIn .5s ease both;}
.pulseamt{animation:pricePulse .4s ease;display:inline-block;}
}
/* Swipe-hint chevron, injected by bd.js next to any row that actually
   overflows sideways; fades once the visitor has swiped. */
.shint{position:absolute;right:8px;width:30px;height:30px;border-radius:50%;background:rgba(255,255,255,.94);border:1px solid var(--line);box-shadow:0 2px 10px rgba(10,31,68,.14);display:flex;align-items:center;justify-content:center;color:var(--blue);font-size:19px;font-weight:700;pointer-events:none;z-index:5;transition:opacity .3s;}
@media (prefers-reduced-motion:no-preference){.shint{animation:shBob 1.6s ease-in-out infinite;}}
/* Bilingual leaves for JS-built UI: CSS picks the language, so toggle
   timing never matters. */
.lang-bn .oe{display:none;}
.lang-en .ob{display:none;}
.fq-more{margin:16px auto 0;display:flex;}
/* Horizontal flow on wide screens: same steps, laid as columns under a
   dashed top rail, so the process reads across instead of down. */
@media (min-width:760px){
.flow{max-width:none;display:grid;grid-template-columns:repeat(var(--fcols,4),1fr);gap:0 22px;}
.fstep{padding:60px 6px 0 0;}
.fstep::before{left:52px;right:-16px;top:20px;bottom:auto;border-left:0;border-top:2px dashed rgba(28,95,204,.32);}
.fstep:last-child::before{display:none;}.fstep h3,.fstep .hsub{padding-top:0;}
}

/* Without/With glance panel, ported from the USA home page: one card that
   says the whole comparison before the table proves it. */

/* Hero cost peek: a one-question price glance in the service hero,
   rendered by bd.js from the same constants the estimator uses, so the
   numbers cannot drift from the pricing page. */
.heropeek{max-width:470px;margin:22px auto 0;background:#fff;border:1px solid var(--line);border-radius:14px;padding:16px 16px 14px;text-align:center;}
.heropeek .pq{font-size:.86rem;font-weight:700;margin:0 0 10px;}
.heropeek .pr{display:flex;gap:8px;justify-content:center;flex-wrap:wrap;}
.heropeek .pr button{font-family:inherit;font-size:.86rem;padding:8px 13px;border:1.5px solid var(--line);border-radius:100px;background:#fff;cursor:pointer;min-height:38px;}
.heropeek .pr button.on{border-color:var(--blue);background:var(--blue-xl);color:var(--blue-d);font-weight:700;}
.heropeek .pa{font-size:1.25rem;font-weight:800;margin:12px 0 2px;color:var(--ink);}
.heropeek .pn2{font-size:.8rem;color:var(--grey);margin:0;}
.heropeek .pl2{display:inline-block;margin-top:8px;font-size:.85rem;font-weight:700;color:var(--blue-d);text-decoration:none;}

/* Fit chooser rows. These were anchors nested inside anchors, which the
   parser splits into stray siblings, scattering the Estimate link onto
   its own lines. A row is now a div holding two separate links. */

/* Team photos: real headshots in the member circles, rendered mono via
   CSS so the mixed lighting and colour of phone photos reads as one set.
   The originals stay untouched on disk; drop the class and colour is back. */
.tphoto{width:110px;height:110px;object-fit:cover;display:block;margin:0 auto 12px;}
/* The Burkland treatment (Abu, 31 Aug, after two rounds: "modern and
   sleek"): the photo tile spans the card, a flat soft brand wash behind the
   cutout, the person anchored to the tile's bottom edge, text left-aligned
   below. No blur, no passport square. */
.pwrap{display:block;width:100%;aspect-ratio:1/1;margin:0 0 14px;border-radius:14px;overflow:hidden;background:var(--blue-xl);}
.pwrap .tphoto{width:100%;height:100%;object-fit:cover;object-position:center bottom;margin:0;}
/* One clean role line per card (Abu: no location with the title - the
   section intro already says USA-led, done in Dhaka). */
.trole{margin:2px 0 0;font-size:.9rem;font-weight:600;color:var(--ink);}
/* THE TRUST BAND (Abu, 31 Aug: "use a trust building theme"). The team
   section sits on deep navy - the register banks and audit firms use - so
   the white cards with the real photographs and the credential numbers
   carry the weight. */
.sec-trust{background:#0A1F44;}
.sec-trust .kicker{background:rgba(255,255,255,.12);color:#BFD3F2;}
.sec-trust h2{color:#fff;}
.sec-trust > .wrap > p{color:#C4CFDE;}
.sec-trust .card{border:1px solid rgba(255,255,255,.08);box-shadow:0 22px 44px -26px rgba(0,0,0,.55);}
.sec-trust > .wrap > p.muted{color:#9FB0C6;}
/* Name and title stay centred; the bio reads left-aligned, since five
   centred ragged lines in a narrow column is the hardest way to read a
   sentence. */
.tbio{text-align:left;}
.mono{filter:grayscale(1) contrast(1.06);}
@media (max-width:640px){
  /* Team portraits on phones: capped so a card fits one screen, and kept
     on the SAME LEFT AXIS as the name, role and bio below - one edge for
     everything on the card (Abu, 1 Sep: "you fixes photos now text are
     not aligning"). */
  .pwrap{max-width:232px;margin:0 auto 12px;}
  .sec-trust .card{text-align:center;}
  .sec-trust .card .tbio{text-align:center;}
}

/* The footer column labels moved from h4 to h2 to close the outline skip.
   As an h4 they were never matched by "body.lang-en h1,body.lang-en h2",
   which sets letter-spacing:-.02em and line-height:1.18; as an h2 they are.
   This restores exactly what they had, at a specificity that wins. */
body.lang-en footer h2,body.lang-bn footer h2{letter-spacing:.14em;line-height:1.4;}

/* 12px floor and minimum tap targets, ported from the US side 17 Sep 2026.
   BD needed far less than the US: six small-text nodes and a few standalone
   links. The contact fields are already 49px and the honeypot input is left
   at 21px deliberately, because it has to stay invisible to a person. */
.fbar span{font-size:12px;}
a.muted,p.center>a,.heropeek>a.pl2{display:inline-block;padding:4px 0;}

/* Hero headline entrance, ported from the US home (19 Sep 2026): one element, because the h1 is a bilingual leaf swapped whole; one-time, no loop, no reflow. */
/* Hero typing (Abu, 20 Sep 2026: "Blue color animation doesn't make clear ... How about do a typing effect and green color?"). The object of the second line is typed and backspaced by a small script; the hidden sizer spans hold the slot at the widest word so the h1 never changes height; the typed word and the line under it are green. It runs for everyone: the reduced-motion guard came off 22 Sep 2026 on Abu's instruction, ported from the US home the same day. */
.hero h1 .tw{display:inline-grid;text-align:left;vertical-align:baseline}
.hero h1 .tw>span{grid-area:1/1;white-space:nowrap}
.hero h1 .tw .tw-w{visibility:hidden}
.hero h1 .tw .typed{position:relative;justify-self:start;color:#12A06A;background:linear-gradient(#12A06A,#12A06A) no-repeat 0 90%/100% .08em}
.hero h1 .tw .typed.out{transition:opacity .18s ease;opacity:0}
/* Underline draws with the letters, no cursor (Abu, 20 Sep 2026, his pick of five typing styles). The underline is the typed span's own background, so it grows with the text; the word fades out instead of backspacing. */

/* OS visuals (19 Sep 2026): the real client portal, shot from the demo build by tools/shoot-portal.mjs; the frame matches the US pages. */
.osf{background:#fff;border:1px solid var(--line);border-radius:14px;box-shadow:0 22px 60px -28px rgba(10,31,68,.3);overflow:hidden;text-align:left}
.osf-bar{display:flex;align-items:center;gap:6px;padding:9px 12px;background:#F5F7FC;border-bottom:1px solid #DCE3F2}
.osf-bar i{width:9px;height:9px;border-radius:50%;background:#D5DCE7;display:block}
.osf-url{margin-left:8px;flex:1;max-width:300px;background:#fff;border:1px solid #DCE3F2;border-radius:6px;font-size:11px;color:#55618C;padding:3px 10px;text-align:center;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}
.osf-clip{position:relative;overflow:hidden}
.osf img{display:block;width:100%;height:auto}
.osf-cap{font-size:12px;color:#55618C;margin-top:10px;text-align:center}
.osf-alt{padding:28px 24px;font-size:13.5px;line-height:1.6;color:#39456E;background:#F5F7FC;min-height:160px}
/* Snippets popped off the portal frame (Abu, 20 Sep 2026: "we should do multiple
   snippets either popped up or floating, instead of one flat dashboard"). Each
   snippet is an element screenshot of one real card or tile from the same portal
   screen the frame shows, cut by tools/shoot-portal.mjs, never drawn. They rise
   in once on scroll and lift under the cursor; nothing cycles and nothing can
   reflow the page. THE LAYOUT FOLLOWS THE FRAME'S OWN WIDTH, not the viewport,
   because the same block sits in a half column on the home pages and at full
   width on the service pages: a container query floats them only where there is
   room, and everywhere else they sit under the frame as a row that wraps. The
   snippets are aria-hidden with empty alt: they are crops of the screen the
   frame's own alt text already describes. */
/* THE SAME TREATMENT AS THE US PAGES (21 Sep 2026). Each callout sits ON the
   tile or chart it was cut from, at its own size, over a dimmed screen; the
   pop comes from contrast, not from size. Its seat arrives in the markup as
   --x, --y and --w, written by tools/place-callouts.mjs from the anchor the
   shoot measured, so a re-shoot moves the callouts with the screen.
   WHY BD HAD TO MOVE NOW: the shared snippet set changed under it. Two of the
   cash snippets became chart CLIPS, 496px wide, and BD was rendering them in
   a 168px corner slot as unreadable stripes. */
.osw{position:relative}
.pqv{position:relative;max-width:1000px;margin:0 auto;aspect-ratio:1224/900;border-radius:16px;overflow:hidden;background:#fff;border:1px solid #DCE3F2;box-shadow:0 22px 60px -30px rgba(10,31,68,.3)}
.pqv-bg{position:absolute;inset:0;overflow:hidden}
/* HALF STRENGTH WAS TUNED ON A SCREEN MADE OF CARDS (OS 0693). saturate(.3)
   with opacity .5 worked when the portal had tinted panels and hairlines to
   lose; on a white sheet there is almost nothing left to desaturate, so the
   same numbers turned ghostly and the frame stopped being a screen. 0.45 and
   0.68 keep the layers apart and keep every figure readable, which is the one
   job the frame has. */
.pqv-bg img{width:100%;height:auto;display:block;filter:saturate(.45) brightness(1.02);opacity:.68;transition:filter .3s ease,opacity .3s ease}
.pqv:hover .pqv-bg img{filter:none;opacity:1}
.pqv-bg:after{content:"";position:absolute;inset:0;background:radial-gradient(130% 110% at 50% 45%,rgba(255,255,255,.08) 42%,rgba(255,255,255,.42) 86%,rgba(255,255,255,.6) 100%)}
.pqv-f{position:absolute;inset:0}
.pqv-c{position:absolute;margin:0;background:#fff;border:1px solid #DCE3F2;border-radius:12px;overflow:hidden;box-shadow:0 26px 52px -18px rgba(10,31,68,.42),0 3px 10px rgba(10,31,68,.1);
  width:calc(var(--w,24) * 1%);left:calc(var(--x,50) * 1%);top:calc(var(--y,50) * 1%);transform:translate(-50%,-50%);transition:box-shadow .25s ease,transform .25s ease}
.pqv-c:hover{box-shadow:0 26px 54px -18px rgba(10,31,68,.46),0 3px 10px rgba(10,31,68,.12);transform:translate(-50%,-50%) scale(1.03)}
.pqv-c img{display:block;width:100%;height:auto}
/* ON A PHONE THE SCREEN IS THE POINT (Abu, 21 Sep 2026, sending two phone
   screenshots: "Mobile site not updated"). It was not updated, and the cause
   was this rule: .pqv-bg was display:none under 780px, so a phone never saw
   the dashboard at all. That was decided when the only frame we had was a
   1224px desktop shot squeezed into 390 and unreadable, and the stacked
   callouts carried the numbers instead. Two things make it wrong now. There is
   a PHONE shot of every screen, taken in a 390 by 844 window, so the screen is
   readable at phone width. And a panel with no callouts, which is the
   statements tab and the register, rendered a 2px empty white box: the reader
   picked a question and got nothing back.
   So the frame shows, served from the phone shot through the picture element,
   and the CALLOUTS go instead. They are crops of tiles the phone frame now
   shows at full size, which is the duplication the 21 Sep note already flagged
   as known and accepted; with the screen present it is simply redundant.
   .pqv-bg goes STATIC here: absolute inside a box with aspect-ratio:auto gives
   the box no height at all, which is the 2px empty card in a second form. */
@media(max-width:780px){
  .pqv{aspect-ratio:auto;border-radius:12px}
  .pqv-bg{position:static}
  .pqv-bg:after{display:none}
  /* Nothing floats over it here, so nothing needs to win: the dim exists to
     let a callout beat the screen, and with the callouts gone it was just
     serving a washed-out screenshot. */
  .pqv-bg img{filter:none;opacity:1}
  .pqv-f{display:none}
  /* CLIPPED ON A PHONE (23 Sep 2026 open item, closed 27 Sep): the whole phone
     shot ran about 1,500px tall at 390, so the frame was two screens of
     scrolling before the page moved on. 460px with a fade, the US home page's
     own rule since 23 Sep, ported here for the BD home and the four BD
     service pages that share this stylesheet. SAFE HERE AND ONLY HERE: under 780px .pqv-f is
     display:none, so nothing pinned to a fraction of the shot can be
     misplaced. Never clip the desktop frame without re-running
     tools/place-callouts.mjs. */
  .pqv{max-height:460px;-webkit-mask-image:linear-gradient(to bottom,transparent 0,#000 22px,#000 calc(100% - 54px),transparent 100%);mask-image:linear-gradient(to bottom,transparent 0,#000 22px,#000 calc(100% - 54px),transparent 100%)}
  .pqv::after{content:"";position:absolute;left:0;right:0;bottom:0;height:96px;background:linear-gradient(to bottom,rgba(255,255,255,0) 0,#fff 88%);pointer-events:none;z-index:2}
}
@media (prefers-reduced-motion:reduce){.pqv-c{transition:none}}

/* A NOTE ON EACH FIGURE, ON HOVER (Abu, 21 Sep 2026: "how about on hover popup
   or zooms with note/comment about it figure?", then "Website and the real
   OS"). A callout says "look at this number". A note says what the number
   MEANS, which is the thing these sections are actually selling: the screen
   shows that the product renders a figure, the note shows that somebody
   understands it.
   The hotspot is a real <button> over the rectangle tools/shoot-portal.mjs
   measured, so the note reaches a keyboard as well as a cursor, and every
   seat is written by tools/place-notes.mjs rather than guessed. */
.pqn{position:absolute;inset:0;pointer-events:none;z-index:4}
.pqn-h{position:absolute;left:calc(var(--x) * 1%);top:calc(var(--y) * 1%);width:calc(var(--w) * 1%);height:calc(var(--h) * 1%);
  margin:0;padding:0;border:1px solid transparent;border-radius:12px;background:none;cursor:help;pointer-events:auto;
  transition:background .2s ease,border-color .2s ease}
.pqn-h:hover,.pqn-h:focus-visible{background:rgba(28,95,204,.07);border-color:rgba(28,95,204,.45);outline:none}
.pqn-s{position:absolute;width:1px;height:1px;overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap}
/* The dot is the only thing that says a figure can be asked about, so it
   breathes. This is the one place the site allows a loop: it is on something
   the reader is meant to act on, and it is out of flow, so it can never change
   the height of anything. It sits top left on a wide region, where a chart's
   axis starts, and top right on a tile, which is the corner with the least ink
   in it. */
/* THE DOT SITS WHERE IT CANNOT BE READ AS THE NEXT FIGURE'S (OS 0693). The
   one-sheet portal closed the gutters between tiles, so a marker at a tile's
   top RIGHT corner lands a few pixels from the next tile's label and reads as
   belonging to it. The bottom left is no better: that is where the tile's own
   sub line sits and the dot covered its first word. It now sits ABOVE the
   label, in the 14px of clear space the tile row keeps under its rule, at the
   tile's own left edge. A wide region is a chart and keeps the top left, where
   its axis starts and where no chart callout ever sits. */
.pqn-d{position:absolute;top:-11px;left:0;width:9px;height:9px;border-radius:50%;background:#1C5FCC;animation:pqnp 2.8s ease-out infinite}
.pqn-h[data-dot="tl"] .pqn-d{bottom:auto;top:7px;left:7px}
@keyframes pqnp{0%{box-shadow:0 0 0 0 rgba(28,95,204,.45)}70%{box-shadow:0 0 0 7px rgba(28,95,204,0)}100%{box-shadow:0 0 0 0 rgba(28,95,204,0)}}
/* The note hangs from the bottom of its own figure, on whichever side keeps it
   inside the frame. pointer-events stay on even while it is hidden, so a
   cursor travelling from the hotspot into the note during the fade keeps it
   open instead of losing it in the gap. */
.pqn-n{position:absolute;top:calc(var(--y2) * 1% + 8px);width:min(272px,58%);margin:0;padding:12px 14px;pointer-events:auto;text-align:left;
  background:#0F1A2B;color:#EAEEF8;border-radius:12px;box-shadow:0 22px 44px -16px rgba(10,31,68,.55);
  opacity:0;visibility:hidden;transform:translateY(-4px);transition:opacity .18s ease,transform .18s ease,visibility .18s}
/* A figure low on the frame opens upward instead, or the note hangs off the
   bottom edge. Marked by the script from the measurement, never guessed. */
.pqn-up{top:auto;bottom:calc(var(--y1) * 1% + 8px);transform:translateY(4px)}
/* Neither above nor below fits, so the note opens over the figure itself,
   hanging from its top edge. Only ever a chart: a tile is too small to carry
   one and always has room under it. */
.pqn-in{top:calc((var(--y2) - var(--h2)) * 1% + 10px)}
.pqn-h:hover + .pqn-n,.pqn-h:focus-visible + .pqn-n,.pqn-n:hover{opacity:1;visibility:visible;transform:none}
.pqn-k{display:block;font-size:11px;font-weight:800;letter-spacing:.08em;text-transform:uppercase;color:#9FC0F5}
.pqn-t{display:block;margin-top:5px;font-size:12.5px;line-height:1.5}
.pqn-w{display:block;margin-top:7px;padding-top:7px;border-top:1px solid rgba(255,255,255,.14);font-size:11px;font-style:normal;color:#8892B4}
/* Under 780px .pqv-bg is display:none and the callouts stack on their own, so
   there is no screen left to point at. The notes go with it rather than
   floating over nothing; the page's own prose carries the argument there. */
@media(max-width:780px){.pqn{display:none}}
@media (prefers-reduced-motion:reduce){.pqn-d{animation:none}.pqn-n{transition:none}.pqn-h{transition:none}}
.ins-wrap{display:grid;grid-template-columns:1fr;gap:28px;align-items:start}
.ins-list{list-style:none;padding:0;margin:18px 0 0;display:grid;gap:10px;font-size:.95rem;line-height:1.55}
.ins-list li{padding-left:18px;position:relative}
.ins-list li:before{content:"";position:absolute;left:0;top:9px;width:8px;height:8px;border-radius:50%;background:var(--blue)}
.ins-list b{font-weight:700}
@media(max-width:860px){.ins-wrap{gap:26px}}

/* THE PORTAL QUESTIONS BLOCK, ported from the US home (1321; the US built it 21 to 23 Sep 2026): three questions down a dark rail, one screen each, the answer above the picture. Every text leaf is bilingual in the markup; these rules are the US rules verbatim. */
.pq-head{max-width:860px;margin:0 auto 18px;text-align:center}
.pq-h{font-family:'Plus Jakarta Sans',system-ui,sans-serif;font-size:clamp(21px,2.6vw,27px);font-weight:800;color:#0A1F44;letter-spacing:-.02em;margin:8px 0 0}
.pq-s{font-size:14.5px;line-height:1.6;color:#39456E;margin:10px 0 0}
/* Scrolls sideways on a phone rather than wrapping: four questions is about
   90 characters and will not fit on three lines at 390px without pushing the
   frame off the screen. */
/* THE QUESTIONS ARE THE NAVIGATION (Abu, 21 Sep 2026: "the tab selection chips
   make part of the dashboard?", then his pick of three). Four pills floating
   above the frame were a website control sitting on a photograph of the app.
   Now they are a rail down the left of one card, carrying the reader's own
   questions where the portal's page names would be. The sidebar was clipped
   out of the shots on purpose, because our navigation is not the client's
   numbers; this puts a rail back that is about the reader instead.
   THE CALLOUT SEATS ARE UNAFFECTED, which is the reason this shape is safe:
   --x and --y are percentages of .pqv, and .pqv still wraps the image alone.
   The rail takes its width from the card, not from the picture. */
/* THE PORTAL PIECES (1 Nov 2026, Abu's pick of eleven mockups: option 11). The
   portal's own written read of the month on top, then four questions with
   pieces from across the portal, set straight on the page: no frame, no rail,
   no cards. Pictures are element screenshots cut by tools/shoot-pieces.mjs and
   placed by tools/place-pieces.mjs; a trend line never stands alone (the
   revenue tile keeps its sparkline beside the number). */
.pp{max-width:1040px;margin:0 auto}
.pp-read{font-size:clamp(17px,1.9vw,23px);line-height:1.4;color:#0A1F44;font-weight:600;letter-spacing:-.015em;margin:0 auto;max-width:900px;text-align:left}
.pp-good{color:#12A06A}
.pp-prov{font-size:12px;color:#7C8AA0;margin:8px auto 0;max-width:900px;text-align:left}
.pp-grid{display:grid;grid-template-columns:1fr 1fr 1fr;gap:32px 48px;margin-top:40px;text-align:left}
.pp-k{display:flex;flex-direction:column;gap:14px}
.pp-k .pp-sen{margin-top:auto}
.pp-p{display:block;height:auto;max-width:100%}
.pp-fig{padding:6px 0 0}
.pp-fig b{display:block;font-size:10.5px;font-weight:800;letter-spacing:.12em;text-transform:uppercase;color:#55618C}
.pp-fig strong{display:block;font-size:34px;font-weight:800;color:#12A06A;letter-spacing:-.02em;line-height:1.15;margin:4px 0 2px}
.pp-fig small{font-size:12px;color:#7C8AA0}
.pp-sen{font-size:14px;line-height:1.5;color:#33415C;margin:0}
.pp-sen:before{content:"";display:inline-block;width:8px;height:8px;border-radius:50%;background:#1C5FCC;margin-right:9px;vertical-align:1px}
.pp-needs{border-left:3px solid #1C5FCC;padding:6px 0 6px 14px;font-size:14px;color:#0A1F44;margin:36px auto 0;max-width:900px;text-align:left}
.pp-needs b{display:block;font-size:10.5px;font-weight:800;letter-spacing:.12em;text-transform:uppercase;color:#7C8AA0;margin-bottom:4px}
@media(max-width:780px){.pp{padding-left:20px;padding-right:20px}.pp-grid{grid-template-columns:1fr;gap:26px;margin-top:28px}.pp-k{gap:10px}.pp-sen{margin-top:0}.pp-k .pp-p{max-width:100%}.pp-read{font-size:17px}.pp-needs{margin-top:28px}}
/* THE ANSWER SITS ABOVE THE PICTURE (Abu, 21 Sep 2026, asked what this line
   was and whether it belonged inside the dashboard). It is the answer to the
   tab's question, and under the frame the reader got question, picture,
   answer. Above it they know what to look for before they look. It cannot go
   INSIDE the frame: the frame is a photograph of the product, so text laid
   over it would either cover a card or read as part of the app. */
/* THE INTERPRETATION IS THE POINT, NOT THE DASHBOARD (Abu, 22 Sep 2026:
   "the metrics dominate when the real differentiator should be the
   interpretation"). This line was 13.5px sitting above an 878px
   screenshot, so it read as a caption on a picture. It is the claim now
   and the screen under it is the evidence. */
.pq-ans{font-size:clamp(16px,1.55vw,20px);line-height:1.5;color:#33415C;margin:0 auto 18px;max-width:58ch;text-align:center;letter-spacing:-.011em}
/* An eyebrow that says what the heading does not, which is the test the
   21 Sep sweep set. The heading is three verbs; this names the thing. */
.pq-ans b{color:#0A1F44;font-weight:800;letter-spacing:-.016em}


/* SERVICES DROPDOWN (8 Nov). The nav carried five links and none was a service,
   so four of the nine service pages were reachable only from scattered in-body
   mentions. Ported from the US pattern; see tools/place_bd_nav.py.
   :focus-within as well as :hover, so the dropdown opens for a keyboard too. */
.nav .has-sub{position:relative;display:inline-flex;align-items:center;}
.nav .has-sub>.sub{
  display:none;position:absolute;top:100%;left:-14px;min-width:232px;
  background:#fff;border:1px solid var(--line);border-radius:12px;
  box-shadow:0 12px 28px rgba(16,32,64,.10);padding:8px;z-index:70;}
.nav .has-sub:hover>.sub,.nav .has-sub:focus-within>.sub{display:block;}
/* 24x24 is the WCAG 2.2 AA target; 38px of row keeps it comfortably clear. */
.nav .has-sub>.sub a{
  display:block;padding:9px 12px;border-radius:8px;font-size:.93rem;
  line-height:1.35;min-height:20px;color:var(--ink-2);white-space:nowrap;}
.nav .has-sub>.sub a:hover{background:var(--wash,#F5F7FC);color:var(--blue-d);}

/* Mobile: the drawer is a flat list already, so the services sit under their
   parent as indented rows rather than behind an accordion nobody asked for. */
.mnav a.mnav-sub{
  padding-left:38px;font-size:.95rem;font-weight:400;color:var(--ink-2);}


/* ---------------------------------------------------------------------------
   DRAWN PORTAL VISUALS, ported from the US side (Abu, 8 Nov: reuse what we have
   in US and customise for the audience).

   The BD pages showed PNG screenshots of the portal with dates baked into the
   pixels: "HOW SEPTEMBER 2026 WAS CLOSED", an axis running to Oct '27. Those
   cannot be re-shot without the OS, which is not in this container, and the
   rule is that any specific date goes stale. The US service pages never had the
   problem because their visuals are DRAWN: HTML, CSS and one inline SVG, with
   every reference an interval ("on the month", "Day 8", "over twelve months").

   Lifted verbatim from tools/place_portal_visuals.py so the two sides cannot
   drift apart. No selector here collides with anything already in bd.css.
   --------------------------------------------------------------------------- */
/* CENTERED. This was max-width:720px with margin-top only and no .wrap
   parent, so a 720px stage sat flush against the left edge of a
   full-width band while the .pq-head heading right above it centers
   itself with margin:0 auto. At 1280 it only looked slightly off; at
   1920 the content rail starts at x=400 and the stage was still at x=0,
   which is what 'outside the page frame' looked like. The calc() keeps
   a 20px gutter below 760px, where a bare max-width box would touch
   both edges. */
.pv{position:relative;height:330px;margin:22px auto 0;max-width:min(720px, calc(100% - 40px));border-radius:0;background:
  radial-gradient(420px 300px at 14% 8%, rgba(28,95,204,.065), transparent 70%),
  radial-gradient(380px 280px at 88% 86%, rgba(18,160,106,.055), transparent 70%)}
.pv-p{position:absolute}
.pv-bare{filter:drop-shadow(0 7px 13px rgba(10,31,68,.14))}
.pv-chip{background:#fff;border-radius:12px;padding:9px 12px;box-shadow:0 2px 4px rgba(10,31,68,.05),0 14px 28px -10px rgba(10,31,68,.26)}
.pv-k{font-size:8.5px;letter-spacing:.14em;text-transform:uppercase;font-weight:700;color:#55618C}
.pv-s{font-size:10px;color:#55618C;margin-top:2px;line-height:1.45}
.pv-up{display:inline-block;font-size:9.5px;font-weight:700;color:#12A06A;background:rgba(18,160,106,.12);border-radius:999px;padding:1px 7px}
.pv-fig{font-size:30px;font-weight:800;line-height:1;letter-spacing:-.03em}
.pv-figs{font-size:19px;font-weight:800;line-height:1;letter-spacing:-.02em}
.pv-num{font-variant-numeric:tabular-nums;letter-spacing:-.03em}
.pv-sp{position:absolute;pointer-events:none}
.pv-t{font-size:10.5px}
.pv-t>div{display:flex;justify-content:space-between;gap:16px;padding:4px 0;border-bottom:1px solid rgba(10,31,68,.09)}
.pv-t>div:last-child{border-bottom:0;border-top:1.8px solid #0A1F44;font-weight:800;padding-top:5px}
.pv-t .pv-m{color:#55618C}
/* Centered like .pv and .pq-head above it. Left as margin:14px 0 0 this
   paragraph was a full-width block starting at x=0, so on a wide screen
   the sentence sat alone against the left edge of the window. */
.pv-cap{font-size:11.5px;color:#8A93AD;margin:14px auto 0;max-width:min(720px, calc(100% - 40px));text-align:center}
@media(max-width:860px){
  .pv{height:auto;display:flex;flex-direction:column;gap:20px;padding:16px 0}
  .pv-p{position:static;width:auto!important;left:auto;right:auto;top:auto;bottom:auto}
  .pv-sp{display:none}
}

/* BD CUSTOMISATION OF THE PORTED .pv VISUAL (8 Nov).
   The US block above is lifted verbatim so the two stay comparable. These
   rules are the localisation, and they are rules rather than edits to the
   markup because bd.js swaps innerHTML per leaf: the same element holds the
   English and the Bangla, so only CSS can treat them differently.

   TEXT-TRANSFORM AND LETTER-SPACING ARE LATIN CONVENTIONS. .pv-k ships
   uppercase at .14em, which does nothing to Bengali script except push the
   glyphs apart and break the conjuncts' reading rhythm. Measured on the
   render, not assumed.

   THE FIGURE CANNOT KEEP ITS SIZE. "$3M" is 4 Latin characters; the attested
   Bangla for it is "৩ মিলিয়ন ডলার", 13 characters, so at the US's 40px it ran
   ~270px wide and swamped the panel. body.lang-bn is already toggled by
   setLang(), so the figure is sized per language. */
body.lang-bn .pv-k{text-transform:none;letter-spacing:.01em;font-size:10.5px}
body.lang-bn .pv-fig{font-size:25px!important;letter-spacing:0}
body.lang-bn .pv-figs{font-size:15.5px;letter-spacing:0}
body.lang-bn .pv-num{font-variant-numeric:normal}
/* Three panels, not the US's four: BD has no verified Bangla for "Months
   covered" or "Floor at 3". A 330px stage sized for four left an empty
   bottom-left quadrant, so the stage is shorter here. */
.pv{height:250px}
@media(max-width:860px){.pv{height:auto}}
/* The close frame carries two panels, not three, so it needs a shorter stage
   or the bottom half reads as a hole. SCOPED TO min-width, deliberately: a
   plain .pv--close rule sits after the max-width:860px block and would beat
   it, and an inline height would beat it from any position -- either way the
   mobile stack would lose its height:auto and the panels would overlap. */
@media(min-width:861px){.pv--close{height:190px}}
/* The split bar is one wide panel, not scattered chips, so it needs its own
   stage height for the same reason .pv--close does, and scoped the same way. */
@media(min-width:861px){.pv--split{height:150px}}

/* ============================================================================
   MOBILE POLISH (Abu, 8 Nov): "how US side, all the hero has nice bold large
   text. That's not the case on the BD side. And the alignment, the layout,
   some buttons are too large, others are too small."

   Measured at 390px before touching anything:
     h1       BD 29.12px / weight 600      US 34px / weight 800
     buttons  BD 48,52,53,54,59,73px tall  US 34 and 46, only
     hero     BD centred on mobile, LEFT on its own desktop
   Nothing overflowed: documentElement.scrollWidth was 390 on all 27 pages.
   ========================================================================== */

/* 1. HEADINGS CARRY WEIGHT, and the two languages cannot carry the same one.
   Plus Jakarta Sans is loaded at 400-800, but Hind Siliguri is loaded at
   300-700 and HAS NO 800 -- asking for it gets a synthesised fake-bold that
   smears Bengali conjuncts. So English takes the US's 800 and Bangla takes
   700, which is the heaviest weight that actually exists in the file. This is
   a real localisation, not a shortfall. */
h1,h2{font-weight:800;}
h3,h4,.hsub{font-weight:700;}
body.lang-bn h1,body.lang-bn h2{font-weight:700;}
body.lang-bn h3,body.lang-bn h4,body.lang-bn .hsub{font-weight:600;}

/* 2. BUTTON HEIGHT COMES FROM min-height, NEVER FROM VERTICAL PADDING.
   That one line is the whole bug. .btn had padding:15px 24px, so a label that
   wrapped to two lines grew to 30px of padding plus two lines of text -- which
   is exactly how the sticky call bar reached 73px while a one-line button next
   to it sat at 53. With the vertical padding gone, a two-line label measures
   ~38px and the 46px floor still decides, so every button is the same height
   whatever its text does. 46/36 are the US's own numbers. */
.btn{padding:0 22px;min-height:46px;font-size:.95rem;font-weight:700;
     border-radius:10px;line-height:1.25;}
.btn-sm{padding:0 14px;min-height:36px;font-size:.85rem;}
.hero .acts .btn{padding:0 22px;min-height:46px;font-size:.95rem;}

/* 3. The footer column headings were 11px, under the 12px floor for running
   text. The drawn-visual labels stay exempt; they are chart labels. */
footer h2{font-size:12px;}

@media (max-width:640px){
  /* 4. The hero matched the US kicker, not the US headline. 1.82rem at weight
     600 is a subheading pretending to be an h1. */
  h1{font-size:2.125rem;line-height:1.16;}
  body.lang-en h1{letter-spacing:-.03em;}
  body.lang-bn h1{font-size:1.95rem;line-height:1.42;letter-spacing:0;}

  /* 5. CENTRED ON MOBILE ONLY, which is why it read as "not fitting". The BD
     hero is left-aligned at every other width; this rule flipped it for small
     screens alone, so the page disagreed with itself. Left everywhere now,
     which is also what the US hero does. */
  .hero-grid > div:first-child{text-align:left;}
  .hero .ticks.two{justify-content:flex-start;}

  /* 7. THE PAGE HEADLINE BLOCK GOES LEFT ON PHONES. Every BD page except the
     home page heads itself with .sec-top, which is centred at every width.
     Centred is right for a short section intro above a grid, and wrong for a
     page's h1 plus a five-line lead paragraph on a 390px screen, where the
     ragged left edge is what you fight to read. :has(h1) picks out the ONE
     .sec-top that is the page headline and leaves every section intro below
     it centred, and desktop is untouched at every width. */
  .sec-top:has(h1){text-align:left;max-width:none;}

  /* 8. The headline block carries margin-bottom:24px for the content that
     normally follows it inside its section. On a page hero nothing does, so
     that 24px stacked on top of the hero's own 42px bottom padding and the
     next section's 42px top padding: 108px of nothing between the lead
     paragraph and the page. Dropped only where the block really is the last
     thing in its parent, so contact and health-check, where a form follows it
     in the same section, keep their breathing room. */
  .sec-top:has(h1):last-child{margin-bottom:0;}

  /* 6b. The "Where can we help right now?" chips had the same mobile-only
     centring as the hero, so a wrapped row of short labels came out as a
     staircase: each chip sized to its text and centred on its own line.
     Left, like the same chips at every other width. */
  .fitcard .chips{justify-content:flex-start;}

  /* 6. THE RAGGED PAIR. .acts .btn goes flex:1 1 100% on mobile, but
     .hero .acts .btn pinned flex:0 0 auto and beat it, so the two home-page
     CTAs sized to their labels and came out 273px and 167px wide, stacked and
     left-aligned under centred text. They match now. */
  .hero .acts .btn{flex:1 1 100%;}
}

/* ============================================================================
   DENSITY (Abu, 8 Nov): "kind of text heavy... too many cards on the pages."

   Measured on /bd/bookkeeping at 390px before touching it: 11,173px tall on
   1,609 words, against US /accounting at 6,891px on 1,721 words -- 62% longer
   to scroll on FEWER words. Where the height went:
       list items  3,529px (32%)   56 of them
       section pad   924px
       card pad      624px
       icons         216px
   Note what this is NOT: BD does not have more boxes than the US. Counted in
   the DOM, US accounting has 29 to BD's 21, US cfo 33 to BD's 14. And the
   sections do not repeat each other -- no pair on any page shares more than
   15% of its 4-word phrases. The pages are long because a third of every one
   of them is bullets, set loose.

   This block buys back the spacing only. The bullets themselves are an
   editorial question, not a CSS one.
   ========================================================================== */
@media (max-width:640px){
  /* 16px between every bullet (8 top + 8 bottom) across 56 of them is 900px of
     a single page. 10px still separates them clearly at this measure. */
  .ticks li{margin:5px 0;}
  .card.big ul li{padding-top:4px;padding-bottom:4px;}

  /* 26px of card padding top and bottom, 12 cards deep, is 624px. */
  .card{padding:18px 16px;}
  .card.big{padding:20px 18px;}

  /* ENGLISH TIGHTENS, BANGLA DOES NOT. body is 1.7 for English and 1.85 for
     Bangla, and that difference is deliberate: Bengali conjuncts stack above
     and below the baseline and need the leading. So only lang-en comes down. */
  body.lang-en{line-height:1.6;}
  body.lang-en .ticks li,body.lang-en .card p{line-height:1.55;}
}

/* NAMED .sitp, NOT .pr: BD already uses .pr for the payroll headcount picker
   inside .heropeek, and a bare .pr{padding:0;overflow:hidden} silently landed
   on it. Checked .sitp against bd.css and every bd page before using it.
   The situation/answer pairs (tools/pair_bd_situations.py). Two columns on a
   wide screen so the eye reads across; stacked on a phone, where the answer
   is indented under its situation with a rule down the left so the couple
   still reads as a couple rather than six loose sentences. */
.sitp{padding:0;overflow:hidden;}
.sitp-head{display:grid;grid-template-columns:1fr 1fr;gap:0 22px;padding:14px 20px;
  background:#F5F7FC;border-bottom:1px solid var(--line);}
/* Icon beside its heading. These came off the two source cards: the first
   version of the pairing tool left them behind and /bd/cleanup and
   /bd/software ended up with no icons at all. */
.sitp-c{display:flex;align-items:center;gap:9px;min-width:0;}
.sitp-c .ico{flex:0 0 auto;width:28px;height:28px;margin:0;display:grid;place-items:center;
  background:var(--blue-xl);border-radius:8px;color:var(--blue-d);}
.sitp-c .ico svg{width:15px;height:15px;}
/* 12px, not .74rem. The gate is "12px minimum on running text" and a legend
   label above a block of prose is running text, not a chart label -- the
   exemption covers .pv-k inside the drawn visuals, not this. Shipped at
   10.56px on mobile first time out. */
.sitp-h{font-size:12px;font-weight:800;letter-spacing:.11em;text-transform:uppercase;
  color:var(--blue-d);}
body.lang-bn .sitp-h{letter-spacing:0;font-size:.88rem;font-weight:700;text-transform:none;}
.sitp-row{display:grid;grid-template-columns:1fr 1fr;gap:0 22px;padding:14px 20px;
  border-bottom:1px solid var(--line);}
.sitp-row:last-of-type{border-bottom:0;}
.sitp-q{margin:0;color:var(--ink);font-weight:600;}
.sitp-a{margin:0;color:var(--ink-2);}
.sitp-rest{margin:0;padding:14px 20px 18px;border-top:1px solid var(--line);background:#FBFCFE;}
@media (max-width:640px){
  /* The legend stays on phones. Hidden, the two icons that came off the
     source cards would be hidden with it, which is how this block ended up
     plainer than the cards it replaced. It reads as a legend above the pairs,
     not as column headers, so the labels shrink and the icons carry it. */
  .sitp-head{padding:11px 16px;gap:0 10px;}
  .sitp-c .ico{width:24px;height:24px;}
  .sitp-c .ico svg{width:13px;height:13px;}
  .sitp-h{font-size:12px;letter-spacing:.07em;}
  body.lang-bn .sitp-h{font-size:12.5px;}
  .sitp-row{grid-template-columns:1fr;gap:6px;padding:14px 16px;}
  .sitp-q{font-weight:700;}
  .sitp-a{padding-left:14px;border-left:2px solid var(--green);color:var(--ink-2);}
  .sitp-rest{padding:12px 16px 16px;}
}

/* 12px FLOOR ON THE LAST TWO LABELS UNDER IT (Abu, 8 Nov). Both predate this
   work and both were running text, not chart labels, so neither qualified for
   the illustration exemption.
     .logo-bd   8.64px  the BANGLADESH lockup under the wordmark
     .cs .lab  11.52px  Situation / What we did / Outcome on three pages
   Measured before changing: at 12px the English lockup grows 76px -> 105px and
   ends at x=163, while the next header element starts at x=238 (x=218 at
   360px). 55px of clearance at the tightest, so nothing collides. The Bangla
   lockup was already 11.84px and does not move. Tracking comes down from .18em
   to .12em because .18em was chosen to make 8.64px readable and at 12px it
   just pushes the lockup wide. */
.logo-bd{font-size:12px;letter-spacing:.12em;}
body.lang-bn .logo-bd{font-size:12px;}
.cs .lab{font-size:12px;}
/* fs:unslide */
/* Abu, 9 Nov: BD card grids are not carousels. The .grid.hs rule above turns
   them into 80%-wide scroll-snap rails at <=640px; this stacks them, which is
   what the US does with the same content. Appended rather than edited in
   place so the original rule stays readable, and later-wins at equal
   specificity does the rest. */
@media (max-width:640px){
  .grid.hs{grid-template-columns:1fr;grid-auto-flow:row;grid-auto-columns:auto;
    overflow-x:visible;scroll-snap-type:none;padding:0;}
  .grid.hs > *{scroll-snap-align:none;}
}
/* fs:unslide end */
/* fs:pp-fig-money */
/* The drawn money pieces on the home portal preview (tools/place-pieces.mjs).
   Green is reserved for the close day; revenue and cash take the brand blue
   the shots they replaced used.
   The one small under a money figure is the +9% delta, and the shot it
   replaced drew that as a green pill, so it keeps the green rather than the
   default grey. The close panel's small is prose and is not .pp-fig--m. */
.pp-fig--m strong{color:#1C5FCC}
.pp-fig--m small{color:#12A06A;font-weight:700}
/* Latin tracking off the Bengali labels; bd.js writes both languages into the
   same element, so the language has to be reached through body.lang-bn. */
body.lang-bn .pp-fig b,body.lang-bn .pp-needs b{text-transform:none;letter-spacing:0}
/* fs:pp-fig-money end */
/* fs:bd-templates */
/* /bd/tools template rows at US density (Abu, 9 Nov). The description is
   clipped, not removed -- the same screen-reader box .tmpl-row .tmpl-desc uses
   on the US page -- so both languages stay in the document. */
#templates .card.dl{padding:16px 14px}
#templates .card.dl h3{font-size:13.5px;line-height:1.3;margin-bottom:0}
#templates .card.dl p{position:absolute;width:1px;height:1px;padding:0;
  overflow:hidden;clip:rect(0,0,0,0);white-space:nowrap;border:0}
#templates .card.dl > .btn{margin-top:12px;min-height:26px;padding:0 12px;
  font-size:11.5px;line-height:26px}
/* fs:bd-templates end */
/* fs:bd-icon-size */
/* Icon pack at US size on BD card headers (Abu, 9 Nov). The US shows these
   same files bare -- .v2svc at 88px, .v2steps and .v2covers at 40px -- so the
   42px tinted chip comes off rather than growing. :has(img.fi) leaves the one
   .ico that holds an inline <svg> with its chip; a browser without :has()
   drops this rule and keeps the old look. .sitp-c markers are untouched. */
.card > .ico:has(img.fi){width:auto;height:auto;background:none;border-radius:0;
  display:block;margin-bottom:14px}
.card > .ico img.fi{width:56px;height:56px;object-fit:contain;display:block}
@media(max-width:860px){.card > .ico img.fi{width:48px;height:48px}}
/* fs:bd-icon-size end */
