diff --git a/index.html b/index.html
index 0b871366..a3037966 100644
--- a/index.html
+++ b/index.html
@@ -89,7 +89,7 @@
 <link rel="stylesheet" type="text/css" href="wcag2ict.css">
 	
 <meta name="color-scheme" content="light">
-<meta name="revision" content="7cbeeea99a15be38151ed58cc27e84098e010c9a">
+<meta name="revision" content="43d12e0494eda502f8cb4660cc5f2ed40b93abab">
 <meta name="description" content="This document, “Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)” describes how the Web Content Accessibility Guidelines (WCAG) versions 2.0 [WCAG20], 2.1 [WCAG21], and 2.2 [WCAG22] principles, guidelines, and success criteria can be applied to non-web Information and Communications Technologies (ICT), specifically to non-web documents and software. It provides informative guidance (guidance that is not normative and does not set requirements).">
 <style>
 var{position:relative;cursor:pointer}
@@ -212,7 +212,7 @@
     }
   },
   "lint": false,
-  "gitRevision": "7cbeeea99a15be38151ed58cc27e84098e010c9a",
+  "gitRevision": "43d12e0494eda502f8cb4660cc5f2ed40b93abab",
   "publishISODate": "2024-07-09T00:00:00.000Z",
   "generatedSubtitle": "W3C Editor's Draft 09 July 2024"
 }</script>
@@ -1725,16 +1725,18 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 </section></section><section id="dfn-contrast-ratio"><div class="header-wrapper"><h4 id="x7-3-8-dfn-contrast-ratio">contrast ratio</h4><a class="self-link" href="#dfn-contrast-ratio" aria-label="Permalink for Section contrast ratio"></a></div><blockquote class="wcag-quote">  <p>(L1 + 0.05) / (L2 + 0.05), where</p>   <ul> <li>L1 is the <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-relative-luminance" id="ref-for-dfn-relative-luminance-1" title="the relative brightness of any point in a colorspace, normalized to 0 for darkest black and 1 for lightest white">relative luminance</a> of the lighter of the colors, and       </li> <li>L2 is the <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-relative-luminance" id="ref-for-dfn-relative-luminance-2" title="the relative brightness of any point in a colorspace, normalized to 0 for darkest black and 1 for lightest white">relative luminance</a> of the darker of the colors.       </li> </ul>   <div class="note" id="wcag-noteissue-container-generatedID--91" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--91" role="heading"><span>Note 1</span></div><p class="">Contrast ratios can range from 1 to 21 (commonly written 1:1 to 21:1).</p></div>   <div class="note" id="wcag-noteissue-container-generatedID--92" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--92" role="heading"><span>Note 2</span></div><p class="">Because authors do not have control over user settings as to how text is rendered       (for example font smoothing or anti-aliasing), the contrast ratio for text can be       evaluated with anti-aliasing turned off.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--93" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--93" role="heading"><span>Note 3</span></div><p class="">For the purpose of Success Criteria 1.4.3 and 1.4.6, contrast is measured with respect       to the specified background over which the text is rendered in normal usage. If no       background color is specified, then white is assumed.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--94" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--94" role="heading"><span>Note 4</span></div><p class="">Background color is the specified color of content over which the text is to be rendered       in normal usage. It is a failure if no background color is specified when the text       color is specified, because the user's default background color is unknown and cannot       be evaluated for sufficient contrast. For the same reason, it is a failure if no text       color is specified when a background color is specified.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--95" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--95" role="heading"><span>Note 5</span></div><p class="">When there is a border around the letter, the border can add contrast and would be       used in calculating the contrast between the letter and its background. A narrow border       around the letter would be used as the letter. A wide border around the letter that       fills in the inner details of the letters acts as a halo and would be considered background.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--96" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--96" role="heading"><span>Note 6</span></div><p class="">WCAG conformance should be evaluated for color pairs specified in the content that       an author would expect to appear adjacent in typical presentation. Authors need not       consider unusual presentations, such as color changes made by the user agent, except       where caused by authors' code.    </p></div>  </blockquote>
 <section id="applying-contrast-ratio-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-8-1-applying-contrast-ratio-to-non-web-documents-and-software">Applying “contrast ratio” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-contrast-ratio-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “contrast ratio” to Non-Web Documents and Software"></a></div>
 <p>This applies directly as written and as described in the WCAG 2 glossary.</p>
-<p>Because relative luminance is defined such that it cannot directly apply to hardware, please note the text in the introduction which reads: “This document does not comment on hardware aspects of products, because the basic constructs on which WCAG 2 is built do not apply to these.”</p>
+<div class="note" role="note" id="issue-container-generatedID-173"><div role="heading" class="note-title marker" id="h-note-165" aria-level="6"><span>Note</span></div><div class="">
+
+<p>Because relative luminance is defined such that it cannot directly apply to hardware, please note the text in the introduction which reads: “This document does not comment on hardware aspects of products, because the basic constructs on which WCAG 2 is built do not apply to these.”</p></div></div><p></p>
 </section></section><section id="dfn-css-pixels"><div class="header-wrapper"><h4 id="x7-3-9-dfn-css-pixels">CSS pixel</h4><a class="self-link" href="#dfn-css-pixels" aria-label="Permalink for Section CSS pixel"></a></div><blockquote class="wcag-quote">  <p>visual angle of about 0.0213 degrees</p>   <p>A CSS pixel is the canonical unit of measure for all lengths and measurements in CSS.       This unit is density-independent, and distinct from actual hardware pixels present       in a display. User agents and operating systems should ensure that a CSS pixel is       set as closely as possible to the <a href="https://www.w3.org/TR/css3-values/#reference-pixel">CSS Values and Units Module Level 3 reference pixel</a> [<cite><a class="bibref" data-link-type="biblio" href="https://www.w3.org/TR/wcag22/#bib-css3-values" title="CSS Values and Units Module Level 3">css3-values</a></cite>], which takes into account the physical dimensions of the display       and the assumed viewing distance (factors that cannot be determined by content authors).    </p>  </blockquote>
 <section id="applying-css-pixel-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-9-1-applying-css-pixel-to-non-web-documents-and-software">Applying “CSS pixel” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-css-pixel-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “CSS pixel” to Non-Web Documents and Software"></a></div>
-<div class="note" id="issue-container-generatedID-173"><div role="heading" class="ednote-title marker" id="h-ednote-7" aria-level="6"><span>Editor's note</span></div><div class="">The WCAG2ICT task force has added additional notes around how “CSS pixel” should be applied to non-web software. These changes were made in response to public comments received on the previous draft. </div></div>
+<div class="note" id="issue-container-generatedID-174"><div role="heading" class="ednote-title marker" id="h-ednote-7" aria-level="6"><span>Editor's note</span></div><div class="">The WCAG2ICT task force has added additional notes around how “CSS pixel” should be applied to non-web software. These changes were made in response to public comments received on the previous draft. </div></div>
 
 <p>This applies directly as written and as described in the WCAG 2 glossary.</p>
-<div class="note" role="note" id="issue-container-generatedID-174"><div role="heading" class="note-title marker" id="h-note-165" aria-level="6"><span>Note 1</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-175"><div role="heading" class="note-title marker" id="h-note-166" aria-level="6"><span>Note 1</span></div><div class="">
     
 <p><a href="#software">Non-web software</a> and its accompanying <a href="#platform-software">platform software</a> do not use CSS pixel measurements. Therefore, use platform-defined density-independent pixel measurements which approximate the CSS reference pixel. Examples of platform-defined density-independent pixel measurements include: points (pt) for iOS and macOS, density-independent pixels (dp) for Android, and effective pixels (epx) for Windows.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-175"><div role="heading" class="note-title marker" id="h-note-166" aria-level="6"><span>Note 2</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-176"><div role="heading" class="note-title marker" id="h-note-167" aria-level="6"><span>Note 2</span></div><div class="">
 Examples where a density-independent pixel may not be defined in the platform:
 
 <ul>
