Merge pull request #295 from w3c/mjm-fix-understanding-doc-links

SHA: 088ddcf Reason: push, by maryjom Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
w3c · Jan 12, 2024 · f3b6daf · f3b6daf
1 parent 515475e
commit f3b6daf
Showing 1 changed file with 9 additions and 8 deletions.
diff --git a/index.html b/index.html
@@ -102,7 +102,7 @@
 
 <link rel="stylesheet" type="text/css" href="wcag2ict.css">
 
-<meta name="revision" content="8b92e5cbaac5c01a77d32c72070dcde4991f1a2d">
+<meta name="revision" content="088ddcf9b475c47703cbee9359fe94e173ff311c">
 <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}
@@ -209,7 +209,7 @@
     }
   },
   "lint": false,
-  "gitRevision": "8b92e5cbaac5c01a77d32c72070dcde4991f1a2d",
+  "gitRevision": "088ddcf9b475c47703cbee9359fe94e173ff311c",
   "publishISODate": "2024-01-12T00:00:00.000Z",
   "generatedSubtitle": "W3C Editor's Draft 12 January 2024"
 }</script>
@@ -457,7 +457,8 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 </section><section id="closed-functionality"><div class="header-wrapper"><h3 id="x2-2-closed-functionality">Closed Functionality</h3><a class="self-link" href="#closed-functionality" aria-label="Permalink for Section 2.2"></a></div>
 <p>The term <strong>closed functionality</strong>, as used in WCAG2ICT, has the meaning below:</p>
 <dl><dt>closed functionality (as used in WCAG2ICT)</dt><dd>
-functionality that prevents users from attaching, installing, or using [assistive technology](#dfn-assistive-technology)</dd></dl>
+
+<p>functionality that prevents users from attaching, installing, or using <a href="#dfn-assistive-technology">assistive technology</a></p></dd></dl><p></p>
 <div class="note" role="note" id="issue-container-generatedID-6"><div role="heading" class="note-title marker" id="h-note-3" aria-level="4"><span>Note</span></div><div class="">
 
 <p>To support users with disabilities, products with closed functionality can instead provide built-in features that function as assistive technology.</p></div></div><p></p>
@@ -472,7 +473,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <p>For non-web content it is necessary to view this a bit more broadly. Within WCAG2ICT, the term “content” is used as follows:</p>
 <dl><dt>content (non-web content) (as used in WCAG2ICT)</dt><dd>
 
-<p>information and sensory experience to be communicated to the user by means of <ins><strong>[<a href="#software">software</a>]</strong></ins>, including code or markup that defines the content's <a href="#dfn-structure">structure</a>, <a href="https://www.w3.org/TR/WCAG22/#dfn-presentation">presentation</a>, and interactions
+<p>information and sensory experience to be communicated to the user by means of <strong><ins>[<a href="#software">software</a>]</ins></strong>, including code or markup that defines the content's <a href="#dfn-structure">structure</a>, <a href="https://www.w3.org/TR/WCAG22/#dfn-presentation">presentation</a>, and interactions
 </p></dd></dl><p></p>
 <div class="note" role="note" id="issue-container-generatedID-7"><div role="heading" class="note-title marker" id="h-note-4" aria-level="4"><span>Note</span></div><div class="">
 
@@ -519,7 +520,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <p>The term <strong>set of documents</strong>, as used in WCAG2ICT, has the meaning below:</p>
 <dl><dt>set of documents (non-web) (as used in WCAG2ICT)</dt><dd>
 
-<p>collection of <ins><strong><a href="#document">documents</a></strong></ins> that share a common purpose, are created by the same author, group or organization <ins><strong>[and that are published together, and the documents all refer to each other by name or link]</strong></ins>
+<p>collection of <strong><ins>[<a href="#document">documents</a>]</ins></strong> that share a common purpose, are created by the same author, group or organization <strong><ins>[and that are published together, and the documents all refer to each other by name or link]</ins></strong>
 </p></dd></dl><p></p>
 <div class="note" role="note" id="issue-container-generatedID-14"><div role="heading" class="note-title marker" id="h-note-11" aria-level="4"><span>Note 1</span></div><div class="">
 
@@ -534,7 +535,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <p>The term <strong>set of software programs</strong>, as used in WCAG2ICT, has the meaning below:</p>
 <dl><dt>set of software programs (as used in WCAG2ICT)</dt><dd>
 
-<p>collection of <ins><strong><a href="#software">software</a> programs]</strong></ins> that share a common purpose, are created by the same author, group or organization <ins><strong>[and that are distributed together and can be launched and used independently from each other, but are interlinked each with every other one such that users can navigate from one program to another via a consistent method that appears in each member of the set]</strong></ins>
+<p>collection of <strong><ins>[<a href="#software">software</a> programs]</ins></strong> that share a common purpose, are created by the same author, group or organization <strong><ins>[and that are distributed together and can be launched and used independently from each other, but are interlinked each with every other one such that users can navigate from one program to another via a consistent method that appears in each member of the set]</ins></strong>
 </p></dd></dl><p></p>
 <div class="note" role="note" id="issue-container-generatedID-16"><div role="heading" class="note-title marker" id="h-note-13" aria-level="4"><span>Note 1</span></div><div class="">
 
