- From: Jon Gunderson <jongund@staff.uiuc.edu>
- Date: Thu, 23 Sep 1999 08:55:53 -0700
- To: Al Gilman <asgilman@iamdigex.net>, w3c-wai-pf@w3.org
- Cc: w3c-wai-ua@w3.org
Response in JRG: >> 3. Event Bubbling: With event bubbling it is impossible for a user agent to >> determine which child elements of a element with an event will or will not >> respond to the parent event. Elements with associated events are considered >> active elements in the user agent guidelines. > > >What would happen if only the element bearing the event-handler attribute were >treated as active? Treating all descendants of a script-bearing element as >active elements defeats the purpose of navigating just the active elements >already, it would seem to me. > >The fundamental requirement, so far as I know, is to be able to reach all >interactive actions available in the document. This is satisfied by treating >the element that actually declares the event handler a member of the effective >active-elements set. > >To me, the script which checks for what descendant the mouse was in when it is >fired is a violation of the WCAG guideline to use structural markup properly. >I am afraid that viewing all descendants of a script-bearing element as active >is an over-reaction to a potential abuse. JRG: Checkpoint 8.1 refers to making scripts accessible, but I do not beleive the WC techniques document talks about this issue. > >Is the method (with heredity of 'active' status over subelements of an active >element which handles an event that can bubble) in use in any browser or >assistive technology or combination at present? Is there any confirmation >with >user testing that it works? JRG: I do not believe that any assistive technologies are treating scripting events as active elements. But this will need to change to make web based user interfaces more accessible. > >Al > > >> >> References in user agent guidelines: >> >> Checkpoint 1.2 Ensure that the user can interact with all active elements >of a >> document in a device independent manner. [Priority 1] >> >> Checkpoint 3.4 Provide time-independent access to time-dependent active >> elements or allow the user to control the timing of changes. [Priority 1] >> >> Checkpoints 8.4 Allow the user to navigate just among all active elements in >> the document. [Priority 2] >> >> Checkpoint 9.7 Provide a mechanism for highlighting and identifying >(through a >> standard interface where available) active elements of a document. [Priority >> 3] >> >> Jon Gunderson, Ph.D., ATP >> Coordinator of Assistive Communication and Information Technology >> Chair, W3C WAI User Agent Working Group >> Division of Rehabilitation - Education Services >> University of Illinois at Urbana/Champaign >> 1207 S. Oak Street >> Champaign, IL 61820 >> >> Voice: 217-244-5870 >> Fax: 217-333-0248 >> E-mail: jongund@uiuc.edu >> WWW: <http://www.staff.uiuc.edu/~jongund>http://www.staff.uiuc.edu/~jongund >> <http://www.w3.org/wai/ua>http://www.w3.org/wai/ua >> ><http://www.als.uiuc.edu/InfoTechAccess>http://www.als.uiuc.edu/InfoTechAccess > > Jon Gunderson, Ph.D., ATP Coordinator of Assistive Communication and Information Technology Chair, W3C WAI User Agent Working Group Division of Rehabilitation - Education Services University of Illinois at Urbana/Champaign 1207 S. Oak Street Champaign, IL 61820 Voice: 217-244-5870 Fax: 217-333-0248 E-mail: jongund@uiuc.edu WWW: http://www.staff.uiuc.edu/~jongund http://www.w3.org/wai/ua http://www.als.uiuc.edu/InfoTechAccess
Received on Thursday, 23 September 1999 09:51:15 UTC