Date: 2026-06-15.
Surface: read-only investigation. No files, WordPress content, registry content, or live systems were modified.
Inspected live SA Element Registry preview for element 18 at https://sa-element-registry.onrender.com/preview/18 and live whiplash page at https://aguiarinjurylawyers.com/car-accident-injuries/whiplash/.
Confirmed element 18 is live as version 2026-06-15b. The registry preview source and computed browser result still use the old trust-list marker path: .sa-sidebar-optb-poppins .sa-sidebar-trust li uses position:relative and padding-left:28px, while .sa-sidebar-optb-poppins .sa-sidebar-trust li .ck uses position:absolute; left:4px; top:8px.
Confirmed the sa-element-registry skill guardrail says sidebar trust-list checkmarks should not use position:absolute, negative margins, transforms, or left offsets that can overlap wrapped text. It requires grid or flex alignment with a fixed marker column and wrapping text column, for example grid-template-columns: 24px minmax(0, 1fr).
On the whiplash page, the same old component CSS appears in the source. There is also a page-level attempted fix with id sa-sidebar-trust-grid-sitewide-fix-2026-06-15 that would set .sa-sidebar-trust li to flex and .sa-sidebar-trust li .ck to position:static. However, that fix is delivered inside a WP Rocket delayed script wrapper and the style tag is empty in the raw source. Firecrawl browser computed-style inspection after waiting showed the sidebar list present with 9 trust items, li display:flex but .ck still computed as position:absolute, left:4px, top:8px, display:block, width:16px. That keeps the overlap risk active.
The likely root cause is the absolute-positioned visible span marker, not the suppressed ::before pseudo marker. The relevant selectors are .sa-sidebar-optb-poppins .sa-sidebar-trust li, .sa-sidebar-optb-poppins .sa-sidebar-trust li .ck, .sa-sidebar.sa-sidebar-optb-poppins .sa-sidebar-trust li::before, and the attempted fix selectors .sa-sidebar-trust li and .sa-sidebar-trust li .ck in the delayed script.
Patch the winning component or live CSS so the marker and text use a single layout path: grid or flex, fixed marker width, real gap, no absolute marker positioning. After patching, QA both the registry preview and whiplash page at mobile and desktop widths. Confirm computed styles show .ck position:static, list rows display:grid or display:flex, no ::before marker content, and long rows such as 1,000+ Five-Star Google Reviews wrap without the checkmark touching the first character.
The requested read-only investigation is complete. No approval was needed because no edits were made. Remaining work is the actual patch and post-patch visual/computed-style QA.
A future agent can start from the selectors above and should avoid adding a second marker path. The durable fix should live where element 18 is generated or in a non-delayed CSS path that outranks the old component CSS. If the registry source is patched, verify the live preview and then apply the same change to any live page copy or shared CSS path that still carries the old absolute .ck rule.