From bd6b04600a43a5a66f8d4f88eee3241196340f4a Mon Sep 17 00:00:00 2001 From: Glenda Sims Date: Mon, 11 Mar 2019 15:14:14 -0700 Subject: [PATCH 1/7] Create tech-timeout-20-hours-or-greater --- .../general/tech-timeout-20-hours-or-greater | 56 +++++++++++++++++++ 1 file changed, 56 insertions(+) create mode 100644 techniques/general/tech-timeout-20-hours-or-greater diff --git a/techniques/general/tech-timeout-20-hours-or-greater b/techniques/general/tech-timeout-20-hours-or-greater new file mode 100644 index 0000000000..05d0948aa0 --- /dev/null +++ b/techniques/general/tech-timeout-20-hours-or-greater @@ -0,0 +1,56 @@ + + + + Timeout occurs after user inactivity of 20 hours or greater + + + +

Failure due to functionality can be operated by pointer input but not with single-pointer activation alone

+
+

Metadata

+

+

general

+

failure

+
+
+

When to Use

+

Describe the situations in which to use the technique, such as types of pages, features in use that might use the technique, etc.

+
+
+

Description

+

Describe how the technique works. This begins with a description of the problem the technique solves, then describes how to apply the technique. The description should be detailed enough to provide all the information a reader needs to be able to apply the technique, without recourse to following example code.

+

The objective of this technique is to ...

+
+
+

Examples

+

Copy the following section for each example. Examples must have a title and a description, and usually have a code sample. Code samples should be elided if necessary to show the core of the technique without necessarily providing all the surrounding code that would also be involved. A working example link references a location where the technique can be shown working live.

+
+

Example Title

+

Description

+ Code sample +

Working example: link

+
+
+
+

Tests

+
+

Procedure

+
    +
  1. Step 1
    2. +
+
+
+

Expected Results

+
    +
  • Result
    • +
+
+
+ + + From 0fcb0675a90b4db79460d48fa1606251a7acdef7 Mon Sep 17 00:00:00 2001 From: Glenda Sims Date: Mon, 11 Mar 2019 15:15:14 -0700 Subject: [PATCH 2/7] Update tech-timeout-20-hours-or-greater --- techniques/general/tech-timeout-20-hours-or-greater | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/tech-timeout-20-hours-or-greater b/techniques/general/tech-timeout-20-hours-or-greater index 05d0948aa0..e6af3ecc22 100644 --- a/techniques/general/tech-timeout-20-hours-or-greater +++ b/techniques/general/tech-timeout-20-hours-or-greater @@ -5,7 +5,7 @@ -

Failure due to functionality can be operated by pointer input but not with single-pointer activation alone

+

Timeout occurs after user inactivity of 20 hours or greater

Metadata

From 17856b43878ca9187bdc23a5a0c69ef09ce5a76e Mon Sep 17 00:00:00 2001 From: Glenda Sims Date: Mon, 11 Mar 2019 16:47:34 -0700 Subject: [PATCH 3/7] Update tech-timeout-20-hours-or-greater --- .../general/tech-timeout-20-hours-or-greater | 40 +++++++++++-------- 1 file changed, 24 insertions(+), 16 deletions(-) diff --git a/techniques/general/tech-timeout-20-hours-or-greater b/techniques/general/tech-timeout-20-hours-or-greater index e6af3ecc22..41ef9abb50 100644 --- a/techniques/general/tech-timeout-20-hours-or-greater +++ b/techniques/general/tech-timeout-20-hours-or-greater @@ -10,46 +10,54 @@

Metadata

general

-

failure

+

sufficient

When to Use

-

Describe the situations in which to use the technique, such as types of pages, features in use that might use the technique, etc.

+

This technique relates to all technologies.

+

This technique relates to Success Criterion 2.2.6 Timeouts.

Description

-

Describe how the technique works. This begins with a description of the problem the technique solves, then describes how to apply the technique. The description should be detailed enough to provide all the information a reader needs to be able to apply the technique, without recourse to following example code.

-

The objective of this technique is to ...

+

The objective of this technique is to enable people with disabilities to start and complete a task, taking breaks as needed, without losing any data. People with cognitive limitations, low vision, motor impairments or blindness may not be able to complete a process in one sitting. They may need to take a break and then return to complete the task. A timeout that occurs after user inactivity of 20 hours or greater, allows for breaks that may be needed by some people with disabilities.

Examples

-

Copy the following section for each example. Examples must have a title and a description, and usually have a code sample. Code samples should be elided if necessary to show the core of the technique without necessarily providing all the surrounding code that would also be involved. A working example link references a location where the technique can be shown working live.

-
-

Example Title

-

Description

- Code sample -

Working example: link

+
    +
  • While making a purchase on an e-commerce Web site, the user has cognitive fatigue and needs to take a break. The user leaves the browser page open to hold their place in the checkout process and takes the break they need. Because there is a 20 hour timeout, the user can return within that 20 hours to complete the checkout and purchase without starting over.
    • +
  • While taking an online training course, the user with a motor disability needs to take a break. The user leaves the online training window open to hold their place and takes the break they need. Because there is a 30 hour timeout, the user can return within that 20 hours to complete that training course without starting over.
    • +

Tests

Procedure

-
    -
  1. Step 1
    2. -
+
    +
  1. Identify any digital content that has a time out function due to user inactivity.
    2. +
  2. Navigate to that digital content and then interact with that content to the point where you have input user data or reached a point in the task path where a user could want to return without starting over.
    3. +
  3. Then do not interact with that content for 19 hours and 59 minutes.
    4. +
  4. At exactly 19 hours and 59 minutes, interact with the content.
    5. +
  5. Check that all of the following are true: +
      +
    • Any user data entered in this digital content process has been retained.
      • +
    • The user can resume at the place where they left off.
      • +
    +
    6. +

