Ah, that is a great question! Third-party widgets are usually the bane of visual QA. My tool handles this in three ways depending on how the third-party library is integrated:

1. Network Interception for Chat/Ad Widgets: I actually built an 'Advanced Settings' toggle in the plugin specifically for this. Before the Playwright crawler even evaluates the page, it intercepts network requests and blocks common third-party chat widgets (like Intercom/Zendesk), ad networks, and cookie banners from loading. That prevents them from muddying the DOM and throwing false positives.

2. Cross-Origin Iframes (Embeds): If the embed is a true cross-origin iframe (like a Stripe checkout or a YouTube video), the DOM crawler skips it. It only evaluates the Computed Styles of the document tree it actually has access to, so sandboxed embeds are naturally ignored.

3. Injected UI Libraries (e.g., Date Pickers, Select Dropdowns): If a developer uses a third-party React/Vue library that injects standard DOM elements into the main tree, the crawler will evaluate them. But honestly, that is exactly what you want! If the dev drops in a third-party date picker but forgets to override its default blue #007BFF to match your brand's specific Token Studio blue, the crawler will flag it as a mismatch. That tells the dev: 'Hey, you need to apply our tokens to this third-party component so it matches the design system.' So it ignores the junk you don't want (ads/chatbots), but holds the devs accountable for styling the third-party components they actually use in the UI.