W3C home > Mailing lists > Public > public-html@w3.org > September 2008

Re: Acessibility of <audio> and <video>

From: James Craig <jcraig@apple.com>
Date: Fri, 5 Sep 2008 16:41:12 -0700
Cc: public-html@w3.org, W3C WAI-XTECH <wai-xtech@w3.org>
Message-Id: <1A986F50-49FD-414A-BDD9-4A062190FACA@apple.com>
To: Leif Halvard Silli <lhs@malform.no>

Leif Halvard Silli wrote:

> VoiceOver is based on WebKit - aka Safari.

VoiceOver works with Safari/WebKit, but it is not based on Safari/ 
WebKit.

> This leads to this strange contradiction: While Apple's Safari  
> supports @longdesc, their Safari based screen reader doesn’t. (The  
> same contradiction applies for the screenreading support in Opera on  
> Mac OS X - which also uses VoiceOver.)

Even if VoiceOver was based on Safari, this is a flawed argument. Just  
because a property is in the DOM doesn't mean that the browser knows  
how to map it to an external API. By the logic of your statement, I  
could also add a custom "myAttribute" attribute to the DOM and then  
state that the value of "myAttribute" wasn't accessible.

> Anyway, my point was to say that the support for @longdesc is much  
> better than Lachlan claims simply because all the mayor browsers, on  
> which the screen readers usually are based, they support it.

The DOM is pretty freeform, so all browsers also support @myAttribute,  
too.
Received on Friday, 5 September 2008 23:41:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:58 UTC