How to automate Flutter and canvas apps when the DOM offers no elements

Developer tools like find and read_page fail entirely on Flutter Web and canvas-rendered apps because their interfaces are drawn as pixels on a single canvas, leaving the DOM and accessibility tree effectively empty. A developer used Claude to automate the Rive animation editor by relying solely on screen coordinates, since no element-based alternative exists in such environments. Key techniques include waiting for the viewport width to stabilize before clicking, zooming into canvas regions to read painted text, and verifying every click visually through a screenshot before proceeding. Standard double-click actions can misfire in canvas editors, so firing two rapid single clicks in one batched action is recommended to reliably trigger hierarchy interactions. The author notes the procedure — stabilize, zoom-read, evidence-check, rapid double-fire — is slower than human interaction but prevents cascading errors from undetected missed clicks.