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

[Bug 10896] New: enable device independent access to event handlers

From: <bugzilla@jessica.w3.org>
Date: Thu, 30 Sep 2010 20:02:44 +0000
To: public-html@w3.org
Message-ID: <bug-10896-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10896

           Summary: enable device independent access to event handlers
           Product: HTML WG
           Version: unspecified
          Platform: All
               URL: http://www.w3.org/WAI/PF/HTML/wiki/Access/event_handle
                    r_requirements
        OS/Version: All
            Status: NEW
          Keywords: a11y, a11ytf
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: lwatson@nomensa.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, public-html-a11y@w3.org,
                    lwatson@nomensa.com


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 manner.

    * 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 
      take.

          * 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.

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

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 30 September 2010 20:02:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:15 GMT