Re: alt use cases

Le 5 mai 2008 à 23:09, Justin James a écrit :
> * Considering how much in-accessible functionality is already in  
> HTML 5
> (particularly with regards to support for AJAX-type work), it is  
> clear that
> this is *not* a goal. From the way the spec supports AJAX and  
> multimedia, it
> is clear the accessibility is a "nice idea" but certainly secondary to
> functionality.

   Accessible Rich Internet Applications (WAI-ARIA) Version 1.0
   implemented in IE8 beta, in Firefox, in Opera, and being  
implemented in Webkit
   (aria-* syntax)

> * If we are going to mandate al text due to CASE #4, we should make  
> the
> <audio> and <video> tags (and anything that does the same in  
> <object>) have
> a mandatory @transcript system.

   I wonder if there are plug-ins supporting the built-in captioning  
   SMIL has a feature for this btw.

"alt" has known limitations too in terms of internationalization and  
markup. I would be interesting in a system, where it is required to  
give a text alternative somewhere in the page.

Usually a longdesc attribute is used for giving a long description of  
the image. The attribute value must be a URI.

	<img src="beach.jpg" longdesc=""/>

Let's imagine a page foo.xhtml containing this markup

<p><img src="beach.jpg" longdesc="#foo"/></p>
<p>… blah blah…</p>
<p>… blah blah…</p>
<p><img src="mike-portrait.jpg" longdesc="#author"/></p>
<p>… blah blah…</p>
<p id="foo">A beach is a geological landform along the shoreline of a  
body of water. It usually consists of loose particles which are often  
composed of rock, such as sand, gravel, shingle, pebbles, or cobble.</p>
<p>This text was provided by <a href=""  
id="author">Mike Myers</a>.</p>

Longdesc could contain URI-reference not only URI. The accessible text  
equivalent could be part of the page and easier to edit and be the  
same than for people with visual abilities.
Things which are only decorative can be ignored.

Karl Dubost - W3C
Be Strict To Be Cool

Received on Tuesday, 6 May 2008 01:56:34 UTC