- From: Jim Ley <jim@jibbering.com>
- Date: Wed, 30 Jan 2002 12:45:47 -0000
- To: "WAI Mailing list" <w3c-wai-ig@w3.org>
"Charles McCathieNevile" > I would agree that the longdesc page should be accessible, and should contain > a repeat of the image being described - after all, that isn't going to make > any difference to people who can't see it, but will help people who are, for > example, trying to get a clearer understanding of what is supposed to be > conveyed (someone with very ow vision, who mostly sees a blur, or someone who > simply doesn't understand what is in the image). I assume that the image on the longdesc page shouldn't have a longdesc attribute... > Using something like an XSLT to automatically include the longdesc in > addition to or in place of an image is an intersting idea for a small tool or > for a proxy-based tool. In Internet Explorer the following "bookmarklet" does this (replaces it with an IFRAME containing the longdesc.): javascript:im=document.images;for (i=0;i<im.length;i++) if (im[i].longDesc!='' && im[i].longDesc!='undefined') im[i].outerHTML="<iframe src='"+im[i].longDesc+"' height='"+im[i].height+"' width='"+im[i].width+"'>";void 0 (all one line of course - wrapped in email.) And for Mozilla and IE this bookmarklet adds the IFRAME of the content. javascript:im=document.images;for (i=0;i<im.length;i++) if (im[i].longDesc!='' && im[i].longDesc!='undefined') im[i].parentNode.innerHTML+="<iframe src='"+im[i].longDesc+"' height='"+im[i].height+"' width='"+im[i].width+"'>"</script> Jim.
Received on Wednesday, 30 January 2002 07:47:44 UTC