Overlay risk concerns the relationship between what a user sees and the operation they approve. On sensitive screens, assess platform signals together with explicit confirmation.
Evaluation approach
Evaluate obscured touches and sensitive-window behavior. Operating-system versions and UI components can affect the result.
Application example
Test obscured-window conditions on a new-recipient confirmation screen. Let the user close the overlay and retry.
Limits and considerations
An overlay is not necessarily malicious. Chat bubbles and accessibility tools can be legitimate.
Evaluate the context of a touch
A window drawn above an application is not inherently hostile. A mismatch between what a user sees and the touch the application receives, however, creates significant risk during sensitive operations. Assess the protection in the context of that screen's purpose.
Include normal notifications, assistive tools and manufacturer interfaces in the test matrix. Blanket screen obscuring or application termination can leave users stuck. Clearly showing that the operation did not complete and offering a safe retry produces a more understandable response.
Checks and decisions
- Select sensitive screens
- Test version differences
- Offer a usable resolution
Include accessibility and ordinary multi-window use in acceptance testing.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.