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

GL 2.2: updated proposals

From: Christophe Strobbe <christophe.strobbe@esat.kuleuven.ac.be>
Date: Wed, 15 Jun 2005 07:09:18 +0200
Message-Id: <6.0.0.22.2.20050614190139.02f9cec8@mailserv.esat.kuleuven.be>
To: w3c-wai-gl@w3.org
Hi,

As a result of the 26 May teleconference [1], I had the following
action items:

    * look at comments on issue 1525 and write proposal to address.
    * rework proposal for Level 1 SC 1 based on feedback.
    * reword proposal for Level 2 SC 1 based on feedback.


Based on the issues and feedback for L1 SC1, the proposal is to remove
the second bullet point from the current wording. This results in the
following:

<proposed>
Content is designed so that time-outs are not an essential part of
interaction, or at least one of the following is true for each time-out
that is a function of the content: [I]
   * the user is allowed to deactivate the time-out or;
   * the user is warned before time expires, allowed to extend the
     time-out with a simple action (for example, "hit any key") and given
     at least 20 seconds to respond or;
   * the time-out is an important part of a real-time event (for example,
     an auction), and no alternative to the time-out is possible or;
   * the time-out is part of an activity where timing is essential
     (for example, competitive gaming or time-based testing) and time
     limits can not be extended further without invalidating the activity.
</proposed>

<rationale>
According to the feedback, the old proposal was not acceptable at
level 1. The current wording was found "helpful", "easier to understand
and to test against", etc.
This addresses issues 943, 1092 and part of 1044 (which comment on
"ten times the default setting" in the second bullet point) and rejects
the concern in issues 1346 and 1381 (which say that this success criterion
violates usability).
Combined with the next proposal, this could close issue 1044.
</rationale>



Based on the issues and feedback for L2 SC1, the new proposal is:

<proposed>
Content does not blink for more than 3 seconds, or a method is
available to stop any blinking content in the delivery unit.
</proposed>

<current>
A method is provided to stop content that blinks for more than 3 seconds.
</current>

<rationale>
The updated proposal avoids that users should stop blinking on an
instance-by-instance basis (instead of once for the whole delivery unit).
</rationale>



Based on the feedback for issue 1525, we might add a new criterion at
level 2 or 3:

<proposed>
When an authenticated session has an inactivity timeout, the user can
continue his activity without loss of data after re-authenticating.
</proposed>

<current> None. </current>

<rationale>
Based on the feedback, it seemed important to cover this scenario,
but server-side timeouts are not covered at level 1.
</rationale>


The HTML document attached to this e-mail contains an update of
the previous issue summaries and proposals.


Regards,

Christophe Strobbe



[1] http://www.w3.org/2005/05/26-wai-wcag-minutes.html



-- 
Christophe Strobbe
K.U.Leuven - Departement of Electrical Engineering - Research Group 
on  Document Architectures
Kasteelpark Arenberg 10 - 3001 Leuven-Heverlee - BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/ 


Received on Wednesday, 15 June 2005 05:10:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:37 UTC