W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2000

RE: Seeking guidance...

From: Bruce Bailey <bbailey@clark.net>
Date: Mon, 10 Apr 2000 10:41:28 -0400
To: <david@davidsaccess.com>
Cc: <w3c-wai-ig@w3.org>
Message-ID: <002601bfa2fa$da783d20$53fe330a@msde>
> Maybe I am dense, but I just do not get the issue, it is not as
> complicated as you are making it.

Well, it shouldn't be so complicated anyway!

> The issue raised on http://www.att.com would be addressed by
> guideline 6.2,
> make the users aware of dynamic content. It should not be on the AT vendor
> to account for it.

Okay, so how should the ATT vendor code differently?  IMHO, they should be
using text instead of pictures of text, but CSS and other techniques are not
so compatible with Navigator.  Its great that they have dynamically changing
ALT content, but I doubt that it is available to screen readers (I know Lynx
doesn't see it).

> I also think that mouseover and onfocus are synonymous.

That's kind of my point -- they SHOULD be synonymous -- but they are not!
Not in the specification and not in actual practice.

> Using IE, I can tab between selectable objects.
> But, the object is not activated until I hit enter.

Right, and the onFocus/onMouseOver script SHOULD occur when you TAB (and NOT
require you to press enter).  This IS what happens when you use the
keyboard.  In order for the onFocus to be triggered by the mouse, however,
one must click (select) the item with the onFocus attribute.  This is NOT
like onMouseOver!  This is NOT the modality users have come to expect!

> I think this echoes what Bruce was saying.

Yep!

> -------------------------------------------------------------------
> David M. Clark
> Director of Accessibility
> halftheplanet.com
> 350 Fifth Ave., Suite 6812, New York, NY 10118
> Phone: 212/643-0650x256 Fax: 212/643-6704
> Email: dclark@halftheplanet.com  URL: http://www.halftheplanet.com
> Boston Office: 617/859-0367 (phone/fax)
>
> -----Original Message-----
> From: w3c-wai-ig-request@w3.org
[mailto:w3c-wai-ig-request@w3.org]On Behalf
Of Charles McCathieNevile
Sent: Friday, April 07, 2000 5:52 PM
To: Leonard R. Kasday
Cc: Bruce Bailey; w3c-wai-ig@w3.org; jpledger@mindspring.com; Marjolein
Katsma
Subject: RE: Seeking guidance...

At some point it is up to the screenreader to work properly. If the authors
have done what is necessary to amke sure that access is possible (including
ensure that the script stuff is not necessary to understand the page) there
needs to be some work done by people who provide access to the content
through software such as browsers and assistive technologies.

Having a way of authoring that supports accessibility is vital for
accessibility, but unless there are also user agents that support
accessibility the web will still be only for some people.

Charles McCN

On Fri, 7 Apr 2000, Leonard R. Kasday wrote:
[snip]
  For example, take http://www.att.com

  As you mouseover items on a menu, another image changes to show some more
info.
  And, bless them, their javascript also changes the alt text of that other
  image.

  Are screenreaders going to show this changed alt text in the other image?

  Also, what if a mouseover changes the image it was on.  What does the
  screenreader read when it the image gets focus?  the original alt text or
  the changed alt text?

  Len
Received on Monday, 10 April 2000 10:44:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:48 GMT