- From: Charles McCathieNevile <charles@w3.org>
- Date: Thu, 6 Apr 2000 10:04:19 -0400 (EDT)
- To: Crystal Allen <crystal@cpd2.usu.edu>
- cc: Melinda Morris-Black <melinda@ink.org>, Accessibility Listserve <w3c-wai-ig@w3.org>
Hmm. I'm going to discuss this in the Web Content Guidelines group, becuase it raises some interesting issues that I think that group should consider. (In other words before I answer I'd like to toss his around a few other people...) Charles McCN On Wed, 5 Apr 2000, Crystal Allen wrote: Charles, Thanks for the useful info. Expanding my question into an area where my knowledge is limited, is it possible to make pop-up menus that are generated by a mouseover accessible? An example is the main menu at http://webaim.org (accessibility note: though the pop-up menus on this page may not be directly accessible, an equivalent to the menus is provided in the form of a submenu on each page). Is there a way to make the pop-up menu directly accessible so that an alternative (submenu) does not need to be provided? Thanks, Crystal Allen ----- Original Message ----- From: "Charles McCathieNevile" <charles@w3.org> To: "Crystal Allen" <crystal@cpd2.usu.edu> Cc: "Melinda Morris-Black" <melinda@ink.org>; "Accessibility Listserve" <w3c-wai-ig@w3.org> Sent: Wednesday, April 05, 2000 12:27 PM Subject: Re: Seeking guidance... > Making HTML 4 mouseover effects accessible to keyboard users is pretty > trivial - add an onfocus/onblur to each element that matches the > onmouseover/onmouseout. > > Making the effects accessible is more complex. It is still important not to > rely on the effects of scripts for providing people with important > functionality, but there are a couple of thigs you can do. THe goal would be > to ensure that the alternative content provided for an image was updated at > the same time as the image was changed by a mouseover. There are other uses > where there is only "accessible" content being affected in the first place, > and in that case the important thing is that the user know what is going to > happen, rather than beng surprised by the way a page works benig changed > seemingly arbitrarily. Although many blind users do not use a mouse, most > computers have them , and particularly in the case of touch-pad mice such as > are ommon on laptops, the user may not know where the mouse is. (Or they may > have been using mousekeys, and know precisely where it is...) > > Sorry that this is only a partial answer for the moment. > > regards > > Charles McCN > > On Wed, 5 Apr 2000, Crystal Allen wrote: > > Is there a way to make mouseovers accessible? If anyone could enlighten me > with a technique to do this it would be much appreciated. > > Crystal Allen > > > ----- Original Message ----- > From: "Melinda Morris-Black" <melinda@ink.org> > To: "Accessibility Listserve" <w3c-wai-ig@w3.org> > Sent: Wednesday, April 05, 2000 9:13 AM > Subject: Seeking guidance... > > > > The issues surrounding inclusion of Javascript and accessibility are a > > little confusing. I'm looking to the list for clarification. What > > types/elements of scripts seem to be at issue? I know mouseovers are > > accessible if tagged correctly. However, I've heard negative feedback > > related to using Javascript forms. Any info on this subject is greatly > > appreciated. > > > > I've included a specific example of a script I'm checking for > > accessibility. It generates a rotating list of links on the home page. > > > > http://www.state.ct.us/ > > > > Any feedback related to the accessibility is welcome. > > > > -- > > Regards, > > > > Melinda Morris-Black > > melinda@ink.org > > > > > > > -- > Charles McCathieNevile mailto:charles@w3.org phone: +61 (0) 409 134 136 > W3C Web Accessibility Initiative http://www.w3.org/WAI > Location: I-cubed, 110 Victoria Street, Carlton VIC 3053 > Postal: GPO Box 2476V, Melbourne 3001, Australia > -- Charles McCathieNevile mailto:charles@w3.org phone: +61 (0) 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI Location: I-cubed, 110 Victoria Street, Carlton VIC 3053 Postal: GPO Box 2476V, Melbourne 3001, Australia
Received on Thursday, 6 April 2000 10:04:21 UTC