2.4.5 Multiple Ways:






***************NOTICE************************************************ 
                                                                                                       
  This work space is being phased out and is no longer kept        
  updated with the latest task force agreements. Please refer to  
  the most recent WCAG2ICT public draft at                                 
  http://www.w3.org/TR/wcag2ict/                                                  
                                                                                                       
************************************************************************* 


NEW TEXT FOR THIS ITEM CAN BE FOUND AT 
                                                                                                            .
https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/remaining-3-scs








                                                                                                                               .
               <NEW TEXT TO SENT OUT FOR REVIEW #2                                     .
                                                                                                                                 

Success Criterion 2.4.5: Multiple Ways (Level AA)

From Success Criterion 2.4.5:

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.

Intent from Understanding Success Criterion 2.4.5 in Understanding WCAG 2.0:

The intent of this Success Criterion is to make it possible for users to locate content in a manner that best meets their needs. Users may find one technique easier or more comprehensible to use than another.

Even small sites should provide users some means of orientation. For a three or four page site, with all pages linked from the home page, it may be sufficient simply to provide links from and to the home page where the links on the home page can also serve as a site map.

Specific Benefits of Success Criterion 2.4.5
  • Providing an opportunity to navigate sites in more than one manner can help people find information faster. Users with visual impairments may find it easier to navigate to the correct part of the site by using a search, rather than scrolling through a large navigation bar using a screen magnifier or screen reader. A person with cognitive disabilities may prefer a table of contents or site map that provides an overview of the site rather than reading and traversing through several Web pages. Some users may prefer to explore the site in a sequential manner, moving from Web page to Web page in order to best understand the concepts and layout.

  • Individuals with cognitive limitations may find it easier to use search features than to use a hierarchical navigation scheme that be difficult to understand.

*** Note: the text just below this section incorrectly reflects the final decision of WCAG as published in Working Draft 13 December 2012 which can be found at: http://www.w3.org/TR/wcag2ict/#navigation-mechanisms-mult-lochttp://www.w3.org/TR/wcag2ict/#navigation-mechanisms-mult-loc
That published text is:
Additional guidance when applying Success Criterion 2.4.5 to Non-Web Documents and Software

For Documents:

This applies as written and described in INTENT of Understanding WCAG 2.0 (above), replacing “Web pages” with “documents” and “set of Web pages” with “set of non-web documents”.

With these substitutions, it would read:

2.4.5 Multiple Ways: More than one way is available to locate a document within a set of non-web documents except where the document is the result of, or a step in, a process.

Note 1: Authors should assume that an infrastructure exists to allow a user to locate documents in the set; for example, by selecting links within a member of the set, browsing through the files that make up the set, or by searching within members of the set for the names of the other members.

Note 2: A file directory would be the equivalent of a site map for documents in that it provides a link to each of the documents in the set of documents. The directory also acts as the HOME for the set.

Note 3: A search function in a file system (that finds documents) would be equivalent to a Web search function for Web pages.

Note 4: Authors can assume that the non-Web documents will be stored and accessed on a major operating system with browse and search abilities unless they have specific information to the contrary.

For Software: 

The WCAG2ICT Task Force has not yet produced additional guidance for software for Success Criterion 2.4.5.


Additional guidance when applying to Non-Web Documents and Software
For Documents:

This applies as written and described in INTENT of Understanding WCAG 2.0 (above), replacing “web pages” with "Documents” and assuming that “set” means a group of items 1) that are published together, and 2) where the items all refer to each other by name or link.

With these substitutions,
the success criterion would read:

2.4.5 Multiple Ways: More than one way is available to locate a document within a set of documents except where the document is the result of, or a step in, a process.

Note 1:  Republishing or bundling previously published documents as a collection does not constitute a set of documents.
Note 2: If a set is broken apart, the individual parts are no longer part of a set, and would be evaluated as any other individual documents.
Note 3: Authors should assume that an infrastructure exists to allow a user to locate documents in the set; for example, by selecting links within a member of the set, browsing through the files that make up the set, or by searching within members of the set for the names of the other members.
Note 4: A file directory would be the equivalent of a site map for documents in that it provides a link to each of the documents in the set of documents. The directory also acts as the HOME for the set.
Note 5: A search function in a file system (that finds documents) would be equivalent to a web search function for web pages.
Note 6: Authors can assume that the non-web documents will be stored and accessed on a major operating system with browse and search abilities unless they have specific information to the contrary.

