- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Wed, 20 Oct 2010 09:29:24 -0500
- To: WAI-ua <w3c-wai-ua@w3.org>
a bit more for the device independence discussion ---------- Forwarded message ---------- From: Gregory J. Rosmaita <oedipus@hicom.net> Date: Thu, Oct 7, 2010 at 7:01 PM Subject: PFWG requirements: enable device independent access to event handlers 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 aloha! i'm sending the following to inform discussion of device independence in DOM3 Events and the apple proposal for UI device independence http://lists.w3.org/Archives/Public/www-dom/2010JulSep/att-0106/UserInterfaceIndependence.html the contents of the following quote: http://www.w3.org/WAI/PF/HTML/wiki/Access/event_handler_requirements 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; QUOTE cite="http://www.w3.org/WAI/PF/HTML/wiki/Access/event_handler_requirements" 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 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. * Explantory Note 1: This is extremely important for analyzing web applications for identifying keyboard support for widgets. UNQUOTE 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. UNQUOTE 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 -------------------------------------------------------------- -- Jim Allan, Accessibility Coordinator & Webmaster Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Wednesday, 20 October 2010 14:30:09 UTC