diff --git a/techniques/failures/F37.html b/techniques/failures/F37.html index 3fe8f663e2..6a3c9d9729 100644 --- a/techniques/failures/F37.html +++ b/techniques/failures/F37.html @@ -1,24 +1,37 @@ -Failure of Success Criterion 3.2.2 due to launching a new window without prior warning - when the selection of a radio button, check box or select list is changed

Failure of Success Criterion 3.2.2 due to launching a new window without prior warning - when the selection of a radio button, check box or select list is changed

ID: F37

Technology: failures

Type: Failure

When to Use

-

HTML

-

Description

-

This document describes a failure that occurs when changing the selection of a - radio button, a check box or an item in a select list causes a new window to - open. It is possible to use scripting to create an input - element that causes a change of context (submit the form, open a new page, a - new window) when the element is selected. Developers can instead use a - submit button (see Providing a submit - button to initiate a change of context) or clearly indicate the - expected action.

-

Examples

-
-

- -

The example below fails the Success Criterion because it processes - the form when a radio button is selected instead of using a submit - button.

- + + + + Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the selection of a radio button, check box or select list is changed + + + +

Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the selection of a radio button, check box or select list is changed

+
+

ID: F37

+

Technology: failures

+

Type: Failure

+
+
+

When to Use

+

HTML

+
+
+

Description

+

This document describes a failure that occurs when changing the selection of a + radio button, a check box or an item in a select list causes a new window to + open. It is possible to use scripting to create an input + element that causes a change of context (submit the form, open a new page, a + new window) when the element is selected. Developers can instead use a + submit button (see Providing a submit + button to initiate a change of context) or clearly indicate the + expected action.

+
+
+

Examples

+
+

The example below fails the Success Criterion because it processes + the form when a radio button is selected instead of using a submit + button.

