) .cc-btn 14px -> 14px frozen (font:inherit) .cc-title 16px -> 37.24px runaway .cc-body 14px -> 28px runaway documentElement.scrollWidth 1425 -> 16546 against a 1440px viewport Everything below is gated behind body[class*="pojo-a11y-resize-font-"]. With no size selected - and again after Reset - this file contributes ZERO computed differences. Verified with a full-DOM diff (font-size, line-height, position, top/bottom/left/right, display, width, max-width, overflow, flex-wrap, white-space, margin on every element in ) at 375 / 900 / 1440 on the home page (desktop hero AND the mobile #detailModal), both template-privacy pages, the blog post, 404 and search: empty on all of them. THE TOOLBAR IS NOT TOUCHED -------------------------- #pojo-a11y-toolbar is a SIBLING of the page content, not a child, so every generic rule carries :not(:where(#pojo-a11y-toolbar *)). :where() has zero specificity, so the exclusion is free. Verified: the toolbar item span still goes 12.8px -> 25.6px, and .pojo-a11y-toolbar-title / -item / -link stay at 16px / 16px / 32px at every step, identical with and without this file. SPECIFICITY ----------- The gate is html body[class*="pojo-a11y-resize-font-"][class] = (0,2,2). The second [class] is deliberate: it lifts every rule here one class-column above the plugin's own body.pojo-a11y-resize-font-200 h1 span = (0,1,3), so this file wins on specificity alone and never depends on the order in which WordPress happens to print the two stylesheets. SOURCES MIRRORED 1:1 -------------------- assets/css/mains.css base (loaded from header.php) assets/css/mobiles.css @media (max-width: 767px) - the theme's ONLY breakpoint bootstrap.rtl.min.css unstyled h1-h6 (responsive heading sizes) contact-form-7/includes/css/styles.css .wpcf7-not-valid-tip cookie-consent.js (#cc-style) .cc-* banner + settings modal inline