Techniques for Guideline 2.2

Good news and bad news on techniques for Guideline 2.2.

The good news is, although the schedule shows that we should be
presenting Guideline 2.2 at tomorrow's call, the editors decided it
would be better to close off 2.1 first rather than move on just because
the schedule says so. So 2.2 is not on the agenda for tomorrow.
Presumably it will be for next week though, so we shouldn't feel free to
take a break.

The bad news is, while we do only have to do one sufficient technique
per success criterion, we must do all the failure techniques. Therefore,
I need to get volunteers for the following techniques (in addition to
the ones not yet claimed from the sufficient techniques):

1. Failure due to using server-side techniques to automatically redirect
pages after a timeout. (2.2.1) (I can take this)

2. Failure due to including blinking content that can't be turned off.
(2.2.2)

3. Failure due to a script that causes a blink effect without a
mechanism to pause the content that blinks for more than three seconds.
(2.2.2)

4. 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. (2.2.2)

5. 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. (2.2.6)

Michael

Received on Wednesday, 11 January 2006 18:08:59 UTC