<script> 
    function goToMirror(theInput) {
     var mirrorSite = "https://download." + theInput.value + "/"; 
@@ -43,20 +56,33 @@ 

<label for="mirror_voxel">voxel (<abbr>US</abbr>)</label><br /> </p> </form>
+
+
+
+

Tests

+
+

Procedure

+
    +
  1. Find each form in a page.
  2. +
  3. For each form control that is a radio button, check box or an item in a select list, + check if changing the selection of the control launches a new window.
  4. +
  5. For each new window resulting from step 2, check if the user is warned in advance.
  6. +
+
+

Expected Results

+

If check #3 is false, then this failure condition applies and content fails the Success Criterion.

+
+
Note that in the case of a set of radio buttons, adding an indication or warning + that selecting a radio button will result in a change of context will pass the requirements of 3.2.2 – however, + this scenario would then still fail 2.1.1 Keyboard, since it's not possible (in current user agents) for a user to + navigate through a set of radio buttons with the keyboard without triggering a change event. +
-

Tests

-

Procedure

-
    -
  1. Find each form in a page.
  2. -
  3. For each form control that is a radio button, check box or an - item in a select list, check if changing the selection of the - control launches a new window.
  4. -
  5. For each new window resulting from step 2, check if the user is - warned in advance.
  6. -
+ -

Expected Results

-

If check #3 is false, then this failure condition applies and content - fails the Success Criterion.

+
+

Resources

-

Resources

\ No newline at end of file + + \ No newline at end of file diff --git a/techniques/general/G13.html b/techniques/general/G13.html index a57bd9e195..5c11114a7e 100644 --- a/techniques/general/G13.html +++ b/techniques/general/G13.html @@ -1,46 +1,72 @@ -Describing what will happen before a change to a form control that causes a change of context to occur is made

Describing what will happen before a change to a form control that causes a change of context to occur is made

ID: G13

Technology: general

Type: Technique

When to Use

-

Applies to all technologies.

-

Description

-

The objective of this technique is to provide information to users about - what will happen when a change to a form control results in a change of - context. Because changing the value of a form control does not typically - result in a change of context, it is important that authors provide - instructions that make the user aware of the behavior in advance. Where - possible, it is a good idea to programmatically associate the instructions - describing the change with the form control itself.

-

The following are some examples of how to provide the instruction in different situations.

-
    -
  • Provide instruction on the Web page with reading order that precedes the user interface element that causes change of context by change of setting.
  • -
  • For a multi-step process where users must complete particular steps in order to reach the user interface element where changes of setting would cause a change of context, provide the instruction as part of the process prior to the step where they would encounter the change of context.
  • -
  • In the case of an intranet where user training is required prior to the use of a Web application where user interface elements that cause changes of context when settings are changed, instruction is provided as part of the training.
  • -
-

Examples

-
    -
  • A series of radio buttons at the top of a page include - options for German, French and Spanish. Instructions precede - the buttons that instruct the user that the language will be - changed upon selecting an option.
  • -
  • A 50 question online survey displays one question at a time. - Instructions appear at the beginning of the survey that - explain that users will be taken to the next question of the - survey upon selecting an answer to each question.
  • -
-

Tests

-

Procedure

+ + + + Describing what will happen before a change to a form control that causes a change of context to occur is made + + + +

Describing what will happen before a change to a form control that causes a change of context to occur is made

+
+

ID: G13

+

Technology: general

+

Type: Technique

+
+
+

When to Use

+

Applies to all technologies.

+
+
+

Description

+

The objective of this technique is to provide information to users about + what will happen when a change to a form control results in a change of + context. Because changing the value of a form control does not typically + result in a change of context, it is important that authors provide + instructions that make the user aware of the behavior in advance. Where + possible, it is a good idea to programmatically associate the instructions + describing the change with the form control itself.

+

The following are some examples of how to provide the instruction in different situations.

+
    +
  • Provide instruction on the Web page with reading order that precedes the user interface element that causes change of context by change of setting.
  • +
  • For a multi-step process where users must complete particular steps in order to reach the user interface element where changes of setting would cause a change of context, provide the instruction as part of the process prior to the step where they would encounter the change of context.
  • +
  • In the case of an intranet where user training is required prior to the use of a Web application where user interface elements that cause changes of context when settings are changed, instruction is provided as part of the training.
  • +
+
+
+

Examples

    -
  • Locate content where changing the setting of a form control +
  • A select dropdown/form control at the top of a page includes + options for German, French and Spanish. Instructions precede + the select control that instruct the user that the language will be + changed upon selecting an option.
  • +
  • A 50 question online survey displays one question at a time, with each + answer marked up as a toggle button. + Instructions appear at the beginning of the survey that + explain that users will be taken to the next question of the + survey upon selecting an answer to each question.
  • +
+

Tests

+

Procedure

+
    +
  • Locate content where changing the setting of a form control results in a change of context
  • -
  • Check to see that an explanation of what will happen when the +
  • Check to see that an explanation of what will happen when the control is changed is available prior to the controls activation
  • -
+ +
+

Expected Results

+
    +
  • Check #2 is true.
  • +
+
-

Expected Results

+ -

Resources

- -
\ No newline at end of file +
+

Resources

+
+ + \ No newline at end of file diff --git a/understanding/20/on-input.html b/understanding/20/on-input.html index 66223c97b6..7b872a32bb 100644 --- a/understanding/20/on-input.html +++ b/understanding/20/on-input.html @@ -104,12 +104,12 @@

Examples of On Input

  • A form is provided for creating calendar entries in a Web based calendaring and scheduling application. Along with the standard fields for subject, time and location, there - is a set of radio buttons to select the type of calendar entry to create. The calendar - entry type can be meeting, appointment or reminder. If the user selects the radio + is a select dropdown/form control to select the type of calendar entry to create. The calendar + entry type can be meeting, appointment or reminder. If the user selects the option for meeting, additional fields are displayed on the page for entering the meeting - participants. Different fields appear if the reminder button is chosen. Because only + participants. Different fields appear if the reminder option is chosen. Because only parts of the entry change and the overall structure remains the same the basic context - remains for the user. + remains for the user.