Why this wireframe works | Cookie banner bar
It does not get in the way of reading
The bar appears at the edge of the screen, so visitors can start reading right away. Its shape alone shows that the site works before anyone chooses.
Accept and Reject look the same
Giving the two buttons the same size and look means either choice takes the same effort, and nobody hesitates before pressing.
Details go behind “Customize”
Leaving category switches out of the bar keeps it to a single line. Only people who want to fine-tune their choice open a separate screen.
Common mistakes | Cookie banner bar
Reject is a small text link
When only Accept is a large button and Reject is a small link inside the text, rejecting becomes harder. Make both of them buttons of the same shape.
The bar hides content or buttons
A fixed bar that sits on top of form buttons or the focused element makes them impossible to use. Add bottom padding equal to the bar’s height to the content.
The bar keeps coming back after a choice
If the choice is not saved, the bar appears on every page. Save the choice and stop showing the bar.
The text never says what cookies are for
“This site uses cookies” alone gives people nothing to decide with. State the purpose, such as analytics or advertising, in one line.
FAQ | Cookie banner bar
Should the bar go at the top or the bottom of the screen?
The bottom interrupts reading less. Another option is to place it above the header without fixing it; it is then the first thing on the page, so screen reader users notice it more easily. Either way, the two buttons still carry equal weight.
Can I show just an “OK” button?
With only an accept button, there is no way to reject. If you are asking for consent, rejecting must take the same effort. If you are only informing people about cookies and data sent to outside services, without asking for consent, word the notice so that is clear.
Is a cookie consent bar always required?
Whether you need consent, and how much you need to explain, depends on the cookies you use, the data sent to outside services, and the rules where your users are. Examples include GDPR and the ePrivacy Directive in the EU, US state laws such as CCPA/CPRA, and Japan’s rules on sending user data to third parties. This pattern is an example of how to build the screen; for legal decisions, check with a specialist as needed.











