View source for F85: 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

[[Category: Techniques]]
[[Category: Failure Techniques]]
[[Category: Techniques Accepted]]
[[Category: Ready for XML]]

==Status==
* Added to XML by AWK Dec 20, 2013
This is an edited version of [http://www.w3.org/TR/WCAG-TECHS/failures.html#F85 F85: 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].
* [https://www.w3.org/2002/09/wbs/35422/20130815ttf/ Techniques Task Force: ARIA techniques for 15 Aug 2013]
* [https://www.w3.org/2002/09/wbs/35422/20130829ttf/ Techniques Task Force: ARIA techniques for 29 Aug 2013]
* [https://www.w3.org/2002/09/wbs/35422/WCAGTechs20130910/results#x2670 10 Sept 2013 survey]

==Applicability==

All technologies.

This failure relates to:

* Success Criterion 2.4.3 (Focus Order)
** How to Meet 2.4.3 (Focus Order)
**Understanding Success Criterion 2.4.3 (Focus Order)

==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, his next action will be to interact with the dialog or menu. If <ins> focus is not set to</ins> the dialog or menu<ins>, and it</ins> 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.
===Examples===
====<ins>Failure</ins> Example 1: <ins>Adding a</ins> dialog or menu embedded on the page <del>is added</del> to the end of the sequential navigation order====

When a <del>DHTML</del> menu or dialog is activated, it is created dynamically, positioned visually near the trigger, and appended to the end of the DOM. <ins>Focus is not changed, so it is still on the element that triggered the menu or dialog.</ins> Because <del>it</del> <ins>the menu or dialog</ins> is appended to the end of the DOM, it is at the end of the sequential navigation order. <ins>Users</ins> <del>The user</del> must tab through the rest of the web page before <del>he</del> <ins>they</ins> can interact with the dialog or menu. <ins>This is often difficult as the background of the dialog may be darkened or focus points obliterated/covered by the dialogue on top. Also, the page (including the dialog) may have no or insufficient focus visibility for users to determine when they could interact with the dialogue.</ins>

====<ins>Failure</ins> Example 2: <ins>Setting focus to the document after </ins> dismissing a menu embedded on the page <del>sets focus to the document</del>====

When a <del>DHTML</del> 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.

==Related Techniques==
* SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element

==Tests==
===Procedure===

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

# Activate 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.
# 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.

===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.