W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2017

RE: Auto focus movement with dynamic updates

From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Date: Thu, 16 Mar 2017 04:02:13 +0000
To: Matt King <a11ythinker@gmail.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <f4cc2848f2924bb1950af26a4859341b@XCH-RCD-001.cisco.com>

In other words, there is no hard and fast rule. It depends on the goal and if the design makes sense. In my situation, I will refer to the dev not to use automatic focus movement as it doesn't make sense.

Sean Murphy
Accessibility Software engineer
Tel: +61 2 8446 7751       Cisco Systems, Inc.
The Forum 201 Pacific Highway
 Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

From: Matt King [mailto:a11ythinker@gmail.com]
Sent: Thursday, 16 March 2017 2:22 PM
To: Sean Murphy (seanmmur) <seanmmur@cisco.com>; w3c-wai-ig@w3.org
Subject: RE: Auto focus movement with dynamic updates


I strongly believe this should be a design decision. There are many factors that could play into what is optimal. For composite widgets that employ ARIA, the authoring practices task force is working on addressing these factors for various design patterns. None of this is normative, and that is intentional.

WCAG should be careful not to be too specific with respect to focus movement in dynamic pages. Instead, it should refer designers and developers to guidance, like the ARIA Authoring Practices, that explains factors to consider when designing a focus sequence.

Matt King

From: Sean Murphy (seanmmur) [mailto:seanmmur@cisco.com]
Sent: Wednesday, March 15, 2017 6:45 PM
To: w3c-wai-ig@w3.org
Subject: Auto focus movement with dynamic updates


I have reviewed 2.4.3, 3.2.2 and 3.2.5 and need verification for web sites that use dynamic content after an action has been initiated on an input element like a link, button, treeivew node, tab strip, etc. After the page has dynamically updated, should the focus move? This is not related to automatic focus movement within a form which is covered by 2.4.3. The actions are:

1.      User moves keyboard focus on to an element. Such as a tree view sub-node or a link.

2.      They press enter to activate the item.

3.      The same page dynamically updates showing new content. The main navigation elements still exist.

4.      The focus moves to the first element on the new content shown.
My feeling the above is incorrect and if so, not sure which WCAG SC would apply. Comments?

Received on Thursday, 16 March 2017 04:03:51 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 16 March 2017 04:03:52 UTC