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.


Thought?


Peter
-- 
Oracle <http://www.oracle.com>
Peter Korn | Accessibility Principal
Phone: +1 650 5069522 <tel:+1%20650%205069522>
500 Oracle Parkway | Redwood City, CA 94065
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to 
developing practices and products that help protect the environment