W3C home > Mailing lists > Public > public-device-apis-log@w3.org > March 2018

[sensors] Improve guidance on UI for user consenting

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Mon, 05 Mar 2018 13:31:49 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-302300706-1520256708-sysbot+gh@w3.org>
anssiko has just created a new issue for https://github.com/w3c/sensors:

== Improve guidance on UI for user consenting ==
In a [response](https://github.com/w3ctag/design-reviews/issues/207#issuecomment-369926278) to the [DAS WG's TAG review summary](https://github.com/w3c/sensors/issues/299#issuecomment-369924348), the following question was brought up and would benefit from a revisit:

>dbaron [commented on Dec 8, 2017](https://github.com/w3ctag/design-reviews/issues/207#issuecomment-350125076)
>Let me restate annevk's question another way: How do you ask the user a question that is both concise and accurate enough that the user's consent is meaningful? Will the user understand, for example, that accurate accelerometer, gyroscope, and magnetometer measurements might reveal all the text that the user types while they're being measured, or what sorts of activities the user is doing, and perhaps their location (based on mapping a pattern of movement to paths that exist on a map)?

The DAS WG's current position on the issue is that such UI aspects (including related strings, UI elements, UX flow) are considered implementation details. The specifications in review reflect this position.

However, given this issue was brought up suggests implementers might benefit from more elaborate informative guidance, so I'd ask the group to look into opportunities to further clarify related informative guidance in the related specification(s).

Please view or discuss this issue at https://github.com/w3c/sensors/issues/352 using your GitHub account
Received on Monday, 5 March 2018 13:31:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 5 March 2018 13:31:55 UTC