How can we effectively evaluate failures of SC 2.1.1 Timing Adjustable on a large number of pages?

Hi gang,

I recently encountered a page that had a multi-hour timeout, whose 
timeout wasn't adjustable, couldn't be turned off by the user, wasn't 
real-time, and was less than 20 hours.  I'm hard pressed to say the 
timeout was "essential".  But basically, after a few hours of logging 
into to this site, without warning, the user was logged out.

This appears to me to be a technical violation of SC 2.2.1 Timing 
Adjustable 
<http://www.w3.org/TR/2008/REC-WCAG20-20081211/#time-limits-required-behaviors>.

First off, I'm curious if my colleagues on this mailing list agree that 
this is a violation of SC 2.2.1.

Second off - and assuming you read it as a violation - I'm curious how 
SC 2.2.1 can be effectively tested on a large site.  If you decide that 
the appropriate sample size for a large site is 50 pages, does that mean 
we could potentially need to spend up to 1,000 hours to test the site 
just for this SC?  (that's 125 person-days, and doesn't deal with the 
fact that you might need a human being to discern when the change 
happened, or are there tools for this we can use?)


Peter
-- 
Oracle <http://www.oracle.com>
Peter Korn | Accessibility Principal
Phone: +1 650 5069522 <tel:+1%20650%205069522>
500 Oracle Parkway | Redwood City, CA 94064
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to 
developing practices and products that help protect the environment