Re: Acessibility of <audio> and <video>

On Mon, 25 Aug 2008 17:19:43 +0200, Edward O'Connor <hober0@gmail.com>  
wrote:
> This is because, for legacy reasons, <img> is an empty element, and so
> its text equivalent lives in an attribute, whereas <audio> and <video>
> both support rich fallback via their content.

Actually, I think the idea is that the content stream itself is  
accessible. The contents of the <audio> and <video> element are a) for  
<source> elements and b) for user agents not supporting <audio> and  
<video>.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>