Re: Technique 9.3.1 Check scripts for logical event handlers

If we don't require it then we are deviating from WCAG, which is a bad step
on the loss of interoperability of W3C specs path. (In particular, it would
mean that the AU group, which relies on WCAG by reference, would have to work
outside the AERT). If indeed this is unnecessary then the first requirement
should be to suggest so to WCAG.

So much for process.

Where there is a stylistic change caused by a mouseover, it is done as a way
of providing an effect when the user is focussed on the event. There is no
good reason why this should be restricted to mouse users. In particular, this
is often used to draw attention to something - that has value for a number of
different types of users. As content becomes better written, we can expect
more such effects, and more of them to use generally accessible features like
CSS changes (this is how it  is done using SMIL/SVG animation).

If there are examples where a mouseover and a focus event do different
things, then I have yet to discover it. They may have different meanings in
specification, but the first is a subset of the latter in most user interface
design for the web. (For Operating systems, by contrast, single-click takes
the place of mouseover for certain types of objects, but not others).

Charles McCN

On Wed, 20 Sep 2000, Leonard R. Kasday wrote:

  I think, and I'd guess this agrees with what Chris had in mind, that no, we 
  don't need a mouseover replacement there.
  
  This brings up another problem though.
  
  What if an object already has both a mouseover and an onfocus event?  They 
  are logically different after all.
  
  Simply replacing the onmouseover with onfocus doesn't work in that case.
  
  Len
  
  At 03:31 PM 9/20/00 -0400, Chris Ridpath wrote:
  >Do ALL device specific event handlers (e.g. OnMouseOver) require replacement
  >with device independent handlers (e.g. OnFocus)?
  >
  >Many pages use OnMouseOver to change the appearance of buttons on the page.
  >This is a small change in appearance and does not affect the functionality
  >of the page if it's missing. Should we require that these pages add an
  >OnFocus handler as well as the OnMouseOver?
  >
  >Chris
  
  --
  Leonard R. Kasday, Ph.D.
  Institute on Disabilities/UAP and Dept. of Electrical Engineering at Temple 
  University
  (215) 204-2247 (voice)                 (800) 750-7428 (TTY)
  http://astro.temple.edu/~kasday         mailto:kasday@acm.org
  
  Chair, W3C Web Accessibility Initiative Evaluation and Repair Tools Group
  http://www.w3.org/WAI/ER/IG/
  
  The WAVE web page accessibility evaluation assistant: 
  http://www.temple.edu/inst_disabilities/piat/wave/
  

-- 
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, Australia
September - November 2000: 
W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France

Received on Thursday, 21 September 2000 08:05:08 UTC