Merge pull request #506 from w3c/daniel-montalvo/issue502

SHA: 0afadc3
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="5b7f2e623ca8598bcd113ae05c52b9cd890742b3">
+<meta name="revision" content="0afadc36c3846e9ef0c9a255007b6d0f2f4cc2bb">
 <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": "5b7f2e623ca8598bcd113ae05c52b9cd890742b3",
+  "gitRevision": "0afadc36c3846e9ef0c9a255007b6d0f2f4cc2bb",
   "publishISODate": "2024-09-09T00:00:00.000Z",
   "generatedSubtitle": "W3C Editor's Draft 09 September 2024"
 }</script>
@@ -1215,7 +1215,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <p>Functions that emulate a keyboard or numeric keypad key press are considered essential.</p></div></div><p></p>
 <div class="example wcag2ict">
 
-Example (Added): Examples of essential functionality for non-web software are features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state).</div><p></p>
+<p><span>Example (Added): </span>Examples of essential functionality for non-web software are features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state).</p></div><p></p>
 <div class="note" role="note" id="issue-container-generatedID-123"><div role="heading" class="note-title marker" id="h-note-117" aria-level="7"><span>Note 5</span></div><div class="">
 
 <p>This requirement applies to <strong><ins>[<a href="#software">software</a> applications that interpret]</ins></strong> pointer actions (i.e. this does not apply to actions that are required to operate the <strong><ins>[underlying <a href="#platform-software">platform software</a>]</ins></strong> or assistive technology).</p></div></div><p></p>
@@ -1472,9 +1472,9 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <li>Content is implemented using HTML or XML (as outlined in the <a href="https://www.w3.org/TR/WCAG21/#h-note-27">WCAG 2.1 note on 4.1.1</a> and the <a href="https://www.w3.org/WAI/WCAG20/errata/#editorial">WCAG 2.0 editorial errata</a> in the thirteenth list item)</li>
 <li>Non-web documents or software are not authored using a markup language.</li>
 <li>Non-web documents or software are authored using a markup language, but accessibility information is exposed via platform accessibility APIs, not by making the markup itself available to assistive technologies.</li></ul></div></div>
-<div class="example">
+<div class="example wcag2ict">
 
-<p><span>Example: </span>Examples where 4.1.1 Parsing would be satisfied:</p>
+<p><span>Example (Added): </span>Examples where 4.1.1 Parsing would be satisfied:</p>
 <ul>
 <li>An HTML page embedded inside a desktop application (as outlined in the <a href="https://www.w3.org/TR/WCAG21/#h-note-27">WCAG 2.1 note on 4.1.1</a> and the <a href="https://www.w3.org/WAI/WCAG20/errata/#editorial">WCAG 2.0 editorial errata</a> in the thirteenth list item)</li>
 <li>A PDF document (not authored using a markup language)</li>