W3C home > Mailing lists > Public > public-html-a11y@w3.org > August 2010

Re: [media] discussion on how to render captions in HTML5

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 19 Aug 2010 21:33:15 +1000
Message-ID: <AANLkTinOLWa71MefwC0vhHgWvR5qEQUyTSJyKbYyu1Sn@mail.gmail.com>
To: Geoff Freed <geoff_freed@wgbh.org>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
Ah, I should clarify: right now what is expected is that if you want to put
captions on an audio resource, you put it into a <video> element. To some
extent that makes sense since the video element has a defined visual
presentation and the audio only has controls.

Cheers,
Silvia.

On Thu, Aug 19, 2010 at 8:40 PM, Geoff Freed <geoff_freed@wgbh.org> wrote:

>
> I wasnít on the call yesterday and havenít seen the minutes yet, so I canít
> comment on other points that may have been raised.  However, I do agree that
> we need to be able to provide captions, subtitles, etc., on <audio> elements
> for all the same reasons we need them on <video>.  It would seem to be a
> step backwards for accessibility to take this away in HTML5.
>
> Iíll wait for the minutes to see what the other arguments were.
> Thanks.
> Geoff/NCAM
>
>
>
> On 8/18/10 7:40 PM, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com> wrote:
>
> Hi media a11y folks, hi Eric,
>
> In today's call we had a brief discussion on the WHATWG specification of
> rendering of time-synchronized text with audio and video resources, see
> http://www.whatwg.org/specs/web-apps/current-work/complete/rendering.html#timed-tracks-0.
>
> The point I was making was that I am disappointed that for <audio> elements
> there is no rendering. I was suggesting that for both, <audio> and <video>
> elements, rendering of time-synchronized text should depend on the @controls
> attribute of the <audio> and <video> elements. The reason behind this is
> that I expect a menu to be made available to the user through the @controls
> that allows the user to activate/deactivate text tracks from the list of
> available text tracks. Because that list is made available through the
> @controls, I would also expect that the rendering of the text cues depends
> on this @controls attribute being available.
>
> However, the specification says that <audio> elements don't render any
> time-synchronized text, but only <video> elements do.
>
> We didn't get very far in the discussion - in particular Eric had some
> important points to make. Thus, I'd like to take up this discussion here
> again.
>
> Cheers,
> Silvia.
>
>
>
Received on Thursday, 19 August 2010 11:34:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:12 UTC