One example of a set documents would be a 3 part report where each part is a separate file. At the beginning of each file the table of contents for "navigating" to the other parts is repeated. Each table of contents might have additional navigation mechanisms for the particular chapter in which it is included, but the items that are repeated in all of the chapters (i.e. the navigation mechanisms to the other chapters) would be in the same order relative to each other.

For Software: 

The task force has to date been unable to come up with a cogent and objective way to apply this provision across all types of  software.  The task force has explored approaches for applying it to software that takes the appearance of a self playing document or book.  But for other types of software the task force did not see any way to apply it consistently or clearly.  This is because the task force was not able to unambiguously define what a "set of software" would be. It is easy to find collections, bundles or suites of software but those are not sets in the same manner as sets of Web pages (where items in the set interlink or have common look and feel).  Further, key to the concept of a set in WCAG 2.0 is that the members of the set are hyperlinked together, and while file URLs exist for documents, they do not exist for running software, nor could the task force find their analog in running software.

Because after considerable effort we were (1) unable to find a viable definition for what a "set of software" means that could be applied across software in general, and (2) unable to find any clear example of "sets of software" in the wild that seemed to be an equivalent of "set of Web pages", the task force is unable to provide any  guidance on how to apply this success criterion to "software in a set of software" in general.  We were also unable to find any specific scoping language that would define to which sets of software it would always apply. 

Individual  instances of software would automatically meet this success criterion - because this success criterion applies only to things that appear in a set.

<        POST JULY 27TH CONSENSUS ITEMS ARE ABOVE  >.   
 <  OUR RESPONSE TO PUBLIC COMMENTS ARE BELOW>




                                                                                                                                   .
               <TEXT AS SENT OUT FOR REVIEW ON  JULY 27TH                             .
                                                                                                                                   .

Success Criterion 2.4.5: Multiple Ways (Level AA)

From Success Criterion 2.4.5:

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.

Intent from Understanding Success Criterion 2.4.5 in Understanding WCAG 2.0:

The intent of this Success Criterion is to make it possible for users to locate content in a manner that best meets their needs. Users may find one technique easier or more comprehensible to use than another.

Even small sites should provide users some means of orientation. For a three or four page site, with all pages linked from the home page, it may be sufficient simply to provide links from and to the home page where the links on the home page can also serve as a site map.

Specific Benefits of Success Criterion 2.4.5
  • Providing an opportunity to navigate sites in more than one manner can help people find information faster. Users with visual impairments may find it easier to navigate to the correct part of the site by using a search, rather than scrolling through a large navigation bar using a screen magnifier or screen reader. A person with cognitive disabilities may prefer a table of contents or site map that provides an overview of the site rather than reading and traversing through several Web pages. Some users may prefer to explore the site in a sequential manner, moving from Web page to Web page in order to best understand the concepts and layout.

  • Individuals with cognitive limitations may find it easier to use search features than to use a hierarchical navigation scheme that be difficult to understand.

Additional guidance when applying Success Criterion 2.4.5 to Electronic Documents and Software Aspects of Products:

The WCAG2ICT Task Force has not yet produced additional guidance for Success Criterion 2.4.5.



                                                                                                                                   .
         </ END OF 
TEXT AS SENT OUT FOR REVIEW ON  JULY 27TH    >            .
                                                                                                                                   .

Success Criteria 2.4.5: 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. (Level AA)


Intent of WCAG Success Criteria 2.4.5  (Quoted from Understanding WCAG 2.0)

The intent of this Success Criterion is to make it possible for users to locate content in a manner that best meets their needs. Users may find one technique easier or more comprehensible to use than another.

Even small sites should provide users some means of orientation. For a three or four page site, with all pages linked from the home page, it may be sufficient simply to provide links from and to the home page where the links on the home page can also serve as a site map.

Specific Benefits of Success Criterion 2.4.5:

  • Providing an opportunity to navigate sites in more than one manner can help people find information faster. Users with visual impairments may find it easier to navigate to the correct part of the site by using a search, rather than scrolling through a large navigation bar using a screen magnifier or screen reader. A person with cognitive disabilities may prefer a table of contents or site map that provides an overview of the site rather than reading and traversing through several Web pages. Some users may prefer to explore the site in a sequential manner, moving from Web page to Web page in order to best understand the concepts and layout.

  • Individuals with cognitive limitations may find it easier to use search features than to use a hierarchical navigation scheme that be difficult to understand.


