Skip to main content
RAWEBA

13.1 For each web page, does the user have control over each time limit modifying the content (excluding special cases)?

WCAG references
  • 2.2.1 Timing Adjustable (A)
  • 2.2.2 Pause, Stop, Hide (A)
Techniques
  • F40
  • F41
  • F58
  • F61
  • G75
  • G76
  • G110
  • G133
  • G180
  • G186
  • G198
  • H76
  • SCR1
  • SCR16
  • SCR36
  • SVR1

Official methodology to test criterion 13.1

Test 1 (13.1.1)

  1. Find in the document the refreshes initiated in the content by an <object>, <embed>, <svg>, <canvas> element or by a <meta http-equiv="refresh" content="[timer]"> element (in the <head> element of the page).
  2. For each refresh, check that
    • either there is a mechanism allowing the user to stop and restart the refresh;
    • or a mechanism is present which allows the user to increase the time limit between two refreshes by at least ten times;
    • or the presence of a mechanism which warns the user of the imminence of the refreshment, allows the user at least 20 seconds to increase the time limit before the next refreshment;
    • or the time limit between two refreshes is at least twenty hours.
  3. If this is the case, the test is validated.

Test 2 (13.1.2)

  1. In the document, find an automatic redirect initiated by a <meta http-equiv="refresh" /> element.
  2. If a redirection process exists, check:
    • either that the redirection is immediate (the content property must have the value 0, for example content="0; URL='https://url.com'")
    • or that the time limit before redirection is at least twenty hours (the content property then has a value greater than or equal to 72000, for example content="80000; URL='https://url.com'").
  3. If this is the case, the test is validated.

Test 3 (13.1.3)

  1. Find in the document the automatic redirects initiated by a script (in the form of a countdown for example).
  2. For each automatic redirect, check that
    • Either there is a mechanism enabling the user to stop and restart the redirect.
    • Or the presence of a mechanism allows the user to increase the time limit before refreshment by at least ten times.
    • Or the presence of a mechanism, that warns the user of the imminence of the refreshment, gives the user at least 20 seconds to increase the time limit before the next refreshment.
    • Or the time limit before the redirect is at least twenty hours.
  3. If this is the case, the test is validated.

Test 4 (13.1.4)

  1. Find in the document the procedures for limiting the time of a session (for example, after authentication).
  2. For each process, check that
    • either the presence of a mechanism allows the user to remove the time limit;
    • or the presence of a mechanism allows the user to increase the time limit;
    • or the time limit is at least twenty hours.
  3. If this is the case, the test is validated.