W3C home > Mailing lists > Public > public-apa@w3.org > September 2016

FW: Vibration API rough draft

From: Drake, Ted <Ted_Drake@intuit.com>
Date: Wed, 14 Sep 2016 16:00:46 +0000
To: "public-apa@w3.org" <public-apa@w3.org>
Message-ID: <6D63FE59-B6BE-4075-8D57-9B8F363AF241@intuit.com>
For today’s meeting.
Ted

From: Ted Drake <Ted_Drake@intuit.com>
Date: Monday, September 12, 2016 at 10:36 AM
To: Janina Sajka <janina@rednote.net>
Subject: Vibration API rough draft

Hi Janina

What are your thoughts on the following additions to the Vibration API? https://www.w3.org/TR/2016/PER-vibration-20160818/



Accessibility considerations

The Vibration API allows applications to send a silent notification to a user in response to an event. While the vibration is a powerful and effective medium of notification, there are users that need to disable and/or control their device’s vibration element at a global level. For instance, a person with Attention Deficit Disorder may block vibrations to avoid distractions. Also, a person with Epilepsy may have an application that is detecting vibrations for tracking symptoms.

For these reasons, the user agent SHOULD inform the user when the API is being used and provide a mechanism to disable the API (effectively no-op), on a per-origin basis or globally.

------

Note
For example, an implementation might abort the algorithm because no vibration hardware is present, the user has set a preference indicating that pages at a given origin should never be able to vibrate the device, the user has disabled vibration at a global level, or an implementation might cap the total amount of time a page may cause the device to vibrate and reject requests in excess of this limit.


Received on Wednesday, 14 September 2016 16:01:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 14 September 2016 16:01:19 UTC