Merge pull request #783 from w3c/maryjom-patch-1

SHA: 0665097
Reason: push, by maryjom

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

Author: maryjom

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="ef603eedefa4b573c5e4e390ce15102db365ee7d">
+<meta name="revision" content="06650977238f3c071b3cec40a92156c930b54e2f">
 <meta name="description" content="This document 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).">
 <link rel="canonical" href="https://www.w3.org/TR/wcag2ict-22/">
 <style>
@@ -238,7 +238,7 @@
     }
   },
   "lint": false,
-  "gitRevision": "ef603eedefa4b573c5e4e390ce15102db365ee7d",
+  "gitRevision": "06650977238f3c071b3cec40a92156c930b54e2f",
   "publishISODate": "2025-08-21T00:00:00.000Z",
   "generatedSubtitle": "W3C Group Note 21 August 2025"
 }</script>
@@ -1273,7 +1273,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <p>This success criterion does not imply that non-web software always needs to directly support a keyboard or “keyboard interface” if one is not provided by the platform software. But if one is provided, the software needs to make all functionality available through it - unless the exception applies.</p></div></div><p></p>
 <div class="note" role="note" id="issue-container-generatedID-89"><div role="heading" class="note-title marker" id="h-note-89" aria-level="7"><span>Note 5 (Added) (for non-web software)</span></div><div class="wcag2ict software">
 
-<p>Nor does this success criterion imply that non-web software always needs to provide its own <a href="#virtual-keyboard">virtual keyboard</a>. But if it does, then the non-web software still needs to support keyboard input from any keyboard interface provided by the platform software.</p></div></div><p></p>
+<p>This success criterion also does not imply that non-web software always needs to provide its own <a href="#virtual-keyboard">virtual keyboard</a>. But if it does, then the non-web software still needs to support keyboard input from any keyboard interface provided by the platform software.</p></div></div><p></p>
 <div class="note" role="note" id="issue-container-generatedID-90"><div role="heading" class="note-title marker" id="h-note-90" aria-level="7"><span>Note 6 (Added) (for non-web software)</span></div><div class="wcag2ict software">
 
 <p>See also the <a href="#comments-on-closed-functionality">Comments on Closed Functionality</a>.</p></div></div><p></p>