This document:Public document·View comments·Disposition of Comments·
Nearby:Accessibility Guidelines Working Group Other specs in this tool Accessibility Guidelines Working Group's Issue tracker
Quick access to LC-2582 LC-2583 LC-2584 LC-2595 LC-2596 LC-2601 LC-2605 LC-2610 LC-2611 LC-2612 LC-2613 LC-2619 LC-2620 LC-2622 LC-2625 LC-2626 LC-2627 LC-2628 LC-2631 LC-2632 LC-2646 LC-2647 LC-2648 LC-2683 LC-2684 LC-2703 LC-2704 LC-2718 LC-2719 LC-2723 LC-2724 LC-2726 LC-2728 LC-2729 LC-2730 LC-2745 LC-2770 LC-2771 LC-2773
Previous: LC-2595 Next: LC-2601
Since timings affecting the user may be hidden (a meta refresh or a server side timeout) and become only apparent after interaction, e.g., when the site responds with a time-out message after a form is submitted, the test in G5 is not really effective. It would either need to limit itself to clearly visible time-dependent interactions (as in interactive games) and openly represented timings (as in online banking numerical or visual count-down displays that are reset with every activity) or it would need a test procedure as complex as the one recently suggested for F61 (Wait 10 times the average duration, check whether content / context is still available). Proposed Change: Limit G5 to visible timed events, or extend test procedure to account for hidden (e.g. server side) time-outs that may affect the user interactions (such as form submission) but are not observable without a procedure as lengthy as the one recently suggested for F61.