RE: rangeslider, a "Tale of Two Thumbs"

My take is that  the semantics, need and usage for it  should be determined
first before one expends time  figuring keyboard behavior.


In truth the more I see  some of these widgets in use I really wonder where
the good old HTML controls are lacking. I agree tree menus and some such are
not available in HTML but I do not see the point of coding an image with an
onclick / mouseover event (and CSS effects) to resemble a button for
instance. (I cannot find any pointers in the ARIA roadmap and associated
docs). I see applications designed with regular buttons in one place and  an
image coded as above in another within the same application. So I wonder who
is gaining from this. Certainly keyboard access is a loser. 


Sailesh Panchang
Accessibility Services Manager (Web and Software)
Deque Systems Inc. (
11130 Sunrise Valley Drive, Suite #140,
Reston VA 20191
Phone: 703-225-0380 (ext 105)


From: [] On Behalf
Of Wlodkowski, Thomas
Sent: Thursday, April 17, 2008 1:49 PM
To: Aaron M Leventhal; David Bolter
Subject: RE: rangeslider, a "Tale of Two Thumbs"


Feel free to propose a keyboard behavior and then join a style guide call
held Tuesdays at noon Eastern and we will discuss.









From: [] On Behalf
Of Aaron M Leventhal
Sent: Thursday, April 17, 2008 1:10 PM
To: David Bolter
Subject: Re: rangeslider, a "Tale of Two Thumbs"

The keyboard interaction is a style guide question. The lack of semantics
for it is a PFWG question. 

- Aaron 

David Bolter <> 
Sent by: 

04/17/2008 07:05 PM 





rangeslider,  a "Tale of Two Thumbs"




Someone in the #dojo channel (on freenode) asked today about what 
keystroke interaction to use for a range slider. It seems this widget, a 
slider with two thumbs, is becoming less rare. Are we looking at 
keyboard interaction for this beast?


Received on Thursday, 17 April 2008 19:45:51 UTC