W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2001

Re: Making all interactive elements visible

From: Jon Gunderson <jongund@uiuc.edu>
Date: Fri, 09 Mar 2001 15:12:07 -0600
Message-Id: <4.3.1.2.20010309150937.027d1ed0@staff.uiuc.edu>
To: Ian Jacobs <ij@w3.org>, w3c-wai-ua@w3.org
I think for this version of the document we want to make sure we have good 
techniques to access event information.  In this case we may want to limit 
the minimal requirements for event related checkpoints to the information 
that is available in current DOM specs.  As DOM provides more information, 
we can then increase the requirement in a later document.  This stengthens 
UAAG requirement of using the DOM.

Jon


At 12:47 PM 3/8/2001 -0500, you wrote:
>Charles McCathieNevile wrote:
> >
> > If UAs don't keep track of the information, they will have a hard time 
> making
> > use  of it.
>
>The DOM API lets you add handlers, trigger them, and remove them,
>so the UA can do useful things through that interface even without
>keeping a list of the handlers available.
>
>  -Ian
>
> > So it becomes an implementation issue. (That doesn't solve it
> > though). In particular, how to make sure that these tings fit in a 
> reasonable
> > navigation context is a question for which it would be nice to provide
> > several techniques.
> >
> > (I have no ideas yet)
> >
> > Charles
> >
> > On Thu, 8 Mar 2001, Ian Jacobs wrote:
> >
> >   Aaron Leventhal wrote:
> >   >
> >   > The only problem I have with
> >   >
> >   >    A[onmouseover] { background: yellow; color: black }
> >   > is that I don't think it supports mouseovers that come from script, 
> such as:
> >   >
> >   > function addMouseOvers()
> >   > {
> >   > var nodeList = document.getElementsByTagName('TD');
> >   > var endList=nodeList.length;
> >   > for (var count =0; count < endList; count++) {
> >   >   node=nodeList[count];
> >   >   // Using setAttribute instead of AddEventListener gets around bug 
> where
> >   >   // the mouseover in the tablecell is ignored when you're over the 
> text inside the cell
> >   >   node.addEventListener('mouseover',showTheSquare, false );
> >   >   }
> >   > }
> >   >
> >   > I think this will be quite common.
> >
> >   Per our discussion with the DOM WG, the DOM 2 event
> >   handler registration mechanism [1] doesn't allow programs
> >   to list the available handlers. So unless UA's keep track
> >   of this information themselves, I don't know how to help
> >   until the WG gives us this information (which we requested
> >   at the meeting).
> >
> >    - Ian
> >
> >   [1]
> >   http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-registration
> >
> > --
> > Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 
> 409 134 136
> > W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 
> 617 258 5999
> > Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
> > (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, 
> France)
>
>--
>Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
>Tel:                         +1 831 457-2842
>Cell:                        +1 917 450-8783

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
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
WWW: http://www.w3.org/wai/ua
Received on Friday, 9 March 2001 16:09:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:29 UTC