W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2002

RE: Support for LONGDESC (back-links)

From: Al Gilman <asgilman@iamdigex.net>
Date: Tue, 06 Aug 2002 10:06:36 -0400
Message-Id: <5.1.0.14.2.20020806095859.02132be0@pop.iamdigex.net>
To: Brian Kelly <b.kelly@ukoln.ac.uk>, "'John Foliot - bytown internet'" <foliot@bytowninternet.com>, w3c-wai-ig@w3.org
Cc: b.kelly@ukoln.ac.uk

At 10:08 AM 2002-08-06, Brian Kelly wrote:

>It's not clear from your example, whether the "Return to referring page"
>link is generated by the browser or is in the longdesc file.  Looking at
>your longdesc file -
>http://www.bytowninternet.com/examples/ctry_usage.html
>I think the link is hardcoded - which will not be what's needed if you
>want a single description linked to from many images.  You could use
>some JavaScript to generate the link to the referrer page, or this could
>be provided by the browser's implementation of longdesc support - but
>you wouldn't want to do both.

The browser provides a 'back' function and should not be generating content into
the document redundant to this.

It is OK to put a scripted backlink in the page, but there should be voice over
in the page text that says something like "use your browser's back button or
this link to..."

Yes, we need a palette of browser techniques and a palette of author techniques
that are compatible in mix-and-match fashion.  The suitability of the techniques
on one end of the comm link should not be entirely dependent on which of the other
end techniques are implemented for this particular browse session / page fetch.

Al
Received on Tuesday, 6 August 2002 10:08:03 GMT

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