We area close !

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)."