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 22:57:43 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P54pr-0003S4-LW@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11003

Tab Atkins Jr. <jackalmage@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jackalmage@gmail.com

--- Comment #3 from Tab Atkins Jr. <jackalmage@gmail.com> 2010-10-10 22:57:43 UTC ---
(In reply to comment #0)
> You can label marks on a "input type='range'" by using the list attribute to
> point to a list of suggestions which may have labels ("label" attribute). These
> labels should be exposed to underlying accessibility APIs.
> 
> http://dev.w3.org/html5/spec/number-state.html#range-state
> http://dev.w3.org/html5/spec/common-input-element-attributes.html#the-list-attribute
> 
> This note might help for the Apple API:
> 
> http://lists.apple.com/archives/Accessibility-dev/2006/Apr/msg00004.html
> 
> See also discussion in Bug 10988.

This seems to be exposed simply by default.  That is, a consumer reading the
page can follow the @list attribute and read the labels.  Was there some
additional specific structure that should be exposed?  Is there a precedent for
talking about Accessiblity API-specific data structures?

-- 
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 22:57:44 UTC

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