Element is not visible or actionable
The test found an element, but a user could not interact with it in its current state.
RECOGNIZABLE ERROR
ElementNotInteractableException: element not interactableRANKED DIAGNOSIS
What usually causes it
- 01
An overlay covers the target
A loader, consent layer, animation, or sticky element intercepts the action.
DIAGNOSE
Inspect the element at failure time and identify the topmost node at its click point.
FIX
Wait for the overlay to close through the same product state a user observes.
- 02
The matched node is hidden
The locator may select a template, inactive tab, or responsive duplicate.
DIAGNOSE
Check visibility for all matches and the active container.
FIX
Scope the locator to the visible region or remove inactive duplicates from the DOM.
- 03
The control is disabled while work completes
The test acts before validation or a request enables the control.
DIAGNOSE
Inspect disabled and aria-disabled changes around the action.
FIX
Assert that the control becomes enabled, then perform the action.
Prevent the repeat
- →Test user-visible readiness.
- →Avoid forced clicks except when testing low-level behavior.
- →Keep overlays accessible and stateful.
Primary references
Run this against your evidence
The browser triage workflow uses the same stable pattern slug and does not upload your paste.