- From: Daniel Dardailler <danield@w3.org>
- Date: Wed, 17 Sep 1997 15:14:09 +0200
- To: Al Gilman <asgilman@access.digex.net>
- cc: w3c-wai-wg@w3.org (WAI Working Group)
> This demonstrates that we need to baseline some concrete LONGDESC > proposal including behavior. I think the HTML4 spec can describe possible behavior but should not mandate any. > When I hear Jason White supporting LONGDESC, I believe he is > talking about a feature where when the image is not displayed, > the content of the resource pointed to by the LONGDESC is inlined > in the space that would otherwise be filled by the image. A > link-traversal and page-change is not desired to get to the > verbal guide to the MAPped links. It wants to be automatic and > inlined. I'm not sure of that, Jason ? > That is why I asked earlier what the proposal is. It's to associate a generic long description (a URI) with an image in the markup. Whether it's rendered inline, on demand, using a popup, a voice command, is secondary (a bit like ALT is being rendered in as a tooltip on some platform or in place of the image). The browser guidelines can be more precise about that, of course.
Received on Wednesday, 17 September 1997 09:15:38 UTC