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

Re: We area close !

From: Peter Korn <peter.korn@oracle.com>
Date: Sun, 16 Sep 2012 20:08:03 -0700
Message-ID: <50569413.4030504@oracle.com>
To: Gregg Vanderheiden <ez1testing@gmail.com>
CC: "public-wcag2ict-tf@w3.org Force" <public-wcag2ict-tf@w3.org>
Hi Gregg,

I really think it would be useful to take the Examples for UI Context 
discussion 
<https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples> 
and apply your suggested definitions to them.

*2.4.1. Bypass Blocks: *

  * Looking at How many Example #1: two document windows
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/how-many-two-document-windows>
    since the menu bar & toolbar can be repeated in the software, some
    bypass mechanism would be needed... *This seems like a reasonable
    application.*
  * Looking at Changed? Example #3: Tabbed panes
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/changed-example-3-tabbed-panes>**there
    is nothing formally repeated, so this wouldn't apply. *That too
    *seems like a reasonable application.**
  * Looking at Changed? Example #24 calender appointments
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/changed-example-24-calender-appointments>
    since the calendar title & days repeat while content below changes,
    arguably again some bypass mechanism would be needed. *This seems
    like a reasonable application.*

*2.4.2 Page Titled:*

  * Looking at How many Example #1: two document windows
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/how-many-two-document-windows>
    there is no obvious visible page title; "Untitled Document 1" is no
    more or less the obvious "software title" than "Untitled Document 2"
    is (and in fact, clearly neither one  is correct). *This seems like
    a poor fit to this situation.
    *
  * Looking at Changed? Example #3: Tabbed panes
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/changed-example-3-tabbed-panes>**we
    don't know for sure what the application name is.  If it is "Media
    Center" then this would be helpful; if not... then not. *This seems
    like may not be a good fit to this situation. *****
  * Looking at Changed? Example #24 calender appointments
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/changed-example-24-calender-appointments>
    it is pretty obvious to folks raised with a cultural familiarity
    with the Julian calendar that this is a calendar / appointment
    application.  It is not at all clear what the software title is; it
    isn't "October".  And consuming a significant portion of a small
    screen to display the software application name would come at
    significant cost, and somewhat questionable benefit. *This seems
    like may not be a good fit to this situation. *

    Note: Since Understanding for 2.4.2 begins with "The intent of this
    Success Criterion is to help users find content and orient
    themselves within it", and specific benefits include "People with
    visual disabilities will benefit from being able to differentiate
    content when multiple Web pages are open" and "People with cognitive
    disabilities, limited short-term memory and reading disabilities
    also benefit from the ability to identify content by its title". 

*2.4.5 Multiple Ways:*

  * Looking at How many Example #1: two document windows
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/how-many-two-document-windows>
    it wouldn't apply, as there isn't a "set of software products"
    visible in the example.*
    *
  * Looking at Changed? Example #3: Tabbed panes
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/changed-example-3-tabbed-panes>**again
    it wouldn't apply, as there isn't a "set of software products"
    visible in the example. **
  * Looking at Changed? Example #24 calender appointments
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/changed-example-24-calender-appointments>
    again it wouldn't apply, as there isn't a "set of software products"
    visible in the example. *
    *

    Note that Understanding is tied to locating content & information,
    not locating applications and functions; not clear how much
    application 2.4.5 has to software UIs.  Or perhaps none of these (or
    any of our) examples are useful to illustrate where 2.4.5 would be
    helpful.  Perhaps we need other examples for software, showing where
    and how it would work.  AND more especially, describing HOW the
    helpfulness in WCAG 2.0 Understanding translates into similar
    helpfulness in the software world!


*3.2.3: Consistent Navigation: *

  * Looking at How many Example #1: two document windows
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/how-many-two-document-windows>
    since the windows are simply repeated except with different non-GUI
    content, if any of the UI components are termed "navigation" this
    would be automatically met.  If none are termed "navigation", then
    it doesn't apply. *This seems like it could be OK; certainly no harm
    is done.*
  * Looking at Changed? Example #3: Tabbed panes
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/changed-example-3-tabbed-panes>**it
    looks like it wouldn't apply, as there aren't any "repeated
    navigation mechanisms" visible in the example.
  * Looking at Changed? Example #24 calender appointments
    <https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples/changed-example-24-calender-appointments>
    again it looks like it wouldn't apply, as there aren't any "repeated
    navigation mechanisms" visible in the example. **

    Note that this seems like it is a rare situation to actually occur
    in most software, other than "content-driven" software like books or
    other sets of information with things like next/prev links on them
    (e.g. Help applications and the like, which are essentially similar
    to HTML/web content).



 From this quick analysis, I think we may have something not too 
unreasonable for 2.4.2 Bypass Blocks.  We might have something for 2.4.5 
Multiple Ways and for 3.2.3 Consistent Navigation - but I think we need 
to come up with a set of positive examples where this really occurs & 
would apply; it isn't clear from the examples we've generated on the 
Examples for UI Context discussion 
<https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/ui-context-examples> 
that they are particularly useful.

