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

RE: feedback on guidelines from DHTML developer

From: Charles (Chuck) Oppermann <chuckop@MICROSOFT.com>
Date: Wed, 13 Jan 1999 10:34:43 -0800
Message-ID: <BB61526CDE70D2119D0F00805FBECA2F04B37C0F@RED-MSG-55>
To: Wendy A Chisholm <chisholm@trace.wisc.edu>, w3c-wai-gl@w3.org
This is great feedback Wendy, thanks for getting it!

>With DHTML, you can now load one large image but only allow a portion of
>that image to show through using a clipping window. I use this clipping
>often to simulate multiple button animations but using only one image.
>An ALT tag here would only be relevant once and not represent all the
>possible button displays.

He can simply set the alt attribute of the IMG object to a different value
when he switches to a different image.

>can be added such as long description. An alternate to ALT tag is
>needed to allow for design control. From a pure design stand point I am
>unwilling to create a default site design to accommodate everyone needs,
>but I am willing to modify the site on the fly using dynamic page
>methods if I can detect the users specific needs, devices, etc. This
>would be tremendous.

I agree.  There needs to be a CSS attribute to control the rendering of the
ALT and TITLE attributes.  Possible values would be:  TOOLTIP or NONE.  That
way, the author can control the visual appearance, and if required, the user
can override it.

For purposes of accessibility, the tool tip doesn't matter - that the
information is there and available in the object is the key (exposed by
DHTML/DOM/MSAA whatever).  The reason the tool tip exists currently is to
make the author more aware of the attribute and to test for it's presence
Received on Wednesday, 13 January 1999 13:34:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:28 UTC