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

Looking at SC 3.1.1 Language of Page with "UI Context"

From: Peter Korn <peter.korn@oracle.com>
Date: Thu, 12 Jul 2012 17:46:38 -0700
Message-ID: <4FFF6FEE.6070404@oracle.com>
To: public-wcag2ict-tf@w3.org
Hi gang,

SC *3.1.1 
<https://sites.google.com/site/wcag2ict/home/3-understandable/31-make-text-content-readable-and-understandable/311-language-of-page>*****was 
not one we reached consensus on. We've had some discussion on it, and I 
feel that proposal #3 was getting there.

My thoughts on that 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 sixth row, but to facilitate discussion, I reiterate them here.

The UIC Proposal is:

    This applies directly as written, and as described in INTENT from
    Understanding WCAG 2.0  (above) with "document or user interface
    context" substituted for "Web Page".

    Note that some document formats can use separate human languages for
    output and input purposes. In such cases both languages should be
    programmatically determinable.

    For software, there are some platforms and software types where
    there is no assistive technology supported method for marking the
    language for the different "user interface contexts" or for marking
    that the application doesn't match the "local" language, as marked
    in the platform, and it would not be possible to meet this success
    criterion with those platforms or software types.

    NOTE: Inheritance is one common method.  For example a document or
    application provides the language that it is using and it can be
    assumed that all user interface contexts within that document or
    application will be using the same language unless it is indicated. 

I don't see how UI Context really helps us here.  It is unlikely that 
two UI Contexts in the same software application will have different 
languages.  Granularity is either at the application level (most common) 
or at the UI component and language passage level (which gets us to SC 
3.1.2).  Scoping this to software applications seems cleaner and more 
direct to me.  Also easier to understand and test.


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
Received on Friday, 13 July 2012 00:47:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 13 July 2012 00:47:13 GMT