@@ -601,7 +602,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 
 <dl><dt>user agent (as used in WCAG2ICT)</dt><dd>
 
-<p>any <a href="#software">software</a> that retrieves and presents <ins><strong>[documents]</strong></ins> for users
+<p>any <a href="#software">software</a> that retrieves and presents <strong><ins>[documents]</ins></strong> for users
 </p></dd></dl><p></p>
 <div class="note" role="note" id="issue-container-generatedID-27"><div role="heading" class="note-title marker" id="h-note-24" aria-level="4"><span>Note 1</span></div><div class="">
 
@@ -1333,7 +1334,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
 <p>See also the discussion on <a href="#closed-functionality">Closed Functionality</a>.</p></div></div><p></p>
 </section><section><h5 id="intent-from-understanding-4.1.2-name,-role,-value">Intent from Understanding 4.1.2 Name, Role, Value</h5><blockquote class="wcag-quote"><p>The intent of this Success Criterion is to ensure that Assistive Technologies (AT)  can gather information about, activate (or set) and keep up to date on the status of  user interface controls in the content.  </p><p>When standard controls from accessible technologies are used, this process is straightforward.  If the user interface elements are used according to specification the conditions  of this provision will be met. (See examples of Success Criterion 4.1.2 below)  </p><p>If custom controls are created, however, or interface elements are programmed (in  code or script) to have a different role and/or function than usual, then additional  measures need to be taken to ensure that the controls provide important information  to assistive technologies and allow themselves to be controlled by assistive technologies.  </p><p>A particularly important state of a user interface control is whether or not it has  focus. The focus state of a control can be programmatically determined, and notifications  about change of focus are sent to user agents and assistive technology. Other examples  of user interface control state are whether or not a checkbox or radio button has  been selected, or whether or not a collapsible tree or list node is expanded or collapsed.  </p><div class="note">  <p>Success Criterion 4.1.2 requires a programmatically determinable name for all user  interface components. Names may be visible or invisible. Occasionally, the name must  be visible, in which case it is identified as a label. Refer to the definition of  name and label in the glossary for more information.  </p>  </div></blockquote></section></section><section id="status-messages"><div class="header-wrapper"><h5 id="x6-4-2-4-status-messages">4.1.3 Status Messages</h5><a class="self-link" href="#status-messages" aria-label="Permalink for Section 6.4.2.4"></a></div><blockquote class="wcag-quote"><p xmlns="http://www.w3.org/1999/xhtml">In content implemented using markup languages, <a>status messages</a> can be <a>programmatically determined</a> through <a>role</a> or properties such that they can be presented to the user by <a>assistive technologies</a> without receiving focus.</p></blockquote>
 <section id="applying-sc-4-1-3-status-messages-to-non-web-documents-and-software"><div class="header-wrapper"><h6 id="x6-4-2-4-1-applying-sc-4-1-3-status-messages-to-non-web-documents-and-software">Applying SC 4.1.3 Status Messages to Non-Web Documents and Software</h6><a class="self-link" href="#applying-sc-4-1-3-status-messages-to-non-web-documents-and-software" aria-label="Permalink for Section 6.4.2.4.1"></a></div>
-<p>This applies directly as written, and as described in <a href="https://www.w3.org/WAI/WCAG21/Understanding/status-messages.html#intent">Intent from Understanding Success Criterion 4.1.3</a> (also provided below) replacing "In content implemented using markup languages" with "In content implemented using markup languages, or that supports status message notifications".</p>
+<p>This applies directly as written, and as described in <a href="https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html#intent">Intent from Understanding Success Criterion 4.1.3</a> (also provided below) replacing "In content implemented using markup languages" with "In content implemented using markup languages, or that supports status message notifications".</p>
 <p>With this substitution, it would read:
 In <ins><strong>[content implemented using markup languages, or that supports status message notifications]</strong></ins>, <a href="https://www.w3.org/TR/WCAG22/#dfn-status-messages">status messages</a> can be <a href="#dfn-programmatically-determined">programmatically determined</a> through <a href="#dfn-role">role</a> or properties such that they can be presented to the user by <a href="#dfn-assistive-technology">assistive technologies</a> without receiving focus.</p>
 <div class="note" role="note" id="issue-container-generatedID-134"><div role="heading" class="note-title marker" id="h-note-127" aria-level="7"><span>Note 1</span></div><div class="">