From d14ed9d51e7c42a81118ee1bd96cadc59b0b814c Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Thu, 25 May 2023 18:36:55 +0100 Subject: [PATCH 01/15] Frances' proposed response --- techniques/failures/F85.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 1cd8c708fa..01892ecf31 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -2,6 +2,7 @@

All technologies.

Description

This describes the failure condition that results when a Web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, and it is not adjacent to the trigger control in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

+

Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a Web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

Examples

Adding a dialog or menu embedded on the page to the end of the sequential navigation order

@@ -23,14 +24,14 @@

Setting focus to the document after dismissing a menu embedded on the pageActivate the trigger control via the keyboard.

  • Check whether focus is in the menu or dialog.
    • -
  • Check whether advancing the focus in the sequential navigation order puts focus in the menu or dialog.
    • +
  • Check whether moving the focus forwards once in the sequential navigation order puts focus in the menu or dialog.
  • -

    Dismiss the menu or dialog.

    +

    Dismiss the menu or dialog

    • Check whether focus is on the trigger control.
      • -
    • Check whether advancing the focus backwards in the sequential navigation order puts focus in the trigger control.
      • +
    • Check whether moving the focus backwards once in the sequential navigation order puts focus in the trigger control.
    • From 17f689a6e12b32217581ad22bc8c7a43e4b39133 Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 30 May 2023 17:29:37 +0100 Subject: [PATCH 02/15] Update techniques/failures/F85.html --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 01892ecf31..8a6539dd01 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -31,7 +31,7 @@

    Setting focus to the document after dismissing a menu embedded on the pageDismiss the menu or dialog

    • Check whether focus is on the trigger control.
      • -
    • Check whether moving the focus backwards once in the sequential navigation order puts focus in the trigger control.
      • +
    • Check whether moving the focus backwards once in the sequential navigation order puts focus on the trigger control.
    From 615b2a046b138ce60728fad1399aceb0c62e49d1 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Wed, 6 Nov 2024 14:36:22 -0800 Subject: [PATCH 03/15] Address comments on moving focus, update DTML content MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 1. Remove content about pressing the Tab key to find the triggering control. 2. Add a check to allow focus to be placed on a logical other control if the triggering element has been removed from the DOM. 3. Updated the “DHTML” content. --- techniques/failures/F85.html | 102 +++++++++++++++++++++-------------- 1 file changed, 63 insertions(+), 39 deletions(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 430ecd8e35..29ce53c874 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -1,47 +1,71 @@ -Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order

    Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order

    ID: F85

    Technology: failures

    Type: Failure

    When to Use

    + + + + Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order + + + +

    Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order

    +
    +

    ID: F85

    +

    Technology: failures

    +

    Type: Failure

    +
    +
    +

    When to Use

    All technologies.

    -

    Description

    -

    This describes the failure condition that results when a Web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, and it is not adjacent to the trigger control in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    -

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a Web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    -

    Examples

    -
    -

    Adding a dialog or menu embedded on the page to the end of the sequential navigation order

    - -

    When a DHTML menu or dialog is activated, it is created dynamically, positioned visually near the trigger, and appended to the end of the DOM. Because it is appended to the end of the DOM, it is at the end of the sequential navigation order. The user must tab through the rest of the web page before they can interact with the dialog or menu.

    - +
    +
    +

    Description

    +

    This describes the failure condition that results when a web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, and it is not adjacent to the trigger control in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    +

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    +
    +
    +

    Examples

    +
    +

    Adding a dialog to the page at the end of the sequential navigation order

    +

    A non native HTML dialog is created, with its code at the end of the DOM (Document Object Model). The dialog is visually positioned above the content of the page and the user's focus isn't moved to the dialog. Because the dialog's code is at the end of the DOM, it is at the end of the keyboard navigation order. Because the user's focus isn't manage, they must tab through the rest of the web page before they can interact with the dialog or menu.

    -

    Setting focus to the document after dismissing a menu embedded on the page

    - -

    When a menu is dismissed, it is removed or hidden from the web page and focus is set to the document. The user must tab from the beginning of the navigation sequence to reach the point from which the menu was opened.

    - +

    Setting focus to the document after dismissing a menu embedded on the page

    +

    When a menu is dismissed, it is removed or hidden from the web page and focus is set to the document. The user must tab from the beginning of the navigation sequence to reach the point from which the menu was opened.

    -

    Tests

    -

    Procedure

    -

    For each menu or dialog embedded on a Web page that is opened via a trigger control:

    +
    +
    +

    Tests

    +
    +

    Procedure

    +

    For each menu or dialog on a web page that is opened via a trigger control:

      -
    1. -

      Activate the trigger control via the keyboard.

      -
        -
      • Check whether focus is in the menu or dialog.
        • -
      • Check whether moving the focus forwards once in the sequential navigation order puts focus in the menu or dialog.
        • -
      -
      2. -
    2. -

      Dismiss the menu or dialog

      -
        -
      • Check whether focus is on the trigger control.
        • -
      • Check whether moving the focus backwards once in the sequential navigation order puts focus on the trigger control.
        • -
      -
      3. -
    +
  • +

    Activate the trigger control via the keyboard.

    +
      +
    • Check whether focus is in the menu or dialog.
      • +
    • Check whether moving the focus forwards once in the sequential navigation order puts focus in the menu or dialog.
      • +
    +
    • +
  • +

    Dismiss the menu or dialog

    +
      +
    • Check whether focus is on the trigger control.
      • +
    • If the trigger control has been removed from the DOM, check whether focus has been moved to a logical other control.
      • +
    +
    • +
    -

    Expected Results

    -
      -
    • If both points under step 1 are false, then this failure condition applies and the content fails this success criterion.
      • -
    • If both points under step 2 are false, then this failure condition applies and the content fails this success criterion.
      • +
      +

      Expected Results

      +
        +
      • If both points under step 1 are false, then this failure condition applies and the content fails this success criterion.
        • +
      • If both points under step 2 are false, then this failure condition applies and the content fails this success criterion.
      -
    +
    + + + From 699eabc60f5d63936417bd980c9a6dfc57dc2440 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 8 Nov 2024 09:52:30 -0800 Subject: [PATCH 04/15] Tweak wording --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 29ce53c874..0503b26a65 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -48,7 +48,7 @@

    Procedure

    Dismiss the menu or dialog

    • Check whether focus is on the trigger control.
      • -
    • If the trigger control has been removed from the DOM, check whether focus has been moved to a logical other control.
      • +
    • If focus needs to be placed on a different control (for example, if the original trigger control has been removed from the DOM), check whether that control is logical.
    From 8aa8b5b6ffb4e2a56a3c93f6a5553ba80d506d62 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 8 Nov 2024 09:56:01 -0800 Subject: [PATCH 05/15] Another tweak --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 0503b26a65..fc651f9a65 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -48,7 +48,7 @@

    Procedure

    Dismiss the menu or dialog

    • Check whether focus is on the trigger control.
      • -
    • If focus needs to be placed on a different control (for example, if the original trigger control has been removed from the DOM), check whether that control is logical.
      • +
    • If focus needs to be placed on a different control (for example, if the original trigger control has been removed from the DOM), check whether that different control is logical.
    From c0f9c7561ada0253d541094292e1177dbde8f391 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Thu, 21 Nov 2024 16:50:08 -0800 Subject: [PATCH 06/15] Expand example into a note --- techniques/failures/F85.html | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index fc651f9a65..40842e6e70 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -2,7 +2,7 @@ Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order - +

    Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order

    @@ -18,7 +18,14 @@

    When to Use

    Description

    This describes the failure condition that results when a web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, and it is not adjacent to the trigger control in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    -

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    + +
    +

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    +
    + +
    +

    Sometimes it's not possible to return focus to the control the user activated to open a dialog. For example: a blog post has a list of tags, each tag containing a delete button. Pressing a delete button opens a modal dialog that asks the user to confirm the deletion. On confirming the deletion, the tag is deleted, the modal dialog closes, and focus is placed on the next tag in the list of tags. Placing focus onto a different, but logical, control is not a failure of Success Criterion 2.4.3.

    +

    Examples

    @@ -48,7 +55,7 @@

    Procedure

    Dismiss the menu or dialog

    • Check whether focus is on the trigger control.
      • -
    • If focus needs to be placed on a different control (for example, if the original trigger control has been removed from the DOM), check whether that different control is logical.
      • +
    • If focus needs to be placed on a different control, check whether that different control is logical.
    From c9498e5babbca15234e8c9a261335c527a07e8b2 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Fri, 22 Nov 2024 08:54:32 -0800 Subject: [PATCH 07/15] Update techniques/failures/F85.html --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 40842e6e70..3a89da6b1d 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -48,7 +48,7 @@

    Procedure

    Activate the trigger control via the keyboard.

    • Check whether focus is in the menu or dialog.
      • -
    • Check whether moving the focus forwards once in the sequential navigation order puts focus in the menu or dialog.
      • +
    • Check whether moving the focus forward once in the sequential navigation order puts focus in the menu or dialog.
  • From 1848a1a085ed727c0cecb51a24a1d200064ad75a Mon Sep 17 00:00:00 2001 From: "Kenneth G. Franqueiro" Date: Fri, 22 Nov 2024 12:04:52 -0500 Subject: [PATCH 08/15] Formatting pass --- techniques/failures/F85.html | 102 +++++++++++++++++------------------ 1 file changed, 51 insertions(+), 51 deletions(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 3a89da6b1d..3eabefdecb 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -1,78 +1,78 @@ - - Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order + + Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order - -

    Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order

    -
    -

    ID: F85

    -

    Technology: failures

    -

    Type: Failure

    -
    -
    -

    When to Use

    + +

    Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order

    +
    +

    ID: F85

    +

    Technology: failures

    +

    Type: Failure

    +
    +
    +

    When to Use

    All technologies.

    -
    -
    -

    Description

    +
    +
    +

    Description

    This describes the failure condition that results when a web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, and it is not adjacent to the trigger control in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    -
    -

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    -
    +
    +

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    +
    -
    -

    Sometimes it's not possible to return focus to the control the user activated to open a dialog. For example: a blog post has a list of tags, each tag containing a delete button. Pressing a delete button opens a modal dialog that asks the user to confirm the deletion. On confirming the deletion, the tag is deleted, the modal dialog closes, and focus is placed on the next tag in the list of tags. Placing focus onto a different, but logical, control is not a failure of Success Criterion 2.4.3.

    -
    -
    -
    -

    Examples

    -
    -

    Adding a dialog to the page at the end of the sequential navigation order

    -

    A non native HTML dialog is created, with its code at the end of the DOM (Document Object Model). The dialog is visually positioned above the content of the page and the user's focus isn't moved to the dialog. Because the dialog's code is at the end of the DOM, it is at the end of the keyboard navigation order. Because the user's focus isn't manage, they must tab through the rest of the web page before they can interact with the dialog or menu.

    +
    +

    Sometimes it's not possible to return focus to the control the user activated to open a dialog. For example: a blog post has a list of tags, each tag containing a delete button. Pressing a delete button opens a modal dialog that asks the user to confirm the deletion. On confirming the deletion, the tag is deleted, the modal dialog closes, and focus is placed on the next tag in the list of tags. Placing focus onto a different, but logical, control is not a failure of Success Criterion 2.4.3.

    +
    +
    +
    +

    Examples

    +
    +

    Adding a dialog to the page at the end of the sequential navigation order

    +

    A non native HTML dialog is created, with its code at the end of the DOM (Document Object Model). The dialog is visually positioned above the content of the page and the user's focus isn't moved to the dialog. Because the dialog's code is at the end of the DOM, it is at the end of the keyboard navigation order. Because the user's focus isn't manage, they must tab through the rest of the web page before they can interact with the dialog or menu.

    -

    Setting focus to the document after dismissing a menu embedded on the page

    +

    Setting focus to the document after dismissing a menu embedded on the page

    When a menu is dismissed, it is removed or hidden from the web page and focus is set to the document. The user must tab from the beginning of the navigation sequence to reach the point from which the menu was opened.

    -
    -
    -

    Tests

    +
    +
    +

    Tests

    -

    Procedure

    -

    For each menu or dialog on a web page that is opened via a trigger control:

    -
      -
    1. -

      Activate the trigger control via the keyboard.

      +

      Procedure

      +

      For each menu or dialog on a web page that is opened via a trigger control:

      +
        +
      1. +

        Activate the trigger control via the keyboard.

          -
        • Check whether focus is in the menu or dialog.
          • +
        • Check whether focus is in the menu or dialog.
        • Check whether moving the focus forward once in the sequential navigation order puts focus in the menu or dialog.
      2. -

        Dismiss the menu or dialog

        +

        Dismiss the menu or dialog

        • Check whether focus is on the trigger control.
          • -
        • If focus needs to be placed on a different control, check whether that different control is logical.
          • +
        • If focus needs to be placed on a different control, check whether that different control is logical.
        3. -
      +
    -

    Expected Results

    +

    Expected Results

      -
    • If both points under step 1 are false, then this failure condition applies and the content fails this success criterion.
      • -
    • If both points under step 2 are false, then this failure condition applies and the content fails this success criterion.
      • -
    +
  • If both points under step 1 are false, then this failure condition applies and the content fails this success criterion.
    • +
  • If both points under step 2 are false, then this failure condition applies and the content fails this success criterion.
    • +
    -
    - - +
    + + From f11d093a40bfd6749915e0e278764b2350ccd73c Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 22 Nov 2024 13:11:35 -0800 Subject: [PATCH 09/15] Update techniques/failures/F85.html Co-authored-by: Scott O'Hara --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 3eabefdecb..79afee8655 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -17,7 +17,7 @@

    When to Use

    Description

    -

    This describes the failure condition that results when a web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, and it is not adjacent to the trigger control in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    +

    This describes the failure condition that results when a web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, or a logical focusable descendent of these widgets, and the widget or a focusable descendent is not the next in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    From 675c36b49d5b3a0406b43629d2a8bb35194803e8 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 22 Nov 2024 13:12:51 -0800 Subject: [PATCH 10/15] Update techniques/failures/F85.html Co-authored-by: Scott O'Hara --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 79afee8655..995c01789e 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -31,7 +31,7 @@

    Description

    Examples

    Adding a dialog to the page at the end of the sequential navigation order

    -

    A non native HTML dialog is created, with its code at the end of the DOM (Document Object Model). The dialog is visually positioned above the content of the page and the user's focus isn't moved to the dialog. Because the dialog's code is at the end of the DOM, it is at the end of the keyboard navigation order. Because the user's focus isn't manage, they must tab through the rest of the web page before they can interact with the dialog or menu.

    +

    A non-native HTML dialog is created, with it being marked up at the end of the DOM (Document Object Model). Script was created to reveal the dialog, but no script was added to move focus to it. The dialog is visually positioned above the content of the page and the user's focus isn't moved to the dialog. Since the dialog is found at the end of the DOM, it is at the end of the keyboard navigation order. Because a user's focus isn't managed, or a keyboard mechanism isn't provided to allow them to immediately move to the invoked dialog, the user will need to tab through the rest of the web page before they can interact with the dialog.

    Setting focus to the document after dismissing a menu embedded on the page

    From c932733c232d77349e726f2107fdb0037ffe4ce0 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 22 Nov 2024 13:13:02 -0800 Subject: [PATCH 11/15] Update techniques/failures/F85.html Co-authored-by: Scott O'Hara --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 995c01789e..2bd12b9db8 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -47,7 +47,7 @@

    Procedure

  • Activate the trigger control via the keyboard.

      -
    • Check whether focus is in the menu or dialog.
      • +
    • Check whether focus has been set to the menu, dialog, or a logical focusable descendent of the widget.
    • Check whether moving the focus forward once in the sequential navigation order puts focus in the menu or dialog.
    • From 1b6c8d9ee37c60cef301491b4629bda9127cdcde Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 22 Nov 2024 13:15:34 -0800 Subject: [PATCH 12/15] Update techniques/failures/F85.html Co-authored-by: Scott O'Hara --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 2bd12b9db8..e5a32281b8 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -48,7 +48,7 @@

    Procedure

    Activate the trigger control via the keyboard.

    • Check whether focus has been set to the menu, dialog, or a logical focusable descendent of the widget.
      • -
    • Check whether moving the focus forward once in the sequential navigation order puts focus in the menu or dialog.
      • +
    • If not, check whether moving the focus forward once in the sequential navigation order puts focus in the menu or dialog.
  • From 60a20b48449cda4036e48849abbb903a23dccc1f Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 6 Dec 2024 08:38:35 -0800 Subject: [PATCH 13/15] Update techniques/failures/F85.html --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index e5a32281b8..74f46ee5e2 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -19,7 +19,7 @@

    When to Use

    Description

    This describes the failure condition that results when a web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, or a logical focusable descendent of these widgets, and the widget or a focusable descendent is not the next in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    -
    +

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    From 9610164b290d3b11f799360f306f59e49d201d23 Mon Sep 17 00:00:00 2001 From: Francis Storr Date: Fri, 6 Dec 2024 08:39:01 -0800 Subject: [PATCH 14/15] Update techniques/failures/F85.html --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index 74f46ee5e2..b2b029ad81 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -23,7 +23,7 @@

    Description

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.

    -
    +

    Sometimes it's not possible to return focus to the control the user activated to open a dialog. For example: a blog post has a list of tags, each tag containing a delete button. Pressing a delete button opens a modal dialog that asks the user to confirm the deletion. On confirming the deletion, the tag is deleted, the modal dialog closes, and focus is placed on the next tag in the list of tags. Placing focus onto a different, but logical, control is not a failure of Success Criterion 2.4.3.

    • From a3752709867bcda82a0cc60fabf374ddfe81e2a3 Mon Sep 17 00:00:00 2001 From: Bruce Bailey Date: Fri, 6 Dec 2024 16:53:05 -0500 Subject: [PATCH 15/15] Update F85.html editorial Changed "the next" to just "next". Might also be "the next item" --- techniques/failures/F85.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F85.html b/techniques/failures/F85.html index b2b029ad81..de4fc361ac 100644 --- a/techniques/failures/F85.html +++ b/techniques/failures/F85.html @@ -17,7 +17,7 @@

    When to Use

    Description

    -

    This describes the failure condition that results when a web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, or a logical focusable descendent of these widgets, and the widget or a focusable descendent is not the next in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    +

    This describes the failure condition that results when a web page opens a dialog or menu interface component embedded on the page in a way that makes it difficult for a keyboard user to operate because of its position in the sequential navigation order. When the user opens the dialog or menu embedded on the page by activating a button or link, their next action will be to interact with the dialog or menu. If focus is not set to the dialog or menu, or a logical focusable descendent of these widgets, and the widget or a focusable descendent is not next in the sequential navigation order, it will be difficult for the keyboard user to operate the dialog or menu.

    Dismissing a dialog or menu means to close it without taking any action on it. For example: a modal dialog opens on a web page and displays a sign-up form for a mailing list. A user dismisses the dialog by either pressing a "close" button or using the Escape key.