Re: user interface/user education

For our Tracker purposes, I believe the following are the existing related issues:

ISSUE-172: How should user agents be required to provide information about DNT?

ISSUE-143: Activating a Tracking Preference must require explicit, informed consent from a user

In case it's useful to have an organizing issue regarding user education, I've also created:

ISSUE-194: How should we address user education about DNT?

(I'm not entirely sure why ISSUE-163 was created, but that would presumably also be resolved by this discussion. Also, Alan's proposal might speak to limitations desired on extensions or other software not the traditional browser; relevant issues are ISSUE-153 and ISSUE-177.)

Those issues have existing proposals we may wish to review side-by-side, including:


Hope this helps,

On Apr 3, 2013, at 8:19 AM, Alan Chapell <> wrote:

> Colleagues - 
> Please see the proposed language for User interface and user education. I've attached a redlined version to help highlight the differences between this version and the current editor's draft. I believe this is on the docket for discussion on NEXT week's call on April 10. I look forward to the discussion.
> 5. User Agent Compliance
> A user agent MUST offer a control to express a tracking preference to third parties. The control MUST communicate the user's preference in accordance with the [TRACKING-DNT] recommendation and otherwise comply with that recommendation. A user agent MUST NOT express a tracking preference for a user unless the user has given express and informed consent to indicate a tracking preference.
> While we do not specify how tracking preference choices are offered to the user or how the preference is enabled, each implementation MUST follow the following user interface guidelines:
> 1.     The User Agent is responsible for determining the user experience by which a tracking preference is enabled. For example, a user might select a check-box in their user agent's configuration, or install an extension or add-on that is specifically designed to add a tracking preference expression so long as the checkbox, extension or add-on otherwise follows these user interface guidelines;
> 2.     The User Agent MUST ensure that the tracking preference choices are communicated to users clearly and conspicuously, and shown at the time and place the tracking preference choice is made available to auser;
> 3.     The User Agent MUST ensure that the tracking preference choices accurately describe DNT, including the parties to whom DNT applies, and MUST make available via a link in explanatory text where DNT is enabled to provide more detailed information about DNT functionality.
> Non-Normative:
> The User Agent plays a key role in enacting the DNT functionality. As a result, it is appropriate for the User Agent to play an equally key role in describing DNT functionality and educating users about DNT in order for this standard to be meaningful.
> While the user interface guidelines do not specify the exact presentation to the user, they are intended to help ensure that users understand their choices with respect to DNT. For example, outlining the parties (e.g., First Parties, Service Providers, Third Parties) to whom DNTapplies and using language that a reasonable user is likely to understand is critical for ensuring that users are in position to provide their informed consent to a tracking preference.
> Moreover, as DNT functionality is complex, it is important that User Agents educate users about DNT, including but not limited to offering a clearly described link that takes the user to additional information about DNT functionality. For example, given that some parties may chose not to comply with DNT, it would be helpful for browsers to educate users about how to check the response header and/or tokens to see if a server is responding with a “public commitment” of compliance.
> Finally, recognizing that DNT settings may be set by non-browser User Agents acting in violation of the user interface guidelines, the browsers should take reasonable steps to ensure that DNT settings are valid.
> <DNT functionality and user education April 3 2013.docx>

Received on Wednesday, 10 April 2013 01:09:41 UTC