/* AI Quest — base styles (vanilla, no framework) — "Sunrise Dojo" theme (P2-C) */ :root{ /* Sunrise Dojo — light-first, one color one job */ /* WY-V3 W-V2-4 (Ram, app-wide ruling A2): secondary body-text token darkened a few shades — the old #5B5A72 passed 4.5:1 on white but still read "a little too light" at small sizes. #45445C is ~7.4:1 on --panel white. Night mode gets the mirror move (LIGHTER, same intent: more contrast against the dark panel). */ --bg:#F7F8FC; --panel:#FFFFFF; --panel2:#EDEBFF; --ink:#2A2440; --muted:#45445C; /* Opus gate (sv150 dark-sweep wave): --ink-soft and --panel2-ink were CONSUMED globally by that wave (.kh-tile-sub here, the minis.js code-output boxes) but only ever DEFINED inside readv2.js's own .readv2 scope -- outside it they fell through to their literal fallbacks in BOTH themes, so night mode lost its themed value. Defined here as real global tokens, reusing readv2's already audited light/night pair (#6B668F / #B3BBDA); readv2's own scoped copies still win inside .readv2. */ --ink-soft:#6B668F; --panel2-ink:#2A2440; /* B24 (Ram-ruled): white #btn text on --brand computed 4.35:1 (just under 4.5). #7C5CFF -> #7458F0 clears 4.5:1 (4.77:1 measured) while staying visually the same purple; brand-shade nudged to match. */ --brand:#7458F0; --brand-shade:#5230C9; --brand2:#00D4B8; --line:#E3E6F2; --good:#2ECC71; --warn:#FFC800; --error:#FF5D5D; --streak:#FF9F1C; /* WP-2 bug-sweep (2026-08-12, dark-mode class-sweep): --good/--error are tuned as fill/border/accent colors (3:1 non-text bar) -- #2ECC71 on white is only 2.10:1 as small BODY TEXT, which is why .opt.right/.msg.ok/.pill.ok already reach past --good for a separate, darker literal (#1C8A4B) whenever the color labels actual text. These two tokens name that "text-safe" pairing so future call sites reuse it instead of reaching for --good/--error (or a fresh hardcoded hex) directly on a panel background. Values are the exact literals already proven throughout .msg.err/.msg.ok/.opt.right/.opt.wrong -- not new colors. */ --error-text:#B23A3A; --good-text:#1C8A4B; --radius:16px; --shadow:0 4px 14px rgba(42,36,64,.08); --font-display:"Baloo 2",system-ui,sans-serif; --font-body:"Nunito",system-ui,sans-serif; --font-mono:"JetBrains Mono",monospace; --belt: var(--brand); --belt-shade: var(--brand-shade); --belt-tint: var(--panel2); } /* P2-F: "Neon Dojo" night mode — grades 7-12 opt-in toggle (kid-home button), same token names so every component that already uses var(--x) just works. Applied via [data-theme="night"] on (app.js setTheme(), localStorage-persisted). */ [data-theme="night"]{ --bg:#0B0E1A; --panel:#151A2E; --panel2:#1E2540; --ink:#F0F2FF; --muted:#B3BBDA; /* WY-V3 W-V2-4: contrast bump (see :root note) */ --ink-soft:#B3BBDA; --panel2-ink:#BFE6CF; /* night halves of the two tokens added in :root above */ /* B24 (Ram-ruled): same white-on-brand-button issue as light theme -- #B98CFF measured ~2.5:1 with white text, well under 4.5:1. Darkened to #7A4DFF (4.85:1) -- still reads as the "neon violet" but passes; brand-shade left as the old --brand value so the button's 3D shadow still darkens further. */ --brand:#7A4DFF; --brand-shade:#5A35D9; --brand2:#00F5D4; --line:#2A3158; --good:#39D98A; --warn:#FFE347; --error:#FF5D7A; --streak:#FF9F1C; --error-text:#FF9DB2; --good-text:#5CE8A6; --shadow:0 4px 18px rgba(0,0,0,.45); } [data-theme="night"] .msg.err{background:#3A1622;color:#FF9DB2;border-color:#5A2233} /* WP-2 dark-sweep completion (sv136, Opus-caught sibling): C2 drag-drop mini injects its own light styles from minis.js (.c2-zone #fbfaff / .c2-chip #fff, no text colour) -> unreadable in night. These attribute-scoped overrides (higher specificity) repaint it in the night palette. */ [data-theme="night"] .c2-zone{background:var(--panel2);border-color:var(--line)} [data-theme="night"] .c2-zone.over{background:var(--panel);border-color:var(--brand)} [data-theme="night"] .c2-zone-sub,[data-theme="night"] .c2-bank-h{color:var(--muted)} [data-theme="night"] .c2-bank{background:var(--panel)} [data-theme="night"] .c2-chip{background:var(--panel2);color:var(--ink);border-color:var(--line)} [data-theme="night"] .c2-chip.placed.ok{background:#173a2c;border-color:var(--good)} /* SBF sweep (payments-wave fix round, 2026-08-14, same defect class as the WP-2 sweep just above): the "wrong category" sibling state was missed when .placed.ok got its night override — minis.js's own .c2-chip.placed.off{background:var(--coral-tint,#fdeee7);...} falls back to that light-pastel literal (--coral-tint is only ever defined inside readv2.js's OWN .readv2-scoped variables, not globally, so it's always undefined here), while the base .c2-chip{color:var(--ink)} override two lines up already resolves near-white in night — near-white text on a light pastel background. #3A1622 is this app's own established "coral, dark mode" literal (already used identically at readv2.js's --coral-tint:#3A1622 and at this same file's [data-theme="night"] .msg.err background, line 39 above) — reused here rather than inventing a new dark red; border-color mirrors .placed.ok's own var(--good)-for-"correct" pairing with var(--error)-for-"wrong". */ [data-theme="night"] .c2-chip.placed.off{background:#3A1622;border-color:var(--error)} [data-theme="night"] .msg.ok{background:#0F3324;color:#5CE8A6;border-color:#1C5A3E} [data-theme="night"] .msg.info{background:var(--panel2);color:var(--brand2);border-color:var(--line)} [data-theme="night"] .msg.warn{background:#3A2E0A;color:#FFE347;border-color:#5A4712} /* R11 bug fix 0e5110f8: email field visibility in dark mode */ [data-theme="night"] #pf-email{border-color:var(--line);color:var(--ink);background:var(--panel)} [data-theme="night"] .opt.right{background:#0F3324;color:#5CE8A6;border-color:var(--good)} [data-theme="night"] .opt.wrong{background:#3A1622;color:#FF9DB2;border-color:var(--error)} [data-theme="night"] .chatmsg.mine{background:#241D42} [data-theme="night"] .beltchip{color:#0B0E1A} [data-theme="night"] .celebrate-overlay{background:rgba(0,0,0,.65)} *{box-sizing:border-box} html,body{margin:0;padding:0} html{background:var(--bg)} body{ font-family:var(--font-body); background:var(--bg); color:var(--ink); min-height:100vh; display:flex; flex-direction:column; } h1,h2,h3,h4,.brand,.btn{font-family:var(--font-display)} a{color:var(--brand-shade);text-decoration:none} .topbar{display:flex;align-items:center;justify-content:space-between;flex-wrap:nowrap;gap:12px; padding:8px 20px;border-bottom:1px solid var(--line);position:sticky;top:0; background:rgba(255,255,255,.92);backdrop-filter:blur(8px);z-index:41; /* UXR2-3: auto-hide on scroll down, reappear on scroll up (all screen sizes). transform only — the sticky element keeps its flow box, so hiding causes NO layout jump. The left rail's own sticky offset (--hdr-h) is unchanged. */ transition:transform .26s ease;will-change:transform} body.topbar-hidden .topbar{transform:translateY(-100%)} @media (prefers-reduced-motion:reduce){.topbar{transition:none}} .brand{display:inline-flex;align-items:center;gap:9px;font-weight:800;font-size:20px;letter-spacing:.3px; color:var(--brand);cursor:pointer;border:0;padding:0;background:none;line-height:1;flex:none} .brand-logo{flex:none;display:block} .brand-word{font-family:var(--font-display);white-space:nowrap} .brand-4{color:#E06A00} @media(max-width:520px){.brand-word{font-size:16px}} .nav{display:flex;gap:10px;align-items:center} .nav .who{color:var(--muted);font-size:13px;margin-right:6px} /* ===== Gold Coins (Fable Brief v1, WP2): top-bar coin chip, kid role only ===== */ .coinchip{display:inline-flex;align-items:center;gap:5px;padding:6px 12px;border-radius:20px; font-size:13px;font-weight:800;color:#7A5A00;background:#FFF3CD;border:1px solid #FFE79E; white-space:nowrap;flex:none} .coinchip-ico{font-size:15px;line-height:1} [data-theme="night"] .coinchip{color:#FFE9A8;background:#4A3A08;border-color:#5A4712} @media(max-width:640px){.coinchip{padding:5px 9px;font-size:12px}} @media(max-width:380px){.coinchip .coinchip-ico{font-size:13px}} /* Tier-1 non-blocking "+N 🪙" toast — fades in near the coin chip, never blocks the lesson flow (celebrate-overlay's modal is reserved for the bigger quiz-band awards). Fixed-position so it floats free of whatever tab/route is on screen when a Tier-1 hook fires. */ .coin-toast{position:fixed;z-index:9996;background:#151A2E;color:#FFE9A8;font-weight:800;font-size:13px; padding:6px 12px;border-radius:12px;box-shadow:0 4px 14px rgba(0,0,0,.3); opacity:0;transform:translateY(-4px);transition:opacity .25s ease,transform .25s ease;pointer-events:none} .coin-toast.show{opacity:1;transform:translateY(0)} @media(max-width:640px){.coin-toast{right:12px !important;left:auto !important;top:64px !important}} /* Quiz-band coin line inside the existing celebrate() modal (never a new component) */ .celebrate-coins{font-size:16px;font-weight:800;color:#7A5A00;background:#FFF3CD; display:inline-block;padding:4px 14px;border-radius:999px;margin-top:8px} [data-theme="night"] .celebrate-coins{color:#FFE9A8;background:#4A3A08} /* ===== R1.3 C2 (WP2): the greeting strip INSIDE the header (Ram's mockup) ===== Avatar -> "Hi !" -> belt chip -> topics-mastered bar -> Invite a friend. It sits between the brand and the nav and takes the slack, so the nav stays hard right. Belt chip + bar are kid-only (app.js only fills them on a belt page). */ .hdr-hi{flex:1;min-width:0;margin:0 18px} /* inline-flex so the card hugs its contents: a parent/admin (greeting only) gets a small pill, a kid (chip + bar + invite) gets a wide one. Without this the empty card spanned the header. */ /* Ram design (shell hotfix): the greeting is a SLIM inline strip (no bordered card) so the top bar reads as one tidy row: avatar + "Hi " + belt chip + a slim inline progress meter. */ .hdr-hi-inner{display:inline-flex;align-items:center;gap:10px;flex-wrap:nowrap;max-width:100%; background:none;border:0;border-radius:0;padding:0} /* QA hotfix 2026-08-13: the button had no width/height, so a kid's CUSTOM avatar photo (an at width:100%/height:100% of this button) rendered at the photo's natural size — a huge picture over the whole header. Fixed circle + overflow clip bounds ANY content (emoji or photo) to icon size; flex centering keeps the emoji exactly as before. */ .hdr-avatar{width:34px;height:34px;font-size:22px;line-height:1;border:0;background:none;cursor:pointer;padding:0;flex:none;display:flex;align-items:center;justify-content:center;border-radius:50%;overflow:hidden} .hdr-hi-txt{display:flex;align-items:center;gap:8px;flex-wrap:nowrap;min-width:0} .hdr-greet{font-family:"Baloo 2",inherit;font-weight:800;font-size:17px;white-space:nowrap;overflow:hidden;text-overflow:ellipsis} .hdr-beltchip{white-space:nowrap} .hdr-progress{display:flex;align-items:center;gap:8px;flex:1;min-width:220px} /* a `display` rule beats the plain [hidden] attribute, so say it explicitly: a parent/teacher/admin (and a kid off a belt page) must NOT see an empty belt chip, an empty bar, or Invite a friend */ .hdr-beltchip[hidden],.hdr-progress[hidden],.hdr-invite[hidden]{display:none !important} .hdr-progress-bar{flex:1;height:9px;background:#e6e2f2;border-radius:6px;overflow:hidden} .hdr-progress-fill{height:100%;background:var(--belt,var(--brand,#6c4cf1));border-radius:6px;transition:width .4s} .hdr-progress-txt{font-size:12px;color:var(--muted);white-space:nowrap} [data-theme="night"] .hdr-progress-bar{background:#2c2740} @media(max-width:900px){ /* narrow: keep the greeting + chip, drop the bar and the invite button — the nav must not wrap away */ .hdr-hi{margin:0 10px} .hdr-progress,.hdr-invite{display:none !important} } @media(max-width:640px){ .topbar{flex-wrap:wrap} .hdr-hi{order:3;flex-basis:100%;margin:8px 0 0} /* B6 (08-12 rulings, settings-menu clipped at 375px): at these widths #nav (coin chip + name + the ⚙️ settings-menu-wrap) can outgrow the room left after brand, so flex-wrap above drops it to its own topbar row. justify-content:space-between only spreads a line's items apart when there are 2+ of them — a LONE wrapped item collapses to flex-start (the line's left edge), dragging .settings-menu-wrap left with it. The ⚙️ dropdown (app.js, WP-A-owned — injected style, not this file) anchors itself with right:0 relative to that wrap; once the wrap is no longer flush against the topbar's true right edge, right:0 still "resolves" but against a point near the LEFT of the screen, so the 220px-wide panel runs off the viewport's left edge — the reported clipping. Root-cause fix: pin #nav to its own line's right edge with an auto margin — a no-op when it still shares line 1 with brand (space-between already put it there) and the real fix when it wraps alone. */ #nav{margin-left:auto} } /* ===== Persistent shell + left belt-menu (kid routes only; hidden elsewhere) ===== */ /* body stays flex-column: header / shell / footer. flex:1 moves OFF .app ONTO .shell. */ .app{max-width:1000px;width:100%;margin:0 auto;padding:26px 20px 130px} /* was: flex:1;max-width:1000px;... — drop flex:1. bottom padding bumped to 130px (Wave 3 fix): the fixed #bug-fab (bottom:16px, ~85px tall) was landing directly on top of end-of-page action buttons (e.g. FakeOut step-1 "Next ->") on pages short enough that the last button naturally sits near the viewport bottom -- a real kid could not tap through it. Extra bottom clearance keeps the last on-page button above the fab on every route. */ .shell{flex:1;display:flex;align-items:flex-start;gap:16px;width:100%;max-width:1180px;margin:0 auto;position:relative} .shell:not(.with-menu) .app{max-width:1000px;margin:0 auto} /* menu hidden -> byte-for-byte old centered layout */ .shell.with-menu .app{max-width:none;flex:1;min-width:0;margin:0} /* menu shown -> #app fills the remaining width */ .belt-menu{flex:0 0 200px;align-self:flex-start;position:sticky;top:88px;z-index:1;max-height:calc(100vh - 100px);overflow-y:auto; background:var(--panel2);border:1px solid var(--line);border-radius:14px;padding:12px 8px;margin:12px 0} .belt-menu[hidden]{display:none} .bm-title{font-size:12px;font-weight:700;text-transform:uppercase;letter-spacing:.06em;color:var(--muted);padding:2px 10px 8px} .bm-belt{display:flex;align-items:center;gap:8px;width:100%;padding:9px 10px;border:0;border-left:4px solid transparent; border-radius:9px;background:transparent;font:inherit;font-size:14px;color:var(--ink);text-align:left;cursor:pointer} .bm-belt:hover{background:rgba(124,92,255,.10)} .bm-belt.on{background:var(--panel);font-weight:700;box-shadow:0 1px 4px rgba(0,0,0,.08)} .bm-belt.locked{opacity:.5} .bm-belt.locked:hover{background:transparent} .bm-dot{width:12px;height:12px;border-radius:50%;flex:0 0 auto;border:1px solid rgba(0,0,0,.15)} .bm-name{flex:1;min-width:0} .bm-badge{font-weight:800;margin-left:auto} .bm-sub{list-style:none;margin:2px 0 8px;padding:0 0 0 26px} .bm-item{display:block;width:100%;text-align:left;font:inherit;font-size:13px;color:var(--ink); background:transparent;border:0;padding:6px 10px;border-radius:8px;cursor:pointer} .bm-item:hover{background:rgba(124,92,255,.10)} .bm-item.on{background:var(--panel);font-weight:700} /* hamburger: desktop hidden; shown <=720px only when a kid menu is present */ .nav-burger{display:none;border:0;background:none;font-size:22px;line-height:1;color:var(--ink);cursor:pointer;padding:0;flex:none} @media(max-width:720px){ body.has-belt-nav .nav-burger{display:inline-flex} .shell{flex-direction:column} .belt-menu{position:fixed;top:0;left:0;bottom:0;z-index:40;flex:none;width:78vw;max-width:300px;margin:0; border-radius:0;transform:translateX(-100%);transition:transform .22s ease;padding-top:88px;box-shadow:0 0 40px rgba(0,0,0,.25)} .belt-menu[hidden]{display:block} /* keep in DOM for the slide; off-canvas transform hides it */ body.bn-open .belt-menu{transform:translateX(0)} body.bn-open::after{content:"";position:fixed;inset:0;z-index:39;background:rgba(0,0,0,.35)} .shell.with-menu .app{max-width:1000px;margin:0 auto} /* on mobile the drawer overlays; #app re-centers */ } [data-theme="night"] .belt-menu{box-shadow:0 0 40px rgba(0,0,0,.55)} /* ===== #18: desktop belt rail aligned to Ram's UI Shell Template — compact static top bar + a FLUSH-LEFT, AUTO-HIDE left rail + a target area. Keeps the aiquest palette; master template file is not touched. Only active >720px (the <=720px off-canvas drawer above stays as-is). ROBUSTNESS: the rail is an IN-FLOW STICKY column (never position:fixed), so it always begins BELOW the top bar — no overlap regardless of top-bar height (greeting card + TESTER banner). Its sticky offset uses --hdr-h, the LIVE top-bar height set by a ResizeObserver in app.js, so a pinned rail sits exactly under the sticky top bar when scrolling. The content column is the flex sibling (auto width); the ☰ button hides the rail (content reflows full-width); a far-left hover strip brings it back. ===== */ .rail-hotzone{display:none} @media(min-width:721px){ body.has-belt-nav .nav-burger{display:inline-flex;color:var(--brand)} .shell.with-menu{max-width:none;margin:0;padding:0;gap:0;align-items:stretch} .shell.with-menu .app{max-width:1000px;margin:0 auto;min-width:0;flex:1 1 auto} .shell.with-menu .belt-menu{position:sticky;top:var(--hdr-h,72px);align-self:flex-start; flex:0 0 220px;width:220px;margin:0;padding:12px 8px 24px;border:0;border-right:1px solid var(--line); border-radius:0;max-height:calc(100vh - var(--hdr-h,72px));overflow-y:auto;background:var(--panel2);z-index:5} body.rail-hidden .shell.with-menu .belt-menu{display:none} .rail-hotzone{position:fixed;left:0;top:var(--hdr-h,72px);bottom:0;width:16px;z-index:31} body.rail-hidden.has-belt-nav .rail-hotzone{display:block} /* keep the top bar to ONE compact row: a SLIM inline progress meter (not the full-width bar), and a belt chip that truncates rather than wrapping. Case File / Bug tracker / Invite now live in the rail. */ .hdr-progress{min-width:0;flex:0 0 auto;gap:6px} .hdr-progress-bar{width:64px;flex:none} .hdr-progress-txt{white-space:nowrap;font-size:12px} .hdr-beltchip{min-width:0;overflow:hidden;text-overflow:ellipsis;white-space:nowrap;flex:0 1 auto} } /* rail "Tools" utility group (Case File / Bug tracker / Invite), separated from the belt list */ .bm-util{margin-top:14px;padding-top:10px;border-top:1px solid var(--line)} .bm-util-item{display:block;width:100%;text-align:left} .loading{color:var(--muted);text-align:center;padding:60px} .foot{display:flex;justify-content:space-between;gap:12px;flex-wrap:wrap; padding:12px 22px;border-top:1px solid var(--line);color:var(--muted);font-size:12px} .foot-tag{opacity:.8;font-style:italic} /* S4 fix (Opus Wave sv138 inspection): groups .foot-tag + .foot-legal as ONE .foot flex child so the tag stays right-aligned against #foot-status exactly like before .foot-legal existed -- scoped to this wrapper only, .foot's own display:flex;justify-content:space-between is untouched. */ .foot-right{display:flex;align-items:center;gap:12px;flex-wrap:wrap} /* buttons — Duolingo-style 3D press: solid fill + darker bottom border that collapses on press */ .btn{display:inline-flex;align-items:center;justify-content:center;min-height:44px; border:0;cursor:pointer;font-weight:700;font-size:15px; padding:12px 20px;border-radius:14px;color:#fff;background:var(--brand); box-shadow:0 4px 0 var(--brand-shade);transform:translateY(0); transition:transform .08s,box-shadow .08s} .btn:hover{filter:brightness(1.04)} .btn:active{transform:translateY(4px);box-shadow:none} .btn.alt{background:var(--panel2);color:var(--ink);box-shadow:0 4px 0 var(--line)} .btn.ghost{background:transparent;border:1px solid var(--line);color:var(--ink);box-shadow:none} .btn.ghost:active{transform:none} .btn.sm{padding:8px 14px;font-size:13px;border-radius:11px;min-height:44px} /* R2 fix wave #7 (Bug_Review_SidV_R2 finding #7, "not able to choose true or false" / "reveal and finish button not responsive"): several mini-project pickers (minis.js C3 fact-check-trail True/False/Can't-tell, the privacy-photo Safe/Unsafe choice, and any other .btn.ghost toggle) add/remove an "on" class on tap to mark the selected choice, exactly like .chip.on / .ltab.on / .bm-item.on elsewhere in this file -- but NO rule ever styled bare .btn.on, so the click WAS registering in JS state (confirmed live: classList picks up "on") with ZERO visible change. A kid tapping True/False saw nothing happen and reasonably reported the button as unresponsive. This one rule covers every existing and future .btn.ghost "on"-toggle picker app-wide. */ .btn.ghost.on{background:var(--brand);color:#fff;border-color:transparent;box-shadow:0 2px 8px rgba(124,92,255,.35)} .btn:disabled{opacity:.5;cursor:not-allowed;transform:none} /* cards & layout */ .grid{display:grid;gap:16px} .grid.cols{grid-template-columns:repeat(auto-fit,minmax(220px,1fr))} .card{background:var(--panel);border:1px solid var(--line);border-radius:var(--radius); padding:20px;box-shadow:var(--shadow)} button.card{font:inherit;color:inherit;display:block;width:100%;cursor:pointer} button.card:disabled{cursor:not-allowed} .card h3{margin:.1em 0 .4em} :focus-visible{outline:3px solid var(--brand2);outline-offset:2px} /* f14: some browsers (older WebKit especially) paint their OWN default blue focus ring on a plain :focus even when a custom :focus-visible rule exists above — the standard fallback is to explicitly suppress the native ring whenever :focus-visible wouldn't have shown one anyway (i.e. a mouse click, not keyboard nav). Covers the quiz-feedback stars/chips and the read/lesson tab buttons, which is where testers saw the stray native outline. */ :focus:not(:focus-visible){outline:none} /* A11Y AUDIT FIX #3 (4/10 score): this rule used to be `.fb-stars .star:focus{outline:none}`, an UNCONDITIONAL :focus (not :focus-visible) suppression that stripped the keyboard focus ring off the quiz-feedback stars even for keyboard/AT users, overriding the correct :focus-visible rule above it. The f14 comment above already gives .fb-stars .star the right behavior generically (native ring hidden only on a non-keyboard :focus, :focus-visible ring shown otherwise) — this rule was pure regression and is removed rather than re-scoped. */ .muted{color:var(--muted)} /* A11Y AUDIT FIX #4: standard visually-hidden utility for aria-live regions that carry an announcement but have no sighted-UI reason to take up layout space (chat-log new-message announcer, etc. — the app had no such class before this pass). Clip-rect technique, not display:none/visibility:hidden, so assistive tech still reads it. */ .sr-only{position:absolute;width:1px;height:1px;padding:0;margin:-1px;overflow:hidden;clip:rect(0,0,0,0);white-space:nowrap;border:0} .hero{text-align:center;padding:40px 10px 10px} .hero h1{font-size:clamp(24px,6vw,34px);margin:.2em 0} .hero p{color:var(--muted);max-width:620px;margin:8px auto;font-size:clamp(14px,3.5vw,16px)} /* role picker */ .roles{display:grid;grid-template-columns:repeat(auto-fit,minmax(200px,1fr));gap:14px;margin-top:22px} .role{cursor:pointer;text-align:center;transition:transform .1s,border-color .1s} .role:hover{transform:translateY(-3px);border-color:var(--brand)} .role .emoji{font-size:34px} /* forms */ .form{max-width:420px;margin:0 auto} .form label{display:block;font-size:13px;color:var(--muted);margin:12px 0 4px} .form input,.form select,.form textarea{width:100%;min-height:44px;padding:11px 12px;box-sizing:border-box;border-radius:9px; border:1px solid var(--line);background:var(--panel);color:var(--ink);font-size:16px} .form textarea{min-height:auto} .form .row{display:flex;gap:10px}.form .row>*{flex:1;min-width:0} .msg{margin:12px 0;padding:10px 12px;border-radius:9px;font-size:13px} .msg.err{background:#FFEAEA;color:#B23A3A;border:1px solid #FFC9C9} .msg.ok{background:#E7F9EF;color:#1C8A4B;border:1px solid #BEEFD3} .msg.info{background:var(--panel2);color:var(--brand-shade);border:1px solid #D8D3FF} /* belt chips */ .belts{display:flex;gap:8px;flex-wrap:wrap;margin-top:10px} .beltchip{padding:6px 10px;border-radius:20px;font-size:12px;font-weight:700;color:#222} .beltchip.big{font-size:18px;padding:12px 22px} /* MAJOR-7 fix: Black Belt (belts.color = #4A4A4A, _content_sql/belts.0.sql) is the one belt dark enough that the shared #222 chip text fails AA -- measured 1.80:1 in day mode, and the night override below (#0B0E1A, meant for the other 6 light pastel belts) made it worse at 2.17:1. The 6 other belts (white/yellow/orange/green/blue/brown) are all light-to-mid pastels and clear >=6.7:1 against #222/#0B0E1A already (see Testing/_monday_nightfix_checks.cjs), so this is scoped to just the one belt color rather than reworked as a per-instance JS contrast calc (chips are rendered inline by many files outside this fix's scope: admin.js/teacher.js/parent.js/sis.js/lesson.js/ placement.js). Matches the inline `style="background:#4A4A4A"` belt.color renders unconditionally emit (case-insensitive, in case of future casing drift) and wins in BOTH themes: measured 8.13:1. */ .beltchip[style*="4A4A4A" i]{color:#F5F5F5} .msg.warn{background:#FFF6DA;color:#8A6B00;border:1px solid #FFE79E} /* placement quiz */ .qtext{white-space:pre-wrap;font-family:inherit;line-height:1.45} .qbar{height:8px;background:var(--panel2);border-radius:999px;margin:8px 0 14px;overflow:hidden} .qbar-fill{height:100%;background:var(--belt,var(--brand));transition:width .3s;border-radius:999px} .opts{display:flex;flex-direction:column;gap:10px;margin-top:14px} .opt{text-align:left;min-height:44px;padding:13px 16px;box-sizing:border-box;border-radius:14px;font-size:14px;cursor:pointer; background:var(--panel);border:2px solid var(--line);color:var(--ink);white-space:pre-wrap; box-shadow:0 3px 0 var(--line);transition:transform .06s,box-shadow .06s} .opt:hover{border-color:var(--brand)} .opt:active{transform:translateY(3px);box-shadow:none} .opt.selected{border-color:var(--brand);box-shadow:0 0 0 2px var(--brand) inset;font-weight:700} .opt:disabled{cursor:default;opacity:.95} .opt.reveal{border-color:var(--good);box-shadow:0 0 0 1px var(--good) inset} .opt.right{background:#E7F9EF;border-color:var(--good);color:#1C8A4B;font-weight:700} .opt.wrong{background:#FFEAEA;border-color:var(--error);color:#B23A3A} /* kid banner + knowledge map */ .kidbanner{display:flex;gap:16px;align-items:center;background:var(--panel); border:1px solid var(--line);border-radius:var(--radius);padding:18px 22px;box-shadow:var(--shadow)} .kb-emoji{font-size:44px} .kmrow{display:flex;gap:12px;align-items:center;margin-top:10px} .kmbar{flex:1;height:12px;background:var(--panel2);border-radius:6px;overflow:hidden} .kmbar-fill{height:100%;background:var(--belt,var(--brand));transition:width .4s;border-radius:6px} /* character picker chips */ .charlist{display:flex;gap:8px;flex-wrap:wrap;margin-top:10px;min-height:10px} .charchip{min-height:44px;display:inline-flex;align-items:center;padding:7px 14px;box-sizing:border-box;border-radius:20px;font-size:13px;cursor:pointer; background:var(--panel2);border:1px solid var(--line)} .charchip:hover{border-color:var(--brand)} .charchip.on{border-color:transparent;background:var(--brand);color:#fff} .chips{display:flex;gap:8px;flex-wrap:wrap;margin-top:6px} /* SBF sweep (payments-wave fix round, 2026-08-14): same missing-color defect shape as .mbtn/.mopt/.c2-chip.placed.off — .chip is rendered as a real