Accessibility as a core constraint In the public sector, accessibility is not optional. It is a regulatory requirement, just like GDPR compliance. With tarteaucitron, this has always been taken seriously. The banner and management panel are designed to be keyboard-navigable, readable, and understandable. This work is largely driven by the open-source community. Several contributors with … Read more
Certification and real obligations Certification is not a legal requirement. It is imposed by some private actors, often themselves subject to consent. This creates confusion between regulatory compliance and commercial requirements. A questionable closed ecosystem Making CMPs pay for certification by actors within the same ecosystem raises obvious neutrality issues. This model favors connections over … Read more
Shared legal constraints Most CMPs look alike because they must comply with the same legal constraints. Visible banners, explicit choices, and service-level management have become standard. Consent rate pressure On top of that comes strong pressure to maximize acceptance rates. Dark patterns and confusing wording are now common. A different approach On tarteaucitron, the average … Read more
Starting with what exists Before even talking about banners or buttons, it is necessary to know what is actually loaded on the site. A CMP does not block “everything”. It blocks what it knows and what is properly configured. Implementation defines compliance GDPR compliance relies on strict technical implementation. Loading the CMP after the scripts … Read more
A deliberately technical definition From a strictly technical perspective, a CMP is a tag manager. Its role is not to collect data, but to condition the loading of third-party scripts. The rule is simple: until the user gives consent, a script must not be executed. An interface at the core This technical logic is exposed … Read more