@@ -1746,23 +1748,23 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <li>Determine a viewing distance that matches the use case and display type. For instance, in the case of a touchscreen, the viewing distance is normally less than the length of an arm, typically around 28 inches (71 cm).</li>
 <li>Calculate the size of the reference pixel: Divide the viewing distance by 2688. The number 2688 is obtained by dividing 28 inches (arm's length) by the derived reference pixel size (1/96 inch). </li></ul></div></div>
 
-<div class="note" role="note" id="issue-container-generatedID-176"><div role="heading" class="note-title marker" id="h-note-167" aria-level="6"><span>Note 3</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-177"><div role="heading" class="note-title marker" id="h-note-168" aria-level="6"><span>Note 3</span></div><div class="">
 Most software and devices are usable at more than one viewing distance. However, only viewing distances that are plausible for the product can be considered an appropriate approximation for the reference pixel. For example, in software designed for use with a touchscreen, a visual-angle pixel longer than 0.11 inch (0.28 mm) would not be plausible, because this would signify a viewing distance of more than arm’s length. </div></div>
 
-<div class="note" role="note" id="issue-container-generatedID-177"><div role="heading" class="note-title marker" id="h-note-168" aria-level="6"><span>Note 4</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-178"><div role="heading" class="note-title marker" id="h-note-169" aria-level="6"><span>Note 4</span></div><div class="">
 People with low vision often use devices at less than the standard viewing distance. However, basing the density-independent pixel on a typical viewing distance provides a balance of benefits for users with disabilities. If a longer viewing distance were chosen as the basis for the density-independent pixel, the viewport would be measured with a smaller number of larger pixels, causing Success Criterion 1.4.10 Reflow to be less stringent. If a shorter viewing distance were chosen, user interface components would be measured with a larger number of smaller pixels, causing some success criteria, such as 2.5.8 Target Size, to be less stringent. </div></div>
 
 </section></section><section id="dfn-down-event"><div class="header-wrapper"><h4 id="x7-3-10-dfn-down-event">down-event</h4><a class="self-link" href="#dfn-down-event" aria-label="Permalink for Section down-event"></a></div><blockquote class="wcag-quote">  <p>platform event that occurs  when the trigger stimulus of a pointer is depressed</p>   <p>The down-event may have different names on different platforms, such as "touchstart" or "mousedown".</p>  </blockquote>
 <section id="applying-down-event-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-10-1-applying-down-event-to-non-web-documents-and-software">Applying “down-event” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-down-event-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “down-event” to Non-Web Documents and Software"></a></div>
 <p>This applies directly as written and as described in the WCAG 2 glossary.
 &nbsp;</p>
-<div class="note" role="note" id="issue-container-generatedID-178"><div role="heading" class="note-title marker" id="h-note-169" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-179"><div role="heading" class="note-title marker" id="h-note-170" aria-level="6"><span>Note</span></div><div class="">
     
 <p>The down-event may have different names on different platforms. For example <ins><strong>["PointerPressed” or “mousedown”]</strong></ins>.</p></div></div><p></p>
 </section></section><section id="dfn-general-flash-and-red-flash-thresholds"><div class="header-wrapper"><h4 id="x7-3-11-dfn-general-flash-and-red-flash-thresholds">general flash and red flash thresholds</h4><a class="self-link" href="#dfn-general-flash-and-red-flash-thresholds" aria-label="Permalink for Section general flash and red flash thresholds"></a></div><blockquote class="wcag-quote">  <p>a <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-flashes" id="ref-for-dfn-flashes-4" title="a pair of opposing changes in relative luminance that can cause seizures in some people if it is large enough and in the right frequency range">flash</a> or rapidly changing image sequence is below the threshold (i.e., content <strong>passes</strong>) if any of the following are true:    </p>   <ol> <li>there are no more than three <strong>general flashes</strong> and / or no more than three <strong>red flashes</strong> within any one-second period; or       </li> <li>the combined area of flashes occurring concurrently occupies no more than a total          of .006 steradians within any 10 degree visual field on the screen (25% of any 10          degree visual field on the screen) at typical viewing distance       </li> </ol>   <p>where:</p>   <ul> <li>A <strong>general flash</strong> is defined as a pair of opposing changes in <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-relative-luminance" id="ref-for-dfn-relative-luminance-4" title="the relative brightness of any point in a colorspace, normalized to 0 for darkest black and 1 for lightest white">relative luminance</a> of 10% or more of the maximum relative luminance (1.0) where the relative luminance of          the darker image is below 0.80; and where "a pair of opposing changes" is an increase          followed by a decrease, or a decrease followed by an increase, and       </li> <li>A <strong>red flash</strong> is defined as any pair of opposing transitions involving a saturated red       </li> </ul>   <p><em>Exception:</em> Flashing that is a fine, balanced, pattern such as white noise or an alternating       checkerboard pattern with "squares" smaller than 0.1 degree (of visual field at typical       viewing distance) on a side does not violate the thresholds.    </p>   <div class="note" id="wcag-noteissue-container-generatedID--101" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--101" role="heading"><span>Note 1</span></div><p class="">For general software or Web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field for standard screen sizes and viewing distances (e.g., 15-17 inch screen at 22-26 inches). This resolution of 75 - 85 ppi is known to be lower, and thus more conservative than the nominal CSS pixel resolution of 96 ppi in CSS specifications. Higher resolutions displays showing the same rendering of the content yield smaller and safer images so it is lower resolutions that are used to define the thresholds.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--102" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--102" role="heading"><span>Note 2</span></div><p class="">A transition is the change in relative luminance (or relative luminance/color for       red flashing) between adjacent peaks and valleys in a plot of relative luminance (or       relative luminance/color for red flashing) measurement against time. A flash consists       of two opposing transitions.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--103" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--103" role="heading"><span>Note 3</span></div><p class="">The new working definition in the field for <strong>"pair of opposing transitions involving a saturated red"</strong> (from WCAG 2.2) is a pair of opposing transitions where, one transition is either to or from a state with a value R/(R + G + B) that is greater than or equal to 0.8, and the difference between states is more than 0.2 (unitless) in the CIE 1976 UCS chromaticity diagram. [<cite><a class="bibref" data-link-type="biblio" href="https://www.w3.org/TR/wcag22/#bib-iso_9241-391" title="Ergonomics of human-system interaction—Part 391: Requirements, analysis and compliance test methods for the reduction of photosensitive seizures">ISO_9241-391</a></cite>] </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--104" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--104" role="heading"><span>Note 4</span></div><p class="">Tools are available that will carry out analysis from video screen capture. However,       no tool is necessary to evaluate for this condition if flashing is less than or equal       to 3 flashes in any one second. Content automatically passes (see #1 and #2 above).    </p></div>  </blockquote>
 <section id="applying-general-flash-and-red-flash-thresholds-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-11-1-applying-general-flash-and-red-flash-thresholds-to-non-web-documents-and-software">Applying “general flash and red flash thresholds” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-general-flash-and-red-flash-thresholds-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “general flash and red flash thresholds” to Non-Web Documents and Software"></a></div>
 <p>This applies directly as written and as described in the WCAG 2 glossary.</p>
-<div class="note" role="note" id="issue-container-generatedID-179"><div role="heading" class="note-title marker" id="h-note-170" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-180"><div role="heading" class="note-title marker" id="h-note-171" aria-level="6"><span>Note</span></div><div class="">
 
 <p>Because this deals with relative luminance and not luminance, it can only be applied to information on a display, not to hardware sources of light.</p></div></div><p></p>
 </section></section><section id="dfn-input-error"><div class="header-wrapper"><h4 id="x7-3-12-dfn-input-error">input error</h4><a class="self-link" href="#dfn-input-error" aria-label="Permalink for Section input error"></a></div><blockquote class="wcag-quote">  <p>information provided by the user that is not accepted</p>   <div class="note" id="wcag-noteissue-container-generatedID--109" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--109" role="heading"><span>Note</span></div><div class=""> <p>This includes:</p> <ol> <li>Information that is required by the <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-web-page-s" id="ref-for-dfn-web-page-s-18" title="a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent">Web page</a> but omitted by the user       </li> <li>Information that is provided by the user but that falls outside the required data          format or values       </li> </ol> </div></div>  </blockquote>
@@ -1772,7 +1774,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>input error</dt><dd>
 
 <p>information provided by the user that is not accepted</p>
-<div class="note" role="note" id="issue-container-generatedID-180"><div role="heading" class="note-title marker" id="h-note-171" aria-level="6"><span>Note</span></div><div class="">This includes:
+<div class="note" role="note" id="issue-container-generatedID-181"><div role="heading" class="note-title marker" id="h-note-172" aria-level="6"><span>Note</span></div><div class="">This includes:
 
 <ol>
 <li><p>Information that is required by the <ins><strong>[<a href="#document">non-web document</a> or <a href="#software">software</a>]</strong></ins> but omitted by the user</p>
@@ -1785,16 +1787,16 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 </section></section><section id="dfn-keyboard-interface"><div class="header-wrapper"><h4 id="x7-3-13-dfn-keyboard-interface">keyboard interface</h4><a class="self-link" href="#dfn-keyboard-interface" aria-label="Permalink for Section keyboard interface"></a></div><blockquote class="wcag-quote">  <p>interface used by software to obtain keystroke input</p>   <div class="note" id="wcag-noteissue-container-generatedID--110" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--110" role="heading"><span>Note 1</span></div><div class=""> <p>A keyboard interface allows users to provide keystroke input to programs even if the         native technology does not contain a keyboard.</p> <aside class="example" id="example-13"><div class="marker">Example</div><p><span>Example: </span>A touchscreen PDA has a keyboard interface built into its operating system as well         as a connector for external keyboards. Applications on the PDA can use the interface         to obtain keyboard input either from an external keyboard or from other applications         that provide simulated keyboard output, such as handwriting interpreters or speech-to-text         applications with "keyboard emulation" functionality.</p></aside> </div></div>   <div class="note" id="wcag-noteissue-container-generatedID--111" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--111" role="heading"><span>Note 2</span></div><p class="">Operation of the application (or parts of the application) through a keyboard-operated       mouse emulator, such as MouseKeys, does not qualify as operation through a keyboard       interface because operation of the program is through its pointing device interface,       not through its keyboard interface.    </p></div>  </blockquote>
 <section id="applying-keyboard-interface-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-13-1-applying-keyboard-interface-to-non-web-documents-and-software">Applying “keyboard interface” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-keyboard-interface-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “keyboard interface” to Non-Web Documents and Software"></a></div>
 <p>This applies directly as written and as described in the WCAG 2 glossary.</p>
-<div class="note" role="note" id="issue-container-generatedID-181"><div role="heading" class="note-title marker" id="h-note-172" aria-level="6"><span>Note 1</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-182"><div role="heading" class="note-title marker" id="h-note-173" aria-level="6"><span>Note 1</span></div><div class="">
 
 <p>Keyboard interface does not refer to a physical device but to the interface between the software and any keyboard or keyboard substitute (i.e., an interface where the software accepts text or other keystroke input). Underlying <a href="#platform-software">platform software</a> may provide device independent input services to applications that enable operation via such a keyboard interface. <a href="#software">Software</a> that supports operation via such platform device independent services would be operable via a keyboard interface and would satisfy the success criterion.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-182"><div role="heading" class="note-title marker" id="h-note-173" aria-level="6"><span>Note 2</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-183"><div role="heading" class="note-title marker" id="h-note-174" aria-level="6"><span>Note 2</span></div><div class="">
 
 <p>This success criterion does not imply that software always needs to directly support a keyboard or “keyboard interface”. Nor does it imply that software always needs to provide a <a href="#virtual-keyboard">virtual keyboard</a>.</p></div></div><p></p>
 </section></section><section id="dfn-keyboard-shortcuts"><div class="header-wrapper"><h4 id="x7-3-14-dfn-keyboard-shortcuts">keyboard shortcut</h4><a class="self-link" href="#dfn-keyboard-shortcuts" aria-label="Permalink for Section keyboard shortcut"></a></div><blockquote class="wcag-quote">  <p>alternative means of triggering an action by the pressing of one or more keys</p>  </blockquote>
 <section id="applying-keyboard-shortcut-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-14-1-applying-keyboard-shortcut-to-non-web-documents-and-software">Applying “keyboard shortcut” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-keyboard-shortcut-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “keyboard shortcut” to Non-Web Documents and Software"></a></div>
 <p>This applies directly as written and as described in the WCAG 2 glossary.</p>
-<div class="note" role="note" id="issue-container-generatedID-183"><div role="heading" class="note-title marker" id="h-note-174" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-184"><div role="heading" class="note-title marker" id="h-note-175" aria-level="6"><span>Note</span></div><div class="">
 
 <p>A key command issued by a long press of a key (2 seconds or more) and other accessibility features provided by the platform are not considered a keyboard shortcut. Such commands often occur when there are limited keys, or no modifier keys, present on a device.</p></div></div><p></p>
 </section></section><section id="dfn-labels"><div class="header-wrapper"><h4 id="x7-3-15-dfn-labels">label</h4><a class="self-link" href="#dfn-labels" aria-label="Permalink for Section label"></a></div><blockquote class="wcag-quote">  <p><a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-text" id="ref-for-dfn-text-10" title="sequence of characters that can be programmatically determined, where the sequence is expressing something in human language">text</a> or other component with a <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-text-alternative" id="ref-for-dfn-text-alternative-3" title="Text that is programmatically associated with non-text content or referred to from text that is programmatically associated with non-text content. Programmatically associated text is text whose location can be programmatically determined from the non-text content.">text alternative</a> that is presented to a user to identify a component within Web <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-content" id="ref-for-dfn-content-3" title="information and sensory experience to be communicated to the user by means of a user agent, including code or markup that defines the content's structure, presentation, and interactions">content</a></p>   <div class="note" id="wcag-noteissue-container-generatedID--112" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--112" role="heading"><span>Note 1</span></div><p class="">A label is presented to all users whereas the <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-name" id="ref-for-dfn-name-4" title="text by which software can identify a component within Web content to the user">name</a> may be hidden and only exposed by assistive technology. In many (but not all) cases       the name and the label are the same.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--113" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--113" role="heading"><span>Note 2</span></div><p class="">The term label is not limited to the label element in HTML.</p></div>  </blockquote>
@@ -1804,10 +1806,10 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>label</dt><dd>
 
 <p><a href="https://www.w3.org/TR/WCAG22/#dfn-text">text</a> or other component with a <a href="https://www.w3.org/TR/WCAG22/#dfn-text-alternative">text alternative</a> that is presented to a user to identify a component within <ins><strong>[<a href="#content-on-and-off-the-web">content</a>]</strong></ins></p>
-<div class="note" role="note" id="issue-container-generatedID-184"><div role="heading" class="note-title marker" id="h-note-175" aria-level="6"><span>Note 1</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-185"><div role="heading" class="note-title marker" id="h-note-176" aria-level="6"><span>Note 1</span></div><div class="">
 
 <p>A label is presented to all users whereas the <a href="#dfn-name">name</a> may be hidden and only exposed by assistive technology <ins><strong>[or by accessibility features of software]</strong></ins>. In many (but not all) cases the name and the label are the same.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-185"><div role="heading" class="note-title marker" id="h-note-176" aria-level="6"><span>Note 2</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-186"><div role="heading" class="note-title marker" id="h-note-177" aria-level="6"><span>Note 2</span></div><div class="">
 
 <p>The term label is not limited to the label element in HTML.</p></div></div></dd></dl><p></p>
 </section></section><section id="dfn-name"><div class="header-wrapper"><h4 id="x7-3-16-dfn-name">name</h4><a class="self-link" href="#dfn-name" aria-label="Permalink for Section name"></a></div><blockquote class="wcag-quote">  <p>text by which software can identify a component within Web content to the user</p>   <div class="note" id="wcag-noteissue-container-generatedID--125" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--125" role="heading"><span>Note 1</span></div><p class="">The name may be hidden and only exposed by assistive technology, whereas a <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-labels" id="ref-for-dfn-labels-4" title="text or other component with a text alternative that is presented to a user to identify a component within Web content">label</a> is presented to all users. In many (but not all) cases, the label and the name are       the same.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--126" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--126" role="heading"><span>Note 2</span></div><p class="">This is unrelated to the name attribute in HTML.</p></div>  </blockquote>
@@ -1817,10 +1819,10 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>name</dt><dd>
 
 <p>text by which software can identify a component within <ins><strong>[<a href="#content-on-and-off-the-web">content</a>]</strong></ins> to the user</p>
-<div class="note" role="note" id="issue-container-generatedID-186"><div role="heading" class="note-title marker" id="h-note-177" aria-level="6"><span>Note 1</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-187"><div role="heading" class="note-title marker" id="h-note-178" aria-level="6"><span>Note 1</span></div><div class="">
 
 <p>The name may be hidden and only exposed by assistive technology <ins><strong>[or by accessibility features of software]</strong></ins>, whereas a <a href="#dfn-labels">label</a> is presented to all users. In many (but not all) cases, the label and the name are the same.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-187"><div role="heading" class="note-title marker" id="h-note-178" aria-level="6"><span>Note 2</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-188"><div role="heading" class="note-title marker" id="h-note-179" aria-level="6"><span>Note 2</span></div><div class="">
 
 <p>This is unrelated to the name attribute in HTML.</p></div></div><p></p>
 <div class="example">
@@ -1830,7 +1832,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 </section></section><section id="dfn-perimeter"><div class="header-wrapper"><h4 id="x7-3-17-dfn-perimeter">perimeter</h4><a class="self-link" href="#dfn-perimeter" aria-label="Permalink for Section perimeter"></a></div><blockquote class="wcag-quote">     <p>continuous line forming the boundary of a shape not including shared pixels, or the <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-bounding-boxes" id="ref-for-dfn-bounding-boxes-2" title="[New]">minimum bounding box</a>, whichever is shortest.</p>   <aside class="example" id="example-16"><div class="marker">Example</div><p><span>Example: </span>The perimeter calculation for a 2 CSS pixel perimeter around a rectangle is 4<em>h</em>+4<em>w</em>, where <em>h</em> is the height and <em>w</em> is the width. For a 2 CSS pixel perimeter around a circle it is 4𝜋<em>r</em>.</p></aside>  </blockquote>
 <section id="applying-perimeter-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-17-1-applying-perimeter-to-non-web-documents-and-software">Applying “perimeter” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-perimeter-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “perimeter” to Non-Web Documents and Software"></a></div>
 <p>This applies directly as written and as described in the WCAG 2 glossary.</p>
-<div class="note" role="note" id="issue-container-generatedID-188"><div role="heading" class="note-title marker" id="h-note-179" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-189"><div role="heading" class="note-title marker" id="h-note-180" aria-level="6"><span>Note</span></div><div class="">
 
 <p>In technologies where CSS is not used, the definition of 'CSS pixel' applies as described in <a href="#applying-css-pixel-to-non-web-documents-and-software">Applying “CSS pixel” to Non-Web Documents and Software</a>.</p></div></div>
 <p></p>
@@ -1847,7 +1849,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <div class="example">
 
 <p><span>Example 2: </span>Determined from technology-specific data structures in a non-markup language and exposed to assistive technology <ins><strong>[and accessibility features of software]</strong></ins> via an accessibility API that is supported by commonly available assistive technology <ins><strong>[and accessibility features of software]</strong></ins>.</p></div><p></p>
-</dd></dl><div class="note" role="note" id="issue-container-generatedID-189"><div role="heading" class="note-title marker" id="h-note-180" aria-level="6"><span>Note</span></div><div class="">
+</dd></dl><div class="note" role="note" id="issue-container-generatedID-190"><div role="heading" class="note-title marker" id="h-note-181" aria-level="6"><span>Note</span></div><div class="">
 
 <p>Software typically enables content to be programmatically determined through the use of <a href="#accessibility-services-of-platform-software">accessibility services of platform software</a>. Non-web documents typically enable <a href="#content-on-and-off-the-web">content</a> to be programmatically determined through the use of accessibility services of the user agent.</p></div></div><p></p>
 </section></section><section id="dfn-programmatically-set"><div class="header-wrapper"><h4 id="x7-3-19-dfn-programmatically-set">programmatically set</h4><a class="self-link" href="#dfn-programmatically-set" aria-label="Permalink for Section programmatically set"></a></div><blockquote class="wcag-quote">  <p>set by software using methods that are supported by user agents, including assistive       technologies    </p>  </blockquote>
@@ -1857,7 +1859,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>programmatically set</dt><dd>
 
 <p>set by software using methods that are supported by <ins><strong>[<a href="#dfn-assistive-technologies">assistive technologies</a> and accessibility features of software]</strong></ins></p>
-</dd></dl><div class="note" role="note" id="issue-container-generatedID-190"><div role="heading" class="note-title marker" id="h-note-181" aria-level="6"><span>Note</span></div><div class="">
+</dd></dl><div class="note" role="note" id="issue-container-generatedID-191"><div role="heading" class="note-title marker" id="h-note-182" aria-level="6"><span>Note</span></div><div class="">
 
 <p>Software typically enables <a href="#content-on-and-off-the-web">content</a> to be programmatically determined through the use of <a href="#accessibility-services-of-platform-software">accessibility services of platform software</a>. Non-web documents typically enable content to be programmatically determined through the use of accessibility services of the user agent.</p></div></div><p></p>
 </section></section><section id="dfn-relative-luminance"><div class="header-wrapper"><h4 id="x7-3-20-dfn-relative-luminance">relative luminance</h4><a class="self-link" href="#dfn-relative-luminance" aria-label="Permalink for Section relative luminance"></a></div><blockquote class="wcag-quote">  <p>the relative brightness of any point in a colorspace, normalized to 0 for darkest       black and 1 for lightest white    </p>   <div class="note" id="wcag-noteissue-container-generatedID--136" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--136" role="heading"><span>Note 1</span></div><div class=""> <p>For the sRGB colorspace, the relative luminance of a color is defined as L = 0.2126       * <strong>R</strong> + 0.7152 * <strong>G</strong> + 0.0722 * <strong>B</strong> where <strong>R</strong>, <strong>G</strong> and <strong>B</strong> are defined as:    </p> <ul> <li>if RsRGB &lt;= 0.04045 then <strong>R</strong> = RsRGB/12.92 else <strong>R</strong> = ((RsRGB+0.055)/1.055) ^ 2.4       </li> <li>if GsRGB &lt;= 0.04045 then <strong>G</strong> = GsRGB/12.92 else <strong>G</strong> = ((GsRGB+0.055)/1.055) ^ 2.4       </li> <li>if BsRGB &lt;= 0.04045 then <strong>B</strong> = BsRGB/12.92 else <strong>B</strong> = ((BsRGB+0.055)/1.055) ^ 2.4       </li> </ul> <p>and RsRGB, GsRGB, and BsRGB are defined as:</p> <ul> <li>RsRGB = R8bit/255</li> <li>GsRGB = G8bit/255</li> <li>BsRGB = B8bit/255</li> </ul> <p>The "^" character is the exponentiation operator. (Formula taken from        [<cite><a class="bibref" data-link-type="biblio" href="https://www.w3.org/TR/wcag22/#bib-srgb" title="Multimedia systems and equipment - Colour measurement and management - Part 2-1: Colour management - Default RGB colour space - sRGB">SRGB</a></cite>].)    </p> </div></div>   <div class="note" id="wcag-noteissue-container-generatedID--137" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--137" role="heading"><span>Note 2</span></div><p class="">Before May 2021 the value of 0.04045 in the definition was different (0.03928). It was taken from an older version of the specification and has been updated. It has no practical effect on the calculations in the context of these guidelines.</p></div>   <div class="note" id="wcag-noteissue-container-generatedID--138" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--138" role="heading"><span>Note 3</span></div><p class="">Almost all systems used today to view Web content assume sRGB encoding. Unless it       is known that another color space will be used to process and display the content,       authors should evaluate using sRGB colorspace. If using other color spaces, see <a href="https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum">Understanding Success Criterion 1.4.3</a>.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--139" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--139" role="heading"><span>Note 4</span></div><p class="">If dithering occurs after delivery, then the source color value is used. For colors       that are dithered at the source, the average values of the colors that are dithered       should be used (average R, average G, and average B).    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--140" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--140" role="heading"><span>Note 5</span></div><p class="">Tools are available that automatically do the calculations when testing contrast and       flash.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--141" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--141" role="heading"><span>Note 6</span></div><p class="">A <a href="https://www.w3.org/TR/wcag22/relative-luminance.html">separate page giving the relative luminance definition using MathML</a> to display the formulas is available.    </p></div>  </blockquote>
@@ -1867,7 +1869,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>relative luminance</dt><dd>
 
 <p>the relative brightness of any point in a colorspace, normalized to 0 for darkest black and 1 for lightest white</p>
-<div class="note" role="note" id="issue-container-generatedID-191"><div role="heading" class="note-title marker" id="h-note-182" aria-level="6"><span>Note 1</span></div><div class="">For the sRGB colorspace, the relative luminance of a color is defined as L = 0.2126 \* **R** + 0.7152 \* **G** + 0.0722 \* **B** where **R**, **G** and **B** are defined as:
+<div class="note" role="note" id="issue-container-generatedID-192"><div role="heading" class="note-title marker" id="h-note-183" aria-level="6"><span>Note 1</span></div><div class="">For the sRGB colorspace, the relative luminance of a color is defined as L = 0.2126 \* **R** + 0.7152 \* **G** + 0.0722 \* **B** where **R**, **G** and **B** are defined as:
 
 <ul>
 <li>if RsRGB &lt;= 0.03928 then <strong>R</strong> = RsRGB/12.92 else <strong>R</strong> = ((RsRGB+0.055)/1.055) ^ 2.4</li>
@@ -1881,21 +1883,21 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <li>BsRGB = B8bit/255</li>
 </ul>
 <p>The “^” character is the exponentiation operator. (Formula taken from <a href="http://www.w3.org/TR/WCAG22/#bib-srgb">[sRGB]</a>).</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-192"><div role="heading" class="note-title marker" id="h-note-183" aria-level="6"><span>Note 2</span></div><div class="">Before May 2021 the value of 0.04045 in the definition was different (0.03928). It was taken from an older version of the specification and has been updated. It has no practical effect on the calculations in the context of these guidelines.</div></div>
-<div class="note" role="note" id="issue-container-generatedID-193"><div role="heading" class="note-title marker" id="h-note-184" aria-level="6"><span>Note 3</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-193"><div role="heading" class="note-title marker" id="h-note-184" aria-level="6"><span>Note 2</span></div><div class="">Before May 2021 the value of 0.04045 in the definition was different (0.03928). It was taken from an older version of the specification and has been updated. It has no practical effect on the calculations in the context of these guidelines.</div></div>
+<div class="note" role="note" id="issue-container-generatedID-194"><div role="heading" class="note-title marker" id="h-note-185" aria-level="6"><span>Note 3</span></div><div class="">
 
 <p>Almost all systems used today to view <ins><strong>[<a href="#content-on-and-off-the-web">content</a>]</strong></ins> assume sRGB encoding. Unless it is known that another color space will be used to process and display the content, authors should evaluate using sRGB colorspace. If using other color spaces, see <a href="http://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum">Understanding Success Criterion 1.4.3</a>.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-194"><div role="heading" class="note-title marker" id="h-note-185" aria-level="6"><span>Note 4</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-195"><div role="heading" class="note-title marker" id="h-note-186" aria-level="6"><span>Note 4</span></div><div class="">
 
 <p>If dithering occurs after delivery, then the source color value is used. For colors that are dithered at the source, the average values of the colors that are dithered should be used (average R, average G, and average B).</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-195"><div role="heading" class="note-title marker" id="h-note-186" aria-level="6"><span>Note 5</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-196"><div role="heading" class="note-title marker" id="h-note-187" aria-level="6"><span>Note 5</span></div><div class="">
 
 <p>Tools are available that automatically do the calculations when testing contrast and flash.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-196"><div role="heading" class="note-title marker" id="h-note-187" aria-level="6"><span>Note 6</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-197"><div role="heading" class="note-title marker" id="h-note-188" aria-level="6"><span>Note 6</span></div><div class="">
     
 <p>A <a href="http://www.w3.org/TR/WCAG22/relative-luminance.html">MathML version of the relative luminance definition</a> is available.</p></div></div>
 </dd></dl><p></p>
-<div class="note" role="note" id="issue-container-generatedID-197"><div role="heading" class="note-title marker" id="h-note-188" aria-level="6"><span>Note 1</span></div><div class="">Because relative luminance is defined such that it cannot directly apply to hardware, please note the text in the introduction which reads: “This document does not comment on hardware aspects of products, because the basic constructs on which WCAG 2 is built do not apply to these.”</div></div>
+<div class="note" role="note" id="issue-container-generatedID-198"><div role="heading" class="note-title marker" id="h-note-189" aria-level="6"><span>Note 1</span></div><div class="">Because relative luminance is defined such that it cannot directly apply to hardware, please note the text in the introduction which reads: “This document does not comment on hardware aspects of products, because the basic constructs on which WCAG 2 is built do not apply to these.”</div></div>
 
 </section></section><section id="dfn-role"><div class="header-wrapper"><h4 id="x7-3-21-dfn-role">role</h4><a class="self-link" href="#dfn-role" aria-label="Permalink for Section role"></a></div><blockquote class="wcag-quote">  <p>text or number by which software can identify the function of a component within Web       content    </p>   <aside class="example" id="example-26"><div class="marker">Example</div><p><span>Example: </span>A number that indicates whether an image functions as a hyperlink, command button,       or check box.    </p></aside>  </blockquote>
 <section id="applying-role-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-21-1-applying-role-to-non-web-documents-and-software">Applying “role” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-role-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “role” to Non-Web Documents and Software"></a></div>
@@ -1908,7 +1910,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 
 <p><span>Example: </span>A number that indicates whether an image functions as a hyperlink, command button, or check box.</p></div>
 </dd></dl><p></p>
-<div class="note" role="note" id="issue-container-generatedID-198"><div role="heading" class="note-title marker" id="h-note-189" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-199"><div role="heading" class="note-title marker" id="h-note-190" aria-level="6"><span>Note</span></div><div class="">
 
 <p>“AccessibleRole” (or the corresponding term used in different APIs) of the Accessibility API of the platform is an example of such a role.</p></div></div><p></p>
 </section></section><section id="dfn-same-functionality"><div class="header-wrapper"><h4 id="x7-3-22-dfn-same-functionality">same functionality</h4><a class="self-link" href="#dfn-same-functionality" aria-label="Permalink for Section same functionality"></a></div><blockquote class="wcag-quote">  <p>same result when used</p>   <aside class="example" id="example-27"><div class="marker">Example</div><p><span>Example: </span>A submit "search" button on one Web page and a "find" button on another Web page may       both have a field to enter a term and list topics in the Web site related to the term       submitted. In this case, they would have the same functionality but would not be labeled       consistently.    </p></aside>  </blockquote>
@@ -1931,13 +1933,13 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>satisfies a success criterion</dt><dd>
     
 <p>the success criterion does not evaluate to 'false' when applied to the <ins><strong>[<a href="#document">non-web document</a> or <a href="#software">software</a>]</strong></ins></p>
-<div class="note" role="note" id="issue-container-generatedID-199"><div role="heading" class="note-title marker" id="h-note-190" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-200"><div role="heading" class="note-title marker" id="h-note-191" aria-level="6"><span>Note</span></div><div class="">
     
 <p>Though WCAG2ICT and WCAG 2 don't use this exact phrase, in this document there are variations of the phrase that use this definition. See "success criteria is satisfied" in <a href="#comments-on-conformance">Section 6 Comments on Conformance</a> and "satisfy any success criterion" in the notes for the definition of <a href="#set-of-software-programs">set of software programs</a>.</p></div></div></dd></dl><p></p>
 </section></section><section id="dfn-set-of-web-pages"><div class="header-wrapper"><h4 id="x7-3-24-dfn-set-of-web-pages">set of web pages</h4><a class="self-link" href="#dfn-set-of-web-pages" aria-label="Permalink for Section set of web pages"></a></div><blockquote class="wcag-quote">  <p>collection of <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-web-page-s" id="ref-for-dfn-web-page-s-19" title="a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent">web pages</a> that share a common purpose and that are created by the same author, group or organization    </p>   <aside class="example" id="example-28"><div class="marker">Example</div><p><span>Example: </span>Examples include:</p> <ul> <li>a publication which is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages.</li> <li>an e-commerce website shows products in a set of Web pages that all share the same navigation and identification. However, when progressing to the checkout process, the template changes; the navigation and other elements are removed, so the pages in that process are functionally and visually different. The checkout pages are not part of the set of product pages.</li> <li>a blog on a sub-domain (e.g. blog.example.com) which has a different navigation and is authored by a distinct set of people from the pages on the primary domain (example.com).</li> </ul></aside>   <div class="note" id="wcag-noteissue-container-generatedID--144" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--144" role="heading"><span>Note</span></div><p class="">Different language versions would be considered different sets of Web pages.</p></div>  </blockquote>
 <section id="applying-set-of-web-pages-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-24-1-applying-set-of-web-pages-to-non-web-documents-and-software">Applying “set of Web pages” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-set-of-web-pages-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “set of Web pages” to Non-Web Documents and Software"></a></div>
 <p>See the guidance on <a href="#set-of-documents">set of documents</a> and <a href="#set-of-software-programs">set of software programs</a> in the <a href="#key-terms">Key Terms</a> section.</p>
-<div class="note" role="note" id="issue-container-generatedID-200"><div role="heading" class="note-title marker" id="h-note-191" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-201"><div role="heading" class="note-title marker" id="h-note-192" aria-level="6"><span>Note</span></div><div class="">
 
 <p>For success criteria that use the term “set of web pages”, either explicitly or implicitly (<a href="#bypass-blocks">2.4.1</a>, <a href="#multiple-ways">2.4.5</a>, <a href="#consistent-navigation">3.2.3</a>, and <a href="#consistent-identification">3.2.4</a>), simply substitute "set of non-web documents" and "set of software programs" when applying this to non-web technologies.</p></div></div><p></p>
 </section></section><section id="dfn-structure"><div class="header-wrapper"><h4 id="x7-3-25-dfn-structure">structure</h4><a class="self-link" href="#dfn-structure" aria-label="Permalink for Section structure"></a></div><blockquote class="wcag-quote">  <ol> <li>The way the parts of a <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-web-page-s" id="ref-for-dfn-web-page-s-20" title="a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent">Web page</a> are organized in relation to each other; and       </li> <li>The way a collection of <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-web-page-s" id="ref-for-dfn-web-page-s-21" title="a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent">Web pages</a> is organized       </li> </ol>  </blockquote>
@@ -1952,7 +1954,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <li><p>The way a <ins><strong>[<a href="#set-of-documents">set of documents</a> or <a href="#set-of-software-programs">set of software programs</a>]</strong></ins> is organized</p>
 </li>
 </ol>
-</dd></dl><div class="note" role="note" id="issue-container-generatedID-201"><div role="heading" class="note-title marker" id="h-note-192" aria-level="6"><span>Note</span></div><div class="">
+</dd></dl><div class="note" role="note" id="issue-container-generatedID-202"><div role="heading" class="note-title marker" id="h-note-193" aria-level="6"><span>Note</span></div><div class="">
 
 <p>See the guidance on <a href="#set-of-documents">sets of documents</a> and <a href="#set-of-software-programs">sets of software programs</a> in the Key Terms section.</p></div></div><p></p>
 </section></section><section id="dfn-style-properties"><div class="header-wrapper"><h4 id="x7-3-26-dfn-style-properties">style property</h4><a class="self-link" href="#dfn-style-properties" aria-label="Permalink for Section style property"></a></div><blockquote class="wcag-quote">  <p>property whose value determines the presentation (e.g. font, color, size, location, padding, volume, synthesized speech prosody) of  content elements as they are rendered (e.g. onscreen, via loudspeaker, via braille display) by user agents</p>   <p>Style properties can have several origins:</p>   <ul> <li>User agent default styles: The default style property values applied in the absence of any author or user styles. Some web content technologies specify a default rendering, others do not;</li> <li>Author styles: Style property values that are set by the author as part of the content (e.g. in-line styles, author style sheets);</li> <li>User styles: Style property values that are set by the user (e.g. via user agent interface settings, user style sheets)</li> </ul>  </blockquote>
@@ -1975,7 +1977,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>target</dt><dd>
     
 <p>region of the display that will accept a pointer action, such as the interactive area of a user interface component</p>
-<div class="note" role="note" id="issue-container-generatedID-202"><div role="heading" class="note-title marker" id="h-note-193" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-203"><div role="heading" class="note-title marker" id="h-note-194" aria-level="6"><span>Note</span></div><div class="">
     
 <p>If two or more targets are overlapping, the overlapping area should not be included in the measurement of the target size, except when the overlapping targets perform the same action or open the same <ins><strong>[<a href="#document">non-web document</a> or <a href="#content-on-and-off-the-web">content</a> presented by <a href="#software">software</a>]</strong></ins>.</p></div></div></dd></dl><p></p>
 </section></section><section id="dfn-technologies"><div class="header-wrapper"><h4 id="x7-3-28-dfn-technologies">technology</h4><a class="self-link" href="#dfn-technologies" aria-label="Permalink for Section technology"></a></div><blockquote class="wcag-quote">  <p><a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-mechanism" id="ref-for-dfn-mechanism-16" title="process or technique for achieving a result">mechanism</a> for encoding instructions to be rendered, played or executed by <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-user-agents" id="ref-for-dfn-user-agents-11" title="any software that retrieves and presents Web content for users">user agents</a></p>   <div class="note" id="wcag-noteissue-container-generatedID--147" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--147" role="heading"><span>Note 1</span></div><p class="">As used in these guidelines "Web Technology" and the word "technology" (when used       alone) both refer to Web Content Technologies.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--148" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--148" role="heading"><span>Note 2</span></div><p class="">Web content technologies may include markup languages, data formats, or programming       languages that authors may use alone or in combination to create end-user experiences       that range from static Web pages to synchronized media presentations to dynamic Web       applications.    </p></div>   <aside class="example" id="example-33"><div class="marker">Example</div><p><span>Example: </span>Some common examples of Web content technologies include HTML, CSS, SVG, PNG, PDF,       Flash, and JavaScript.    </p></aside>  </blockquote>
@@ -1992,7 +1994,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <section id="applying-up-event-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-29-1-applying-up-event-to-non-web-documents-and-software">Applying “up-event” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-up-event-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “up-event” to Non-Web Documents and Software"></a></div>
 <p>This applies directly as written and as described in the WCAG 2 glossary.
 &nbsp;</p>
-<div class="note" role="note" id="issue-container-generatedID-203"><div role="heading" class="note-title marker" id="h-note-194" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-204"><div role="heading" class="note-title marker" id="h-note-195" aria-level="6"><span>Note</span></div><div class="">
     
 <p>The up-event may have different names on different platforms, such as <ins><strong>[“PointerReleased” or “mouseup”]</strong></ins>.</p></div></div><p></p>
 </section></section><section id="dfn-user-agents"><div class="header-wrapper"><h4 id="x7-3-30-dfn-user-agents">user agent</h4><a class="self-link" href="#dfn-user-agents" aria-label="Permalink for Section user agent"></a></div><blockquote class="wcag-quote">  <p>any software that retrieves and presents Web content for users</p>   <aside class="example" id="example-36"><div class="marker">Example</div><p><span>Example: </span>Web browsers, media players, plug-ins, and other programs — including <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-assistive-technologies" id="ref-for-dfn-assistive-technologies-8" title="hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents">assistive technologies</a> — that help in retrieving, rendering, and interacting with Web content.    </p></aside>  </blockquote>
@@ -2005,13 +2007,13 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>user interface component</dt><dd>
 
 <p>a part of the <a href="#content-on-and-off-the-web">content</a> that is perceived by users as a single control for a distinct function</p>
-<div class="note" role="note" id="issue-container-generatedID-204"><div role="heading" class="note-title marker" id="h-note-195" aria-level="6"><span>Note 1</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-205"><div role="heading" class="note-title marker" id="h-note-196" aria-level="6"><span>Note 1</span></div><div class="">
 
 <p>Multiple user interface components may be implemented as a single programmatic element. "Components" here is not tied to programming techniques, but rather to what the user perceives as separate controls.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-205"><div role="heading" class="note-title marker" id="h-note-196" aria-level="6"><span>Note 2</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-206"><div role="heading" class="note-title marker" id="h-note-197" aria-level="6"><span>Note 2</span></div><div class="">
 
 <p>User interface components include form elements and links as well as components generated by scripts.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-206"><div role="heading" class="note-title marker" id="h-note-197" aria-level="6"><span>Note 3</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-207"><div role="heading" class="note-title marker" id="h-note-198" aria-level="6"><span>Note 3</span></div><div class="">
 
 <p>What is meant by "component" or "user interface component" here is also sometimes called "user interface element".</p></div></div><p></p>
 <div class="example">
@@ -2025,17 +2027,17 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <dl><dt>viewport</dt><dd>
 
 <p>object in which the <ins><strong>[<a href="#software">software</a>]</strong></ins> presents <a href="#content-on-and-off-the-web">content</a></p>
-<div class="note" role="note" id="issue-container-generatedID-207"><div role="heading" class="note-title marker" id="h-note-198" aria-level="6"><span>Note 1</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-208"><div role="heading" class="note-title marker" id="h-note-199" aria-level="6"><span>Note 1</span></div><div class="">
 
 <p>The <ins><strong>[software]</strong></ins> presents content through one or more viewports. Viewports include windows, frames, loudspeakers, and virtual magnifying glasses. A viewport may contain another viewport (e.g., nested frames). Interface components created by the <ins><strong>[software]</strong></ins> such as prompts, menus, and alerts are not viewports.</p></div></div><p></p>
-<div class="note" role="note" id="issue-container-generatedID-208"><div role="heading" class="note-title marker" id="h-note-199" aria-level="6"><span>Note 2</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-209"><div role="heading" class="note-title marker" id="h-note-200" aria-level="6"><span>Note 2</span></div><div class="">
 
 <p>This definition is based on <a href="http://www.w3.org/TR/WAI-USERAGENT/glossary.html">User Agent Accessibility Guidelines 1.0 Glossary</a>.</p></div></div>
 </dd></dl><p></p>
 </section></section><section id="dfn-web-page-s"><div class="header-wrapper"><h4 id="x7-3-33-dfn-web-page-s">Web page</h4><a class="self-link" href="#dfn-web-page-s" aria-label="Permalink for Section Web page"></a></div><blockquote class="wcag-quote">  <p>a non-embedded resource obtained from a single URI using HTTP plus any other resources       that are used in the rendering or intended to be rendered together with it by a <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-user-agents" id="ref-for-dfn-user-agents-13" title="any software that retrieves and presents Web content for users">user agent</a></p>   <div class="note" id="wcag-noteissue-container-generatedID--157" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--157" role="heading"><span>Note 1</span></div><p class="">Although any "other resources" would be rendered together with the primary resource,       they would not necessarily be rendered simultaneously with each other.    </p></div>   <div class="note" id="wcag-noteissue-container-generatedID--158" role="note"><div aria-level="3" class="note-title marker" id="wcag-noteh-note--158" role="heading"><span>Note 2</span></div><p class="">For the purposes of conformance with these guidelines, a resource must be "non-embedded"       within the scope of conformance to be considered a Web page.    </p></div>   <aside class="example" id="example-39"><div class="marker">Example 1</div><p><span>Example 1: </span>A Web resource including all embedded images and media.</p></aside>   <aside class="example" id="example-40"><div class="marker">Example 2</div><p><span>Example 2: </span>A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program       lives entirely at http://example.com/mail, but includes an inbox, a contacts area       and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar       to display, but do not change the URI of the page as a whole.    </p></aside>   <aside class="example" id="example-41"><div class="marker">Example 3</div><p><span>Example 3: </span>A customizable portal site, where users can choose content to display from a set of       different content modules.    </p></aside>   <aside class="example" id="example-42"><div class="marker">Example 4</div><p><span>Example 4: </span>When you enter "http://shopping.example.com/" in your browser, you enter a movie-like       interactive shopping environment where you visually move around in a store dragging       products off of the shelves around you and into a visual shopping cart in front of       you. Clicking on a product causes it to be demonstrated with a specification sheet       floating alongside. This might be a single-page Web site or just one page within a       Web site.    </p></aside>  </blockquote>
 <section id="applying-web-page-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-33-1-applying-web-page-to-non-web-documents-and-software">Applying “Web Page” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-web-page-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “Web Page” to Non-Web Documents and Software"></a></div>
 <p>This applies directly as written and as described in the WCAG 2 glossary.</p>
-<div class="note" role="note" id="issue-container-generatedID-209"><div role="heading" class="note-title marker" id="h-note-200" aria-level="6"><span>Note</span></div><div class="">
+<div class="note" role="note" id="issue-container-generatedID-210"><div role="heading" class="note-title marker" id="h-note-201" aria-level="6"><span>Note</span></div><div class="">
 
 <p>For those success criteria that use the term “web page”, WCAG2ICT provides specific replacement term(s) for “Web page”.</p></div></div><p></p>
 </section></section></section></section>
@@ -2046,7 +2048,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <p>This Working Group Note does not introduce any new security considerations. Horizontal Review Groups are encouraged to provide further feedback during the Horizontal Review process.</p>
 </section>
 		<section class="appendix" id="success-criteria-problematic-for-closed-functionality"><div class="header-wrapper"><h2 id="a-success-criteria-problematic-for-closed-functionality">A. Success Criteria Problematic for Closed Functionality</h2><a class="self-link" href="#success-criteria-problematic-for-closed-functionality" aria-label="Permalink for Section A. Success Criteria Problematic for Closed Functionality"></a></div>
-<div class="note" id="issue-container-generatedID-210"><div role="heading" class="ednote-title marker" id="h-ednote-8" aria-level="3"><span>Editor's note</span></div><div class="">This section has been updated to include new WCAG 2.1 and 2.2 criteria that are problematic for Closed Functionality as well as remove obsolete criteria. The Task Force has also updated some of the existing content in this section to reflect new insights learned since the 2013 WCAG2ICT Note and to address public comments received on the previous draft.</div></div>
+<div class="note" id="issue-container-generatedID-211"><div role="heading" class="ednote-title marker" id="h-ednote-8" aria-level="3"><span>Editor's note</span></div><div class="">This section has been updated to include new WCAG 2.1 and 2.2 criteria that are problematic for Closed Functionality as well as remove obsolete criteria. The Task Force has also updated some of the existing content in this section to reflect new insights learned since the 2013 WCAG2ICT Note and to address public comments received on the previous draft.</div></div>
 
 <p>There are success criteria that can be problematic for developers of ICT with closed functionality.  Some criteria discuss making information available in text (which can be read by assistive technologies), making it “programmatically determinable” (rendered by a user agent and readable by assistive technologies), or doing something else to make content compatible with assistive technologies.  Where ICT with closed functionality doesn’t support use of assistive technology or the platform does not have an accessibility API, providing equivalent information and operation through another mechanism, such as functions built into the software that behave like assistive technology, would help meet the intent of these success criteria. See also the <a href="#comments-on-closed-functionality">Comments on Closed Functionality</a> section.</p>
 <p>Other success criteria would apply to systems with closed functionality either if they are partially closed or if they allow for the connection of some types of devices. As an example, Success Criterion 2.1.1 Keyboard would apply to systems that are closed to screen readers, but have a physical keyboard, a connector for standard keyboards, or allow the installation of alternate keyboards.  While these criteria, as written, are not always applicable to closed functionality, most of them can inform and aid development of built-in features needed to make products with closed functionality accessible. </p>
@@ -2063,25 +2065,25 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <li><a href="#contrast-minimum">1.4.3 Contrast (Minimum)</a> — There are cases where applying this success criterion to non-web software for products with closed functionality is problematic:
 <ul>
 <li>When the contrast of the content is determined by the hardware and not modifiable by the software author, it may not be possible to meet this success criterion.
-<div class="note" role="note" id="issue-container-generatedID-211"><div role="heading" class="note-title marker" id="h-note-201" aria-level="3"><span>Note 1</span></div><div class="">Contrast requirements for hardware are out of scope for WCAG2ICT (and this success criterion).</div></div></li>
+<div class="note" role="note" id="issue-container-generatedID-212"><div role="heading" class="note-title marker" id="h-note-202" aria-level="3"><span>Note 1</span></div><div class="">Contrast requirements for hardware are out of scope for WCAG2ICT (and this success criterion).</div></div></li>
 <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" role="note" id="issue-container-generatedID-212"><div role="heading" class="note-title marker" id="h-note-202" aria-level="3"><span>Note 2</span></div><div class="">Photographs (e.g., of a hardware display) 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></div></li>
+<div class="note" role="note" id="issue-container-generatedID-213"><div role="heading" class="note-title marker" id="h-note-203" aria-level="3"><span>Note 2</span></div><div class="">Photographs (e.g., of a hardware display) 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></div></li>
 </ul></li>
 <li><a href="#resize-text">1.4.4 Resize Text</a> — Non-web software on closed functionality products may offer more limited text rendering support than the support found in user agents for the Web. As a result, meeting Success Criterion 1.4.4 in a closed environment may place a much heavier burden on the content author.</li>
 <li><a href="#images-of-text">1.4.5 Images of Text</a> — To enable assistive technology to modify displayed text (e.g., adjusting contrast, increasing font size), machine-readable text is needed, as opposed to mere images of text. Not all ICT with closed functionality has the capability to support visual modification of displayed text or images of text, given there is no interoperability with assistive technology and/or lack of platform support.</li>
 <li><a href="#reflow">1.4.10 Reflow</a> — Some software on ICT with closed functionality does not support scrolling content, or zooming, or changing the viewport (examples include, but are not limited to, software for self-service transaction machines or kiosks).  Therefore, some other non-WCAG requirements would be needed for products with closed functionality to ensure that content is readable by persons with low vision without scrolling in two dimensions.
 
-<div class="note" role="note" id="issue-container-generatedID-213"><div role="heading" class="note-title marker" id="h-note-203" aria-level="3"><span>Note 3</span></div><div class="">Some ICT with closed functionality does not display large chunks of text and only has UI controls.  In such cases, two-dimensional scrolling to access the text and UI controls may be considered essential, thus meeting an exception, and the success criterion would be satisfied.</div></div></li>
+<div class="note" role="note" id="issue-container-generatedID-214"><div role="heading" class="note-title marker" id="h-note-204" aria-level="3"><span>Note 3</span></div><div class="">Some ICT with closed functionality does not display large chunks of text and only has UI controls.  In such cases, two-dimensional scrolling to access the text and UI controls may be considered essential, thus meeting an exception, and the success criterion would be satisfied.</div></div></li>
 <li><a href="#non-text-contrast">1.4.11 Non-text Contrast</a> — There are cases where applying this success criterion to non-web software on products with closed functionality is problematic:
 <ul>
 <li>When the contrast of the content is determined by the hardware and not modifiable by the software author, it may not be possible to meet this success criterion.
-<div class="note" role="note" id="issue-container-generatedID-214"><div role="heading" class="note-title marker" id="h-note-204" aria-level="3"><span>Note 4</span></div><div class="">Hardware requirements for contrast are out of scope for WCAG2ICT (and this success criterion).</div></div></li>
+<div class="note" role="note" id="issue-container-generatedID-215"><div role="heading" class="note-title marker" id="h-note-205" aria-level="3"><span>Note 4</span></div><div class="">Hardware requirements for contrast are out of scope for WCAG2ICT (and this success criterion).</div></div></li>
 <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" role="note" id="issue-container-generatedID-215"><div role="heading" class="note-title marker" id="h-note-205" aria-level="3"><span>Note 5</span></div><div class="">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></div></li>
+<div class="note" role="note" id="issue-container-generatedID-216"><div role="heading" class="note-title marker" id="h-note-206" aria-level="3"><span>Note 5</span></div><div class="">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></div></li>
 </ul></li>
 <li><a href="#text-spacing">1.4.12 Text Spacing</a> — In software with closed functionality the ability for users to modify line, paragraph, letter, or word spacing is rarely supported.  Regardless, the success criterion applies as written and 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> — Assumes operation via a keyboard interface which also allows for alternative input devices. It may not be possible to satisfy this success criterion when the ICT does not have a built-in keyboard, and it also does not support an alternative input method (hardware or software) that provides keyboard-like access to all functionality.
-<div class="note" role="note" id="issue-container-generatedID-216"><div role="heading" class="note-title marker" id="h-note-206" aria-level="3"><span>Note 6</span></div><div class="">A keypad that provides full access to functionality might be considered a keyboard.</div></div></li>
+<div class="note" role="note" id="issue-container-generatedID-217"><div role="heading" class="note-title marker" id="h-note-207" aria-level="3"><span>Note 6</span></div><div class="">A keypad that provides full access to functionality might be considered a keyboard.</div></div></li>
 <li><a href="#no-keyboard-trap">2.1.2 No Keyboard Trap</a> — This criterion applies when focus can be moved using a keyboard interface. In some closed systems, tactile input like numeric keypads or other functional groups of keys may be available, but there is no mechanism for onscreen focus; for example, the keys are mapped directly to functions without moving focus between on-screen controls. In this case, there is no concept of focus, and therefore keyboard traps cannot exist and this success criterion would be satisfied.</li>
 <li><a href="#character-key-shortcuts">2.1.4 Character Key Shortcuts</a> — Certain closed systems lack a mechanism for keyboard shortcuts because their mode of operation revolves around a single key performing a single function. For such systems, this success criterion is satisfied.</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>
@@ -2092,8 +2094,8 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <li><a href="#pointer-cancellation">2.5.2 Pointer Cancellation</a> — As noted in the section <a href="#applying-sc-2-5-2-pointer-cancellation-to-non-web-documents-and-software">Applying SC 2.5.2 Pointer Cancellation to Non-Web Documents and Software</a>, examples of ‘essential’ functionality are features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state).</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="#target-size-minimum">2.5.8 Target Size (Minimum)</a> — This success criterion uses CSS pixels for defining the target size.  ICT with closed functionality may not use CSS pixels as a standard measurement, but the definition of ‘CSS pixel’ still applies as described in <a href="#applying-css-pixel-to-non-web-documents-and-software">Applying “CSS pixel” to Non-Web Documents and Software</a>.  If the system supports a density-independent pixel measurement, it should be used in place of CSS pixels.
-<div class="note" role="note" id="issue-container-generatedID-217"><div role="heading" class="note-title marker" id="h-note-207" aria-level="3"><span>Note 7</span></div><div class="">If the viewing distance and pixel density of the system are unknown, approximating the reference pixel as described in Applying “CSS pixel” to Non-Web Documents and Software is not possible.</div></div>
-<div class="note" role="note" id="issue-container-generatedID-218"><div role="heading" class="note-title marker" id="h-note-208" aria-level="3"><span>Note 8</span></div><div class="">For software designed to run on specific known hardware, a physical size standard would be more straightforward to apply, as calculations for a CSS pixel are dependent on the viewing distance or pixel density of the display.</div></div></li>
+<div class="note" role="note" id="issue-container-generatedID-218"><div role="heading" class="note-title marker" id="h-note-208" aria-level="3"><span>Note 7</span></div><div class="">If the viewing distance and pixel density of the system are unknown, approximating the reference pixel as described in Applying “CSS pixel” to Non-Web Documents and Software is not possible.</div></div>
+<div class="note" role="note" id="issue-container-generatedID-219"><div role="heading" class="note-title marker" id="h-note-209" aria-level="3"><span>Note 8</span></div><div class="">For software designed to run on specific known hardware, a physical size standard would be more straightforward to apply, as calculations for a CSS pixel are dependent on the viewing distance or pixel density of the display.</div></div></li>
 <li><a href="#language-of-page">3.1.1 Language of Page</a> — Depends upon language information being in a programmatically determinable form intended to drive correct pronunciation.  Where another mechanism achieves correct pronunciation for products with closed functionality, such as self-voicing, the intent of this success criterion would be met.</li>
 <li><a href="#language-of-parts">3.1.2 Language of Parts</a> — Depends upon language information in a programmatically determinable form intended to drive correct pronunciation.  Where another mechanism achieves correct pronunciation for ICT with closed functionality, such as self-voicing, the intent of this success criterion would be met.</li>
 <li><a href="#consistent-navigation">3.2.3 Consistent Navigation</a> — This success criterion is interpreted to only apply to “sets of software programs” which are very rare.  See the second note in the section <a href="#applying-sc-3-2-3-consistent-navigation-to-non-web-documents-and-software">Applying SC 3.2.3 Consistent Navigation to Non-Web Documents and Software</a>.</li>
@@ -2108,7 +2110,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 </li>
 <li><a href="#name-role-value">4.1.2 Name, Role, Value</a> — Requires information in a programmatically determinable form.</li>
 <li><a href="#status-messages">4.1.3 Status Messages</a> — Depends upon status messages being programmatically determinable using <a href="#dfn-role">role</a> or properties.
-<div class="note" role="note" id="issue-container-generatedID-219"><div role="heading" class="note-title marker" id="h-note-209" aria-level="3"><span>Note 9</span></div><div class="">Non-web software with closed functionality would need equivalent facilitation to provide access to status messages.</div></div></li>
+<div class="note" role="note" id="issue-container-generatedID-220"><div role="heading" class="note-title marker" id="h-note-210" aria-level="3"><span>Note 9</span></div><div class="">Non-web software with closed functionality would need equivalent facilitation to provide access to status messages.</div></div></li>
 </ul></section>
 		<section class="appendix" id="background-on-text-command-line-terminal-applications-and-interfaces"><div class="header-wrapper"><h2 id="b-background-on-text-command-line-terminal-applications-and-interfaces">B. Background on Text / Command-line / Terminal Applications and Interfaces</h2><a class="self-link" href="#background-on-text-command-line-terminal-applications-and-interfaces" aria-label="Permalink for Section B. Background on Text / Command-line / Terminal Applications and Interfaces"></a></div>
 <section id="how-text-interfaces-are-realized"><div class="header-wrapper"><h3 id="b-1-how-text-interfaces-are-realized">B.1 How text interfaces are realized</h3><a class="self-link" href="#how-text-interfaces-are-realized" aria-label="Permalink for Section B.1 How text interfaces are realized"></a></div>
@@ -2124,10 +2126,10 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <p>As noted above, in a text interface the terminal application renders the characters on the screen, just as a Web browser typically renders content for a Web application. As an example, for success criterion <a href="http://www.w3.org/TR/WCAG22/#resize-text">1.4.4 Resize Text</a>, a text application could achieve 200 percent resizing when the terminal application client that is rendering it has this capability (cf. WCAG 2 Technique <a href="http://www.w3.org/WAI/WCAG22/Techniques/general/G142">G142 Using a technology that has commonly-available user agents that support zoom</a>). Many web pages and web applications use this approach to meet success criterion <a href="http://www.w3.org/TR/WCAG22/#resize-text">1.4.4 Resize Text</a> through no explicit action of their own.</p>
 <p>A similar approach could also be used for success criterion <a href="http://www.w3.org/TR/WCAG22/#contrast-minimum">1.4.3 Contrast (minimum)</a> (cf. WCAG 2 Technique <a href="http://www.w3.org/WAI/WCAG22/Techniques/general/G148">G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults</a>): relying on the terminal application client to render the text with sufficient contrast against the background. In fact, many terminal applications allow the user to force all text to share a single user-chosen foreground color (and a single user-chosen background color), overriding the text application's specified colors to meet the user's desires or needs.</p>
 <p>Since many assistive technology analysis techniques depend upon discerning the location of the text input cursor, terminal application use of “soft cursors” and “highlight bars” may bypass those analysis techniques and cause failures of success criteria.</p>
-<div class="note" role="note" id="issue-container-generatedID-220"><div role="heading" class="note-title marker" id="h-note-210" aria-level="4"><span>Note 1</span></div><div class="">It is outside of the scope of this document to define WCAG techniques for non-web ICT. These examples are simply illustrations of how WCAG 2 success criteria can be applied to this class of non-web software applications.</div></div>
+<div class="note" role="note" id="issue-container-generatedID-221"><div role="heading" class="note-title marker" id="h-note-211" aria-level="4"><span>Note 1</span></div><div class="">It is outside of the scope of this document to define WCAG techniques for non-web ICT. These examples are simply illustrations of how WCAG 2 success criteria can be applied to this class of non-web software applications.</div></div>
 
 <p>The way to think about "accessibility supported" and "programmatically determined" may seem a little different for text applications, but the definitions are unchanged. Unlike the semantic objects of graphical user interfaces and web pages, the output of text-based applications consists of plain text. A terminal emulator acts as the user agent for text-based applications; it might render some content such as escape codes as semantic elements, but otherwise exposes only lines of text to assistive technology. Where assistive technology is able to interpret the text and any semantic objects accurately, the content is "programmatically determinable"—even though no explicit markup was necessarily used to make it so.</p>
-<div class="note" role="note" id="issue-container-generatedID-221"><div role="heading" class="note-title marker" id="h-note-211" aria-level="4"><span>Note 2</span></div><div class="">The terminal application itself is “traditional” non-web software ICT. It is only for the text application that there is a need to take this approach with these glossary terms.</div></div></section></section>
+<div class="note" role="note" id="issue-container-generatedID-222"><div role="heading" class="note-title marker" id="h-note-212" aria-level="4"><span>Note 2</span></div><div class="">The terminal application itself is “traditional” non-web software ICT. It is only for the text application that there is a need to take this approach with these glossary terms.</div></div></section></section>
 		<section class="appendix" id="acknowledgements"><div class="header-wrapper"><h2 id="c-acknowledgements">C. Acknowledgements</h2><a class="self-link" href="#acknowledgements" aria-label="Permalink for Section C. Acknowledgements"></a></div>
 <section id="active-participants-of-the-wcag2ict-task-force-involved-in-the-development-of-this-document"><div class="header-wrapper"><h3 id="c-1-active-participants-of-the-wcag2ict-task-force-involved-in-the-development-of-this-document">C.1 Active Participants of the WCAG2ICT Task Force Involved in the Development of this Document</h3><a class="self-link" href="#active-participants-of-the-wcag2ict-task-force-involved-in-the-development-of-this-document" aria-label="Permalink for Section C.1 Active Participants of the WCAG2ICT Task Force Involved in the Development of this Document"></a></div>
 <ul>
@@ -2153,7 +2155,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <li>Gregg Vanderheiden (Raising the Floor)</li>
 </ul>
 </section><section id="participants-in-the-ag-working-group-that-actively-reviewed-and-contributed"><div class="header-wrapper"><h3 id="c-2-participants-in-the-ag-working-group-that-actively-reviewed-and-contributed">C.2 Participants in the AG Working Group that Actively Reviewed and Contributed</h3><a class="self-link" href="#participants-in-the-ag-working-group-that-actively-reviewed-and-contributed" aria-label="Permalink for Section C.2 Participants in the AG Working Group that Actively Reviewed and Contributed"></a></div>
-<div class="note" id="issue-container-generatedID-222"><div role="heading" class="ednote-title marker" id="h-ednote-9" aria-level="4"><span>Editor's note</span></div><div class="">This list will be updated as AG WG reviews and contributions are completed.</div></div>
+<div class="note" id="issue-container-generatedID-223"><div role="heading" class="ednote-title marker" id="h-ednote-9" aria-level="4"><span>Editor's note</span></div><div class="">This list will be updated as AG WG reviews and contributions are completed.</div></div>
 
 <ul>
 <li>Jonathan Avila (Level Access)</li>