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

Re: [media] demos of Google with WebVTT

From: Geoff Freed <geoff_freed@wgbh.org>
Date: Tue, 7 Jun 2011 07:35:22 -0400
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-ID: <CA13853A.6E15%geoff_freed@wgbh.org>

Hi, Silvia:

I took a look at http://www.html5videoguide.net/demos/google_io/2_audesc/ and http://www.html5videoguide.net/demos/google_io/3_navigation/  with JAWS 12.0.1161 and IE9.08112/Firefox 4.0.1 on Windows 7, and VoiceOver w/Safari 5.0.5 on OS 10.6.6.  In all cases I wasn't able to focus on or locate any of the player controls or toggles from the keyboard/screen reader.  On the description sample, I wasn't to hear the descriptions even after I turned them on with the mouse.  (I could hear the descriptions with ChromeVox, however.)

On the navigation sample, I could focus on the navigation links; activating them moved the video to the appropriate point in the timeline but I could not start the video from the keyboard.

Keep us posted.


On 6/6/11 10:02 PM, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com> wrote:

Hi all,

Thought this would be of interest to people here: Naomi from the
Google a11y team showed some demos for use of WebVTT for captions,
text descriptions and navigation (chapter style). You can watch the
video here:


I've helped create those demos and Naomi actually allowed me to make
those publicly available that do not depend on the custom compiled
Chromium, but only on already released HTML5 Web browsers.

You can check them out for yourself at the following addresses. You
will need a screen reader to see the effects. We've tested them with
ChromeVox in Google Chrome, but I would be very curious to see whether
other screen readers are able to deal with the examples, too. (I think
they should but if there are any bugs, let me know.)

This one shows how we can expect text descriptions to work:
It relies heavily on the use of aria-live. There are problems when the
text cues are longer than the author expected them to be based on an
average reading rate. This cannot be resolved in JavaScript alone and
needs a proper a11y API for text descriptions.

This one shows how we can do navigation:
It relies on the use of lists to provide the navigation on the player
controls. Please try and test them heavily. The navigation on the
right is just there to expose the availabe "table of content" more
visually. You get the names of the chapter, too, when you just mouse
over the segments on the player controls.

Please note that all of this is experimenting with new user interfaces
for video, so have some patience and give us feedback if the controls
are not working in the way that you expect them to work.

Received on Tuesday, 7 June 2011 11:37:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:59:02 UTC