Edit comment LC-1238 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-641 Next: LC-819

Comment LC-1238: Comment Shortname:; Commenter: Kiyochika Nakamura <nakamura-kiyochika@mitsue.co.jp> on behalf of Mitsue-Links Co., Ltd.; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Comment: Why this criterion allows the time-out which is not essential for its function? If the first three list items of the criteria are allowed, some users might not be able to read through the content. For example, when the function to deactivate the time-out is provided but it is placed on the end of the page, then some users cannot reach the function before the time-out.

Proposed Change:

Omit the first three list items from this criterion.; Related issues: (space separated ids); WG Notes: [TEAMC] MichaelC: It is expected by this SC that users can adjust the timeout before the first time they get zinged by it. Although it doesn't specify in so many words, I'd say it's pretty well implied by the requirement that users be able to adjust the timeout. Some clarifications might help, though. See action at http://www.w3.org/WAI/GL/2006/07/10-wcag-teamc-minutes.html Discussed in the 08 February 2007 telecon: Resolution: close issue LC-1238 by not adding the failure and by adding the phrase "before encountering it" to the first two bullets of SC 2.2.1 http://www.w3.org/WAI/GL/2007/02/08-wai-wcag-minutes.html [partial accept] DONE Revise fist two bullets of 2.2.1: Deactivate: the user is allowed to deactivate the [begin change]time limit[end change] <add>before encountering it</add>; or Adjust: the user is allowed to adjust the [begin change]time limit[end change] <add>before encountering it</add> over a wide range... Internal WD updated 22 March 2007. @@When technique "Providing a way for the user to turn the time-out off (future link)" is created, ensure it specifies that the user must be able to find and use the mechanism to turn off the time-out before the time-out happens. Response: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0064.html; Resolution: Providing a mechanism to update a time-out that the user may not encounter before the time-out expires would not meet the requirements of this SC. We have revised SC 2.2.1 to clarify this: 2.2.1 Timing: For each time limit that is set by the content , at least one of the following is true: * Deactivate: the user is allowed to deactivate the time limit before encountering it; or * Adjust: the user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or * Extend: the user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "hit any key"), and the user is allowed to extend the time limit at least ten times; or * Real-time Exception: the time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or * Essential Exception: the time limit 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.; (Please make sure the resolution is adapted for public consumption)