A fictional ticket seller requires one checkbox that accepts the purchase terms, promotional messages and sharing with event partners.
Forced or bundled consentTicket checkoutCheckout
This is an original fictional comparison. It depicts no real business and is not a regulator finding, statutory category or legal safe harbour.
Ticket checkoutCheckout
Purchase terms combined with promotions
A fictional ticket seller requires one checkbox that accepts the purchase terms, promotional messages and sharing with event partners.
Potentially problematicAgree to continue
Agree to continue. Purchase, newsletters and partner offers use one required checkbox.. Selected: Accept all terms and offers. Continue with selected choices
Purchase, newsletters and partner offers use one required checkbox.
Accept all terms and offers
Continue with selected choices
→
Neutral alternativeConfirm purchase terms
Confirm purchase terms. The contract control is required; marketing and partner choices are separate and optional.. Complete purchase. Only task-relevant details requested. Purpose and refusal effect, expanded: The form explains why “Complete purchase” is requested and what happens if it is not used.
The contract control is required; marketing and partner choices are separate and optional.
Complete purchase
Only task-relevant details requested
Purpose and refusal effectThe form explains why “Complete purchase” is requested and what happens if it is not used.
Why the first version can mislead: The additional dependency controls access to the checkout goal. The panel states: “Purchase, newsletters and partner offers use one required checkbox.” Reviewers need to establish whether “Accept all terms and offers” is necessary for the selected task or pressures the user into a separable action. Refusing unrelated marketing appears to prevent completion of the requested transaction.
What a fairer design does: Keep contract acceptance distinct from optional marketing and partner permissions with unticked controls.
Show annotated differences (4)
Potentially problematic version
Purchase, newsletters and partner offers use one required checkbox.Why this state matters: The additional dependency controls access to the checkout goal. The panel states: “Purchase, newsletters and partner offers use one required checkbox.” Reviewers need to establish whether “Accept all terms and offers” is necessary for the selected task or pressures the user into a separable action. Refusing unrelated marketing appears to prevent completion of the requested transaction.
Continue with selected choicesReview prompt: What functional need makes “Accept all terms and offers” necessary for the ticket checkout goal, and can that need be met with less disclosure or commitment?
Neutral alternative
The contract control is required; marketing and partner choices are separate and optional.Fairer design: Keep contract acceptance distinct from optional marketing and partner permissions with unticked controls.
Purpose and refusal effect, expanded: The form explains why “Complete purchase” 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: “At least one consequence appears separable from the core function”?
Review questions (3)
What functional need makes “Accept all terms and offers” necessary for the ticket checkout goal, and can that need be met with less disclosure or commitment?
Which fields or permissions are required, what happens on refusal, and does the resulting state support this criterion: “At least one consequence appears separable from the core function”?
Could the stated purpose make this dependency genuinely necessary under the boundary “bundle with granular equivalent controls and no penalty for refusal”, and what product evidence would demonstrate that necessity?
Side-by-side ticket checkout interface showing “Agree to continue” and the clearer alternative “Confirm purchase terms”.Provenance: Original hypothetical ticket checkout example created for this library; no real business, product or interface is depicted.
Complete practice context
How this example relates to Forced or bundled consent
Access is conditioned on accepting optional or separable data uses, communications or permissions as one bundled choice. 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 news service presents one accept control for essential storage, audience analytics, advertising profiles and partner sharing, while access is blocked.
A fictional video service starts another clip when a user’s chosen twenty-minute limit is reached and hides the leave action behind a full-screen recommendation.
A fictional marketplace continuously inserts new products and removes pagination, position and viewed-item markers while promotional prompts follow the shopper.