Techniques for 2.2

In the Team C teleconference today we winnowed down the list of techniques for Guideline 2.2. Given that we only need to produce a minimum of one sufficient technique for each success criterion, there are six techniques we need to produce. Below are listed the first sufficient technique in each of the success criterion. I would like to ask each member of the team to volunteer to take one of them. Please reply to the list so we don't get duplicates. If I don't get volunteers soon, I'll make assignments. :)
1. Providing a script on page that warns the user and allows the user to extend time or turn off the timeout <> . (see 
2. Ensuring content blinks for less than three seconds <>  (see
3. Allowing the content to be paused and restarted from where it was stopped <> . (see
4. Designing an activity so that timing is not an essential part of the activity <> . (see
5. Providing a mechanism to postpone any updating of content <>  (See
6. 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 <> . (see
Sorry for the formatting - using a Webmail client that's a pain.

Received on Tuesday, 10 January 2006 01:08:31 UTC