Merge pull request #490 from w3c/pday1-patch-1

SHA: 1c2d997
Reason: push, by maryjom

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

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="13532b0c8dfb55745f6c5e99226c1d658943b3d4">
+<meta name="revision" content="1c2d9972d150eddf8255f46efbeb1598a411afd5">
 <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": "13532b0c8dfb55745f6c5e99226c1d658943b3d4",
+  "gitRevision": "1c2d9972d150eddf8255f46efbeb1598a411afd5",
   "publishISODate": "2024-09-03T00:00:00.000Z",
   "generatedSubtitle": "W3C Editor's Draft 03 September 2024"
 }</script>
@@ -348,7 +348,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <li><a href="https://www.w3.org/WAI/WCAG22/quickref/">How to Meet WCAG (Quick Reference)</a></li>
 <li><a href="https://w3c.github.io/Mobile-A11y-TF-Note/">Mobile Accessibility: How WCAG 2.0 and other <abbr title="World Wide Web Consortium">W3C</abbr>/WAI Guidelines Apply to Mobile</a> - This draft resource, as of the date of the WCAG2ICT Note publication, is undergoing an update by the Mobile Accessibility Task Force to cover WCAG 2.2.</li>
 </ul>
-<p>While WCAG 2 was designed to be technology-neutral, it assumes the presence of a “user agent” such as a browser, media player, or assistive technology as a means to access web content. Therefore, the application of WCAG 2 to documents and software in non-web contexts necessitates some interpretation in order to determine how the intent of each WCAG 2 success criterion could be met in these different contexts of use. Therefore, the bulk of the Task Force's work involved evaluating how each WCAG 2 success criterion would apply in the context of non-web ICT, if it were applied to non-web ICT.</p>
+<p>While WCAG 2 was designed to be technology-neutral, it assumes the presence of a “user agent” such as a browser, media player, or assistive technology as a means to access web content. As a result, the application of WCAG 2 to documents and software in non-web contexts necessitates some interpretation in order to determine how the intent of each WCAG 2 success criterion could be met in these different contexts of use. Therefore, the bulk of the Task Force's work involved evaluating how each WCAG 2 success criterion would apply in the context of non-web ICT, if it were applied to non-web ICT.</p>
 <p>The Task Force found that the majority of success criteria from WCAG 2 can be applied to non-web documents and software with either no or minimal changes. Since many of the Level A and AA success criteria do not include any web-related terms, they apply directly as written and as described in the “Intent” sections from the <a href="https://www.w3.org/WAI/WCAG22/Understanding/">Understanding WCAG 2.2</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-understanding-wcag22" title="Understanding Web Content Accessibility Guidelines 2.2">UNDERSTANDING-WCAG22</a></cite>] resource. Additional notes were provided, as needed, to provide assistance in applying them to non-web documents and software.</p>
 <section id="interpretation-of-web-terminology-in-a-non-web-context"><div class="header-wrapper"><h4 id="x1-2-1-interpretation-of-web-terminology-in-a-non-web-context">Interpretation of Web Terminology in a Non-web Context</h4><a class="self-link" href="#interpretation-of-web-terminology-in-a-non-web-context" aria-label="Permalink for Section Interpretation of Web Terminology in a Non-web Context"></a></div>
 <p>When certain Web-specific terms or phrases like “web page(s)” were used in success criteria, those were replaced with non-web terms or phrases like “non-web document(s) and software”. Additional notes were also provided to explain the terminology replacements.</p>