- From: Joshue O Connor <joshue.oconnor@cfit.ie>
- Date: Wed, 15 Oct 2008 12:49:35 +0100
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- Cc: W3C WAI-XTECH <wai-xtech@w3.org>, html4all <list@html4all.org>, "John Foliot - WATS.ca" <foliot@wats.ca>, Jim Jewett <jimjjewett@gmail.com>
Hi Laura, >Jim Jewett said: >In an ideal world, the accessibility features would be in the video. > > In the real world, often they aren't. > > The page creator may not be able to modify the audio or video. > Sometimes this is a matter of not having the video (embedded 3rd party > videos) or not having legal authority; sometimes it is just a matter > of not knowing how. > > By all means encourage authors to put the accessibility information > within the video. But there needs to be a fallback for cases where > that doesn't happen. Yes, of course > John Foliot has talked of a clean, semantic, explicit association to > transcripts, text descriptions, captions, audio descriptions and/or > streams that could be toggled on or off by the end user. Yes. We need an approach that covers all bases. > He has also provided examples > that hint on some best practices that not only native players and but > HTML 5 as a whole could approach multi-media content.[3] Thanks I will check them out. Cheers Josh [3] http://esw.w3.org/topic/HTML/MultimediaAccessibilty#head-9dc3a1bce8ca03b38a207a12b27c25e2fcd47aeb
Received on Wednesday, 15 October 2008 18:20:41 UTC