[Jason] 2.2.1 uses the phrase “time limit that is set by the content”. Real-time events and “essential” exceptions are then handled as exceptions (i.e., special cases). This treatment makes it clear that such cases are indeed instances of “time limits set by the content” as this phrase is used in WCAG, contrary to your assertion above. If you want to exclude them from any proposal, it has to be done explicitly. The difference is that 2.2.1 is about adjusting the timing for a limit, and there are three exceptions for making that happen – one is that the limit is essential, another is that the limit is long (more than 20 hours), and finally if it is part of the real-time event. It feels very "chicken and egg”-ish to me – are the time limits for a real-time event set by the web site or by the (for example) auctioneer? I suppose theoretically a time-limit for a real-time event could be controlled by a web site, but then the time limit is known by the web site and can be communicated. If the limit is based on seat availability and how many other people in the world buy tickets, then that is real time but not controlled by the content. If it made people more comfortable I wouldn’t have a concern about adding: Time Limits: For each time limit set by the content where user-entered data can be lost, the user is advised about the length of the time limit at the start of the process, unless any user-entered data is preserved for at least 24 hours after the limit is reached. * Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and the length of the time limit is not known. How’s that sound? AWK
Received on Friday, 12 May 2017 14:19:30 UTC