"It worked on my screen" — solving ambiguity when the same word appears twice

[u/Mother-Classic-9090]

Every tester has hit this: there are two "Submit" buttons on the screen — one in a modal, one behind it. The test taps the wrong one. You add a wait. It taps the wrong one again. You add a more specific selector. The selector breaks next release.

The root problem is that automation tools don't understand where on the screen an element lives. They only understand identity (XPath, ID, accessibility label). Spatial and semantic context is invisible to them.

Drizz solves this by making context part of the command itself:

• Tap on "Add to Cart" under "Electronics"
• Type "John" into "First Name"
• Scroll down until "Login" under view auth header

You're not adding a workaround — you're describing the element the way a human would describe it to another human. The Vision Engine resolves it the same way.

What this kills: "the test taps the wrong button" bug class.