Action-231, 252, 253, 45, 227

Mark and I did some work on 4.9. Still a bit rough, but should serve as a
basis for discussion.

Jim and Mark

Action-227 http://www.w3.org/WAI/UA/tracker/actions/227

4.9.8 Navigate Multimedia: The user can navigate efficiently along the
timebase using a continuous scale, and by relative time units within
rendered audio and animations (including video and animated images) that
last three or more seconds at their default playback rate. (Level A) 

4.9.9 Navigation by semantic structure within the time-based media, such as
by chapters or scenes, if present in the media (AA).

Action-231 http://www.w3.org/WAI/UA/tracker/actions/231 

4.9.10 Track Enable/Disable of Time-Based Media
During time-based media playback, the user can determine which tracks are
available and select or deselect tracks. These selections may override
global default settings for captions, audio descriptions, etc. (delete
4.9.b)

Implementation-.@@need to retrieve info from html 5, track selection.etc

Action-253 http://www.w3.org/WAI/UA/tracker/actions/253 
Action-252 http://www.w3.org/WAI/UA/tracker/actions/252 

4.9.11 User has the ability to scale/size the playback viewport within the
limits of the containing viewport.

Implementation: 
User needs video larger but still needs access to other application (take
notes during playback), fullscreen does not allow that.  Content should
reflow as user adjusts playback viewport. 
@@need SC for full screen

4.9.12 User has ability to scale and position alternative media tracks
independent of  base video. 

Implementation:
Text scaling - default setting should apply, UA should allow separate
control of the caption tracks. User needs larger captions. Snap captions
outside of video, change text size and caption viewport size/position.
User need to reposition and make the sign language track larger. 

Action-45 http://www.w3.org/WAI/UA/tracker/actions/45 
4.9.13 User has ability to control the contrast and brightness of the
content within the playback viewport.

Implementation for all of 4.9

If the browser is playing the video natively, then there is only 1 user
agent. Then it falls on the browser to meet the UAAG spec.
If author uses windows media player inside the video element, the browser
needs to map its native controls to the embedded wmp controls, and provide
access to all the controls.  
User needs to be able to define rendering parameters of playback at render
time. 
For example, a YouTube video wall (9 videos playing) you get to focus on one
to have the live audio, captions, etc. need good javascript interface, so
when focus changes the default size audio, alternative media setting swith
to the focused. Other play but audio, captions, etc, cease.

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 Thursday, 18 February 2010 18:02:35 UTC