W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2003

Re: HTML techniques - Embedded objects (no blocker)

From: Roberto Ellero <rellero@webaccessibile.org>
Date: Sat, 1 Nov 2003 11:03:27 +0100
Message-ID: <00dc01c3a05f$683c5eb0$3a29fea9@K6jt1f6N1cl0f>
To: "Yvette P. Hoitink" <y.p.hoitink@heritas.nl>, <w3c-wai-gl@w3.org>

> If we do want to include techniques for obsolete elements for backwards
> compatibility purposes, this should be made explicit with each technique
> that uses them.

I agree, and I think that the current example for movies (Flash-only):

http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20031020.html#noembed
<embed src="moviename.swf" width="100" height="80"
      pluginspage="http://example.com/shockwave/download/" />
  <noembed>
    <img alt="Still from Movie" src="moviename.gif"
    width="100" height="80" />
  </noembed>

may be misleading, as it is available a good solution for swf files, by Drew
McLellan in an article in A List Apart
http://www.alistapart.com/articles/flashsatay/, that in synthesis leads to a
code like this:

<object type="application/x-shockwave-flash" data="file.swf"
 width="100" height="100">
 <param name="movie" value="file.swf" />
 <a href="page.htm"><img src="noflash.gif" width="100" height="100" alt="alt
text" /></a>&nbsp;
</object>

It is valid, and if the browser doesn't play objects with a MIME type of
application/x-shockwave-flash, it will go for the next child element (in the
example img, but may be a text).

Roberto Ellero



----- Original Message ----- 
From: "Yvette P. Hoitink" <y.p.hoitink@heritas.nl>
To: <w3c-wai-gl@w3.org>
Sent: Friday, October 31, 2003 5:16 PM
Subject: HTML techniques - Embedded objects (no blocker)


>
> In the HTML techniques document, there is two techniques for the Embed
> element,  called "Alt content for embed":
>
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20031020.html#noembed>
> and Alt text for embed.
>
> However, EMBED is no longer supported in HTML4+. I do not think we should
> give techniques for elements that are no longer in the HTML specification.
> If we do want to include techniques for obsolete elements for backwards
> compatibility purposes, this should be made explicit with each technique
> that uses them.
>
> In the next section below, called "Embedding multimedia objects", it does
> mention that you should use EMBED within OBJECT for backward
compatibility,
> however it does not say that EMBED is no longer part of the specification
> and will lead to invalid documents. If I were a casual visitor, I would
> think that OBJECT is the preferred way, but also that EMBED is still
allowed
> which is not the case.
>
> Also, I think we should include some more examples of how to embed a movie
> or sound fragment (for example an AVI or WAV file). I am currently
building
> a website with some movies and sounds, but have had a very hard time
finding
> out how to make this accessible and cross-browser. My added problem was
that
> we create these pages on the fly (server-side), without knowing the actual
> width and height of the movies.
>
> The current example for movies are Flash-only, where there normally is one
> designated plugin. This is contrary to other movies which can use
different
> programs to be played, depending on the user's preferences, operating
> system, browser, etc.
>
> Yvette Hoitink
> CEO Heritas, Enschede, The Netherlands
>
>
Received on Saturday, 1 November 2003 05:07:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:26 GMT