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

RE: [Techs] Short text alternatives for object element

From: John M Slatin <john_slatin@austin.utexas.edu>
Date: Wed, 18 Aug 2004 17:17:26 -0500
Message-ID: <C46A1118E0262B47BD5C202DA2490D1A03E6152C@MAIL02.austin.utexas.edu>
To: "Joe Clark" <joeclark@joeclark.org>, "WAI-GL" <w3c-wai-gl@w3.org>

Joe Clark wrote:
<blockquote>The concern is hypothetical, since <object> is so rarely
Nonetheless, you're acting as though <object> were a replacement for 
<img>. (It is in XHTML 2, but who cares about that?) ....

Um, yes, that's exactly what I was doing, and I realize now that I *was*
confused. But I wasn't so much confused about the way <object> works, as
I was confused about what techniques we were recommending for what

The 30 July Working Draft of the document called Gateway to Techniques
for WCAG 2.0 discusses isses related to Guideline 1.1. There is a
section called "Resources," and in that section is a list of links to
various sections of the document called HTML Techniques for WCAG 2.0.
The list includes a link to a technique for using the alt attribute to
associate a text alternative with an <img> element. Anoteher link points
to the technique I've been going on about, for putting the text
alternative in the body of the <object> element. I misread the list as
implying that these two techniques were interchangeable, and went
bonkers trying to figure out how that could be when it manifestly won't
work if you try to interchange them.   The document doesn't actually
*say* that they're interhcangeable, and clearly nobody intended fo rme
to get that impression.  But there's nothing anywhere that says these
things serve entirely different purposes.

So... Note to self, since I'm one of those trying to write the Gateway
document(s) and make the linkages to Techniques clear: clarify!

Received on Wednesday, 18 August 2004 22:17:37 UTC

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