A fictional shop displays account creation as the only button and places guest checkout inside a collapsed paragraph titled “Other information”.
Obstructed alternativeRetail basketCheckout
This is an original fictional comparison. It depicts no real business and is not a regulator finding, statutory category or legal safe harbour.
Retail basketCheckout
Guest checkout hidden behind account copy
A fictional shop displays account creation as the only button and places guest checkout inside a collapsed paragraph titled “Other information”.
Potentially problematicSave time with an account
Save time with an account. The visible action creates an account; the guest path is buried in unrelated copy.. Selected: Create account. Not selected: Continue as guest
The visible action creates an account; the guest path is buried in unrelated copy.
Create account
Continue as guest
→
Neutral alternativeChoose a checkout route
Choose a checkout route. Guest checkout and optional account creation appear together.. Not selected: Continue as guest. Not selected: Create account. Choice consequences, expanded: The consequence of selecting “Continue as guest” is displayed beside the option.
Guest checkout and optional account creation appear together.
Continue as guest
Create account
Choice consequencesThe consequence of selecting “Continue as guest” is displayed beside the option.
Why the first version can mislead: The route adds avoidable effort between the user’s stated intention and completion. In this retail basket example, the obstacle is: “The visible action creates an account; the guest path is buried in unrelated copy.” Evidence should show whether the alternative remains usable and whether “Continue as guest” reaches the represented state. A viable alternative becomes materially harder to discover than the business-preferred account route.
What a fairer design does: Present guest and account routes together with clear consequences and comparable interaction effort.
Show annotated differences (4)
Potentially problematic version
The visible action creates an account; the guest path is buried in unrelated copy.Why this state matters: The route adds avoidable effort between the user’s stated intention and completion. In this retail basket example, the obstacle is: “The visible action creates an account; the guest path is buried in unrelated copy.” Evidence should show whether the alternative remains usable and whether “Continue as guest” reaches the represented state. A viable alternative becomes materially harder to discover than the business-preferred account route.
Not selected: Continue as guestReview prompt: How many steps, waits and channel changes separate “Create account” from the completed retail basket outcome?
Neutral alternative
Guest checkout and optional account creation appear together.Fairer design: Present guest and account routes together with clear consequences and comparable interaction effort.
Choice consequences, expanded: The consequence of selecting “Continue as guest” is displayed beside the option.Review prompt: Capture every peer option, its default state and visual prominence; do those states support “The options address the same decision”?
Review questions (3)
How many steps, waits and channel changes separate “Create account” from the completed retail basket outcome?
Capture every peer option, its default state and visual prominence; do those states support “The options address the same decision”?
Measure the same task through the clearest available route: does the effort difference persist once “Different actions with genuinely different complexity” is accounted for?
Side-by-side retail basket interface showing “Save time with an account” and the clearer alternative “Choose a checkout route”.Provenance: Original hypothetical retail basket example created for this library; no real business, product or interface is depicted.
Complete practice context
How this example relates to Obstructed alternative
A relevant alternative within the current decision is hidden, blocked or made materially harder than the business-favoured action. 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.
A fictional platform labels a control “Delete account”, but the confirmation only hides the profile and leaves data and reactivation available indefinitely.
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.