Report #76205
[frontier] Why screenshot-based agents hallucinate on dynamic UIs while DOM-based agents fail on custom rendering
Use accessibility tree \(DOM/AX\) as primary signal with screenshot as validation layer, not source of truth
Journey Context:
Screenshot agents fail when pixels change \(animations, loading states, responsive layouts\). DOM agents fail on canvas/WebGL. The pattern is hierarchical: AX tree for structure, vision for semantic verification when text is ambiguous. Most agents default to screenshots for 'ease' but this creates brittle pixel dependencies; accessibility trees provide resolution-independent, semantic anchors that survive styling changes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T10:29:55.964244+00:00— report_created — created