- From: Maciej Stachowiak <mjs@apple.com>
- Date: Fri, 05 Nov 2010 08:50:41 +0100
- To: Frank Olivier <Frank.Olivier@microsoft.com>
- Cc: "public-html@w3.org" <public-html@w3.org>, "HTML Accessibility Task Force (public-html-a11y@w3.org)" <public-html-a11y@w3.org>
Thanks, Frank, for writing this up. I'd like to suggest that the WG and the Task Force should focus on the following 11 SPECNEW items, where we believe some changes to the HTML5 spec itself may be needed. The remaining items are either already handled with current spec text, or primarily requirements for a timed text format or a set of UA guidelines; these 11 are the key issues for HTML5 proper, assuming we do not put a timed text format in the HTML5 draft itself. Separately, the Chairs and Team are discussing the possibility of taking up WebSRT as a separate W3C deliverable, either in this WG or a new one created for the purpose. For each of these SPECNEW items, we need to determine the following: (1) What are the kinds of changes needed to the HTML5 spec to support this requirement? (2) Do we agree that this requirement is reasonable and implementable? (3) In detail what are the exact spec changes needed to support this requirement? If anyone is interested in discussing a specific requirement, please fork a new thread with a subject line that refers to the particular requirement. On Nov 4, 2010, at 5:55 PM, Frank Olivier wrote: > SPECNEW, SPECCED: (SL-1) Support sign-language video either as a track as part of a media resource or as an external file. > SPECNEW, SPECCED: (SL-2) Support the synchronized playback of the sign-language video with the media resource. > SPECNEW, TRACK: (CC-5) Support positioning in all parts of the screen - either inside the media viewport but also possibly in a determined space next to the media viewport. This is particularly important when multiple captions are on screen at the same time and relate to different speakers, or when in-picture text is avoided. > SPECNEW, TRACK: (CN-1) Provide a means to structure media resources so that users can navigate them by semantic content structure. > SPECNEW, UX: (CC-25) Support edited and verbatim captions, if available. > SPECNEW, UX: (DV-8) Allow the author to provide fade and pan controls to be accurately synchronized with the original soundtrack. > SPECNEW: (CN-3) Support both global navigation by the larger structural elements of a media work, and also the most localized atomic structures of that work, even though authors may not have marked-up all levels of navigational granularity. > SPECNEW: (CN-6) Support direct access to any structural element, possibly through URIs. [Media fragment-like issue] > SPECNEW: (CNS-1) All identified structures, including ancillary content as defined in "Content Navigation" above, must be accessible with the use of "next" and "previous," as refined by the granularity control. [May be handled with cue ranges] > SPECNEW: (DAC-2) The user has a global option to specify which types of alternative content by default and, in cases where the alternative content has different dimensions than the original content, how the layout/reflow of the document should be handled. (UAAG 2.0 3.1.2). [Probably minimal spec text required: Media queries would work nicely here; also UX issue (user sets media query to match)] > SPECNEW: (DAC-5) Non-synchronized alternatives (e.g., short text alternatives, long descriptions) can be rendered as replacements for the original rendered content (UAAG 2.0 3.1.3).
Received on Friday, 5 November 2010 07:51:18 UTC