Techniques to review week of February 13 2006

Here's another batch of techniques for Team C to review. I've included
Christophe, David, and Gez in this, who have been volunteered to help us
out on behalf of Team A. If you can all review your two techniques by
the time of next Monday's call it will help us to stay on track. Note
the way the techniques are assigned is pseudo-random and I apologize if
your techniques fall outside your area of best expertise - but please do
your best nonetheless!

Suggestions for how to review the techniques are the same as in the last
round - see
http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jan/0057.html.
One thing that was particularly helpful when we discussed the techniques
in this week's call was the way Sofia and Andi put suggestions directly
in the wiki, and responded to each others' suggestions there. It was
much easier to keep everything in context and make decisions on the
call, so I'd like to encourage everyone to follow that model if you can.

Andi

* Controlling blink with script and stopping it after three seconds
<http://tinyurl.com/a8vjn>
* Failure due to including blinking content that can't be turned off
<http://tinyurl.com/7rnmc>

Makoto

* Failure due to a script that causes a blink effect without a mechanism
to pause the content that blinks for more than three seconds
<http://tinyurl.com/9vxh2>
* Failure due to an object, such as Java or Flash, that has blinking
content without a mechanism to pause the content that blinks for more
than three seconds <http://tinyurl.com/8k86h>

Michael

* Allowing the content to be paused and restarted from where it was
stopped <http://tinyurl.com/9odcy>
* Failure due to including scrolling content where there is not a
mechanism to pause the content <http://tinyurl.com/arsvr>

Sofia

* Designing an activity so that timing is not an essential part of the
activity <http://tinyurl.com/76h2r>
* Providing a mechanism to postpone any updating of content
<http://tinyurl.com/8ff7e>

Tim

* Allowing users to request updates instead of automatically updating
content <http://tinyurl.com/aqypt>
* If users submit data when the user is no longer authenticated, the
data is saved and the data is reused after the user re-authenticates
<http://tinyurl.com/8qda2>

Christophe

* Having no mechanism to save the data a user has entered when a session
times out, thus forcing the user to re-enter all the data after
re-authenticating <http://tinyurl.com/7wvmv>
* Providing a text message that identifies the field as mandatory
<http://tinyurl.com/b9g9a>

David

* Providing a text message when the user provides any information that
falls outside the required data format or values
<http://tinyurl.com/cv6mg>
* Providing client-side validation and alert <http://tinyurl.com/dk2rp>

Gez

* Providing client-side validation and adding error text via the DOM
<http://tinyurl.com/9blwe>
* Providing a text message that identifies the field as mandatory
<http://tinyurl.com/7qjv4>

Received on Tuesday, 14 February 2006 18:54:27 UTC