<End of material Quoted from Understanding WCAG 2.0>


Additional guidance when applying to ICT

< Task force language goes here when consensus is reached > 

                                                                                                                                   .
</ END OF TASK FORCE CONSENSUS CONTENT FOR APPLICATION NOTE >.
              (only EDITORS should make edits above this line.                                      .
     -- and then only after text is approved by consensus by the Task force.              .
                                                                                                                                   .



PROPOSALS FOR  CONSENSUS TEXT =================

Insert your proposals for the text to go above.  Label each Proposal separately.  Trace has provided a startup proposal for each.   Below is a template.  Please copy it and leave a template behind for others to add their proposal.
 

Proposal #1 (Trace Center) ========================

Additional guidance when applying to Electronic Documents and Software Aspects of Products

This applies directly as written, and as described in  INTENT  from Understanding WCAG 2.0  (above) with the word “document” substituted for Web Page. If there is no set of related documents, (chapters, sections, documents in a set) then the provision is automatically met.  

For sets of documents, (e.g. a collection of chapters, sections, or papers) browsing ( in this case turning pages) is defined in WCAG as one mode and a table of contents would be a second or listing of papers in the set would be a second.

(see Introduction for how to interpret "content")

Additional guidance when applying to Software Aspects of Products

This applies directly as written and as described in INTENT from WCAG (above) with the word “interaction context” substituted for Web Page. 

Generally software provides multiple ways to access functionality including menus, dialogs, ribbons and help systems. Note that WCAG does not require multiple ways of getting to each item in a web page (read here as ‘interaction context’ ) but rather just multiple ways to find the different web pages (contexts of interaction).

Help text is one way to get to interaction contexts. 

Proposal #2 (Loïc Martínez) ========================

Additional guidance when applying to Electronic Content and Electronic Documents 

This applies directly as written, and as described in  INTENT  from Understanding WCAG 2.0  (above) with the word “document” substituted for Web Page. If there is no set of related documents (chapters, sections, documents in a set) then the provision is automatically met.  

For sets of documents, (e.g. a collection of chapters, sections, or papers) browsing ( in this case turning pages) is defined in WCAG as one mode and providing a table of contents or listing the papers in the set would be a second way of locating documents in the set.


Additional guidance when applying to Software Aspects of Products
This success criterion is to be interpreted with the words "interaction context" substituted for "web page". This success criterion does not apply to software user interfaces, as it would require multiple ways of reaching any interaction context (window, dialog...) and that is not always feasible nor desirable.


Proposal #3 (Gregg Van Draft in Process with Pierce, Al, David, Loic, Alex) ========================

Success Criteria 2.4.5: 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. (Level AA)

Additional guidance when applying to Electronic Documents and Software Aspects of Products

In WCAG a web page does not mean a printed page but rather a document or a major section of what would be a compound document made up of web pages.   In the electronic document context this would be equivalent to either a document in a set of documents or a major author defined division (e.g. chapter, section etc) of a large document.  In software this would be equivalent to a set of programs that the author had designed as a set (and not just a collection from an author) or major author defined divisions (e.g. named divisions of the program that a person would move between)  of a large program. 

For documents this success criterion applies directly as written, and as described in  INTENT  from Understanding WCAG 2.0  (above) with the word “document or major division of a document” substituted for Web Page and  "author defined set of documents or major author defined divisions of a document" for "set of web pages".    If there is no set of related documents created by the author, or no major divisions in a document (chapters, sections) defined by the author then the provision is automatically met.  

For software this success criterion applies directly as written, and as described in  INTENT  from Understanding WCAG 2.0  (above) with the word  "program or major author defined division in a program" substituted for "Web Page"  and "author defined set of programs or major divisions of a program"   for "set of web pages".   If there is no set of related programs created by the author, or no major divisions in a program defined by the author then the provision is automatically met.  

NOTE:  In the Understanding WCAG 2.0 writeup for this success criterion the WCAG Working Group gives examples of browsing and search as two possible methods for locating a Web page within a set of Web pages.  Both of these approaches would appear to be supported by most Electronic Documents,  and browsing and searching of help functions would appear to allow locating major sections in software as well. 

Note: Modal dialog boxes by their nature are considered part of a process that you can not navigate away from and must completed or cancelled before continuing.

< note to task force. The last note comes close to providing techniques -- though it might skirt it because it  simply comments on WCAG understanding document examples (not the sufficient techniques in WCAG but just the examples).  In this case - it might be considered informative since it is not specific or definitive and it is needed to make this provision understandable and to make it clear that it is not hard to meet this if documents are not locked down and software uses standard good practice for design.   >

Proposal #4 (Gregg Loic Mike) ========================

Success Criteria 2.4.5: 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. (Level AA)

Additional guidance when applying to Electronic Documents and Software Aspects of Products

For documents, this applies directly as written and as described in  INTENT  from Understanding WCAG 2.0  (above) with the word “document” substituted for Web Page  and "set of documents published as a single entity" substituted for "set of web pages".

For software this applies directly as written and as described in  INTENT  from Understanding WCAG 2.0  (above) with the word “user interface context” substituted for Web Page  and "software program" substituted for "set of web pages".

NOTE:  In the Understanding WCAG 2.0 writeup for this success criterion the WCAG Working Group gives examples of browsing and search as two possible methods for locating a Web page within a set of Web pages.  Both of these approaches would appear to be supported by most Electronic Documents,  and browsing and searching of help functions would appear to allow locating major sections in software as well. 

Note: Modal dialog boxes by their nature are considered part of a process that you can not navigate away from and must completed or cancelled before continuing, and are therefore covered by the exception.

 

Proposal #5 (Gregg Van - modification of Gregg Loic Mike) =====================

Success Criteria 2.4.5: 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. (Level AA)

Additional guidance when applying to Electronic Documents and Software Aspects of Products

For documents, this applies directly as written and as described in  INTENT  from Understanding WCAG 2.0  (above) with the word “document” substituted for Web Page  and "set of documents published as a single entity" substituted for "set of web pages".

For software this applies directly as written and as described in INTENT from Understanding WCAG 2.0 (above) with the word [“user interface context” or whatever we choose for Web Page] substituted for Web Page and "software aspects of a single product" substituted for "set of web pages".    However the group found that most software would automatically meet the "multiple ways" by its design and that cataloguing all of the ways to make it clear what constituted a "way" would be near impossible making

NOTE:  In the Understanding WCAG 2.0 writeup for this success criterion the WCAG Working Group gives examples of browsing and search as two possible methods for locating a Web page within a set of Web pages.  Both of these approaches would appear to be supported by most Electronic Documents,  and browsing and searching of help functions would appear to allow locating major sections in software as well. 

Note: Modal dialog boxes by their nature are considered part of a process that you can not navigate away from and must completed or cancelled before continuing, and are therefore covered by the exception.

 Proposal #6 (Submitter) ========================

Additional guidance when applying to Electronic Documents and Software Aspects of Products
For BOTH documents and software --   a set is a set.   not anything "related to" or "by the same author" or "linked somewhere in"  or the other things suggested and argued against. 

Documents "published as a set" are a set.  Everything else is a collection of some sort or less. 

Software -- becomes  "UI contexts" or whatever else we determine is equiv of web page --- that are published as a set.  This boil down to 'the software aspects of a single product".  (which is what I propose we look at here)  That might be a one or more "programs" that are published as one  (e.g. OpenOffice"  but would not be every bundle of software that is sold together.   They have to be 'published as a set"  not sold together. 


Proposal #7  (Gregg ) ========================

Additional guidance when applying to Electronic Documents and Software Aspects of Products

This applies to documents directly as written, and as described in  INTENT  from Understanding WCAG 2.0  (above)  replacing for "Web Pages" with “documents” and replacing "set of web pages" with "documents published at the same time and labeled as a set".

NOTE: Examples of "labeled as a set" include, a 4 part report, and an encyclopedia, both of which are obviously a set from their names and the way the individual documents are labeled.   

This applies to software aspects of products directly as written and as described in INTENT from Understanding WCAG (above) replacing "Web Pages" with the phrase "software programs" and replacing "a set of web pages" with "set of software programs published at the same time and labeled as a set".

Proposal #8  (Pierce and just for Docs) ========================

Additional guidance when applying to Electronic Documents
 
This applies to documents directly as written, and as described in INTENT from Understanding WCAG 2.0  (above)  replacing for "web pages" with “documents” and replacing "set of web pages" with "set of documents”.  A set of documents is a group of documents that are 1) published at the same time, 2) identified as a set in at least one member document, and 3) that contain links in at least one member document to the other documents in the set.  Republishing previously published documents as a collection does not constitute a set of documents.
 
NOTE: Authors should assume that the set is not broken apart, and that an infrastructure exists to allow a user to locate documents in the set by selecting links within a member document, browsing through the files that make up the set, and by searching the documents' contents or the names of the member documents.

Proposal #9  (Coming out of 31Aug12 meeting) ========================

Additional guidance when applying to Electronic Documents

This applies to documents directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "web pages" with "documents" and replacing "set of web pages" with "set of documents". A set of documents is a group of documents that are 1) published together, and 2) labeled as a set within at least one member document. Republishing previously published documents as a collection does not constitute a set of documents.

