Editorial: Update lone reference of "alternative text" to "text alter…

…native" (#2062) SHA: 8a9828a Reason: push, by pkra Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
w3c · Oct 20, 2023 · e769541 · e769541
1 parent 1dc525f
commit e769541
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/index.html b/index.html
@@ -141,7 +141,7 @@
 
 
 
-<meta name="revision" content="05c5c5e9cbcd504b8b78722ea3b24871b7924f65">
+<meta name="revision" content="8a9828a2888a80b81af61bcc68cf729a85d7e105">
 <meta name="description" content="Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This version adds features new since WAI-ARIA 1.1 [wai-aria-1.1] to improve interoperability with assistive technologies to form a more consistent accessibility model for [HTML] and [SVG2]. This specification complements both [HTML] and [SVG2].">
 <style>
 .hljs{display:block;overflow-x:auto;padding:.5em;color:#383a42;background:#fafafa}
@@ -310,16 +310,16 @@
     }
   },
   "lint": false,
-  "gitRevision": "05c5c5e9cbcd504b8b78722ea3b24871b7924f65",
-  "publishISODate": "2023-10-16T00:00:00.000Z",
-  "generatedSubtitle": "W3C Editor's Draft 16 October 2023"
+  "gitRevision": "8a9828a2888a80b81af61bcc68cf729a85d7e105",
+  "publishISODate": "2023-10-20T00:00:00.000Z",
+  "generatedSubtitle": "W3C Editor's Draft 20 October 2023"
 }</script>
 <link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED"></head>
 <body class="h-entry" data-cite="dom accname-1.2 core-aam-1.2 infra HTML"><div class="head">
     <p class="logos"><a class="logo" href="https://www.w3.org/"><img crossorigin="" alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72">
   </a></p>
     <h1 id="title" class="title">Accessible Rich Internet Applications (WAI-ARIA) 1.3</h1> 
-    <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2023-10-16">16 October 2023</time></p>
+    <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2023-10-20">20 October 2023</time></p>
     <details open="">
       <summary>More details about this document</summary>
       <dl>
@@ -6378,7 +6378,7 @@ <h4 class="role-name" title="none" aria-describedby="desc-none"><code>none</code
 <span class="hljs-tag">&lt;<span class="hljs-name">span</span>&gt;</span> Sample Content <span class="hljs-tag">&lt;<span class="hljs-name">a</span> <span class="hljs-attr">href</span>=<span class="hljs-string">"..."</span>&gt;</span>let's go!<span class="hljs-tag">&lt;/<span class="hljs-name">a</span>&gt;</span> <span class="hljs-tag">&lt;/<span class="hljs-name">span</span>&gt;</span></code></pre>
       </div>
 				<p>In <abbr title="Hypertext Markup Language">HTML</abbr>, the <code>&lt;img&gt;</code> <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a> is treated as a single entity regardless of the type of image file. Consequently, using <code>role="none"</code> or <code>role="presentation"</code> on an <abbr title="Hypertext Markup Language">HTML</abbr> <code>img</code> is equivalent to using <code>aria-hidden="true"</code>. In order to make the image contents accessible, authors can embed the object using an <code>&lt;object&gt;</code> or <code>&lt;iframe&gt;</code> <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a>, or use inline <abbr title="Scalable Vector Graphics">SVG</abbr> code, and follow the accessibility guidelines for the image content.</p>
-				<p>Authors <em class="rfc2119">SHOULD NOT</em> provide meaningful alternative text (for example, use <code>alt=""</code> in <abbr title="Hypertext Markup Language">HTML</abbr>) when the <code>none</code>/<code>presentation</code> role is applied to an image.</p>
+				<p>Authors <em class="rfc2119">SHOULD NOT</em> provide a meaningful text alternative (for example, use <code>alt=""</code> in <abbr title="Hypertext Markup Language">HTML</abbr>) when the <code>none</code>/<code>presentation</code> role is applied to an image.</p>
 				<p>In the following code sample, the containing <a href="#img" class="role-reference"><code>img</code></a> and is appropriately labeled by the caption paragraph. In this example the <code>img</code> element can be marked as <a href="#none" class="role-reference"><code>none</code></a>/<a href="#presentation" class="role-reference"><code>presentation</code></a> because the role and the text alternatives are provided by the containing element.</p>
 				<div class="example" id="example-13">
         <div class="marker">