I think this approach fails for 2.4.2 Page Titled.  If we instead say 
that the "title" of the "software" is the software applications "name" 
(whether the executable name or the name as it appears in things like 
the Windows Start menu), then we have moved significantly away from what 
Understanding for 2.4.2 is all about -> helping users locate the content 
& information they want. Rather, if we want to apply 2.4.2 to the GUI 
environment, going with window title seems a better match.  But then 
what do we do about the burgeoning world of mobile software UIs?  And 
what about audio UIs? Does Page Titled really make sense in those 
worlds?  Maybe not...


Peter


On 9/14/2012 5:04 AM, Gregg Vanderheiden wrote:
>
> We have just 4 success criterion left.   And I think we are 
> overthinking ourselves.
>
> Taking a cue from Mike -- we need to take a step back and look at what 
> it is that we are trying to do.  Substituting individual words works 
> for much but not all.    But if we look at the objective of the 
> success criteria -- and we look at the fact that
>
>   * Web Apps often (usually?) are just a single web page -  then we
>     can equate  "software" with "web page" in many places.
>   * "web page in a set of web pages" also often (usually?) is intended
>     to apply to a set of pages that work as an entity on the web.  So
>     the equiv of "web page in a set of web pages" for these SC would
>     also be "software" (or document).
>
>
> this then leads us to something like the following  (Which I have put 
> into the worksite as proposals.
>
> but look at them here and we may be able to close these.
>
> Replace “web pages” with “documents” and “software”
> *
> *
> *We have just 4 success criterion outstanding*
>
> * 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of 
> content that are repeated on multiple Web pages.*
>
>  *
>     Replace “ multiple web pages” with “in a document” and “in software"
>
> Note that the INTENT section of WCAG already says:
>
> “Examples of repeated blocks of content include but are not limited to 
> navigation links, heading graphics, and advertising frames. Small 
> repeated sections such as individual words, phrases or single links 
> are not considered blocks for the purposes of this provision”
>
> *2.4.2: Page Titled: Web pages have titles that describe topic or 
> purpose.*
>
>  *
>     Replace “web pages” with “documents” and “software”
>
>     Note that web pages are often full applications,  so a software
>     application would be parallel.
>
> *2.4.5: Multiple Ways: More than one way is available to locate a Web 
> page within a set of Web pages except where the Web Page is the result 
> of, or a step in, a process.*
>
>   * replacing "web pages" with "documents" and replacing "set of web
>     pages" with "set of documents"
>   * replacing "web pages" with "software products" and replacing "set
>     of web pages" with "set of software products"
>
> NOTES:
>
> 1.*A set of documents *(or software products) is a group of documents 
> (or software products) that are
>
>     1.*published together*, and
>
>     2.*labeled as a set* within at least one of the member documents
>     (or software products).
>
> 2.*Republishing or bundling *previously published documents or 
> software products as a collection does not constitute a set of 
> documents. (i.e. They do not become a set if bundled but not 
> originally published as a set)
>
> 3.*A set that is broken* apart and distributed is no longer a set.
>
> 4.*A file directory *would be the equivalent of a site map for 
> documents (or software products) in that it provides a link to each of 
> the documents (software products) in the set of documents (software 
> products).  The directory also acts as the HOME for the set.
>
> 5.*A search function* in an operating systems (that finds documents or 
> software products) would be equivalent to a web search function for 
> web pages.
>
> 6.*Authors can assume* that the non-web documents or software products 
> will be stored and accessed on a major operating system with browse 
> and search abilities unless they have specific information to the 
> contrary.
>
> Final note to those evaluating 2.4.5:
>
> Although this provision is easily met, it is not always met.  The 
> presence of this success criteria also makes it easier for people 
> creating support materials to later include a wide range of advisory 
> techniques that, while not always applicable, would
>
> *3.2.3: Consistent Navigation:Navigational mechanisms that are 
> repeated on multiple Web pages within a set of Web pages occur in the 
> same relative order each time they are repeated, unless a change is 
> initiated by the user.*
>
>   * Replace “multiple Web pages within a set of Web pages*” * with “in
>     documents” and “in software”
>
>     And ask WCAG to add the following or something like it to the
>     Understanding WCAG 2.0 document
>
>     "In this success criteria the term 'navigation mechanisms' is
>     meant to refer to active lists of standard (not user generated)
>     locations in the content that are provided by the author and that,
>     when activated, cause the user to move to that particular standard
>     location.
>
>     Navigation bars, a pull down menu that jumps you to different
>     locations, and a set of tabs provided by the author, would be
>     examples.
>
>     The following may be used for navigation but are not included in
>     what is meant by navigation mechanisms in this success criterion
>     :  escape keys, arrow keys, page down keys, headers that are only
>     in the text of the document, tabs that a user creates or re-orders
>     (because they are initiated by the user), the OK and Cancel
>     buttons on a dialog (don't take you to consistent locations)."
>
>
>

-- 
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 Monday, 17 September 2012 03:08:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 17 September 2012 03:08:39 GMT