W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2000

Re: Proposed edits around freezing motion (3.3, 3.5, 3.6, and 4.6)

From: Harvey Bingham <hbingham@acm.org>
Date: Tue, 20 Jun 2000 22:48:21 -0400
Message-Id: <4.3.2.7.2.20000620182610.00b15820@pop.tiac.net>
To: w3c-wai-ua@w3.org
At 2000-06-19 22:47-0400, Ian Jacobs wrote:
>Hello,
>
>Per my action of the 15 June teleconference [1], please
>consider the following proposal. In the 10 June guidelines,
>we have the following checkpoints:
>
>3.3 Allow the user to freeze video.
>3.5 Allow the user to freeze animated or blinking text.
>3.6 Allow the user to freeze animations and blinking images.
>4.6 Allow the user to start, stop, pause, advance, and rewind audio,
>     video, and animations.
>
>All of these checkpoints are Priority 1. Recall that in previous
>versions of the document, checkpoints 3.3, 3.5, and 3.6 read
>"turn on and off" instead of "freeze", but I believe that the
>accessibility
>issue in cases of animated text, animated images, and video is the
>motion
>(and not the mere visual information).
>
>For the purposes of this email, I consider that "freeze" is a
>subset of "pause". With "pause" the user agent is required to allow
>"play" again; with "freeze", there is no requirement to play again.
>
>Therefore, since checkpoint 4.6 already includes video and animations
>(which I interpret to be animated images and text), and it requires
>a pause functionality that is more powerful than a simple freeze, and
>the checkpoints are all priority 1, I propose that checkpoints 3.3, 3.5
>and 3.6 all be deleted in favor of the following two checkpoints:
>
><NEW 1>
>    Allow the user to start, stop, and pause audio, video, and
>graphically
>    animated and blinking content.
></NEW 1>
To belabor what you said: restart is implied by pause, but not necessarily
implied by stop. As this wasn't clear to me, I propose instead:

     Allow the user to start, stop, pause, and restart content that is
     audio, video, blinking or graphically animated.

     This checkpoint makes no attempt to consider maintaining
synchronization where content uses more than one modality.

?I'm not sure if you meant that blinking always is associated with
graphically animated? That was my reason for changing the ending text.

><NEW 2>
>    Allow the user to advance and rewind audio, video, and graphically
>    animated content.
></NEW 2>

?Rewind (to the beginning), or stoppable? I suggest instead:

     Allow the user to advance or reverse, and to rewind to the beginning
     content that is audio, video, or graphically animated.


>I have opted for two checkpoints since I'm not sure that it's necessary
>to advance and rewind blinking content. While this could be considered
>a degenerate case of animated content, it may confuse people.
>
>[1] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0481.html
>[2] http://www.w3.org/WAI/UA/WD-UAAG10-20000610
>--
>Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
>Tel:                         +1 831 457-2842
>Cell:                        +1 917 450-8783


Regards/Harvey Bingham <hbingham@acm.org>
Received on Tuesday, 20 June 2000 22:52:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:03 GMT