W3C home > Mailing lists > Public > public-html@w3.org > April 2011

Re: longdesc - beside the box

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Tue, 26 Apr 2011 12:10:17 +1000
Message-ID: <BANLkTi=cSfx_F49CyP-sh_0=bWoK39xQrA@mail.gmail.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Cc: Laura Carlson <laura.lee.carlson@gmail.com>, HTMLWG WG <public-html@w3.org>
On Tue, Apr 26, 2011 at 11:32 AM, Leif Halvard Silli
<xn--mlform-iua@xn--mlform-iua.no> wrote:
> Silvia Pfeiffer, Tue, 26 Apr 2011 10:56:09 +1000:
>> On Tue, Apr 26, 2011 at 3:20 AM, Laura Carlson
>> <laura.lee.carlson@gmail.com> wrote:
>>> HI all,
>>>
>>> Silvia wrote:
>>>
>>>> I think we need this for video, too. How about a @transcription
>>>> attribute on the <img> element (and <video> and <audio>) that contains
>>>> the link outright? Can be a link to some other element on the same
>>>> page or a different page altogether.
>>>>
>>>> It would be displayed in text-only browsers instead of the media and
>>>> be keyboard focusable for AT users to be read out and followed.
>>>
>>> Another a clear and specific use case is for people on slow
>>> connections with GUI browsers. Playing a video for people on dialup is
>>> not an option.  People on slow connections need a way to obtain a
>>> transcript so at least they can obtain *some* content.
>>
>> I wonder: When you turn off images in a browser, does that also turn
>> off video and audio? (In Chrome I don't even see a preference setting
>> for images any more.)
>
> Yeah, how should a text browser render <video>? If we look at <object
> data=image.jpg>fallback</object>, then it presents the fallback.
> Whereas for <img alt="fallback"> it renders the alt text in a different
> color.
>
> 3 options: 1) Behave like for <object>. 2) Behave like for object but
> still color the text or something. 3) Treat <video> more or less as an
> image map: Introduce a @alt attribute on <video> which is meant to
> represent the video including the first frame. By pressing the video
> element, the user can download the content of the src attribute. If the
> video contains multiple video formats and/or fallback, then let the
> user "open" the video element and navigate inside it to select video
> format to download and read the fallback.

Careful about the use of the term "fallback" here. We already have
"fallback" for non-HTML5 browsers, which is the stuff inside the video
element. I really don't want to use the term "fallback" for text-only
HTML5 browsers. I'd prefer if we can focus on calling it "text
alternative" or something along those lines.

Also, we need to be careful what types of text alternatives we
introduce. I was here not talking about short text alternatives such
as can be done with @alt or @aria-describedby. I was particularly
talking about full transcriptions, which typically would be provided
in a separate html page or sometimes further down. So, it would
definitely have to have a URI reference as value, e.g. "#desc" or
"desc.html". That URI would be shown only when the video is not
displayed (in a HTML5 browser!) and it would also be exposed to AT
somehow - maybe a special sound could be made to make people aware
that such a URL is available. It could also be exposed in a context
menu such that anyone can have access. But it is not something that
would go on a <source> or some attribute inside the video - it would
go straight onto the <video> element. The DOM inside a video should
never be exposed to AT since it represents a single entity.

Silvia.
Received on Tuesday, 26 April 2011 02:11:05 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:24 UTC