Expected Results

-
    -
  • Result
    • +
      +
    • Check #5 is true.
From fa7906c96fe9a96e2223f64a530063721e1fbbf6 Mon Sep 17 00:00:00 2001 From: Glenda Sims Date: Mon, 11 Mar 2019 16:51:05 -0700 Subject: [PATCH 4/7] Update tech-timeout-20-hours-or-greater --- techniques/general/tech-timeout-20-hours-or-greater | 1 - 1 file changed, 1 deletion(-) diff --git a/techniques/general/tech-timeout-20-hours-or-greater b/techniques/general/tech-timeout-20-hours-or-greater index 41ef9abb50..f0e5cff3db 100644 --- a/techniques/general/tech-timeout-20-hours-or-greater +++ b/techniques/general/tech-timeout-20-hours-or-greater @@ -27,7 +27,6 @@
  • While making a purchase on an e-commerce Web site, the user has cognitive fatigue and needs to take a break. The user leaves the browser page open to hold their place in the checkout process and takes the break they need. Because there is a 20 hour timeout, the user can return within that 20 hours to complete the checkout and purchase without starting over.
  • While taking an online training course, the user with a motor disability needs to take a break. The user leaves the online training window open to hold their place and takes the break they need. Because there is a 30 hour timeout, the user can return within that 20 hours to complete that training course without starting over.
    • -

    Tests

    From 3ab586d46a2586d38993031af36fade81463e92a Mon Sep 17 00:00:00 2001 From: Glenda Sims Date: Mon, 11 Mar 2019 16:54:10 -0700 Subject: [PATCH 5/7] Update tech-timeout-20-hours-or-greater --- techniques/general/tech-timeout-20-hours-or-greater | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/general/tech-timeout-20-hours-or-greater b/techniques/general/tech-timeout-20-hours-or-greater index f0e5cff3db..5ee82d37f4 100644 --- a/techniques/general/tech-timeout-20-hours-or-greater +++ b/techniques/general/tech-timeout-20-hours-or-greater @@ -24,8 +24,8 @@

    Examples

      -
    • While making a purchase on an e-commerce Web site, the user has cognitive fatigue and needs to take a break. The user leaves the browser page open to hold their place in the checkout process and takes the break they need. Because there is a 20 hour timeout, the user can return within that 20 hours to complete the checkout and purchase without starting over.
      • -
    • While taking an online training course, the user with a motor disability needs to take a break. The user leaves the online training window open to hold their place and takes the break they need. Because there is a 30 hour timeout, the user can return within that 20 hours to complete that training course without starting over.
      • +
    • While making a purchase on an e-commerce Web site, the user has cognitive fatigue and needs to take a break. The user leaves the browser page open to hold their place in the checkout process and takes the break they need. Because there is a 20-hour timeout, the user can return within that 20 hours to complete the checkout and purchase without starting over.
      • +
    • While taking an online training course, the user with a motor disability needs to take a break. The user leaves the online training window open to hold their place and takes the break they need. Because there is a 20-hour timeout, the user can return within that 20 hours to complete that training course without starting over.
    From 037f17e7c52da5693ed878c08093cba5dbf17cc2 Mon Sep 17 00:00:00 2001 From: Glenda Sims Date: Mon, 11 Mar 2019 16:57:59 -0700 Subject: [PATCH 6/7] Update tech-timeout-20-hours-or-greater --- techniques/general/tech-timeout-20-hours-or-greater | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/tech-timeout-20-hours-or-greater b/techniques/general/tech-timeout-20-hours-or-greater index 5ee82d37f4..3cdb2af459 100644 --- a/techniques/general/tech-timeout-20-hours-or-greater +++ b/techniques/general/tech-timeout-20-hours-or-greater @@ -19,7 +19,7 @@

    Description

    -

    The objective of this technique is to enable people with disabilities to start and complete a task, taking breaks as needed, without losing any data. People with cognitive limitations, low vision, motor impairments or blindness may not be able to complete a process in one sitting. They may need to take a break and then return to complete the task. A timeout that occurs after user inactivity of 20 hours or greater, allows for breaks that may be needed by some people with disabilities.

    +

    The objective of this technique is to enable people with disabilities to start and complete a task, taking breaks as needed, without losing any data. People with cognitive limitations, low vision, motor impairments or blindness may not be able to complete a process in one sitting. They may need to take a break and then return to complete the task. A timeout that occurs after user inactivity of 20 hours or greater, allows for breaks that are needed by some people with disabilities.

    Examples

    From 478a9a9120c49b28e6a87ca08ea3e61f0a5832ed Mon Sep 17 00:00:00 2001 From: Glenda Sims Date: Mon, 11 Mar 2019 17:03:58 -0700 Subject: [PATCH 7/7] Update tech-timeout-20-hours-or-greater --- techniques/general/tech-timeout-20-hours-or-greater | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/general/tech-timeout-20-hours-or-greater b/techniques/general/tech-timeout-20-hours-or-greater index 3cdb2af459..021cb356a1 100644 --- a/techniques/general/tech-timeout-20-hours-or-greater +++ b/techniques/general/tech-timeout-20-hours-or-greater @@ -36,7 +36,7 @@
  • Identify any digital content that has a time out function due to user inactivity.
  • Navigate to that digital content and then interact with that content to the point where you have input user data or reached a point in the task path where a user could want to return without starting over.
  • Then do not interact with that content for 19 hours and 59 minutes.
    • -
  • At exactly 19 hours and 59 minutes, interact with the content.
    • +
  • At 19 hours and 59 minutes, interact with the content.
  • Check that all of the following are true:
    • Any user data entered in this digital content process has been retained.