Consequences Explained Before Agreement

Test Procedure from the W3C Draft

Quoted from the provision's informative document, informative/guidelines/policy-and-protection/risk/consequences-explained-before-agreement.md. It is the group's own procedure, not an editorial testing guide.

W3C Working Group Status

The draft records no open editors' notes on this provision.

W3C Threads on This Provision

1 GitHub thread carrying 0 comments, fetched from w3c/wcag3 by the tracker. Titles, numbers and states are the threads' own.

Nobody has read these threads and written up the positions yet, so only the threads themselves are listed.

• #677 Drop “privacy” and/or “security” as categories for consequences open 0 comments · updated 2026-05-26

WCAG 2.2 Criteria That Map Here

From this site's reviewed WCAG 2.2 → WCAG 3 map. The map is an interpretation, not a W3C mapping: W3C has not published one yet.

W3C Raw Source Text

Verbatim from guidelines/groups/policy-and-protection/risk/consequences-explained-before-agreement.md · informative document: informative/guidelines/policy-and-protection/risk/consequences-explained-before-agreement.md

Legal, financial, privacy, and security consequences are provided before finalizing an agreement.

:::applies-when
- Entering an agreement is required.
:::