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

Proposal for the last three items

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Wed, 24 Oct 2012 04:10:22 -0400
To: "public-wcag2ict-tf@w3.org Force" <public-wcag2ict-tf@w3.org>
Message-id: <E126FEDA-EA73-4E9B-838C-C46412588003@trace.wisc.edu>


Here area the ones left
============================================================
 2.4.1: Bypass Blocks (Level A)
A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
[agreement for non-embedded content]

2.4.5: Multiple Ways (Level AA)
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.

3.2.3: Consistent Navigation (Level AA)
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.



SUGGEST THAT WE DO THE FOLLOWING

In all three cases we   

1) Say "applies as written etc.  replacing  web page(s)  with   NWNE Content and Software  "

2)  add the following two notes to each

NOTE 1: Because content this is not on a web is not as easily defined as a set by its location, the WCAG2ICT TF found that a clearer definition of what constituted a set was needed for Non-web content and software.  The following definition of SET was adopted because it provided a clear indication (by virtual of the bi-directional linkages) that they items were indeed meant to work together as a set and not just be a collection.

NOTE 2: For software the WCAG2ICT TF found that this provision can be applied to software but such sets of software are rare, and most would meet this success criterion automatically by their natural design.   So this provision would never ordinarily be included in a set of software requirements because of it rarity and the fact that it is not much of a problem for software so the provision would not be of much value.  
	ALso we did not find that WCAG applied this within a web page or single unit web app (at a single URI) so we didn’t feel we could apply it within software.  But we do recognize the utility of applying this general concept in different ways to parts of software.   WCAG would not require it, but it would be good practice consider the general concept when designing software. 

3)  refer to our definition a definition of Set as follows
	SET  (of NWNE Content or Software)
group of items that are linked bidirectionally to each other via h,yperlinks or a menu of links that move you between the items in the group.


Comments welcome
(some tweaking may be needed between SC) 


========================


Background - for reference
23 success criteria  "This [success criterion] applies directly as written, and as described in INTENT from Understanding WCAG 2.0' 

8 success criteria  "This [ success criterion] applies directly as written, and as described in INTENT from Understanding WCAG 2.0  
replacing "Web page(s)", "Each Web page", "Content" or "Web content"  with "Non-embeded Content and Software"

4 success criterion    "This [success criterion] applies directly as written, and as described in INTENT from Understanding WCAG 2.0 
had individual substitutions
(1.3.2 Meaningful Sequence)  
replacing "Content", with "Non-Web content" 
(1.4.2 Audio Control)  
replacing “a Web page” with “ in non-embedded content or software” and “any content” with “any part of non-embedded content or software
(3.2.4 Consistent Identification)   
replacing “a set of Web pages” with "non-embedded content or software”
(4.1.1 Parsing)   
replacing “In content implemented using markup languages”  with  “For software and non-embedded content that use markup languages, in such a way that the markup is separately exposed and available to assistive technology (AT) or to a user-selectable user agent".





Gregg
--------------------------------------------------------
Gregg Vanderheiden Ph.D.
Director Trace R&D Center
Professor Industrial & Systems Engineering
and Biomedical Engineering University of Wisconsin-Madison
Technical Director - Cloud4all Project - http://Cloud4all.info
Co-Director, Raising the Floor - International - http://Raisingthefloor.org
and the Global Public Inclusive Infrastructure Project -  http://GPII.net
Received on Wednesday, 24 October 2012 08:11:05 UTC

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