Why cookie consent is usually an implementation question
This page is designed to give high-level, practical guidance only. Exact obligations can depend on how your website operates, the technologies it uses, the audiences it serves and the way the underlying business model works in practice.
Cookie consent is often discussed as though it were a design choice, but the bigger issue is how the website actually behaves. If tracking technologies or similar tools are being used, the public-facing wording, the choices offered to users and the technical behaviour all need to align.
That is why many businesses feel comfortable because a banner exists, while the underlying controls are weaker than they look. Scripts may fire earlier than expected, categories may be too broad, choices may not be as clear as they appear or third-party tools may have been added without proper review.
The safest high-level mindset is not to ask whether a banner looks modern. It is to ask whether the implementation, public messaging and actual website behaviour still match each other.
If you want the broader view rather than a banner-only question, start with the high-level compliance check page or use the compliance estimator.