Next #W3CWorkshop will be looking at how to manage access to sensitive features in #Web #browsers! w3.org/Privacy/permissions-w… - hosted by @Qualcomm, September 18-19, in #SanDiego, CA 🇺🇸
This tweet is unavailable
1
1
2
Browsers provide access to more and more features that cannot be granted to any random #Web site. One way to gate this access is by asking permission from the #user. But getting the user consent is not necessarily easy...
1
First, how informed is that consent? Very little if the request gets made when the page has hardly finished loading, or if the underlying risks are hard to grasp.

Jul 16, 2018 · 4:44 PM UTC

1
Second, the well-known dialogue fatigue means that bombarding #user with permission requests makes each decision less meaningful. This leads to situations where a feature gets removed from sight because it creates too much noise, as illustrated by
Firefox 🔥
 @firefox
30 Apr 2018
Chances are you don't want push notifications from most (any??) sites. . . go ahead and block sites from even asking: mzl.la/2DXfLzI
1
1
And there is an art of how and when to ask for permission, in which Web app developers need to play their part - @mulligan shared his best practices on the matter a while ago: techcrunch.com/2014/04/04/th…
1
On the #Web, this is made all the more complicated as pages can be embedded in other pages, making the context of the permission request harder to understand for end #users.
1
All these considerations and more will be part of what workshop participants will discuss in September. If you want to contribute to the conversation, please submit an expression of interest or a position paper before August 17 - @w3c workshops are open to all, do not hesitate!