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 23:20:18 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P55Bi-0004As-K0@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11003

--- Comment #4 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2010-10-10 23:20:18 UTC ---
(In reply to comment #3)
> (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.

[snip]

> This seems to be exposed simply by default.  That is, a consumer reading the
> page can follow the @list attribute and read the labels.

I'm not sure I follow.

The semantics are indeed defined by HTML.

However, the purpose of mapping HTML semantics to platform accessibility APIs
is to avoid platform accessibility API clients having to become direct DOM
consumers to provide user interfaces on top of those semantics.

So the fact that the semantics are extractable with direct DOM access does not
reduce the utility of documenting how to map the extracted semantics to
accessibility APIs.

> Was there some additional specific structure that should be exposed?  Is there a precedent for
> talking about Accessiblity API-specific data structures?

I don't understand what you're talking about. Do the Apple Accessibility API
and UI Automation examples above constitute the sort of precedents you're
looking for?

-- 
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 23:20:20 UTC

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