- From: Masatomo Kobayashi <MSTM@jp.ibm.com>
- Date: Fri, 7 Jun 2013 21:30:23 +0900
- To: Jim Allan <jimallan@tsbvi.edu>
- Cc: John Foliot <john@foliot.ca>, HTML Accessibility Task Force <public-html-a11y@w3.org>, WAI-ua <w3c-wai-ua@w3.org>
Please let me show a use case of the pause-on-exit flag to provide lengthy descriptions, as the reporter of Bug 13624. As far as I know, 'extended' video descriptions are expected to be implemented using JavaScript (at least for now), although in the future screen readers and browsers might provide the native support. So I think this issue is relevant not only with screen readers and browsers, but also with the HTML5 spec. Hiroshima City provides several videos to introduce their city, which have 'extended' descriptions based on HTML5 <track> elements. Here is one of their videos with text-based descriptions: http://www.city.hiroshima.lg.jp/riyou/movie/bunkanomiti_p.html (Unfortunately for now the only language they use is Japanese, and no translation is provided) It uses the experimental JS code included in the Eclipse EASEL package, which aims to provide HTML5 videos with 'extended' descriptions: http://www.eclipse.org/actf/downloads/tools/EASEL/ (Please note that the above example uses pre-synthesized audio snippets to simulate the expected Web Speech API support, which means the JS can be notified when the voicing is finished. Also it uses customized user controls to simulate the paused-for-user-interaction state) As shown in the above example, 'extended' descriptions can be implemented with a simple JS code if the pause-on-exit flag is exploited. However, as mentioned in Silvia's comment, JS developers will need a 'special' pausing state that is independent of user controls, but the current spec does not provide any API to do it. That is why I hope the pause-on-exit flag support the 'paused for user interaction' state (for the latest spec, the 'paused for in-band content' state might be more appropriate for this purpose). Masatomo From: Jim Allan <jimallan@tsbvi.edu> To: John Foliot <john@foliot.ca>, Cc: WAI-ua <w3c-wai-ua@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org> Date: 2013/06/07 02:26 Subject: Re: HTML5 Bug 13624 - <video> The pause-on-exit flag The User Agent Working group (UAWG) reviewed Bug 13624 and references provided. We did not find a compelling use case for making this part of HTML5. This bug describes an interaction between screen readers and browsers. As such, the user is not actively involved. The bug does not interfere with or contradict any Success Criteria in UAAG20. If there's a compelling use case, please bring it to our attention, we can certainly consider it. Otherwise, we concur with closing this bug.\ Jim Allan, Co-Chair User Agent Working Group On Thu, May 23, 2013 at 11:12 AM, John Foliot <john@foliot.ca> wrote: Greetings UAWG colleagues, I have been tasked with bringing this bug to the attention of the UAWG, in case there is a concern/comment you wish to bring forward. It is related to pausing video when supplemental content requires additional time [sic], and in particular the final comment from Silvia Pfeiffer is worth looking at. The current status of this bug is "Rejected", and barring any serious concern/feedback from your group, I will look to close this bug. If you could kindly provide some feedback (one way or the other) in the next week or so I would appreciate that. Thanks. (This email closes ACTION 155 - https://www.w3.org/WAI/PF/HTML/track/actions/155) JF --------------- John Foliot Web Accessibility Specialist W3C Invited Expert | Co-Facilitator, W3C HTML5 Accessibility Task Force (Media) Co-Founder, Open Web Camp -- Jim Allan, Accessibility Coordinator & Webmaster Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Friday, 7 June 2013 12:31:01 UTC