Thread Subject: Time limit provision - Harmonizing with WCAG

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: Andrew LaHart
Date: Tue, Aug 14 2007 10:10 AM

In June, we agreed to harmonize most of parts of the 1194.22(p) Time Limit
provision with WCAG 2. The two remaining discussion points for
harmonization of this provision were on the Adjust and the Essential
Exception bullets.

The current wording of the Time Limit provision from the July 18 TEITAC
draft and WCAG 2 May 17 draft says:
"For each time limit that is set by the content, at least one of the
following must be 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 and time limits can not be extended further without invalidating
the activity. "

For the Adjust bullet, a concern was raised that ""before encountering"
might be confusing, and the suggestion was to add explanatory data
explaining what "before encountering" means. Having stewed on this for a
couple of weeks, is the feeling that "before encountering" is still
confusing? Does anyone object to accepting the Adjust bullet as is written
in WCAG?

For the essential exception bullet, Tom wanted to add text about time
limits that are in place for data security purposes. Tom added an
alternate proposal but we have not yet come to a resolution on this
provision. Here is Tom's comment from June 20:
"In the systems that I have been involved in testing that involved the
Federal Retirement information the scenario was that an annuitant was
unable to complete their transaction and leaving the connection open would
pose a security threat to other people's data. Perhaps it would be better
worded...

the time limit is part of an activity where timing is essential and time
limits can not be extended further without compromising the integrity of
the
data involved in the activity and invalidating the activity."

One could argue that the "timing is essential" portion of this bullet
covers the issue Tom brings up, but that requires a loose interpretation
of "timing is essential". What other thoughts does the Subcommittee have
on this issue and Tom's proposed edit?

Thanks
Drew

Andrew LaHart
IBM Human Ability and Accessibility Center
www.ibm.com/able

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University