W3C home > Mailing lists > Public > public-html-a11y@w3.org > October 2010

[Bug 10988] add slider element

From: <bugzilla@jessica.w3.org>
Date: Sun, 10 Oct 2010 16:34:02 +0000
To: public-html-a11y@w3.org
Message-Id: <E1P4yqY-00084s-Le@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10988

--- Comment #20 from Shelley Powers <shelleyp@burningbird.net> 2010-10-10 16:34:02 UTC ---
(In reply to comment #19)
> (In reply to comment #18)
> > > I don't see any concept of tick marks in ARIA.
> > 
> > Hopefully an accessibility expert will correct me if I'm wrong, by tick marks
> > themselves are a visual aid. The actual value should be read out for screen
> > readers. 
> 
> To be clearer: I mean I don't see any obvious ARIA mapping for suggested labels
> for a range control.
> 

I believe the one example that I linked does demonstrate a possible ARIA
mapping, but it is dependent on user agents to make the mapping between
position of range indicator and associated option label. 

> > Labels, though, are a different story. I'm assuming if a specific value in the
> > range is given a label, it is the label that should be spoken, not the value. 
> 
> Maybe. I'd be happy to expose both bits of information and let UAs (including
> AT) expose them to the user as they feel is most appropriate.
> 
> > Currently, though, I don't see that there is a true mapping between the values
> > given in the list/datalist and the actual range value.
> 
> The value of the option element in the list is always an actual range value.
>

What needs to be clarified is what is available via API when the range
indicator is at a specific position. 

> > > The proposed Note mapping HTML5 semantics to native accessibility APIs should
> > > cover the mapping of native sliders, including option labels.
> > > 
> > > http://dev.w3.org/html5/html-api-map/overview.html
> > > 
> > 
> > Well, yes and no. It maps out the input type of range without the associated
> > list/datalist. And the reference to the datalist in the mapping document is
> > specific to something selectable, and that strikes me is not the equivalent
> > behavior in this specific use case.
> 
> Sorry, I mean "should" as in: this information *should* be included, but it is
> not yet.

That's the purpose of filing bugs -- filling in the gaps.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Sunday, 10 October 2010 16:34:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:22 GMT