W3C home > Mailing lists > Public > public-wcag2ict-tf@w3.org > July 2012

RE: Looking at SC 2.4.3 Focus Order with "UI Context"

From: Michael Pluke <Mike.Pluke@castle-consult.com>
Date: Fri, 13 Jul 2012 09:08:19 -0400
To: "Hoffman, Allen" <Allen.Hoffman@HQ.DHS.GOV>, Peter Korn <peter.korn@oracle.com>, "public-wcag2ict-tf@w3.org" <public-wcag2ict-tf@w3.org>
Message-ID: <5735ED0D92A3E6469F161EB41E7C28A81D1B9819BF@MAILR001.mail.lan>
Hi Peter and Allen

Maybe I am missing the problem here?

Firstly the SC starts with "If ..". So in case where the user interface elements or information cannot be navigated sequentially the SC does not apply.

I am a little unclear what you (Peter) are actually concerned about being navigated sequentially, as you refer to "set of windows' content" which doesn't appear anywhere in the SC as it appears in WCAG, neither does this phrase appear in the UI context definition? Leaving that uncertainty aside, the SC is only applicable where navigation sequences affect meaning or operation - which significantly reduces the size of the set of software use cases where it might apply.

If the "if" and "and" clauses of the SC apply (which very frequently they will not in many parts of a software UI), then it makes sense that the navigation sequence within a UI context should be such that it "preserves meaning and operability". So I really do not see exactly what is the problem?

Best regards


From: Hoffman, Allen [mailto:Allen.Hoffman@HQ.DHS.GOV]
Sent: 13 July 2012 13:34
To: Peter Korn; public-wcag2ict-tf@w3.org
Subject: RE: Looking at SC 2.4.3 Focus Order with "UI Context"

I agree with your note regarding the within window sequentialness of navigation.  The sequences related to the "UIC".

From: Peter Korn [mailto:peter.korn@oracle.com]<mailto:[mailto:peter.korn@oracle.com]>
Sent: Thursday, July 12, 2012 8:45 PM
To: public-wcag2ict-tf@w3.org<mailto:public-wcag2ict-tf@w3.org>
Subject: Looking at SC 2.4.3 Focus Order with "UI Context"

Hi gang,

SC 2.4.3<https://sites.google.com/site/wcag2ict/home/2-operable/24-provide-ways-to-help-users-navigate-find-content-and-determine-where-they-are/243-focus-order> Focus Order was one we reached consensus on.  However, I thought it would be useful to look at it with the new UI Context definition, to help evaluate that definition and where we might use it.  My thoughts on this can be found at the Applying UI Context<https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/applying-ui-context> page in the fourth row, but to facilitate discussion, I reiterate them here.

Looking only at software, and doing a direct definition substitution for "web page" with the existing SC text, we get:
If a [set of user interface elements and the presented information, within a product, that can be accessed using only navigation commands] can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)
I have yet to see a "set of windows' content" be navigated sequentially.  Sequential navigation only takes place within a window, typically within a portion of a window.  While the consensus text arguably has a similar deficiency, I think it is more likely to be understood by readers as applying to a single window's UI, and not all of the windows (as constituting the "software interface").  Perhaps public comments on this consensus text will reveal any such potential concerns.


Peter Korn | Accessibility Principal
Phone: +1 650 5069522<tel:+1%20650%205069522>
500 Oracle Parkway | Redwood City, CA 94065
[cid:image002.gif@01CD6100.07A96A50]<http://www.oracle.com/commitment>Oracle is committed to developing practices and products that help protect the environment

(image/gif attachment: image001.gif)

(image/gif attachment: image002.gif)

Received on Friday, 13 July 2012 13:08:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:17:44 UTC