Obstruction · Australia
Dead end
Dead end is a working label for this design mechanism: A consumer-favourable route cannot reach its represented outcome and instead loops, stalls or loses progress. This is editorial implementation guidance for Australian journeys, not a finding of unlawfulness. From 1 July 2027, a similar interface is relevant to ACL section 28B only if the complete consumer-connection, manipulation or unreasonable-distortion and actual-or-likely-detriment test is met. Current ACL rules require a separate assessment.
- Family
- Obstruction
- Also known as
- Journey stages
Definition
What is this pattern?
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.
How it works
A consumer-favourable route cannot reach its represented outcome and instead loops, stalls or loses progress. A route represents that a request can complete but then loops, errors or changes no durable state, without a working recovery path or confirmation record.
Warning signs
- The interface represents or reasonably implies that the outcome is available.
- Repeated execution cannot reach that outcome under controlled conditions.
- A business-favoured route remains functional or the failure systematically burdens the alternative.
Potential harms
- A customer may abandon a valid request after repeating work without a way to complete or recover.
- The represented outcome is not reached, leaving the subscriber exposed to another charge.
Learn by comparison
What does this look like?
These fictional examples make the design mechanism easier to recognise. They do not depict a real company and do not establish that an individual interface is unlawful.
Illustrative example 1 · 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.
Potential consumer harm: A customer may abandon a valid request after repeating work without a way to complete or recover.
Illustrative example 2 · 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.
Potential consumer harm: The represented outcome is not reached, leaving the subscriber exposed to another charge.
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.
Submit refund request. The form loops to an empty first screen without identifying a fix.. Order number: Enter order number. Refund reason: Enter refund reason. Requested amount: Enter requested amount. Try again
We could not submit the request. Entered details are saved and a supported fallback is offered.. Saved order number: Enter saved order number. Saved refund reason: Enter saved refund reason. Saved requested amount: Enter saved requested amount. Resume or contact support. Purpose and refusal effect, expanded: The form explains why “Resume or contact support” is requested and what happens if it is not used.
Why the first version can mislead: The route adds avoidable effort between the user’s stated intention and completion. In this order support example, the obstacle is: “The form loops to an empty first screen without identifying a fix.” Evidence should show whether the alternative remains usable and whether “Resume or contact support” reaches the represented state. A customer may abandon a valid request after repeating work without a way to complete or recover.
What a fairer design does: Preserve entered data, explain the specific error and provide a tested fallback route with a reference number.
Show annotated differences (4)
- The form loops to an empty first screen without identifying a fix.Why this state matters: The route adds avoidable effort between the user’s stated intention and completion. In this order support example, the obstacle is: “The form loops to an empty first screen without identifying a fix.” Evidence should show whether the alternative remains usable and whether “Resume or contact support” reaches the represented state. A customer may abandon a valid request after repeating work without a way to complete or recover.
- Try againReview prompt: How many steps, waits and channel changes separate “Try again” from the completed order support outcome?
- Entered details are saved and a supported fallback is offered.Fairer design: Preserve entered data, explain the specific error and provide a tested fallback route with a reference number.
- Purpose and refusal effect, expanded: The form explains why “Resume or contact support” is requested and what happens if it is not used.Review prompt: Which fields or permissions are required, what happens on refusal, and does the resulting state support this criterion: “The interface represents or reasonably implies that the outcome is available”?
Review questions (3)
- How many steps, waits and channel changes separate “Try again” from the completed order support outcome?
- Which fields or permissions are required, what happens on refusal, and does the resulting state support this criterion: “The interface represents or reasonably implies that the outcome is available”?
- Measure the same task through the clearest available route: does the effort difference persist once “General outage affecting all paths” is accounted for?
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)
- 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?
- 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?
What is a fairer alternative?
Provide a functional completion route, preserve progress, and surface recoverable errors equally across options.
Legal and information status
How Australian law may apply
A consumer-favourable route cannot reach its represented outcome and instead loops, stalls or loses progress. A route represents that a request can complete but then loops, errors or changes no durable state, without a working recovery path or confirmation record. These harms describe a review risk, not an automatic legal conclusion. Australian section 28B commences on 1 July 2027 and requires its complete, context-specific test. Existing ACL provisions remain a separate current-law assessment.
ACL section 28B, inserted by the 2026 Act
Possible risk indicator
In account management and cancellation journeys, the dead end mechanism may warrant review where it manipulates a consumer or unreasonably distorts the decision environment and causes, or is likely to cause, detriment. The obstruction label and an interface similarity do not establish a contravention; the complete section 28B test, scope, facts and evidence must be applied from 1 July 2027.
Dark-pattern research taxonomy
Editorial analysis
The cited research sources support this working pattern within the obstruction family. It is editorial implementation guidance, not an Australian statutory category, regulator finding or legal safe harbour.
Evidence layers and open questions
Applicable law, enforcement records, policy preparation, stakeholder input, editorial analysis and unknown future details remain visibly distinct.
Final Act mappingEditorial implementation guidance
This editorial practice label is not itself an express statutory prohibition. Apply the complete provision and its scope to the facts.
Possible general-test applicationCommences 1 July 2027
ACL section 28B, inserted by the 2026 Act: In account management and cancellation journeys, the dead end mechanism may warrant review where it manipulates a consumer or unreasonably distorts the decision environment and causes, or is likely to cause, detriment. The obstruction label and an interface similarity do not establish a contravention; the complete section 28B test, scope, facts and evidence must be applied from 1 July 2027.
Existing ACLCurrent enforcement
Existing ACL provisions continue to apply on their own elements before and after commencement. The 2027 provisions must not be applied early.
Verified enforcement contextCurrent enforcement
No named pattern-specific enforcement example is asserted on this page. Existing ACL analysis remains fact-specific and separate from the 2027 provisions.
RegulationsRegulation pending
Later regulations may affect specified exclusions, matters or exceptions. That uncertainty does not postpone a core enacted rule unless the provision itself depends on prescription.
Regulator implementation materialGuidance pending
Government funding and parliamentary material anticipate regulator education and guidance. No dedicated final ACCC implementation guide is treated here as published.
Journey and evidence recommendationsEditorial implementation guidance
Provide a functional completion route, preserve progress, and surface recoverable errors equally across options. This is editorial portal guidance, not a statutory duty, regulator safe harbour or compliance certificate.
Context matters
Context and boundary cases
- The interface represents or reasonably implies that the outcome is available.
- Repeated execution cannot reach that outcome under controlled conditions.
- A business-favoured route remains functional or the failure systematically burdens the alternative.
- Boundary to test: General outage affecting all paths
- Boundary to test: validation error caused by invalid fixture input
- Boundary to test: clearly unavailable option
When a similar design can serve a legitimate purpose
- General outage affecting all paths
- validation error caused by invalid fixture input
- clearly unavailable option
Operational review
What teams should review
- Teams
- How many steps, waits and channel changes separate “Try again” from the completed order support outcome?
- Which fields or permissions are required, what happens on refusal, and does the resulting state support this criterion: “The interface represents or reasonably implies that the outcome is available”?
- Measure the same task through the clearest available route: does the effort difference persist once “General outage affecting all paths” is accounted for?
- 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?
Evidence to retain
- Annotated account management and cancellation screenshots at each responsive breakpoint
- The complete state sequence before, during and after the consumer decision
- Design-system component, content, default and configuration records for the reviewed release
- Operational records substantiating price, availability, timing and eligibility claims
- Usability, accessibility, reversal, complaint and support evidence relevant to consumer impact
- A dated product and legal review record identifying evidence, uncertainties and release decisions
Legal map and implementation tools
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
- Competition and Consumer Act 2010, including Schedule 2: Australian Consumer LawFederal Register of Legislation · Primary · checked 2026-09-14 · C2004A00109
- Unfair trading tricks and traps to be bannedTreasury Ministers · Primary · checked 2026-09-14
- Inquiry into the Competition and Consumer Amendment (Unfair Trading Practices) Bill 2026Senate Economics Legislation Committee · Primary · checked 2026-08-09