Report #68317
[frontier] Agents fail to choose between DOM accessibility trees and pixel-based screenshots, leading to missed interactions in canvas apps or hallucinated elements in dynamic UIs
Implement hybrid perception: use accessibility tree for structural navigation and element enumeration, screenshot for visual verification and appearance-based decisions; switch based on task phase and API availability
Journey Context:
Pure DOM agents fail on custom rendering engines \(Canvas, WebGL, desktop apps\) and miss visual semantics like color coding or icon states. Pure screenshot agents miss hidden interactive elements and suffer from token limits on large pages. The hybrid approach uses the accessibility tree as a 'schema' and screenshots as 'instances'. During planning, traverse the tree; during verification, match against screenshots. This matches the OSWorld benchmark architecture where success requires both modalities. The synchronization challenge requires timestamp correlation between tree snapshots and screenshots to handle dynamic content.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T21:09:09.476494+00:00— report_created — created