The EKY agent's sitewide inventory (qa_inventory.xlsx, 542 items) flagged two defects beyond the EKY page: Defect 1, an invisible or empty Call Now button on 323 pages and posts (157 pages, 166 posts), root cause stated as .sa-sidebar-cta * { color:#fff !important } overriding .sa-phone-link; Defect 2, an empty video embed gap on Northern KY (page id 45085) and Western KY (page id 45081). Sam asked one question: is this a real problem? No fixes were authorized; he gated any change behind his greenlight. Goal of this session was verification only.
I did not touch the live site. I confirmed the canonical design intent from the sa-template-reference skill: white text inside .sa-sidebar-cta is intentional because the CTA sits on a dark Visible Depth gradient (linear-gradient(0deg,#000,#0B212D)). So white text is not by itself a bug.
I inspected live shipped HTML and CSS via curl across a 25-page sample plus targeted pages, and traced the full cascade.
Key finding: the site has TWO Call Now button patterns.
.sa-phone-link{background:#fff} CSS rule is dead/unused on these pages. Examples confirmed: amazon-delivery-vehicle-accidents, car-accident-injuries/cervical-spine, car-accident-injuries/chest-injuries. These are FALSE POSITIVES in the inventory.<a class="sa-phone-link"> with no inline style, relying on CSS. Two sub-cases: base background #0b212d (dark) renders fine (example northern-kentucky); base background #fff (white) renders broken.Defect 1 CONFIRMED REAL on bullitt-county-personal-injury-lawyer. Cascade traced: .sa-phone-link{background:#fff;color:#0b212d!important} at source position ~74560, then .sa-sidebar-cta *{color:#fff!important} at ~77151 (later, equal specificity, both !important) wins and forces text to white. Background stays #fff. Result: white text on a white button (orange border still visible). The phone number is unreadable.
Conclusion on count: the 323 figure is NOT trustworthy. It appears keyed on CSS-rule or wildcard presence, not on the actually rendered button. The true affected set is only class-based .sa-phone-link pages with a #fff base background and no inline override. A rendered-button classifier crawl across the ~1,194 sitemap URLs is needed to produce the real list.
Defect 2 (video gap, NKY and WKY): both pages have NO actual video embedded. The only youtube reference is a WP Rocket lazyload artifact (.rll-youtube-player); the single iframe is the GTM tag. No empty video container was found in static HTML. Whether the absence produces a visible gap needs a rendered-DOM or screenshot check. High confidence there is no video; low confidence it is a visible defect.
mcp workspace web_fetch timed out at 180s on the first page; switched to curl in the sandbox with -L (pages 301-redirect to /practice-areas/ slugs), which worked reliably. Coarse grep classifier (counting any .sa-phone-link background match) over-counted because it matched dead CSS and could not see inline-styled buttons; replaced with a Python parser that extracts the actual rendered sidebar CTA anchor and its inline styles.
Report findings and hold all fixes for Sam's greenlight, per his explicit gate and the destructive-on-live-system rule for CSS. Recommended fix approach: a single higher-specificity global rule that beats the wildcard everywhere, e.g. .sa-sidebar-cta a.sa-phone-link{background:linear-gradient(0deg,#000,#0b212d)!important;color:#fff!important;border:2px solid #f89c22!important}. One reversible change fixes all Pattern-B #fff pages and is harmless to inline-pill pages. Caveat to verify first: these styles ship per-page, so stylesheet load order must be confirmed before relying on a global override (global rule must load after page-level styles to win).
No files created or modified. Live verification only. Reference skills used: sa-template-reference (references/sidebar.md confirms white text is required on dark gradient). qa_inventory.xlsx referenced by the EKY agent was NOT present in this session's mounted workspace; could not be opened here.
Defect 1 confirmed real on at least one live page (bullitt-county). Defect mechanism fully understood. The exact affected page list is unknown pending a classifier crawl. Defect 2 is unconfirmed as a visible problem. No remediation applied. Awaiting Sam's decision on next step.