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

Re: Vibration API rough draft

From: Janina Sajka <janina@rednote.net>
Date: Wed, 14 Sep 2016 15:06:07 -0400
To: "Hakkinen, Mark T" <mhakkinen@ets.org>
Cc: Katie Haritos-Shea GMAIL <ryladog@gmail.com>, "White, Jason J" <jjwhite@ets.org>, "'Drake, Ted'" <Ted_Drake@intuit.com>, "public-apa@w3.org" <public-apa@w3.org>
Message-ID: <20160914190607.GD2789@opera.rednote.net>
Hi, Mark:

The APA call participants have asked me to initiate a Call for Consensus
(CfC) requesting the addition of an Assccessibility Impact" section to
the Vibration API specification based on the draft Ted Drake provided:

http://lists.w3.org/Archives/Public/public-apa/2016Sep/0017.html

Because we're fairly late with this request, we actually need to turn
this around fairly quickly. The Advisory Council is requested to vote on
advancing this specification by end of day Sunday.

I'm not seeing an actual objection in your comments below. Is that
incorrect? If you think it would be helpful, I would be willing to
incorporate a portion of your remarks in our CfC.

Janina

Hakkinen, Mark T writes:
> Vibration seems generally associated with notifications and not as an augmenting modality for enhancing interaction with touch interfaces.  While our past research here at ETS (and elsewhere) has focused on vibration as a component of touch exploration for graphical information, we have also prototyped the use of the vibration API to add feedback to controls, to highlight syllabic boundaries in words, etc.
> 
> One can be certain that as Web developers discover the use of Vibration beyond notification, we see a variety of creative applications.  Some will likely enhance usability and accessibility, and others will complicate it.
> 
> I’m happy to discuss this further at TPAC.
> 
> Mark
> 
> From: Katie Haritos-Shea GMAIL [mailto:ryladog@gmail.com]
> Sent: Wednesday, September 14, 2016 12:46 PM
> To: White, Jason J <jjwhite@ets.org>; 'Drake, Ted' <Ted_Drake@intuit.com>; public-apa@w3.org
> Subject: RE: Vibration API rough draft
> 
> Actually this is a really good point Jason. However, it really should not  lengthy at all….
> 
> ​​​​​
> 
> 
> 
> * katie *
> 
> Katie Haritos-Shea
> Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
> 
> Cell: 703-371-5545 | ryladog@gmail.com<mailto:ryladog@gmail.com> | Oakton, VA | LinkedIn Profile<http://www.linkedin.com/in/katieharitosshea/> | Office: 703-371-5545 | @ryladog<https://twitter.com/Ryladog>
> 
> From: White, Jason J [mailto:jjwhite@ets.org]
> Sent: Wednesday, September 14, 2016 12:44 PM
> To: Drake, Ted <Ted_Drake@intuit.com<mailto:Ted_Drake@intuit.com>>; public-apa@w3.org<mailto:public-apa@w3.org>
> Subject: RE: Vibration API rough draft
> 
> The Vibration API can also be highly valuable for improving the accessibility of graphical material by enabling the generation of vibratory haptics on devices that support it. Researchers here at ETS and investigators elsewhere have successfully explored the effectiveness of vibratory haptics as a means of providing non-visual access to diagrams, for example.
> 
> I think you should note the benefits of the Vibration API for conveying information, in addition to its potentially distracting effects.
> 
> For purposes of a haptics-based Web application, the user shouldn’t have to enable the Vibration API whenever the application is loaded – we don’t want users to be prompted whenever a page loads that makes use of the API. I think the recommended UA implementation should be a configuration setting rather than a prompt, or at the very least, a prompt that manipulates a stored value retained between sessions.
> A leading accessibility researcher with considerable expertise in haptics, Mark Hakkinen, plans to be at TPAC next week, as do I. We’re both available, if desired, to discuss the Vibration API in connection with the work mentioned above.
> 
> 
> ________________________________
> 
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
> 
> 
> Thank you for your compliance.
> 
> ________________________________
> 
> ________________________________
> 
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
> 
> 
> Thank you for your compliance.
> 
> ________________________________

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Wednesday, 14 September 2016 19:06:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 14 September 2016 19:06:39 UTC