NOTE: Authors should assume that the set is not broken apart, and that an infrastructure exists to allow a user to locate documents in the set; for example, by selecting links within a member document, browsing through the files that make up the set, or by searching the documents' contents or the names of the member documents.


Examples of sets of documents

  1. Muse Test Suite, Part 1 Test Objectives (link) & Part 2 Test Methods (link).  
    • Published together on Jan 6, 2006. Labeled as a set in 1.1 Scope.

  2. User Guide to Audio editing with Audacity, Part 1 (link) & Part 2 (link). 
    • Published together in 2009 and labeled as a set in Part 2.



Proposal #10  (Gregg - Based on 31Aug12 meeting and email exchanges on the list) ========================

Additional guidance when applying to Electronic Documents

This applies to documents directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "web pages" with "documents" and replacing "set of web pages" with "set of documents". 

NOTES:
  1. A set of documents is a group of documents that are 1) published together, and 2) labeled as a set within at least one member document. 
  2. Republishing previously published documents as a collection does not constitute a set of documents.
  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 in that it provides a link to each of the documents in the set of documents.  The directory also acts as the HOME for the set.
  5. A search function in an operating systems would be equivalent for documents to a web search function for web pages.
  6. Authors can assume that an infrastructure exists that allows users to locate documents in the set; for example, by selecting links within a member document, browsing through the files that make up the set, or by searching the documents' contents or the names of the member documents, since document names and the ability for machine access to the text are required by other success criteria.
