Re: Haptics CSS extension proposal

I must admit I strongly agree with you, here. A combinaison of ARIA (role, 
...) and existing CSS (appearence in particular) seems to be sufficient to 
describe nearly every possible situation defined in the current draft, and 
much more. After that, it's an OS task to understand those informations and 
apply the appropriate touch feedback (if needed), and not a browser task (at 
least, at my eyes).

But I didn't see any advance on the appearance property for a while, which 
can be a concern. Where are we in the standardisation process of that 
property ?

From: "Brad Kemper" <>
Sent: Monday, June 14, 2010 4:46 PM
To: "Daniel Glazman" <>
Cc: <>; "Gronholm Kim.1 (Nokia-D/Tampere)" 
<>; "Arthur Barstow" <>; "Lars 
Knoll" <>; "Ilkka Oksanen" <>; 
"Haverinen Henry (Nokia-D-Qt/Oslo)" <>
Subject: Re: Haptics CSS extension proposal

> On Jun 14, 2010, at 1:21 AM, Daniel Glazman wrote:
>> We have been researching tactile feedback (haptics) support for touch 
>> based web user interfaces, and we would like to propose the results of 
>> the research to be elaborated as web standards.
>> Tactile feedback is based on the sense of touch, for example vibrating 
>> the screen or giving a more realistic sense of a physical object when the 
>> user touches the UI.  As the physical feel of an element can be 
>> considered a part of its style, we're proposing to extend CSS to allow 
>> assigning the tactile feedback style to web elements. According to our 
>> studies the most convenient and natural way to specify haptic feedback is 
>> CSS. We also considered implementing haptics for web using WAI-ARIA but 
>> came to the conclusion that haptics is not (just) an accessibility 
>> feature although it can be used for improving accessibility as well.
>> So please check out our initial draft here:
>> and let us know if the members of the WG (or the CSS Community at large) 
>> are interested in contributing to the evolution of the spec.
>> Any comments would be most welcome and we'll be happy to answer all 
>> questions!
> My initial impression is that most of this (aside from 
> 'haptic-tap-strength') should be handled by the 'appearance' property, to 
> get a UA-appropriate representation of a button, checkbox, etc.. That 
> would also handle the :active state of the button, etc. automatically. The 
> state of the checkbox or deciding if something is a link or not would be 
> decided by the document language and DOM. 

Received on Monday, 14 June 2010 15:00:21 UTC