W3C home > Mailing lists > Public > public-privacy@w3.org > January to March 2016

Re: [vibration] privacy consideration PING comments

From: Lukasz Olejnik (W3C) <lukasz.w3c@gmail.com>
Date: Sat, 27 Feb 2016 19:43:41 +0100
Message-ID: <CAC1M5qp4gHUiQ2=NzwAc8MW-s1DnAG5xRozf_HZC_AWnftUNaw@mail.gmail.com>
To: Chaals McCathie Nevile <chaals@yandex-team.ru>
Cc: Frederick Hirsch <w3c@fjhirsch.com>, W3C Device APIs WG <public-device-apis@w3.org>, "public-privacy (W3C mailing list)" <public-privacy@w3.org>
> 6. Applications might want to give indications when vibration is in use.
>> Definitely, there SHOULD be an option to indicate it...
> I don't think that's right. There is an indication that vibration is in
> use: the device is *moving*.

It is, if the user is monitoring this device at that very moment, and also
including your considerations below (thanks!).

> So there are a couple of more interesting things:
> When a foregrounded page has permission for vibration, there should be an
> indicator. The same applies to a backgrounded page - I think something like
> the audio playing thing that browsers have started doing would be useful.
> Indeed, it would copy a familiar iconic paradigm from the world of phones
> which have had vibrators for more than two decades (and therefore is
> unlikely to have any IPR issues outstanding).
> There are plenty of use cases for a backgrounded page having vibrate
> permission - the simple one being the same as the phone, that it is less
> obtrusive as a way of requesting attention, and works without actually
> seeing the device.
> And finally, of course it is important that all such notifications or
> status indicators are actually *accessible* - have sufficient contrast, are
> announced to screen readers / magnifiers, etc. While this is something that
> browsers should be doing, rather than technically part of the spec, it is
> worth noting that in the privacy considerations and mitigations, and
> tracking whether we have acieved the goal. A spec that provides theoretical
> accessibility but is implemented consistently in a way that discriminates
> against users with disabilities really isn't good enough.

This is, in essence, somewhat similar to what I was thinking about for long
now. I do hope to make the PDF public asap, definitely I'll post it to the


> cheers
> Chaals
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
>  chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Saturday, 27 February 2016 18:44:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:49:32 UTC