Re: Acessibility of <audio> and <video>

That was going to be my next challenge.  Even on windows, there is variance 
in what AT and UA support.

I have yet to get opera to work with VoiceOver.

----- Original Message ----- 
From: "Leif Halvard Silli" <lhs@malform.no>
To: "David Poehlman" <david.poehlman@handsontechnologeyes.com>
Cc: "Lachlan Hunt" <lachlan.hunt@lachy.id.au>; <public-html@w3.org>; "W3C 
WAI-XTECH" <wai-xtech@w3.org>
Sent: Friday, September 05, 2008 9:19 AM
Subject: Re: Acessibility of <audio> and <video>



But I qualfied what I meant by "all browsers".

The built-in screen reader of Mac OS X - VoiceOver does not
support @longdesc. VoiceOver is based on WebKit - aka Safari.

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.)

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.


David Poehlman 2008-09-05 14.49:

> you didn't list all browses.


> David Poehlman 2008-09-05 00.23:
>
>> Actually, unless you cover all the variables, it will most likely prove
>> your
>> first #2.  Not all browsers support longdesc and maybe even not all
>> assistive technologies recognize it as such?
>
> Actually, all browsers (WebKit, Opera, Firefox, IE) support
> longdesc via JavaScript - since longdesc is defined in DOM.

-- 
leif halvard silli

Received on Friday, 5 September 2008 13:39:01 UTC