W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

PFWG requirements: enable device independent access to event handlers

From: Gregory J. Rosmaita <oedipus@hicom.net>
Date: Fri, 8 Oct 2010 01:01:50 +0100
To: public-webapps@w3.org, wai-xtech@w3.org, www-dom@w3.org
Cc: jcraig@apple.com, cfleizach@apple.com, schepers@w3.org, ian@hixie.ch, janina@rednote.net
Message-Id: <20101007235559.M34627@hicom.net>

i'm sending the following to inform discussion of device independence 
in DOM3 Events and the apple proposal for UI device independence


the contents of the following quote:


has been indirectly referred to the WebApps group by the HTML5 editor 
through the bugzilla system, and it is PFWG's desire that these 
requirements inform discussion of these documents;

Note: The first three of the following four [... requirements ... 
developed and approved by PFWG ...] were requested by the UAWG and 
reviewed by both PFWG the HTML Accessibility Task Force

REQUIREMENT EV1: a user must have the ability to obtain the list of input 
device event handlers explicitly associated with an element in a device 
independent manner.

   * Explanatory note EV1.1: Users interacting with a web browser may 
     be doing so by voice, keyboard, mouse or another input technology 
     or a combination of any of these. No matter how the user is 
     controlling the user agent, he or she needs to know all the input 
     methods assigned to a particular piece of content.

REQUIREMENT EV2: a user must be able to activate any input device event 
handlers explicitly associated with an element in a device independent 

   * Explanatory note EV2.1: Although it should not be so designed, 
     some Web content is designed to work only with certain input 
     devices, such as a mouse, thereby limiting the availability of 
     those event handlers to specific devices. Some users interacting 
     with a web browser may be doing so by voice, keyboard, mouse or 
     another input technology or a combination of any of these. No 
     matter how the user is controlling the user agent, he or she must 
     be able to activate any of the event handlers regardless of the 
     interaction technology being used.

   * Explanatory note EV2.2: A user who cannot use a mouse needs to 
     activate a flyout menu that normally appears OnMouseOver. The user 
     should be able to navigate to a link and activate it using 
     keyboard shortcuts.

REQUIREMENT EV3: a user must be able to simultaneously activate all input 
device event handlers explicitly associated with an element in a 
device-independent manner.

   * Explanatory note EV3.1: One input method should not hold back 
     another. People who don't use a mouse shouldn't necessarily have 
     to map their input methods to the same steps a mouse user would 

         * Examples:
               + Speech input users may combine moving the mouse up, 
                 left and clicking in a single command phrase.

               + A link has an onmousedown and an onmouseup event 
                 link. The keyboard user should be able to use 1 key 
                 click to activate both events.

REQUIREMENT EV4: HTML5 must provide a standard way to enumerate the 
events on a DOM node and a parallel method to use addEventListener and 
removeEventListener to obtain a collection of "events" or an 
enumeration function.

   * Explantory Note 1: This is extremely important for analyzing 
     web applications for identifying keyboard support for widgets. 

the above requirements were logged as a bug against HTML5 after review 
by the HTML Accessibility Task Force at its 2010-09-30 meeting, but 
after comments by one of the HTML WG chairs, have been referred to the 
WebApps WG by the HTML5 editor (thank you, hixie):

QUOTE cite="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10896"

Comment 1  Maciej Stachowiak      2010-10-02 05:00:23 UTC

Isn't this an issue for DOM Level 3 Events, not HTML5? HTML5 does not 
define the concept of event handlers, it just uses it.

Comment 2  Ian 'Hixie' Hickson 2010-10-07 21:45:07 UTC

Reassigning to DOM Events, since this doesn't seem to be HTML-specific.

Doug: Feel free to reassign back to me if you think this should be dealt 
with at the HTML level.

so i wanted those to whom this information was referred to have some
context about the event handler device independence issues which will
be discussed across-groups

thank you, gregory.
You cannot depend on your eyes when your imagination is out of
focus.                                          -- Mark Twain
Gregory J. Rosmaita: oedipus@hicom.net
  Camera Obscura: http://www.hicom.net/~oedipus/
         Oedipus' Online Complex: http://my.opera.com/oedipus
Received on Friday, 8 October 2010 00:03:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:13 UTC