Dead end
Refund form loops after submission
A fictional refund form accepts every field, then returns to the first screen with “Something went wrong” and no saved state or alternative route.
Individual HTML example · Obstruction
Cancellation confirmation changes no account state
A fictional service shows “Cancellation complete” but returns the user to an active-plan dashboard and continues renewal without a receipt or status event.
This is an original fictional comparison. It depicts no real business and is not a regulator finding, statutory category or legal safe harbour.
Cancellation confirmation changes no account state
A fictional service shows “Cancellation complete” but returns the user to an active-plan dashboard and continues renewal without a receipt or status event.
Cancellation complete. The plan remains active and no confirmation record exists.. Blocking step: upcoming. Obscured outcome: upcoming
Plan ends on 30 September. The account status, renewal setting and receipt all reflect the completed request.. Completion step: upcoming. Recorded outcome: upcoming. Request recorded: Download confirmation
Why the first version can mislead: The route adds avoidable effort between the user’s stated intention and completion. In this subscription account example, the obstacle is: “The plan remains active and no confirmation record exists.” Evidence should show whether the alternative remains usable and whether “Download confirmation” reaches the represented state. The represented outcome is not reached, leaving the subscriber exposed to another charge.
What a fairer design does: Update the account state atomically, display the effective date and issue a durable receipt that support can verify.
Show annotated differences (4)
Potentially problematic version
- The plan remains active and no confirmation record exists.Why this state matters: The route adds avoidable effort between the user’s stated intention and completion. In this subscription account example, the obstacle is: “The plan remains active and no confirmation record exists.” Evidence should show whether the alternative remains usable and whether “Download confirmation” reaches the represented state. The represented outcome is not reached, leaving the subscriber exposed to another charge.
- Obscured outcome: upcomingReview prompt: How many steps, waits and channel changes separate “Back to account” from the completed subscription account outcome?
Neutral alternative
- The account status, renewal setting and receipt all reflect the completed request.Fairer design: Update the account state atomically, display the effective date and issue a durable receipt that support can verify.
- Request recorded: Download confirmationReview prompt: Count steps, waits, offers and channel changes through final confirmation; where does the route meet “Repeated execution cannot reach that outcome under controlled conditions”?
Review questions (3)
- How many steps, waits and channel changes separate “Back to account” from the completed subscription account outcome?
- Count steps, waits, offers and channel changes through final confirmation; where does the route meet “Repeated execution cannot reach that outcome under controlled conditions”?
- Measure the same task through the clearest available route: does the effort difference persist once “validation error caused by invalid fixture input” is accounted for?
Complete practice context
How this example relates to Dead end
A consumer-favourable route cannot reach its represented outcome and instead loops, stalls or loses progress. This is a design and research taxonomy for learning and evidence review, not a statutory offence label or an automatic finding that an interface is unlawful.
The full guide explains inclusion and exclusion criteria, potential harms, fairer design, evidence questions and separate Australian legal information layers. The example page isolates one scenario so it can be shared and discussed without reproducing the complete library on one page.
Continue comparing
Related examples
Open this example
Account deletion obstruction
Deactivation presented as deletion
A fictional platform labels a control “Delete account”, but the confirmation only hides the profile and leaves data and reactivation available indefinitely.
Account deletion obstruction
Deletion buried behind an unsupported ticket
A fictional retailer places account deletion behind six help pages and requires a support ticket containing an order number even for users who never ordered.
Sources and provenance for this example
Evidence base
Sources
- An Ontology of Dark Patterns KnowledgeGray et al.; ACM CHI 2024 · Secondary · checked 2026-09-14 · DOI 10.1145/3613904.3642436; arXiv:2309.09640
- Competition and Consumer Amendment (Unfair Trading Practices) Act 2026Federal Register of Legislation · Primary · checked 2026-09-14 · C2026A00064