Recognition signals
- A declined request returns without a meaningful change in context.
- Dismissal is temporary while acceptance is treated as durable.
- Repeated interruption makes normal use or task completion harder.
Dark-pattern family · 1 patterns
Repeatedly interrupts or asks the user to take a business-favoured action after the user has declined, deferred or ignored it.
This family groups related interface mechanisms for learning and journey review. It is not a legal category and does not make every matching interface unlawful. Start with the mechanism, then examine the complete decision, audience, effect and EU rule actually within scope.
Recognition framework
Trace the same request across sessions and screens after decline, dismissal and non-response. Measure frequency, interruption cost and whether the service remembers the choice. A single contextual reminder is different from a system designed to make refusal temporary while acceptance remains durable.
A later reminder may be relevant after a material context change or an explicitly chosen snooze period. Review should distinguish that case from immediate repetition, unrelated triggers and prompts that progressively remove the refusal route.
EU legal and policy context
A family name helps teams compare interface mechanisms. It is not an EU legal category, and similarity to an example does not establish that a current rule has been infringed or that a future Digital Fairness Act will use the same label.
The UCPD and any relevant sector instrument require their own scope, conduct, information and likely-effect assessment. The complete journey and evidence matter; a taxonomy match is only a prompt to investigate.
The Commission is preparing a legislative DFA initiative and currently places a proposal in Q4 2026. That planning date is indicative, and no published proposal yet creates a family-specific duty.
The call for evidence discusses possible policy responses to digital fairness concerns. Options, consultation questions and stakeholder submissions are not Commission proposals or present obligations.
Final instrument form, scope, definitions, thresholds, enforcement, transition and application remain unknown until primary legislative text is published and validated.
Journey coverage
Review the state before the decision, the controls and information available at that moment, the immediate result and any later account or billing consequence. Journey links below show where this family appears in the published taxonomy; they do not imply that every product or every stage contains the mechanism.
1 related pattern
Signup is where access, identity, permissions and first-run choices meet. A useful review follows the user from the promise made before registration through every required field, default, consent request and first-use screen. The question is not whether signup is persuasive, but whether people can understand what is necessary, what is optional and what each control will do before they commit.
Open the journey guide →1 related pattern
Checkout concentrates price, add-ons, urgency, identity and the final payment action. Review should begin with the state carried into the basket and finish only when the order, receipt and account state agree. A control that appears clear in isolation can still be misleading when a fee arrives late, a removed item returns or the final button does more than its label predicts.
Open the journey guide →Pattern directory
Each detail page contains two fictional interface comparisons, practical recognition and exclusion criteria, a fairer alternative, review questions and a legal-status map that keeps editorial taxonomy separate from current law and the announced DFA process.
A business-favoured request repeatedly interrupts the user after decline, dismissal or non-response without a durable way to stop it. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See visual examples: Repeated promptingEvidence-led workflow
Evidence base