W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

in defence of listener discovery

From: Al Gilman <Alfred.S.Gilman@IEEE.org>
Date: Thu, 23 Mar 2006 11:04:05 -0500
Message-Id: <p06110400c0486e82382d@[10.0.1.2]>
To: WebAPI WG <public-webapi@w3.org>
Cc: wai-liaison@w3.org

Chaals has been frustrated by having some information of use to your
group buried in Member space.

Here's a summary of the issue.  HTH.

Question:
Why does the accessibility community want the hasEventListener?
Actually, as I read the current Note, it is willTrigger and not 
hasEventListener
that is the key method to enable the functionality needed for UI adaptablility.

http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTarget

* short form

<quote
cite="http://www.w3.org/2006/03/01-Gilman/tree2.xhtml">
- Why an Accessible Dynamic Web Content Roadmap?
-- Fulfill platform-API contract with Assistive Technology
--- [...]
-- afford functional and usable adapted views
--- function: orientation --
---- Where am I?
---- What is there?
---- What can I do?
--- function: actuation --
---- from keyboard and from API
---- navigation: move "Where am I?
</quote>

Event handlers represent actions that the user can take.

They need to afford flexible, including alternate, actuation.

Assistive technologies need to be able to discover these action opportunities
in order to set up alternate actuation modalities for their users.

Examples are voice prompts and on-screen-keyboard menus.

* long form

See the following for a summary of the negotiations leading up to
the inclusion of listener-discovery functions in DOM3.  And read
the list leading up to that summary for more detail.

http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JanMar/0032.html

HTH

Al
Received on Thursday, 23 March 2006 16:05:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT