Techniques for WCAG 2.0

Skip to Content (Press Enter)

This document is a draft, and is designed to show changes from a previous version. It is presently showing added text,changed text,deleted text,[start]/[end] markers,and Issue Numbers.

Hide All Edits   |   Toggle Deletions  |   Toggle Issue Numbers   |   Toggle [start]/[end] Markers   |   Show All Edits

Changes are displayed as follows:

-

SCR1: Allowing the user to extend the default time limit

Applicability

Time limits that are controlled by client-side scripting.

This technique relates to:

Description

The objective of this technique is to allow user to extend the default time limit by providing a mechanism to extend the time when scripts provide functionality that has default time limits. In order to allow the user to request a longer [begin delete]than default [end delete]time limit, the script can provide a form (for example) allowing the user to enter a larger [begin delete]default [end delete]time limit [begin add]or indicating that more time is needed[end add]. [begin delete]Making this available as a preference setting allows users to indicate their requirements in advance. [end delete]If warning the user a time limit is about to expire (see SCR16: Providing a script that warns the user a time limit is about to expire), this form can be made available from the warning dialog. [begin add]The user can extend the time limit to at least 10 times the default time limit, either by allowing the user to indicate how much additional time is needed or by repeatedly allowing the user to extend the time limit.[end add]

Examples

Resources

Resources are for information purposes only, no endorsement implied.

  1. setting session and default time limits using Java servlets

  2. Overriding timeouts in peers applications

  3. PHPBuilder Time-out Info

Tests

Procedure

  1. On a Web page that uses scripts to enforce a time limit, wait until the time limit has expired.

  2. Determine if an option was provided to extend the time limit.

Expected Results