Trick Questions

The Trick Questions pattern operates within the “Sneaking” and “Interface Interference” domains. It employs deliberate linguistic obfuscation, convoluted phrasing, and syntactic traps (most notably, double negatives) to deceive the user into answering a question in a way they did not intend. This pattern frequently appears in consent management platforms, registration forms, and checkout flows. A classic implementation involves a series of checkboxes where the semantic polarity abruptly shifts—for instance, checking the first box means “I want to receive emails,” while checking the adjacent, visually identical box means “I do not want to share my data.” This exploits the user's reading fatigue and expectation of consistent interface logic, weaponizing cognitive load to induce automated, erroneous interactions.

1

Structural Label-Input Semantic Mismatch

Trick Questions: Structural Label-Input Semantic Mismatch

Newsletter subscription

You are currently subscribed. Manage your preference below.

Subscribed
Condition 1: Structural Label-Input Semantic Mismatch
Given
To establish a structural baseline for Trick Questions, the algorithm examines <input>, <select>, and <button> elements for a mismatch between their structural aria-label or associated <label> text and the NLP-inferred action semantics. The feature triggers if a form element's programmatic label () maps to one action (e.g., “Opt out”) while its visual label text () maps to its semantic opposite (e.g., “Stay subscribed”), creating a structural double-bind:
2

Affordance-Consequence Mismatch

Trick Questions: Affordance-Consequence Mismatch

Welcome bonus

New customers get a $10 bonus credited to their account after signup.

Condition 2: Affordance-Consequence Mismatch
Given
To capture the manipulation of standard UI heuristics, we define as the physical affordance of checking a box, which psychologically aligns with acceptance, inclusion, or addition. We then map the actual backend consequence of that action to using semantic classification. Defining as the domain of rejection or exclusion (e.g., “do not send” or “opt-out”), the feature triggers if the positive physical action of checking the box explicitly maps to a negative or exclusionary intent. This reversal of standard UI conventions acts as a trap for users who quickly skim text:
3

Syntactic Obfuscation via Multiple Negations

Trick Questions: Syntactic Obfuscation via Multiple Negations

You’ve been selected for an exclusive offer!

As a valued customer, you qualify for Premium Gold Access — a $49.99/mo value, available to you for the introductory price of just $0.00 for the first 30 days. After your trial, your plan auto-renews at full price unless you cancel.

Condition 3: Syntactic Obfuscation via Multiple Negations
Given
To quantify linguistic deception, we extract the text label associated with a boolean input node (e.g., a checkbox) and generate its syntactic dependency tree using an NLP parser. By isolating —the discrete count of negation modifiers (e.g., “not”, “un-”, “prevent”, “refuse”) directly acting upon the primary action verbs—the feature triggers if the system detects an unnatural stacking of negations (such as double or triple negatives). This structural convolution is deliberately designed to overwhelm the user's cognitive parsing capacity: