Thread Subject: Re: Time limit provision - Harmonizing withWCAG
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Brad Hodges
Date: Wed, Jun 20 2007 9:35 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Time limit provision - Harmonizing withWCAG"
- Previous message in thread: Gregg Vanderheiden: "Re: Time limit provision - Harmonizing withWCAG"
- Messages sorted by: Author | Thread | Date
Greetings:
I share the concern that this will be used in an overly broad manner I
suggest adding the word only to the text.
Essential Exception: only when the time limit is part of an activity
where timing is essential and time limits can not be extended further
without invalidating the activity and compromising the integrity of the
data involved in the activity.
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Tom
Brett
Sent: Wednesday, June 20, 2007 10:45 AM
To: 'TEITAC Web/Software Subcommittee'
Subject: Re: [teitac-websoftware] Time limit provision - Harmonizing
withWCAG
I would think that many developers would use the proposed wording of the
Essential Exception to get away with not providing methods alternative
methods to adjust the timing.
I would propose:
Essential Exception: the time limit is part of an activity where timing
is essential and time limits can not be extended further without
invalidating the activity and compromising the integrity of the data
involved in the activity.
Tom Brett
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of David
Poehlman
Sent: Wednesday, June 20, 2007 10:27 AM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Time limit provision - Harmonizing
withWCAG
Looking at this, I havfe a concern where testing is done. I am under
the impression that persons with disabilities have an exemption or an
adjustment
in this regard.
----- Original Message -----
From: "Andrew LaHart" < = EMAIL ADDRESS REMOVED = >
To: < = EMAIL ADDRESS REMOVED = >
Sent: Wednesday, June 20, 2007 9:51 AM
Subject: [teitac-websoftware] Time limit provision - Harmonizing with
WCAG
Last week we agreed to harmonize parts of the 1194.22(p) Time Limit
provision with WCAG 2. For a detailed recap of the 1194.22(p)
discussion, please see the notes from last weeks meeting (
http://teitac.org/wiki/Web_and_Software:_June_13).
The current wording of the Time Limit provision from the May Plenary
Meeting Draft says:
"For each time limit that is set by the content, at least one of the
following is true:
Deactivate: the user shall be allowed to deactivate the time limit; or
Adjust: the user shall be allowed to adjust the time limit over a wide
range that is at least ten times the length of the default setting; or
Extend: the user shall be 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 an important 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. "
The WCAG 2 May 17 Working Draft says
"For each time limit that is set by the content , at least one of the
following is true:
Turn off: the user is allowed to turn off 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, time-based testing) and time limits can not be
extended further without invalidating the activity. "
There was agreement to harmonize the Turn off, Extend, and Real-time
exception bullets.
For the Adjust bullet, the concern was that "before encountering" might
be
confusing, and the suggestion was to add explanatory data explaining
what
"before encountering" means. If we
For the Essential Exception bullet, we agreed to remove the parentheses
and associated text. There were other questions about this bullet, but
we
ended the discussion after agreement to remove the text in parentheses.
Are there still concerns with the bullet, even when the parentheses are
removed? The new bullet would look like this:
Essential Exception: the time limit is part of an activity where timing
is
essential and time limits can not be extended further without
invalidating
the activity.
Thanks,
Drew
Andrew LaHart
IBM Human Ability and Accessibility Center
w3.ibm.com/able
------------------------------------------------------------------------
----
----
- Next message in Thread: Gregg Vanderheiden: "Re: Time limit provision - Harmonizing withWCAG"
- Previous message in Thread: Gregg Vanderheiden: "Re: Time limit provision - Harmonizing withWCAG"