Sem opção de rejeição ou rejeição suprimida

Porque isto importa

As orientações do EDPB exigem que rejeitar seja tão fácil quanto aceitar. Se Reject estiver escondido, visualmente desvalorizado ou abaixo do fold, o consentimento pode não ter sido dado livremente.

Como verificar manualmente

1. Open the first-layer banner on common desktop and mobile breakpoints.
2. Check whether Reject is visible without extra clicks or scrolling.
3. Compare button size, contrast, opacity, and placement against Accept.

Causas típicas

• CMP template only exposes Accept on the first layer.
• Custom CSS hides or de-emphasizes the Reject control.
• Reject is available only in a second-layer preference center.

Correção no GTM

1. Configure the CMP template to show Accept and Reject on the first layer.
2. Keep both actions visible without extra clicks.
3. Validate button prominence using equal font size, contrast, and placement rules.

Correção em WordPress ou plugins CMP

1. Enable the reject or decline button in plugin settings.
2. Adjust theme CSS so Reject is visible above the fold on desktop and mobile breakpoints.
3. Avoid custom CSS that lowers reject contrast or hides the control.

Correção genérica para developers

1. Display Reject in the same layer and viewport area as Accept.
2. Use equivalent visual weight: size, contrast, opacity, and spacing.
3. Avoid patterns requiring extra navigation for rejection.

.cmp-btn-accept,
.cmp-btn-reject {
  min-height: 44px;
  font-size: 14px;
  opacity: 1;
}

Como confirmar que a correção funciona

• Verify Reject is visible and clickable above the fold on both desktop and mobile.
• Click Reject and confirm optional tags do not fire.
• Run a re-scan and confirm the reject-flow issue is resolved.