Examples -  of sets of documents on the web that could be saved with meaningful file names to a hard disk and distributed as non-web sets of documents.
  1. Muse Test Suite, Part 1 Test Objectives (link) & Part 2 Test Methods (link).  
    • Published together on Jan 6, 2006. Labeled as a set in 1.1 Scope.

  2. User Guide to Audio editing with Audacity, Part 1 (link) & Part 2 (link). 
    • Published together in 2009 and labeled as a set in Part 2.

'

Proposal #10.5  ( same as 10 but extended to cover SOFTWARE as well) (Gregg - Based on 31Aug12 meeting and email exchanges on the list) ========================


Additional guidance when applying to Electronic Documents and Software Aspects of Products

This applies to electronic documents directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "web pages" with "documents" and replacing "set of web pages" with "set of documents". 

This applies to software directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) 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 these success criteria:
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 make it easier for people with cognitive disabilities to find their way around.



FOR REFERENCE


Success Criterion 2.4.5:    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.


Proposal #11  (from Gregg's whitepaper) ========================

Additional guidance when applying to Electronic Documents and Software Aspects of Products

For non-embedded content, this applies directly as written, and as described in  INTENT  from Understanding WCAG 2.0  (above) replacing "a Web page" and "Web pages" with "non-embedded content".

For software, this applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "a Web page" and "Web pages" with "software".



Proposal #12  ( Gregg based on offline discussions and comments in survey)  (Same as  11 but with notes  )     ========================


Additional guidance when applying to Electronic Documents and Software Aspects of Products

For non-embedded content, this applies directly as written, and as described in  INTENT  from Understanding WCAG 2.0  (above) replacing "a Web page" and "Web pages" with "non-embedded content".

For software, this applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "a Web page" and "Web pages" with "software".

Where set is defined as

SET
group of non-embedded content or software products that are 1) published together at the same time, 2) never distributed or installed separately, 3) all referenced from at least one parent item with back references from the children to the parent.

