- From: Vivienne CONWAY <v.conway@ecu.edu.au>
- Date: Fri, 20 Sep 2013 15:53:41 +0800
- To: "w3c-wai-ig@w3.org list" <w3c-wai-ig@w3.org>
- Message-ID: <8AFA77741B11DB47B24131F1E38227A9013E6D5BAC2B@XCHG-MS1.ads.ecu.edu.au>
Hi all I'm trying to get my head around what would constitute a failure for 2.2.4 Interruptions. Looking at G75, it would seem that it could allow the user to postpone updates and might thereby make a decision based on out-dated information as in the example given of changing the update timing for stock market quotations. Can anyone give me an example of where this might be beneficial? I don't really think the above example is sufficient. Regards Vivienne L. Conway, B.IT(Hons), MACS CT, AALIA(CS) PhD Candidate & Sessional Lecturer, Edith Cowan University, Perth, W.A. Director, Web Key IT Pty Ltd. v.conway@ecu.edu.au<mailto:v.conway@ecu.edu.au> v.conway@webkeyit.com<mailto:v.conway@webkeyit.com> Mob: 0415 383 673 This email is confidential and intended only for the use of the individual or entity named above. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify me immediately by return email or telephone and destroy the original message. ________________________________ This e-mail is confidential. If you are not the intended recipient you must not disclose or use the information contained within. If you have received it in error please return it to the sender via reply e-mail and delete any record of it from your system. The information contained within is not the opinion of Edith Cowan University in general and the University accepts no liability for the accuracy of the information provided. CRICOS IPC 00279B
Received on Friday, 20 September 2013 07:54:52 UTC