- From: <akirkpat@adobe.com>
- Date: Tue, 02 Dec 2014 16:01:11 +0000
- To: Makoto Ueki <makoto.ueki@gmail.com>
- Cc: public-comments-wcag20@w3.org
Dear Makoto Ueki , The Web Content Accessibility Guidelines Working Group has reviewed the comments you sent [1] on the Last Call Working Draft [2] of the Web Content Accessibility Guidelines (WCAG) 2.0 published on 11 Dec 2008. Thank you for having taken the time to review the document and to send us comments! The Working Group's response to your comment is included below. Please review it carefully and let us know by email at public-comments-wcag20@w3.org if you agree with it or not before 10 Dec 2014. In case of disagreement, you are requested to provide a specific solution for or a path to a consensus with the Working Group. If such a consensus cannot be achieved, you will be given the opportunity to raise a formal objection which will then be reviewed by the Director during the transition of this document to the next stage in the W3C Recommendation Track. Thanks, For the Web Content Accessibility Guidelines Working Group, Michael Cooper W3C Staff Contact 1. http://www.w3.org/mid/E1Xee6F-0003WV-AZ@shauna.w3.org 2. http://www.w3.org/TR/2008/REC-WCAG20-20081211/ ===== Your comment on 2.2.3 No Timing: Timing is not an essential part of the ev...: > "2.2.1 Timing Adjustable" reads "For each time limit that is set by the > content,". "2.2.3 No Timing" reads "Timing is not an essential part of > the event or activity presented by the content". > > And then, in "Understanding SC 2.2.3", it reads "This differs from the > Level A Success Criterion in that the only exception is for real-time > events." in the section of "Intent of this Success Criterion". > > Is there any difference between "Time limit" and "Timing"? I'd like to > know the reason why "Timing" is used in SC 2.2.3 rather than "Time > limit". Working Group Resolution (LC-2972): The term Timing was used because it is the more general term. The term Timing can be used to indicate a time limit, and this is what SC 2.2.1 is directly addressing, but it can also be used to refer to a situation where user activities are timed and the information is used to evaluate the outcome, for example in the case of an online test where the user is evaluated not only on the accuracy of their answers but also on the time required to complete the test. In this case there is no time limit that prevents the user from completing the activity (which would be covered by 2.2.1) but the timing is an essential part of the activity In general, for SC 2.2.1 we meant to limit “timing” to just a simple time out on an activity which prevents users from completing an activity beyond a certain period of time. In SC 2.2.3 we refer to the broader issue of timing beyond time limits. As a result, the two SC use the term “Timing” in their titles to indicate their relation to each other, but SC 2.2.1 refers only to time limits. ----
Received on Tuesday, 2 December 2014 16:01:18 UTC