Merge branch 'main' into maryjom-change-parsing-sc

comments-on-conformance.md

@@ -4,7 +4,7 @@ Comments on Conformance
 WCAG2ICT is not a standard, so it is not possible to conform to WCAG2ICT. However, some entities may wish to use the information in WCAG2ICT to help establish standards or regulations regarding accessibility in ICT that are based on WCAG 2.2. While such standards or regulations will need to address matters of conformance themselves, the following notes may be of assistance to those wishing to draft their own requirements:
 
 1.  The WCAG 2.2 success criteria and the conformance requirements were designed to work together, such that the language of the success criteria is based on the nature of the conformance requirements. The choice of what level to use for a given criteria (A vs. AA vs. AAA) was further influenced by a number of factors specific to the web domain, as set forth in [Understanding Levels of Conformance](http://www.w3.org/WAI/WCAG22/Understanding/conformance#levels).
-2.  In the WCAG 2.2 conformance model, a success criteria is satisfied if the item being evaluated does not fail it. If the success criterion is in relation to something that does not exist for the item being evaluated (e.g. a success criterion is about captioning audio and there is no audio) then the success criterion is automatically met. This approach is central to the way the success criteria in WCAG are structured and worded.
+2.  In the WCAG 2.2 conformance model, a [success criteria is satisfied](#dfn-satisfies-a-success-criterion) if the item being evaluated does not fail it. If the success criterion is in relation to something that does not exist for the item being evaluated (e.g. a success criterion is about captioning audio and there is no audio), where some might consider the criterion "not applicable", the success criterion is automatically met. This approach is central to the way the success criteria in WCAG are structured and worded.
 3.  WCAG 2.2 conformance is applied to the item being evaluated (i.e. web page) as a whole, except when a process includes use of several items, in which case all of the items that are needed in order to complete the process must conform.
 4.  In WCAG 2.2, when conformance relies on accessibility features of the platform (i.e. browser for web content) or on assistive technologies, WCAG 2.2 requires that there are assistive technologies, etc. that work with the product (web page). That is, conformance with WCAG 2.2 requires that the approaches used are supported by assistive technologies.
 5.  WCAG 2.2 allows information on part of a page to not conform if the same information is available elsewhere on the page in conforming fashion. However WCAG 2.2 identifies 4 success criteria that must be met on all areas of the page because they can interfere with the user's ability to access and use other parts of the page:

introduction.md

@@ -41,7 +41,7 @@ The following are out of scope for this document:
 
 ### Document Overview
 
-This document includes text quoted from the WCAG 2.2 principles, guidelines, and success criteria, without any changes. It also includes excerpted text from the “Intent” sections of the WCAG 2.2 supporting document [Understanding WCAG 2.2 (Public Review Draft)](https://www.w3.org/WAI/WCAG22/Understanding/) \[\[UNDERSTANDING-WCAG22\]\]. The guidance provided by this document for each success criterion is preceded by a heading beginning with “Additional Guidance…”. This guidance was created by the WCAG2ICT Task Force, then reviewed and approved by the AG Working Group.
+This document includes text quoted from the WCAG 2.2 principles, guidelines, and success criteria, without any changes. It also includes excerpted text from the “Intent” sections of the WCAG 2.2 supporting document [Understanding WCAG 2.2 (Public Review Draft)](https://www.w3.org/WAI/WCAG22/Understanding/) \[\[UNDERSTANDING-WCAG22\]\]. The guidance provided by this document for each principle, guideline, success criterion, and definition is preceded by a heading beginning with “Applying…”. This guidance was created by the WCAG2ICT Task Force, then reviewed and approved by the AG Working Group.
 
 Additional supporting documents for WCAG 2.2, such as the [WCAG 2 Overview](https://www.w3.org/WAI/intro/wcag.php), [Techniques for WCAG 2.2](https://www.w3.org/WAI/WCAG22/Techniques/) \[\[WCAG22-TECHS\]\], and [How to Meet WCAG (Quick Reference)](https://www.w3.org/WAI/WCAG21/quickref/), remain available for web content, but have not been changed to apply to non-web documents and software.
 
@@ -51,12 +51,13 @@ Additional supporting documents for WCAG 2.2, such as the [WCAG 2 Overview](http
 The following stylistic conventions are used in this document:
 
 *   Quotes from WCAG 2.2 and Understanding WCAG 2.2 are in `<blockquote>` elements and visually styled with a gray bar on the left, and immediately follow the heading for the principle, guideline, or success criterion.
-*   Additional guidance provided by this document begins with the phrase “Guidance When Applying” and has no special visual styling.
+*   Additional guidance provided by this document begins with the phrase “Applying” and has no special visual styling.
 *   Replacement text that is presented to show how an SC would read as modified by the advice in this document are in `<ins>` elements visually styled as bold green text with a dotted underline.
 *   Notes are slightly inset and begin with the phrase “NOTE”. Each note is in its own inset box styled in pale green with a darker green line on the left side of the box.
 *   References to glossary items from WCAG 2.2 are presented in `<cite>` elements visually styled as ordinary text with a dotted underline, and contain title attributes noting these are WCAG definitions. They turn blue with a yellow background when mouse or keyboard focus is placed over them.
 *   References to glossary items in this document are presented in `<cite>` elements visually styled as ordinary text with a dark gray underline.
 *   Hereafter, the short title “WCAG2ICT” is used to reference this document.
+*   In headings the term "Success Criterion" has been shortened to “SC” for brevity.
 
 ### Comparison with the 2013 WCAG2ICT Note
 
@@ -81,6 +82,7 @@ The following changes and additions have been made to update the 2013 WCAG2ICT d
     * [Success Criterion 4.1.3 Status Messages](#status-messages)
 * New WCAG 2.2 Success Criteria
     * [Success Criterion 2.5.8 Target Size (Minimum)](#target-size-minimum)
+    * [Success Criterion 3.3.7 Redundant Entry](#redundant-entry)
 * Obsolete and Removed WCAG 2.2 Success Criteria
     * [Success Criterion 4.1.1 Parsing](#parsing)
 * New terms

key-terms.md

@@ -78,6 +78,19 @@ An assembly of files that represented the video, audio, captions and timing file
 
 Counterexample: A binder file used to bind together the various exhibits for a legal case would not be a document.</div>
 
+### Menu-driven Interface
+
+The term **menu-driven interface**, as used in WCAG2ICT, has the meaning below:
+
+<DL><DT>menu-driven interface (as used in WCAG2ICT)</DT><DD>
+
+an interface composed of menus and sub-menus which the user accesses by pressing buttons or using a touch-screen
+</DD></DL>
+
+<div class="example">
+
+Products that have a menu-driven interface include, but are not limited to, self-service transaction machines, printers, and IP-based telephones.</div>
+
 ### Set of Documents
 
 The term **set of documents**, as used in WCAG2ICT, has the meaning below:
@@ -119,7 +132,7 @@ Consistent does not mean identical. For example, if a list of choices is provide
 If a member of the set is separated from the set, it is no longer part of a set, and would be evaluated as any other individual software program.</div>
 <div class="note">
 
-Any software program that is not part of a set, per this definition, would automatically satisfy any success criterion that is specified to apply to “sets of” software (as is true for any success criterion that is scoped to only apply to some other type of content).</div>
+Any software program that is not part of a set, per this definition, would automatically [satisfy any success criterion](#dfn-satisfies-a-success-criterion) that is specified to apply to “sets of” software (as is true for any success criterion that is scoped to only apply to some other type of content).</div>
 <div class="note">
 
 If there is any ambiguity whether the group is a set, then the group is not a set.</div>

success-criteria-problematic-for-closed-functionality.md

@@ -13,7 +13,7 @@ There are Success Criteria that can be problematic for developers of closed func
 <li><a href="#audio-description-or-media-alternative-prerecorded">1.2.3 Audio description or Media Alternative</a> — One of the options available to authors for success criterion 1.2.3 is providing a media alternative that is text which, in the absence of connected assistive technology, would need to be made available in different modalities.</li>
 <li><a href="#info-and-relationships">1.3.1 Info and Relationships</a> — Requires information in a programmatically determinable form.</li>
 <li><a href="#meaningful-sequence">1.3.2 Meaningful Sequence</a> — Requires information in a programmatically determinable form. Instead, a closed functionality software equivalent would be to provide a meaningful reading sequence through auditory output or some other non-visual means that helps users correlate the output with the corresponding information displayed on the screen.</li>
-<li><a href="#orientation">1.3.4 Orientation</a> — Closed functionality products that have fixed-in-place displays or other limitations to modifying the physical display orientation are covered under the essential exception and are not required to provide support for orientation changes. See the note in the section <a href="#guidance-when-applying-success-criterion-1-3-4-to-non-web-documents-and-software">Guidance When Applying Success Criterion 1.3.4 to Non-Web Documents and Software</a>.</li>
+<li><a href="#orientation">1.3.4 Orientation</a> — Closed functionality products that have fixed-in-place displays or other limitations to modifying the physical display orientation are covered under the essential exception and are not required to provide support for orientation changes. See the note in the section <a href="#applying-sc-1-3-4-orientation-to-non-web-documents-and-software">Applying SC 1.3.4 Identify Input Purpose to Non-Web Documents and Software</a>.</li>
 <li><a href="#identify-input-purpose">1.3.5 Identify Input Purpose</a> — Requires information in a programmatically determinable form; in the absence of programmatic capabilities, text labels need to be specific and be provided to the user in other modalities (e.g. auditory).</li>
 <li><a href="#audio-control">1.4.2 Audio Control</a> — The intent of this success criterion is to avoid interference of audio with assistive products, which are not available in a system with closed functionality. But if the built-in accessibility features of the closed system provide speech output, then the interference may happen and this SC applies. In addition, there are existing closed functionality requirements in standards such as the EN 301 549 and U.S. Revised 508 Standards (402.3 Volume) that cover volume control for closed functionality products.</li>
 <li><a href="#contrast-minimum">1.4.3 Contrast (Minimum)</a> — There are cases where applying this Success Criterion to non-web software on closed functionality products is problematic:
@@ -33,10 +33,11 @@ There are Success Criteria that can be problematic for developers of closed func
 <li>When the color contrast ratio cannot be programmatically measured due to system limitations (e.g. lockdown), precise quantifiable testing of color contrast cannot be performed by a third party. In such cases, the software author would need to confirm that the color combinations used meet the contrast requirement.
 <div class="note">Photographs are not sufficient for testing that content meets this Success Criterion. This is because the quality of the lighting, camera, and physical aspects of the hardware display can dramatically affect the ability to capture the content for testing purposes.</div></li>
 </ul></li>
-<li><a href="#text-spacing">1.4.12 Text Spacing</a> — In closed functionality software the ability for users to modify line, paragraph, letter, or word spacing is rarely supported. However, if encountered, the Success Criterion applies as noted in the <a href="#guidance-when-applying-success-criterion-1-4-12-to-non-web-documents-and-software">Guidance when Applying Success Criterion 1.4.12 to Non-Web Documents and Software</a>.</li>
-<li><a href="#keyboard">2.1.1 Keyboard</a>—requires operation via a keyboard interface which allows alternative input devices;</li>
+<li><a href="#text-spacing">1.4.12 Text Spacing</a> — In closed functionality software the ability for users to modify line, paragraph, letter, or word spacing is rarely supported. However, if encountered, the Success Criterion applies as noted in the <a href="#applying-sc-1-4-12-text-spacing-to-non-web-documents-and-software">Applying SC 1.4.12 Text Spacing to Non-Web Documents and Software</a>.</li>
+<li><a href="#keyboard">2.1.1 Keyboard</a>—Requires operation via a keyboard interface which allows alternative input devices. When a product with closed functionality either does not have a standard keyboard or one cannot be connected, it would need an alternate way to access all functionality that does not require accurate pointing, path-based movements, or specific timings.</li>
 <li><a href="#bypass-blocks">2.4.1 Bypass Blocks</a> — The WCAG2ICT interpretation of this success criterion replaces "sets of Web pages" with "sets of software programs" which are extremely rare - especially for closed functionality software. However, being able to bypass blocks of content that are repeated within software is generally considered best practice.</li>
-<li><a href="#page-titled">2.4.2 Page Titled</a>—where software is an integral part of hardware that provides a single function, such as a calculator or IP telephone, there is no need for a title;</li>
+<li><a href="#page-titled">2.4.2 Page Titled</a>—Where the software is part of a product that provides a single function, or has a menu-driven interface, there is no need for a title.</li>
+<li><a href="#multiple-ways">2.4.5 Multiple Ways</a>—The WCAG2ICT interpretation of this Success Criterion replaces "set of Web pages" with "set of software programs." Such sets, particularly in the context of closed functionality software, are exceedingly rare. There are a number of notes in the section <a href="#applying-sc-2-4-5-multiple-ways-to-non-web-documents-and-software">Applying SC 2.4.5 Multiple Ways to Non-Web Documents and Software</a> that are applicable to closed functionality software.</li>  
 <li><a href="#label-in-name">2.5.3 Label in Name</a>—requires information in a programmatically determinable form; specifically, the programmatic name contains the text of the visual label;</li>
 <li><a href="#language-of-page">3.1.1 Language of Page</a>—requires information in a programmatically determinable form;</li>
 <li><a href="#language-of-parts">3.1.2 Language of Parts</a>—requires information in a programmatically determinable form;</li>

wcag2ict.js

@@ -280,7 +280,7 @@ function getTocItem(id) {
 function hideDeepNums() {
 	document.querySelectorAll("#comments-by-guideline-and-success-criterion section").forEach(function(item) {
 		var id = item.id;
-		if (id.startsWith("guidance-when-")) {
+		if (id.startsWith("applying-")) {
 			var tocItem = getTocItem(id);
 			if (tocItem != null) tocItem.remove();
 			var secno = item.querySelector("bdi.secno");
@@ -292,7 +292,7 @@ function hideDeepNums() {
 function hideDeepNumsGlossary() {
 	document.querySelectorAll("#glossary-items-with-specific-guidance section").forEach(function(item) {
 		var id = item.id;
-		if (id.startsWith("guidance-when-")) {
+		if (id.startsWith("applying-")) {
 			var tocItem = getTocItem(id);
 			if (tocItem != null) tocItem.remove();
 			var secno = item.querySelector("bdi.secno");