proposed HTML keyboard requirements based on UAAG 2.0 GL 4.2 "Provide access to event handlers"

aloha!  i have seperated the 3 SC in GL 4.2 into 3 requirements with
explanatory material as follows:


REQUIREMENT EV1: a user must, through keyboard input alone, have the 
ability to obtain the list of input device event handlers explicitly 
associated with an element.

     Explanatory note 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 need to know all the input 
     methods assigned to a particular piece of content.

     Explanatory note 2: this is a Level A requirement of UAAG 2.0 
     SC 4.2.1. "List Event Handlers



REQUIREMENT EV2: a user must, through keyboard input alone, be able to 
activate any input device event handlers explicitly associated with an 
element.


     Explanatory note 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 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.

     Explanatory note 3: This is a UAAG 2.0 SC 4.2.2 "Activate any event 
     handler", a Level A requirement



REQUIREMENT EV3: a user must, through keyboard input alone, be able to 
simultaneously activate all input device event handlers explicitly 
associated with an element.


     Explanatory note 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:
        1. Speech input users may combine moving the mouse up, left 
           and clicking in a single command phrase.

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

     Explanatory note 2: this is UAAG 2.0 SC 4.2.3 "Activate all event 
     handlers" a Level A requirement


----------------------------------------------------------------
CONSERVATIVE, n.  A statesman who is enamored of existing evils,
as distinguished from the Liberal, who wishes to replace them 
with others.         -- Ambrose Bierce, _The Devil's Dictionary_
----------------------------------------------------------------
             Gregory J. Rosmaita, oedipus@hicom.net
  Camera Obscura: http://www.hicom.net/~oedipus/index.html
----------------------------------------------------------------

Received on Thursday, 23 September 2010 19:12:11 UTC