/* AUTO-GENERATED from qa-fixes-responsive.css via rtlcss. Do not edit by hand.
   Loaded only on AR pages by inc/i18n-setup.php.
*/
/* ──────────────────────────────────────────────────────────────────
 * qa-fixes-responsive.css — 2026-05-07
 * Closes a ~197px horizontal-overflow bug seen on every WP-rendered
 * page at viewport widths ≤ 480px. Audit: every URL in /, /pricing/,
 * /demo-request/, /onboarding/, /contractors/, /eor/ overflows by
 * exactly 197px at 375px width. Live doesn't.
 *
 * Root cause: Webflow's `.trusted-badges-bg-track` (and similar
 * decorative marquee tracks) are `position: absolute; width: 200%`
 * for a parallax-scroll effect. Live's CSS contains them via
 * overflow:hidden on a parent that isn't selecting on staging
 * (likely a class-chain mismatch).
 *
 * The simplest reliable fix is to clip horizontal overflow at body
 * level on small screens, which contains the decorative track without
 * affecting vertical scroll, sticky positioning, or modal overlays.
 * ────────────────────────────────────────────────────────────────── */

@media (max-width: 991px) {
    html, body {
        overflow-x: hidden;
        max-width: 100vw;
    }
}

/* Belt-and-braces: known-wide decorative tracks contained explicitly so
   layout-changes inside the carousel section don't escape via a missed
   parent. NOTE: do NOT add .swiper-container or .swiper-wrapper here —
   Swiper.js needs overflow-visible on the wrapper to translateX slides
   into view. The clipping happens at the OUTER section level instead.
   2026-05-07: removed swiper-* selectors after they broke home-page
   carousels (integrations, country slider, testimonials). */
.new_landing_page_badges,
.trusted-badges-bg,
[class*="vertical-cards-container"],
[class*="-section"]:has(> .trusted-badges-bg-track) {
    overflow-x: hidden;
}

/* =============================================================================
   Designer Review 2 — 2026-05-08
   EX30 — Homepage feature sections must stack vertically on mobile.
   The designer flagged that one feature section isn't stacking at ≤768px.
   Without browser access to identify which, the rule covers all likely
   2-col / multi-col homepage feature blocks. Webflow's .w-row already
   stacks via .w-col-stack at ≤767px in their own CSS, but compound
   selectors elsewhere can override that — these forcing rules win.
   ============================================================================= */
@media (max-width: 768px) {
    .home-vertical-cards .hero_double_section_mask.w-row,
    .home-solution-cards .grid-4-cols,
    .home-go-global .double-section-hero-container.w-row,
    .home-support .double-section-hero-container.w-row,
    .home-support .hero_double_section_mask.w-row,
    [class*="feature-section-grid"],
    [class*="feature-grid"] {
        display: flex !important;
        flex-direction: column !important;
        grid-template-columns: 1fr !important;
    }
    .home-vertical-cards .w-col,
    .home-solution-cards .w-col,
    .home-go-global .w-col,
    .home-support .w-col,
    .grid-4-cols > * {
        width: 100% !important;
        max-width: 100% !important;
        flex: 0 0 100% !important;
    }
}