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

[Bug 11003] Map input type="range" suggestion labels to accessibility APIs

From: <bugzilla@jessica.w3.org>
Date: Sun, 10 Oct 2010 17:42:06 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P4zuQ-0001vg-Gy@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11003

--- Comment #2 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2010-10-10 17:42:05 UTC ---
(In reply to comment #1)
> The question I have is when will the text of these labels be made available?
> 
> When the control is range control first gets focus? Or as the range indicator
> moves to the value that has an associated label?

I think this is up to individual consumers of the accessibility APIs. A bit
like HTML5 itself, they expose semantics and functionality; they do not dictate
the user interface client software presents on top of said semantics and
functionality.

For instance, in UI Automation I guess the list should be exposed as a series
of ListItem instances inside the range API with the labels mapped to the names
of those items. Each list item is a IValueProvider but so is the Slider control
as a whole:

Slider control:
http://msdn.microsoft.com/en-us/library/ee671644(VS.85).aspx

ListItem control:
http://msdn.microsoft.com/en-us/library/ee671635(v=VS.85).aspx

IValueProvider interface:
http://msdn.microsoft.com/en-us/library/ee671565(v=VS.85).aspx

UI Automation does not appear to constrain the order in which this information
is presented to the user.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 10 October 2010 17:42:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:59 UTC