Notes:  References do not need to be links but if they are links that would be one means of locating the items, as would browsing if the items have meaningful file or directory names. 

NOTE: For non-web content, this has a direct parallel with web content and would apply the same was as the content would if it were placed on line and viewable through a browser.   For software this has a parallel application as well but is of minor importance since individual software products are rarely distributed only in sets and when they are they are almost always linked in ways that would make this provision be automatically met. 




Success Criterion 2.4.5:    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.



<Not yet approved by WCAG WG - "document" replaced by "non-embedded content" as agreed by resolution. Some additional editing for readability was required.>
Additional guidance when applying to Electronic Documents

This applies to non-embedded content directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "web pages" with "non-embedded content" and replacing "set of web pages" with "set of non-embedded content". A set of non-embedded content is a group of non-embedded content that is 1) published together, and 2) labeled as a set within at least one member of the set. Republishing previously published non-embedded content as a collection does not constitute a set of non-embedded content.

NOTE: Authors should assume that the set is not broken apart, and that an infrastructure exists to allow a user to locate non-embedded content in the set; for example, by selecting links within a member of the set, browsing through the files that make up the set, or by searching within members of the set for the names of the other members.

DISCUSSION POINTS, OPINIONS, ISSUES, NOTES etc. 

8/14 (Bruce) Trying language proposed for 3.2.3 (also still under discussion), replacing “Web Page” with the phrase “part of a software user interface” and replacing “set of web pages” with “software user interface” then we have:

Success Criteria 2.4.5 (for software):  More than one way is available to locate a part of software user interface within a software user interface except where the part of a software user interface is the result of, or a step in, a process.

That doesn’t work, what we really want is something like:

Success Criteria 2.4.5 (for software): More than one way is available to locate a feature/function within a software product/package except where the feature/function is the result of, or a step in, a process.

This implies replacing “Web Page” with the phrase “feature/function” and replacing “set of web pages” with “software product/package”.

---- Proposal explanation -----

Proposal #2 (Loïc Martínez)

  • Documents. I've taken the TRACE proposal and just changed the second paragraph trying to improve clarity.
  • Software. In the M376 we decided that this success criterion did not apply because we thought that we could not mandate that all software have multiple ways of reaching each interaction context (window, dialog...). We agree that, in general, it is common and desirable to provide multiple ways of accessing the same functionality, but these multiple ways may imply the use of different interaction contexts.I still believe that this success criterion is difficult to apply to any type of software. My proposal explains this agreement of the M376 team.

---- ISSUES-----

Note that M376 work identifies 2.4.5 as one of two “success criteria that do not apply for user interfaces of software”. See Draft EN 301 549 V0.0.4 (2012-04) Table 4, p. 30.

RE - Documents

Issue1: "Generally won't apply to nearly all documents...  TOC? Index? Footnotes?"          :

Comment on Issue1: “Is automatically met by nearly all documents.”

 

RE - Software

Issue1: Not clear what this means in a software context.  Key topic for group discussion!  :

Comment on Issue1: See above in contribution.   Examples would be very good here—but we need to be careful we don’t get into “sufficient” techniques.

 

IBM comments on 2011 ANPRM, Appendix A (p. 21, 6 March 2012)
What does this mean in the context of a software application?  Is a “Web page” equivalent to an application, a window within the application or some text in a window?  Does “a set of Web pages” mean the application, a suite of applications (e.g. an office suite), or the entire set of applications on the computer?  If this is about finding an individual application among a set of applications (e.g. using Windows -> Start menu -> Find as one way and locating it underneath the Programs folder being another way), how can an individual application be seen as meeting or not meeting this criterion?  Is this requirement instead more along the lines of applying only to a feature within an application, or maybe a specific window within an application?


2010 ANPRM Text (22 March 2010)
406.4 Multiple Ways to Locate Content.  More than one way shall be provided for a user to locate content within ICT.
EXCEPTION:  When the content is the result of, or a step in a process, more than one way for a user to locate content is not required.


Teitac Report (3 April 2008)
3-W: Multiple Ways
There must be more than one way available to locate CONTENT within a set of Web pages where CONTENT is not the result of, or a step in, a process.  For example, providing a site map, index, table of contents, or search would be sufficient.




Comments