Inconsistent Activation Behavior

Id InconsistentActivationBehavior
Summary Controls of the same type respond inconsistently to touch or gesture input
Severity N/A
Category Touch Interaction
Affects Resource files and Kotlin and Java files
Implementation Manual testing - requires context about expected behavior and user flows, which lint cannot infer.

Symptom

UI components don't respond to activation gestures on their primary interactive area, requiring users to target secondary or adjacent elements to trigger the expected action.

Rationale

Creates unpredictable interaction patterns for assistive technology users who expect consistent activation behavior, forcing them to explore and discover alternative interaction methods which increases cognitive load and task completion time.

GitHub issues under this tag