Skip to content

update to focus placement for modal dialogs #3214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 18 commits into from
Jan 22, 2025
Merged

update to focus placement for modal dialogs #3214

Changes from 14 commits
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
d14ed9d
Frances' proposed response
alastc May 25, 2023
17f689a
Update techniques/failures/F85.html
alastc May 30, 2023
57f9f48
Merge branch 'main' into Issue518-focus-dialogues
patrickhlauke Oct 18, 2024
615b2a0
Address comments on moving focus, update DTML content
fstrr Nov 6, 2024
699eabc
Tweak wording
fstrr Nov 8, 2024
8aa8b5b
Another tweak
fstrr Nov 8, 2024
c0f9c75
Expand example into a note
fstrr Nov 22, 2024
aef974f
Merge branch 'main' into Issue518-focus-dialogues
patrickhlauke Nov 22, 2024
c9498e5
Update techniques/failures/F85.html
mbgower Nov 22, 2024
1848a1a
Formatting pass
kfranqueiro Nov 22, 2024
f11d093
Update techniques/failures/F85.html
fstrr Nov 22, 2024
675c36b
Update techniques/failures/F85.html
fstrr Nov 22, 2024
c932733
Update techniques/failures/F85.html
fstrr Nov 22, 2024
1b6c8d9
Update techniques/failures/F85.html
fstrr Nov 22, 2024
60a20b4
Update techniques/failures/F85.html
fstrr Dec 6, 2024
9610164
Update techniques/failures/F85.html
fstrr Dec 6, 2024
a375270
Update F85.html editorial
bruce-usab Dec 6, 2024
0fcc8ee
Merge branch 'main' into Issue518-focus-dialogues
mbgower Jan 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
110 changes: 71 additions & 39 deletions techniques/failures/F85.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,46 +1,78 @@
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>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</title><link rel="stylesheet" type="text/css" href="../../css/sources.css" class="remove"/></head><body><h1>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</h1><section class="meta"><p class="id">ID: F85</p><p class="technology">Technology: failures</p><p class="type">Type: Failure</p></section><section id="applicability"><h2>When to Use</h2>
<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>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</title>
<link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"/>
</head>
<body>
<h1>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</h1>
<section class="meta">
<p class="id">ID: F85</p>
<p class="technology">Technology: failures</p>
<p class="type">Type: Failure</p>
</section>
<section id="applicability">
<h2>When to Use</h2>
<p>All technologies.</p>
</section><section id="description"><h2>Description</h2>
<p>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.</p>
</section><section id="examples"><h2>Examples</h2>
</section>
<section id="description">
<h2>Description</h2>
<p>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.</p>

<div role="note">
<p>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 <kbd>Escape</kbd> key.</p>
</div>

<div role="note">
<p>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.</p>
</div>
</section>
<section id="examples">
<h2>Examples</h2>
<section class="example">
<h3>Adding a dialog or menu embedded on the page to the end of the sequential navigation order</h3>

<p>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.</p>

<h3>Adding a dialog to the page at the end of the sequential navigation order</h3>
<p>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.</p>
</section>
<section class="example">
<h3>Setting focus to the document after dismissing a menu embedded on the page</h3>

<p>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.</p>

<h3>Setting focus to the document after dismissing a menu embedded on the page</h3>
<p>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.</p>
</section>
</section><section id="tests"><h2>Tests</h2>
<section class="procedure"><h3>Procedure</h3>
<p>For each menu or dialog embedded on a Web page that is opened via a trigger control:</p>
<ol>
<li>
<p>Activate the trigger control via the keyboard.</p>
<ul>
<li>Check whether focus is in the menu or dialog.</li>
<li>Check whether advancing the focus in the sequential navigation order puts focus in the menu or dialog.</li>
</ul>
</li>
<li>
<p>Dismiss the menu or dialog.</p>
<ul>
<li>Check whether focus is on the trigger control.</li>
<li>Check whether advancing the focus backwards in the sequential navigation order puts focus in the trigger control.</li>
</ul>
</li>
</ol>
</section>
<section id="tests">
<h2>Tests</h2>
<section class="procedure">
<h3>Procedure</h3>
<p>For each menu or dialog on a web page that is opened via a trigger control:</p>
<ol>
<li>
<p>Activate the trigger control via the keyboard.</p>
<ul>
<li>Check whether focus has been set to the menu, dialog, or a logical focusable descendent of the widget.</li>
<li>If not, check whether moving the focus forward once in the sequential navigation order puts focus in the menu or dialog.</li>
</ul>
</li>
<li>
<p>Dismiss the menu or dialog</p>
<ul>
<li>Check whether focus is on the trigger control.</li>
<li>If focus needs to be placed on a different control, check whether that different control is logical.</li>
</ul>
</li>
</ol>
</section>
<section class="results"><h3>Expected Results</h3>
<ul>
<li>If both points under step 1 are false, then this failure condition applies and the content fails this success criterion.</li>
<li>If both points under step 2 are false, then this failure condition applies and the content fails this success criterion.</li>
</ul>
<section class="results">
<h3>Expected Results</h3>
<ul>
<li>If both points under step 1 are false, then this failure condition applies and the content fails this success criterion.</li>
<li>If both points under step 2 are false, then this failure condition applies and the content fails this success criterion.</li>
</ul>
</section>
</section><section id="related"><h2>Related Techniques</h2><ul>
<li><a href="../client-side-script/SCR26">SCR26</a></li>
</ul></section></body></html>
</section>
<section id="related">
<h2>Related Techniques</h2>
<ul>
<li><a href="../client-side-script/SCR26">SCR26</a></li>
</ul>
</section>
</body>
</html>