The Consent Banner on Mobile: Where the Reject Button Goes to Hide

A user opens a site on their phone. The banner fills the screen. Accept is a large button in the center. Reject is a small link at the bottom, below the fold, in gray text. The user taps Accept, not because they agreed, but because it was the only button they could reach. The consent was not freely given. It was designed.

The reject button goes to hide

Mobile is where banner dark patterns concentrate, because the screen is small and the design choices are stark. Accept gets the button. Reject gets the link. Accept gets the first layer. Reject gets the second, behind a Manage preferences button that most users never tap. Accept gets the thumb zone. Reject gets the bottom of the screen, below the fold, in text that is barely readable. Each choice is small. Together they are a banner that collects consent by making refusal hard, and the CNIL fines named exactly this pattern: Google fined 325 million euros and Shein fined 150 million euros in September 2025, for banners that made acceptance easy and refusal hard. The patterns are named, measured, and no longer a gray area.

The footer banner that hides consent is the same failure at desktop scale: placement read as intent, and hidden consent read as no consent. On mobile the placement is more consequential, because the screen leaves nowhere to hide a second layer.

What prominence means on a 390-pixel screen

GDPR Article 7(3) says withdrawing consent must be as easy as giving it, and the EDPB guidelines extend the same logic to the choice itself: refusing has to be as easy as accepting. On a phone that means the same size, on the same layer, requiring the same effort. If Accept is a button and Reject is a link, they are not equal, because a link is smaller, harder to tap, and visually weaker. If Accept is on the first layer and Reject is two clicks deep, they are not equal, because most users never reach the second layer. If Accept is in the thumb zone and Reject is at the bottom of the screen, they are not equal, because the thumb decides. The test is not whether a determined user can refuse. It is whether an ordinary user, on a phone, in a hurry, can refuse as easily as they can accept.

The patterns that cost money

Pre-ticked boxes, because consent has to be a positive action and a ticked box is a default. A banner that blocks content until the user accepts, because consent given under pressure is not freely given. A Continue button that accepts everything without saying so. A reject path that asks the user to confirm, twice, whether they are sure. Each one has been fined, and each one is still common, because the patterns convert. The conversion is the point: a banner that makes refusal hard gets more acceptances, and the acceptances are worthless, because they were not freely given and they will not survive a complaint.

Test it on the phone, not the emulator

Open the site on a real phone, with a real thumb, on the smallest screen you support. Try to refuse. Count the taps. Measure the size of the reject button against the accept button. If refusal takes more effort than acceptance, the banner fails, and the fix is not a redesign. It is a second button, the same size, on the same layer, in the same place. The emulator will not tell you what a thumb will, and the complaint will not come from an emulator.

Frequently asked questions

Have regulators actually fined anyone for banner design?

Yes, and they have. In September 2025 France's CNIL fined Google 325 million euros and Shein 150 million euros for cookie-banner dark patterns. The fines named the patterns: accept made easy, reject made hard, and consent that was not freely given. The numbers are the enforcement record, not a warning.

What does equal prominence mean on a mobile banner?

The same size, on the same layer, requiring the same effort. If accept is a button and reject is a link, they are not equal. If accept is on the first layer and reject is two clicks deep, they are not equal. The test is whether a user can refuse as easily as they can accept.

Are pre-ticked consent boxes allowed?

Pre-ticked boxes, because consent has to be a positive action. A box that is already ticked is not consent. It is a default, and the EDPB guidelines are explicit that silence or inaction does not constitute consent.

How do I test my mobile banner?

Test it on a real phone, with a real thumb, on the smallest screen you support. If the reject button is hard to reach, hard to see, or on a second layer, it fails. An emulator will not tell you what a thumb will.