- From: <bugzilla@jessica.w3.org>
- Date: Wed, 06 Oct 2010 11:48:52 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10941 --- Comment #9 from Masatomo Kobayashi <mstm@jp.ibm.com> 2010-10-06 11:48:52 UTC --- (In reply to comment #7) > Which case are we talking about here? Or is it a third case I haven't > considered? At least for now, I'm talking about the first case. A good example movie with extended descriptions (provided by WGBH) is found at http://web.mac.com/eric.carlson/w3c/NCAM/extended-audio.html . The background of this technology is introduced at http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Requirements#Extended_video_descriptions . SMIL is known as means to provide this type of descriptions ( http://www.w3.org/TR/WCAG-TECHS/SM1 and http://www.w3.org/TR/WCAG-TECHS/SM2 ), but SMIL seems to be too much for this purpose. So we are testing a simpler way to present extended descriptions (using an "extended" flag) in our prototype auditory browser ( http://www.eclipse.org/actf/downloads/tools/aiBrowser/ ). My original intention to post this bug was that APIs like media.pauseInternally() will allow to provide extended descriptions using JavaScript even if they are not natively supported by browsers. However, of course it will be better if extended descriptions are natively supported. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Wednesday, 6 October 2010 11:48:54 UTC