diff --git a/index.html b/index.html
index 666207887..8ef40b6a2 100644
--- a/index.html
+++ b/index.html
@@ -1,6 +1,6 @@
 <!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US"><head>
 <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
-<meta name="generator" content="ReSpec 35.0.0">
+<meta name="generator" content="ReSpec 35.0.2">
 <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
 <style>
 span.example-title{text-transform:none}
@@ -125,7 +125,8 @@
 
 
 
-<meta name="revision" content="af75c5c1c6af0098befab36b2a9384b80577eb0a">
+<meta name="color-scheme" content="light">
+<meta name="revision" content="62057402622db35c28866b5b974bd75a43db7f9b">
 <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{--base:#fafafa;--mono-1:#383a42;--mono-2:#686b77;--mono-3:#717277;--hue-1:#0b76c5;--hue-2:#336ae3;--hue-3:#a626a4;--hue-4:#42803c;--hue-5:#ca4706;--hue-5-2:#c91243;--hue-6:#986801;--hue-6-2:#9a6a01}
@@ -306,16 +307,16 @@
     }
   },
   "lint": false,
-  "gitRevision": "af75c5c1c6af0098befab36b2a9384b80577eb0a",
-  "publishISODate": "2024-04-29T00:00:00.000Z",
-  "generatedSubtitle": "W3C Editor's Draft 29 April 2024"
+  "gitRevision": "62057402622db35c28866b5b974bd75a43db7f9b",
+  "publishISODate": "2024-05-02T00:00:00.000Z",
+  "generatedSubtitle": "W3C Editor's Draft 02 May 2024"
 }</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="2024-04-29">29 April 2024</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="2024-05-02">02 May 2024</time></p>
     <details open="">
       <summary>More details about this document</summary>
       <dl>
@@ -10501,7 +10502,7 @@ <h4 class="role-name" title="window" aria-describedby="desc-window"><code>window
 <dt><a href="#aria-haspopup" class="property-reference">aria-haspopup</a></dt>
 <dd><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn">Indicates</a> the availability and type of interactive popup element, such as menu or dialog, that can be triggered by an <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a>.</dd>
 <dt><a href="#aria-hidden" class="state-reference">aria-hidden</a></dt>
-<dd><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn">Indicates</a> whether the <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a> is exposed to an accessibility <abbr title="application programming interface">API</abbr>. See related <a href="https://w3c.github.io/aria/#aria-disabled" class="state-reference"><code>aria-disabled</code></a>.</dd>
+<dd><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn">Indicates</a>, when set to <code>true</code>, that an <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a> and its entire subtree are hidden from assistive technology, regardless of whether it is visibly rendered.</dd>
 <dt><a href="#aria-invalid" class="state-reference">aria-invalid</a></dt>
 <dd><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn">Indicates</a> the entered value does not conform to the format expected by the application. See related <a href="https://w3c.github.io/aria/#aria-errormessage" class="property-reference"><code>aria-errormessage</code></a>.</dd>
 <dt><a href="#aria-keyshortcuts" class="property-reference">aria-keyshortcuts</a></dt>
@@ -12038,11 +12039,12 @@ <h4><span class="property-name" title="aria-haspopup" aria-describedby="desc-ari
 		<section class="state notoc" id="aria-hidden">
 			<h4><span class="state-name" title="aria-hidden" aria-describedby="desc-aria-hidden"><code>aria-hidden</code> <span class="type-indicator">state</span></span></h4>
 			<div class="state-description" id="desc-aria-hidden" role="definition">
-				<p><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-indicates-11">Indicates</a> whether the <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a> is exposed to an accessibility <abbr title="application programming interface">API</abbr>. See related <a href="https://w3c.github.io/aria/#aria-disabled" class="state-reference"><code>aria-disabled</code></a>.</p>
+				<p><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-indicates-11">Indicates</a>, when set to <code>true</code>, that an <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a> and its entire subtree are hidden from assistive technology, regardless of whether it is visibly rendered.</p>
 				<p>User agents determine an element's <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-3">hidden</a> status based on whether it is rendered, and the rendering is usually controlled by <abbr title="Cascading Style Sheets">CSS</abbr>. For example, an element whose <code>display</code> property is set to <code>none</code> is not rendered. An element is considered <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-4">hidden</a> if it, or any of its ancestors are not rendered or have their <code>aria-hidden</code> attribute value set to <code>true</code>.</p>
-				<p>Authors <em class="rfc2119">MAY</em>, with caution, use aria-hidden to hide visibly rendered content from assistive technologies <em>only</em> if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content. Authors using aria-hidden to hide visible content from screen readers <em class="rfc2119">MUST</em> ensure that identical or equivalent meaning and functionality is exposed to assistive technologies.</p>
+				<p>Authors <em class="rfc2119">MAY</em>, with caution, use aria-hidden to hide visibly rendered content from assistive technologies <em>only</em> if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content. Authors using aria-hidden to hide visible content <em class="rfc2119">MUST</em> ensure that identical or equivalent meaning and functionality is exposed to assistive technologies.</p>
 				<div class="note" role="note" id="issue-container-generatedID-52"><div role="heading" class="note-title marker" id="h-note-52" aria-level="4"><span>Note</span></div><p class="">Authors are advised to use extreme caution and consider a wide range of disabilities when hiding visibly rendered content from assistive technologies. For example, a sighted, dexterity-impaired individual might use voice-controlled assistive technologies to access a visual interface. If an author hides visible link text "Go to checkout" and exposes similar, yet non-identical link text "Check out now" to the accessibility <abbr title="application programming interface">API</abbr>, the user might be unable to access the interface they perceive using voice control. Similar problems can also arise for screen reader users. For example, a sighted telephone support technician might attempt to have the blind screen reader user click the "Go to checkout" link, which they might be unable to find using a type-ahead item search ("Go to…").</p></div>
-				<div class="note" role="note" id="issue-container-generatedID-53"><div role="heading" class="note-title marker" id="h-note-53" aria-level="4"><span>Note</span></div><p class="">At the time of this writing, <code><a href="https://w3c.github.io/aria/#aria-hidden" class="state-reference"><code>aria-hidden</code></a>="false"</code> is known to work inconsistently in browsers. As future implementations improve, use caution and test thoroughly before relying on this approach.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-53"><div role="heading" class="note-title marker" id="h-note-53" aria-level="4"><span>Note</span></div><p class="">As of ARIA 1.3, <code><a href="https://w3c.github.io/aria/#aria-hidden" class="state-reference"><code>aria-hidden</code></a>="false"</code> is now synonymous with <code>aria=hidden="undefined"</code>.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-54"><div role="heading" class="note-title marker" id="h-note-54" aria-level="4"><span>Note</span></div><p class="">The original intent for <code>aria-hidden="false"</code> was to allow user agents to expose content that was otherwise hidden from the accessibility tree. However, due to ambiguity in the specification and inconsistent browser support for the <code>false</code> value, the original intent is no longer supported.</p></div>
 			</div>
 			<table class="state-features">
 				<caption>Characteristics:</caption>
@@ -12076,15 +12078,15 @@ <h4><span class="state-name" title="aria-hidden" aria-describedby="desc-aria-hid
 				<tbody>
 					<tr>
 						<th class="value-name" scope="row">false</th>
-						<td class="value-description">The element is exposed to the accessibility <abbr title="application programming interface">API</abbr> as if it was rendered.</td>
+						<td class="value-description">The element's <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-5">hidden</a> state is determined by the user agent based on whether it is rendered. Synonym of <code>undefined</code>.</td>
 					</tr>
 					<tr>
 						<th class="value-name" scope="row">true</th>
-						<td class="value-description">The element is <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-5">hidden</a> from the accessibility <abbr title="application programming interface">API</abbr>.</td>
+						<td class="value-description">The element is <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-6">hidden</a> from the accessibility <abbr title="application programming interface">API</abbr>.</td>
 					</tr>
 					<tr>
 						<th class="value-name" scope="row"><strong class="default">undefined (default)</strong></th>
-						<td class="value-description">The element's <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-6">hidden</a> state is determined by the user agent based on whether it is rendered.</td>
+						<td class="value-description">The element's <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-7">hidden</a> state is determined by the user agent based on whether it is rendered.</td>
 					</tr>
 				</tbody>
 			</table>
@@ -12096,7 +12098,7 @@ <h4><span class="state-name" title="aria-invalid" aria-describedby="desc-aria-in
 				<p>If the value is computed to be invalid or out-of-range, the application author <em class="rfc2119">SHOULD</em> set this <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-attribute">attribute</a> to <code>true</code>. <a data-link-type="dfn|abstract-op" data-type="dfn" href="https://infra.spec.whatwg.org/#user-agent">user agents</a> <em class="rfc2119">SHOULD</em> inform the user of the error. Application authors <em class="rfc2119">SHOULD</em> provide suggestions for corrections if they are known.</p>
 				<p>When the user attempts to submit data involving a field for which <a href="https://w3c.github.io/aria/#aria-required" class="property-reference"><code>aria-required</code></a> is <code>true</code>, authors <em class="rfc2119">MAY</em> use the <a href="https://w3c.github.io/aria/#aria-invalid" class="state-reference"><code>aria-invalid</code></a> attribute to signal there is an error. However, if the user has not attempted to submit the form, authors <em class="rfc2119">SHOULD NOT</em> set the <a href="https://w3c.github.io/aria/#aria-invalid" class="state-reference"><code>aria-invalid</code></a> attribute on required <a href="#dfn-widget" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-widget-25">widgets</a> simply because the user has not yet entered data.</p>
 				<p>For future expansion, the <a href="https://w3c.github.io/aria/#aria-invalid" class="state-reference"><code>aria-invalid</code></a> attribute is a token type. Any value not recognized in the list of allowed <span>values</span> <em class="rfc2119">MUST</em> be treated by user agents as if the value <code>true</code> had been provided. If the attribute is not present, or its value is <code>false</code>, or its value is the empty string, the default value of <code>false</code> applies.</p>
-				<div class="note" role="note" id="issue-container-generatedID-54"><div role="heading" class="note-title marker" id="h-note-54" aria-level="4"><span>Note</span></div><p class="">This state is being deprecated as a global state in ARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-55"><div role="heading" class="note-title marker" id="h-note-55" aria-level="4"><span>Note</span></div><p class="">This state is being deprecated as a global state in ARIA 1.2. In future versions it will only be allowed on roles where it is specifically supported.</p></div>
 			</div>
 			<table class="state-features">
 				<caption>Characteristics:</caption>
@@ -12258,7 +12260,7 @@ <h4><span class="property-name" title="aria-labelledby" aria-describedby="desc-a
 				<p>If the interface is such that it is not possible to have a visible label on the screen, authors <em class="rfc2119">SHOULD</em> use <a href="https://w3c.github.io/aria/#aria-label" class="property-reference"><code>aria-label</code></a> and <em class="rfc2119">SHOULD NOT</em> use <a href="https://w3c.github.io/aria/#aria-labelledby" class="property-reference"><code>aria-labelledby</code></a>. Authors <em class="rfc2119">MUST NOT</em> specify <code>aria-labelledby</code> on an element which has an explicit or implicit <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> role where <code>aria-labelledby</code> is <a href="#prohibitedattributes">prohibited</a>. As required by the <a href="#textalternativecomputation">accessible name and description computation</a>, user agents give precedence to <a href="https://w3c.github.io/aria/#aria-labelledby" class="property-reference"><code>aria-labelledby</code></a> over <a href="https://w3c.github.io/aria/#aria-label" class="property-reference"><code>aria-label</code></a> when computing the accessible name property.</p>
 				<p>The <a href="https://w3c.github.io/aria/#aria-labelledby" class="property-reference"><code>aria-labelledby</code></a> attribute is similar to <a href="https://w3c.github.io/aria/#aria-describedby" class="property-reference"><code>aria-describedby</code></a> in that both reference other elements to calculate a text alternative (an accessible name, and description, respectively). While a concise accessible name is preferable, a description can either be concise, or provide more verbose information.</p>
 				
-				<div class="note" role="note" id="issue-container-generatedID-55"><div role="heading" class="note-title marker" id="h-note-55" aria-level="4"><span>Note</span></div><p class="">The expected spelling of this property in <abbr title="United States">U.S.</abbr> English is "labeledby." However, the <a href="#dfn-accessibility-api" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-accessibility-api-28">accessibility <abbr title="Application Programing Interfaces">API</abbr></a> features to which this property is mapped have established the "labelledby" spelling. This property is spelled that way to match the convention and minimize the difficulty for developers.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-56"><div role="heading" class="note-title marker" id="h-note-56" aria-level="4"><span>Note</span></div><p class="">The expected spelling of this property in <abbr title="United States">U.S.</abbr> English is "labeledby." However, the <a href="#dfn-accessibility-api" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-accessibility-api-28">accessibility <abbr title="Application Programing Interfaces">API</abbr></a> features to which this property is mapped have established the "labelledby" spelling. This property is spelled that way to match the convention and minimize the difficulty for developers.</p></div>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>
@@ -12293,8 +12295,8 @@ <h4><span class="property-name" title="aria-level" aria-describedby="desc-aria-l
 				<p>Levels increase with depth. If the <abbr title="Document Object Model">DOM</abbr> ancestry does not accurately represent the level, authors <em class="rfc2119">SHOULD</em> explicitly define the <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-attribute">attribute</a>.</p>
 				<p>This attribute is applied to elements that act as leaf nodes within the orientation of the set, for example, on elements with role <a href="https://w3c.github.io/aria/#treeitem" class="role-reference"><code>treeitem</code></a> rather than elements with role <a href="https://w3c.github.io/aria/#group" class="role-reference"><code>group</code></a>. This means that multiple elements in a set can have the same value for this attribute. Although it would be less repetitive to provide a single value on the container, restricting this to leaf nodes ensures that there is a single way for <a href="#dfn-assistive-technologies" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-assistive-technologies-69">assistive technologies</a> to use the attribute.</p>
 				<p>If the <abbr title="Document Object Model">DOM</abbr> ancestry accurately represents the level, the <a data-type="dfn" href="https://infra.spec.whatwg.org/#user-agent">user agent</a> can calculate the level of an item from the document structure. This attribute can be used to provide an explicit indication of the level when that is not possible to calculate from the document structure or the <a href="https://w3c.github.io/aria/#aria-owns" class="property-reference"><code>aria-owns</code></a> attribute. User agent support for automatic calculation of level might vary; authors <em class="rfc2119">SHOULD</em> test with <a data-link-type="dfn|abstract-op" data-type="dfn" href="https://infra.spec.whatwg.org/#user-agent">user agents</a> and assistive technologies to determine whether this attribute is needed. If the author intends for the user agent to calculate the level, the author <em class="rfc2119">SHOULD</em> omit this attribute.</p>
-                <div class="note" role="note" id="issue-container-generatedID-56"><div role="heading" class="note-title marker" id="h-note-56" aria-level="4"><span>Note</span></div><p class=""> In the case of a <a href="https://w3c.github.io/aria/#treegrid" class="role-reference"><code>treegrid</code></a>, <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> is supported on elements with the role <a href="https://w3c.github.io/aria/#row" class="role-reference"><code>row</code></a>, not elements with role <a href="https://w3c.github.io/aria/#gridcell" class="role-reference"><code>gridcell</code></a>. At first glance, this might seem inconsistent with the application of <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> on <a href="https://w3c.github.io/aria/#treeitem" class="role-reference"><code>treeitem</code></a> elements, but it is consistent in that the <a href="https://w3c.github.io/aria/#row" class="role-reference"><code>row</code></a> acts as the leaf node within the vertical orientation of the <a href="https://w3c.github.io/aria/#grid" class="role-reference"><code>grid</code></a>, whereas the <a href="https://w3c.github.io/aria/#gridcell" class="role-reference"><code>gridcell</code></a> is a leaf node within the horizontal orientation of each <a href="https://w3c.github.io/aria/#row" class="role-reference"><code>row</code></a>. Level is not supported on sets of cells within rows, so the <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> attribute is applied to the element with the role <a href="https://w3c.github.io/aria/#row" class="role-reference"><code>row</code></a>.</p></div>
-<div class="note" role="note" id="issue-container-generatedID-57"><div role="heading" class="note-title marker" id="h-note-57" aria-level="4"><span>Note</span></div><p class="">On elements with role <a href="https://w3c.github.io/aria/#heading" class="property-reference"><code>heading</code></a>, values for <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> above 6 can create difficulties for users. Also, at the time of this writing, most combinations of user agents and assistive technologies only support <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> integers 1-9 on headings.</p></div>
+                <div class="note" role="note" id="issue-container-generatedID-57"><div role="heading" class="note-title marker" id="h-note-57" aria-level="4"><span>Note</span></div><p class=""> In the case of a <a href="https://w3c.github.io/aria/#treegrid" class="role-reference"><code>treegrid</code></a>, <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> is supported on elements with the role <a href="https://w3c.github.io/aria/#row" class="role-reference"><code>row</code></a>, not elements with role <a href="https://w3c.github.io/aria/#gridcell" class="role-reference"><code>gridcell</code></a>. At first glance, this might seem inconsistent with the application of <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> on <a href="https://w3c.github.io/aria/#treeitem" class="role-reference"><code>treeitem</code></a> elements, but it is consistent in that the <a href="https://w3c.github.io/aria/#row" class="role-reference"><code>row</code></a> acts as the leaf node within the vertical orientation of the <a href="https://w3c.github.io/aria/#grid" class="role-reference"><code>grid</code></a>, whereas the <a href="https://w3c.github.io/aria/#gridcell" class="role-reference"><code>gridcell</code></a> is a leaf node within the horizontal orientation of each <a href="https://w3c.github.io/aria/#row" class="role-reference"><code>row</code></a>. Level is not supported on sets of cells within rows, so the <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> attribute is applied to the element with the role <a href="https://w3c.github.io/aria/#row" class="role-reference"><code>row</code></a>.</p></div>
+<div class="note" role="note" id="issue-container-generatedID-58"><div role="heading" class="note-title marker" id="h-note-58" aria-level="4"><span>Note</span></div><p class="">On elements with role <a href="https://w3c.github.io/aria/#heading" class="property-reference"><code>heading</code></a>, values for <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> above 6 can create difficulties for users. Also, at the time of this writing, most combinations of user agents and assistive technologies only support <a href="https://w3c.github.io/aria/#aria-level" class="property-reference"><code>aria-level</code></a> integers 1-9 on headings.</p></div>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>
@@ -12444,7 +12446,7 @@ <h4><span class="property-name" title="aria-multiline" aria-describedby="desc-ar
 			<div class="property-description" id="desc-aria-multiline" role="definition">
 				<p><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-indicates-15">Indicates</a> whether a text box accepts multiple lines of input or only a single line.</p>
 				
-				<div class="note" role="note" id="issue-container-generatedID-58"><div role="heading" class="note-title marker" id="h-note-58" aria-level="4"><span>Note</span></div><p class="">In most user agent implementations, the default behavior of the <kbd>ENTER</kbd> or <kbd>RETURN</kbd> key is different between the single-line and multi-line text fields in <abbr title="Hypertext Markup Language">HTML</abbr>. When user has focus in a single-line <code>&lt;input type="text"&gt;</code> element, the keystroke usually submits the form. When user has focus in a multi-line <code>&lt;textarea&gt;</code> element, the keystroke inserts a line break. The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <code>textbox</code> role differentiates these types of boxes with the <a href="https://w3c.github.io/aria/#aria-multiline" class="property-reference"><code>aria-multiline</code></a> attribute, so authors are advised to be aware of this distinction when designing the field.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-59"><div role="heading" class="note-title marker" id="h-note-59" aria-level="4"><span>Note</span></div><p class="">In most user agent implementations, the default behavior of the <kbd>ENTER</kbd> or <kbd>RETURN</kbd> key is different between the single-line and multi-line text fields in <abbr title="Hypertext Markup Language">HTML</abbr>. When user has focus in a single-line <code>&lt;input type="text"&gt;</code> element, the keystroke usually submits the form. When user has focus in a multi-line <code>&lt;textarea&gt;</code> element, the keystroke inserts a line break. The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <code>textbox</code> role differentiates these types of boxes with the <a href="https://w3c.github.io/aria/#aria-multiline" class="property-reference"><code>aria-multiline</code></a> attribute, so authors are advised to be aware of this distinction when designing the field.</p></div>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>
@@ -12501,7 +12503,7 @@ <h4><span class="property-name" title="aria-multiselectable" aria-describedby="d
 			<div class="property-description" id="desc-aria-multiselectable" role="definition">
 				<p><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-indicates-16">Indicates</a> that the user can select more than one item from the current selectable descendants.</p>
 				<p>Authors <em class="rfc2119">SHOULD</em> ensure that selected descendants have the <a href="https://w3c.github.io/aria/#aria-selected" class="state-reference"><code>aria-selected</code></a> <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-attribute">attribute</a> set to <code>true</code>, and selectable descendants that are not selected have the <a href="https://w3c.github.io/aria/#aria-selected" class="state-reference"><code>aria-selected</code></a> attribute set to <code>false</code>. Authors <em class="rfc2119">SHOULD NOT</em> use the <a href="https://w3c.github.io/aria/#aria-selected" class="state-reference"><code>aria-selected</code></a> attribute on descendants that are not selectable.</p>
-				<div class="note" role="note" id="issue-container-generatedID-59"><div role="heading" class="note-title marker" id="h-note-59" aria-level="4"><span>Note</span></div><p class="">Lists and trees are examples of roles that might allow users to select more than one item at a time.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-60"><div role="heading" class="note-title marker" id="h-note-60" aria-level="4"><span>Note</span></div><p class="">Lists and trees are examples of roles that might allow users to select more than one item at a time.</p></div>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>
@@ -12560,7 +12562,7 @@ <h4><span class="property-name" title="aria-multiselectable" aria-describedby="d
 			<h4><span class="property-name" title="aria-orientation" aria-describedby="desc-aria-orientation"><code>aria-orientation</code> <span class="type-indicator">property</span></span></h4>
 			<div class="property-description" id="desc-aria-orientation" role="definition">
 				<p><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-indicates-17">Indicates</a> whether the element's orientation is horizontal, vertical, or unknown/ambiguous.</p>
-				<div class="note" role="note" id="issue-container-generatedID-60"><div role="heading" class="note-title marker" id="h-note-60" aria-level="4"><span>Note</span></div><p class="">In ARIA 1.1, the default value for <a href="https://w3c.github.io/aria/#aria-orientation" class="property-reference"><code>aria-orientation</code></a> changed from <code>horizontal</code> to <code>undefined</code>. Implicit defaults are defined on some roles (e.g., <a href="https://w3c.github.io/aria/#slider" class="role-reference"><code>slider</code></a> defaults to horizontal; <a href="https://w3c.github.io/aria/#scrollbar" class="role-reference"><code>scrollbar</code></a> defaults to vertical) but remain undefined on roles where an expected default orientation is ambiguous (e.g., <a href="https://w3c.github.io/aria/#radiogroup" class="role-reference"><code>radiogroup</code></a>).</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-61"><div role="heading" class="note-title marker" id="h-note-61" aria-level="4"><span>Note</span></div><p class="">In ARIA 1.1, the default value for <a href="https://w3c.github.io/aria/#aria-orientation" class="property-reference"><code>aria-orientation</code></a> changed from <code>horizontal</code> to <code>undefined</code>. Implicit defaults are defined on some roles (e.g., <a href="https://w3c.github.io/aria/#slider" class="role-reference"><code>slider</code></a> defaults to horizontal; <a href="https://w3c.github.io/aria/#scrollbar" class="role-reference"><code>scrollbar</code></a> defaults to vertical) but remain undefined on roles where an expected default orientation is ambiguous (e.g., <a href="https://w3c.github.io/aria/#radiogroup" class="role-reference"><code>radiogroup</code></a>).</p></div>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>
@@ -12663,8 +12665,8 @@ <h4><span class="property-name" title="aria-placeholder" aria-describedby="desc-
 				<p><a href="#dfn-defines" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-defines-13">Defines</a> a short hint (a word or short phrase) intended to aid the user with data entry when the control has no value. A hint could be a sample value or a brief description of the expected format.</p>
 				<p>Authors <em class="rfc2119">SHOULD NOT</em> use <a href="https://w3c.github.io/aria/#aria-placeholder" class="property-reference"><code>aria-placeholder</code></a> instead of a label as their purposes are different: The label indicates what kind of information is expected. The placeholder text is a hint about the expected value. See related <a href="https://w3c.github.io/aria/#aria-labelledby" class="property-reference"><code>aria-labelledby</code></a> and <a href="https://w3c.github.io/aria/#aria-label" class="property-reference"><code>aria-label</code></a>.</p>
 				<p>Authors <em class="rfc2119">SHOULD</em> present this hint to the user by displaying the hint text at any time the control's <span>value</span> is the empty string. This includes cases where the control first receives focus, and when users remove a previously-entered value.</p>
-				<div class="note" role="note" id="issue-container-generatedID-61"><div role="heading" class="note-title marker" id="h-note-61" aria-level="4"><span>Note</span></div><p class="">As is the case with the related <code><code><a data-link-type="element-attr" data-type="element-attr" href="https://html.spec.whatwg.org/multipage/input.html#attr-input-placeholder">placeholder</a></code></code> attribute in <abbr title="Hypertext Markup Language">HTML</abbr>, use of placeholder text as a replacement for a displayed label can reduce the accessibility and usability of the control for a range of users including older users and users with cognitive, mobility, fine motor skill or vision impairments. While the hint given by the control's label is shown at all times, the short hint given in the placeholder attribute is only shown before the user enters a value. Furthermore, placeholder text might be mistaken for a pre-filled value, and as commonly implemented the default color of the placeholder text provides insufficient contrast and the lack of a separate visible label reduces the size of the hit region available for setting focus on the control.</p></div>
-				<div class="note" role="note" id="issue-container-generatedID-62"><div role="heading" class="note-title marker" id="h-note-62" aria-level="4"><span>Note</span></div><p class="">The following examples do not use the <abbr title="Hypertext Markup Language">HTML</abbr> <code>label</code> element as it cannot be used to label <abbr title="Hypertext Markup Language">HTML</abbr> elements with <code>contenteditable</code>.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-62"><div role="heading" class="note-title marker" id="h-note-62" aria-level="4"><span>Note</span></div><p class="">As is the case with the related <code><code><a data-link-type="element-attr" data-type="element-attr" href="https://html.spec.whatwg.org/multipage/input.html#attr-input-placeholder">placeholder</a></code></code> attribute in <abbr title="Hypertext Markup Language">HTML</abbr>, use of placeholder text as a replacement for a displayed label can reduce the accessibility and usability of the control for a range of users including older users and users with cognitive, mobility, fine motor skill or vision impairments. While the hint given by the control's label is shown at all times, the short hint given in the placeholder attribute is only shown before the user enters a value. Furthermore, placeholder text might be mistaken for a pre-filled value, and as commonly implemented the default color of the placeholder text provides insufficient contrast and the lack of a separate visible label reduces the size of the hit region available for setting focus on the control.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-63"><div role="heading" class="note-title marker" id="h-note-63" aria-level="4"><span>Note</span></div><p class="">The following examples do not use the <abbr title="Hypertext Markup Language">HTML</abbr> <code>label</code> element as it cannot be used to label <abbr title="Hypertext Markup Language">HTML</abbr> elements with <code>contenteditable</code>.</p></div>
 				<p>The following example shows a <a href="https://w3c.github.io/aria/#searchbox" class="role-reference"><code>searchbox</code></a> in which the user has entered a value:</p>
 				<div class="example" id="example-33">
         <div class="marker">
@@ -12918,8 +12920,8 @@ <h4><span class="property-name" title="aria-relevant" aria-describedby="desc-ari
 				<p><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-indicates-19">Indicates</a> what notifications the user agent will trigger when the <a href="#dfn-accessibility-tree" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-accessibility-tree-4">accessibility tree</a> within a live region is modified. See related <a href="https://w3c.github.io/aria/#aria-atomic" class="property-reference"><code>aria-atomic</code></a>.</p>
 				<p>The <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-attribute">attribute</a> is represented as a space-separated list of the following <span>values</span>: <code>additions</code>, <code>removals</code>, <code>text</code>; or a single catch-all value <code>all</code>.</p>
 				<p>This is used to describe <a href="#dfn-semantics" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-semantics-6">semantically</a> meaningful changes, as opposed to merely presentational ones. For example, nodes that are removed from the top of a log are merely removed for purposes of creating room for other entries, and the removal of them does not have meaning. However, in the case of a buddy list, removal of a buddy name indicates that they are no longer online, and this is a meaningful <a href="#dfn-event" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-event-9">event</a>. In that case <a href="https://w3c.github.io/aria/#aria-relevant" class="property-reference"><code>aria-relevant</code></a> will be set to <code>all</code>. When the <a href="https://w3c.github.io/aria/#aria-relevant" class="property-reference"><code>aria-relevant</code></a> attribute is not provided, the default value, <code>additions text</code>, indicates that text modifications and node additions are relevant, but that node removals are irrelevant.</p>
-				<div class="note" role="note" id="issue-container-generatedID-63"><div role="heading" class="note-title marker" id="h-note-63" aria-level="4"><span>Note</span></div><p class=""><a href="https://w3c.github.io/aria/#aria-relevant" class="property-reference"><code>aria-relevant</code></a> values of removals or all are to be used sparingly. Assistive technologies only need to be informed of content removal when its removal represents an important change, such as a buddy leaving a chat room.</p></div>
-				<div class="note" role="note" id="issue-container-generatedID-64"><div role="heading" class="note-title marker" id="h-note-64" aria-level="4"><span>Note</span></div><p class="">Text removals should only be considered relevant if one of the specified values is 'removals' or 'all'. For example, for a text change from 'foo' to 'bar' in a live region with a default <a href="https://w3c.github.io/aria/#aria-relevant" class="property-reference"><code>aria-relevant</code></a> value, the text addition ('bar') would be spoken, but the text removal ('foo') would not.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-64"><div role="heading" class="note-title marker" id="h-note-64" aria-level="4"><span>Note</span></div><p class=""><a href="https://w3c.github.io/aria/#aria-relevant" class="property-reference"><code>aria-relevant</code></a> values of removals or all are to be used sparingly. Assistive technologies only need to be informed of content removal when its removal represents an important change, such as a buddy leaving a chat room.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-65"><div role="heading" class="note-title marker" id="h-note-65" aria-level="4"><span>Note</span></div><p class="">Text removals should only be considered relevant if one of the specified values is 'removals' or 'all'. For example, for a text change from 'foo' to 'bar' in a live region with a default <a href="https://w3c.github.io/aria/#aria-relevant" class="property-reference"><code>aria-relevant</code></a> value, the text addition ('bar') would be spoken, but the text removal ('foo') would not.</p></div>
 				<p><a href="https://w3c.github.io/aria/#aria-relevant" class="property-reference"><code>aria-relevant</code></a> is an optional attribute of live regions. This is a suggestion to <a href="#dfn-assistive-technologies" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-assistive-technologies-72">assistive technologies</a>, but assistive technologies are not required to present changes of all the relevant types.</p>
 				<p>When <a href="https://w3c.github.io/aria/#aria-relevant" class="property-reference"><code>aria-relevant</code></a> is not defined, an element's value is inherited from the nearest ancestor with a defined value. Although the value is a <a href="#valuetype_token_list">token list</a>, inherited values are not additive; the value provided on a descendant element completely overrides any inherited value from an ancestor element.</p>
 				<p>When text changes are denoted as relevant, user agents <em class="rfc2119">MUST</em> monitor any descendant node change that affects the <a href="#textalternativecomputation">accessible name and description computation</a> of the live region as if the accessible name were determined from contents (<a href="#namecalculation">nameFrom: contents</a>). For example, a text change would be triggered if the <abbr title="Hypertext Markup Language">HTML</abbr> <code>alt</code> attribute of a contained image changed. However, no change would be triggered if there was a text change to a node outside the live region, even if that node was referenced (via <a href="https://w3c.github.io/aria/#aria-labelledby" class="property-reference"><code>aria-labelledby</code></a>) by an element contained in the live region.</p>
@@ -12982,7 +12984,7 @@ <h4><span class="property-name" title="aria-required" aria-describedby="desc-ari
 			<div class="property-description" id="desc-aria-required" role="definition">
 				<p><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-indicates-20">Indicates</a> that user input is required on the <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a> before a form can be submitted.</p>
 				<p>For example, if the user needs to fill in an address field, the author will need to set the field's <a href="https://w3c.github.io/aria/#aria-required" class="property-reference"><code>aria-required</code></a> attribute to <code>true</code>.</p>
-				<div class="note" role="note" id="issue-container-generatedID-65"><div role="heading" class="note-title marker" id="h-note-65" aria-level="4"><span>Note</span></div><p class="">The fact that the element is required is often presented visually (such as a sign or symbol after the <a href="#dfn-widget" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-widget-27">widget</a>). Using the <a href="https://w3c.github.io/aria/#aria-required" class="property-reference"><code>aria-required</code></a> <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-attribute">attribute</a> allows the author to explicitly convey to <a href="#dfn-assistive-technologies" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-assistive-technologies-73">assistive technologies</a> that an element is required.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-66"><div role="heading" class="note-title marker" id="h-note-66" aria-level="4"><span>Note</span></div><p class="">The fact that the element is required is often presented visually (such as a sign or symbol after the <a href="#dfn-widget" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-widget-27">widget</a>). Using the <a href="https://w3c.github.io/aria/#aria-required" class="property-reference"><code>aria-required</code></a> <a data-type="dfn" href="https://dom.spec.whatwg.org/#concept-attribute">attribute</a> allows the author to explicitly convey to <a href="#dfn-assistive-technologies" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-assistive-technologies-73">assistive technologies</a> that an element is required.</p></div>
 				<p>Unless an exactly equivalent native attribute is available, host languages <em class="rfc2119">SHOULD</em> allow authors to use the <a href="https://w3c.github.io/aria/#aria-required" class="property-reference"><code>aria-required</code></a> attribute on host language form elements that require input or selection by the user.</p>
 			</div>
 			<table class="property-features">
@@ -13060,7 +13062,7 @@ <h4><span class="property-name" title="aria-roledescription" aria-describedby="d
 					<li>The element to which <code>aria-roledescription</code> is applied has a valid <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role or has an implicit <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> role semantic.</li>
 					<li>The value of <code>aria-roledescription</code> is not empty or does not contain only <a data-link-type="dfn|abstract-op" data-lt="ascii whitespace" data-type="dfn" href="https://infra.spec.whatwg.org/#ascii-whitespace">whitespace</a> characters.</li>
 				</ol>
-				<div class="note" role="note" id="issue-container-generatedID-66"><div role="heading" class="note-title marker" id="h-note-66" aria-level="4"><span>Note</span></div><p class="">Depending on the assistive technology, user verbosity settings, or other factors, certain elements' role descriptions might not be conveyed. If specifying <code>aria-roledescription</code> on such elements, then the custom role descriptions might also not be conveyed by these assistive technologies.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-67"><div role="heading" class="note-title marker" id="h-note-67" aria-level="4"><span>Note</span></div><p class="">Depending on the assistive technology, user verbosity settings, or other factors, certain elements' role descriptions might not be conveyed. If specifying <code>aria-roledescription</code> on such elements, then the custom role descriptions might also not be conveyed by these assistive technologies.</p></div>
 				<p>Additionally, authors <em class="rfc2119">MUST NOT</em> specify <code>aria-roledescription</code> on an element which has an explicit or implicit <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> role where <code>aria-roledescription</code> is <a href="#prohibitedattributes">prohibited</a>.</p>
 				<p>User agents <em class="rfc2119">MUST NOT</em> expose the <code>aria-roledescription</code> property if any of the following conditions exist:</p>
 				<ol>
@@ -13580,7 +13582,7 @@ <h4><span class="property-name" title="aria-valuemax" aria-describedby="desc-ari
 			<div class="property-description" id="desc-aria-valuemax" role="definition">
 				<p><a href="#dfn-defines" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-defines-21">Defines</a> the maximum allowed value for a range <a href="#dfn-widget" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-widget-29">widget</a>.</p>
 				<p>Authors <em class="rfc2119">MUST</em> ensure the value of <a href="https://w3c.github.io/aria/#aria-valuemax" class="property-reference"><code>aria-valuemax</code></a> is greater than or equal to the value of <a href="https://w3c.github.io/aria/#aria-valuemin" class="property-reference"><code>aria-valuemin</code></a>. If the <a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a> has a known maximum and minimum, the author <em class="rfc2119">SHOULD</em> provide properties for <a href="https://w3c.github.io/aria/#aria-valuemax" class="property-reference"><code>aria-valuemax</code></a> and <a href="https://w3c.github.io/aria/#aria-valuemin" class="property-reference"><code>aria-valuemin</code></a>.</p>
-				<div class="note" role="note" id="issue-container-generatedID-67"><div role="heading" class="note-title marker" id="h-note-67" aria-level="4"><span>Note</span></div><p class="">A range widget starts with a given value, which can be increased until reaching the maximum value, defined by this <a data-link-type="dfn|abstract-op" href="#dfn-property" class="internalDFN" id="ref-for-dfn-property-27">property</a>. Declaring the minimum and maximum <span>values</span> allows assistive technology to convey the size of the range to users.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-68"><div role="heading" class="note-title marker" id="h-note-68" aria-level="4"><span>Note</span></div><p class="">A range widget starts with a given value, which can be increased until reaching the maximum value, defined by this <a data-link-type="dfn|abstract-op" href="#dfn-property" class="internalDFN" id="ref-for-dfn-property-27">property</a>. Declaring the minimum and maximum <span>values</span> allows assistive technology to convey the size of the range to users.</p></div>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>
@@ -13629,7 +13631,7 @@ <h4><span class="property-name" title="aria-valuemin" aria-describedby="desc-ari
 			<div class="property-description" id="desc-aria-valuemin" role="definition">
 				<p><a href="#dfn-defines" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-defines-22">Defines</a> the minimum allowed value for a range <a href="#dfn-widget" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-widget-30">widget</a>.</p>
 				<p>Authors <em class="rfc2119">MUST</em> ensure the value of <a href="https://w3c.github.io/aria/#aria-valuemin" class="property-reference"><code>aria-valuemin</code></a> is less than or equal to the value of <a href="https://w3c.github.io/aria/#aria-valuemax" class="property-reference"><code>aria-valuemax</code></a>. If the <a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a> has a known maximum and minimum, the author <em class="rfc2119">SHOULD</em> provide properties for <a href="https://w3c.github.io/aria/#aria-valuemax" class="property-reference"><code>aria-valuemax</code></a> and <a href="https://w3c.github.io/aria/#aria-valuemin" class="property-reference"><code>aria-valuemin</code></a>.</p>
-				<div class="note" role="note" id="issue-container-generatedID-68"><div role="heading" class="note-title marker" id="h-note-68" aria-level="4"><span>Note</span></div><p class="">A range widget starts with a given value, which can be decreased until reaching the minimum value, defined by this <a data-link-type="dfn|abstract-op" href="#dfn-property" class="internalDFN" id="ref-for-dfn-property-28">property</a>. Declaring the minimum and maximum <span>values</span> allows assistive technology to convey the size of the range to users.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-69"><div role="heading" class="note-title marker" id="h-note-69" aria-level="4"><span>Note</span></div><p class="">A range widget starts with a given value, which can be decreased until reaching the minimum value, defined by this <a data-link-type="dfn|abstract-op" href="#dfn-property" class="internalDFN" id="ref-for-dfn-property-28">property</a>. Declaring the minimum and maximum <span>values</span> allows assistive technology to convey the size of the range to users.</p></div>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>
@@ -13682,7 +13684,7 @@ <h4><span class="property-name" title="aria-valuenow" aria-describedby="desc-ari
 				<p>The value of <a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a> is a decimal number. If the range is a set of numeric values, then <a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a> is one of those values. For example, if the range is [0, 1], a valid <a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a> is 0.5. A value outside the range, such as -2.5 or 1.1, is invalid.</p>
 				<p>For <a href="https://w3c.github.io/aria/#progressbar" class="role-reference"><code>progressbar</code></a> elements and <a href="https://w3c.github.io/aria/#scrollbar" class="role-reference"><code>scrollbar</code></a> elements, assistive technologies <em class="rfc2119">SHOULD</em> render the value to users as a percent, calculated as a position on the range from <a href="https://w3c.github.io/aria/#aria-valuemin" class="property-reference"><code>aria-valuemin</code></a> to <a href="https://w3c.github.io/aria/#aria-valuemax" class="property-reference"><code>aria-valuemax</code></a> if both are defined, otherwise the actual value with a percent indicator. For elements with role <a href="https://w3c.github.io/aria/#slider" class="role-reference"><code>slider</code></a> and <a href="https://w3c.github.io/aria/#spinbutton" class="role-reference"><code>spinbutton</code></a>, assistive technologies <em class="rfc2119">SHOULD</em> render the actual value to users.</p>
 				<p>When the rendered value cannot be accurately represented as a number, authors <em class="rfc2119">SHOULD</em> use the <a href="https://w3c.github.io/aria/#aria-valuetext" class="property-reference"><code>aria-valuetext</code></a> attribute in conjunction with <a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a> to provide a user-friendly representation of the range's current value. For example, a slider might have rendered values of <code>small</code>, <code>medium</code>, and <code>large</code>. In this case, the values of <a href="https://w3c.github.io/aria/#aria-valuetext" class="property-reference"><code>aria-valuetext</code></a> would be one of the strings: <code>small</code>, <code>medium</code>, or <code>large</code>.</p>
-				<div class="note" role="note" id="issue-container-generatedID-69"><div role="heading" class="note-title marker" id="h-note-69" aria-level="4"><span>Note</span></div><p class="">If <a href="https://w3c.github.io/aria/#aria-valuetext" class="property-reference"><code>aria-valuetext</code></a> is specified, assistive technologies render that instead of the value of <a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a>.</p></div>
+				<div class="note" role="note" id="issue-container-generatedID-70"><div role="heading" class="note-title marker" id="h-note-70" aria-level="4"><span>Note</span></div><p class="">If <a href="https://w3c.github.io/aria/#aria-valuetext" class="property-reference"><code>aria-valuetext</code></a> is specified, assistive technologies render that instead of the value of <a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a>.</p></div>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>
@@ -13814,15 +13816,15 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 	  
           <p>If not excluded from the accessibility tree per the rules above in <a href="#tree_exclusion">Excluding Elements in the Accessibility Tree</a>, user agents <em class="rfc2119">MUST</em> provide an <a href="#dfn-accessible-object" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-accessible-object-2">accessible object</a> in the <a class="termref informative internalDFN" href="#dfn-accessibility-tree" data-link-type="dfn" id="ref-for-dfn-accessibility-tree-11">accessibility tree</a> for <abbr title="Document Object Model">DOM</abbr> <a data-link-type="dfn|abstract-op" data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">elements</a> that meet any of the following criteria:</p>
           <ul>
-            <li>Elements that are not <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-7">hidden</a> and can fire an <a href="#dfn-accessibility-api" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-accessibility-api-30">accessibility <abbr title="Application Program Interface">API</abbr></a> <a href="#dfn-event" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-event-11">event</a>, including:
+            <li>Elements that are not <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-8">hidden</a> and can fire an <a href="#dfn-accessibility-api" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-accessibility-api-30">accessibility <abbr title="Application Program Interface">API</abbr></a> <a href="#dfn-event" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-event-11">event</a>, including:
               <ul>
                 <li>Elements that are currently focused, even if the element or one of its ancestor elements has its <a href="https://w3c.github.io/aria/#aria-hidden" class="state-reference"><code>aria-hidden</code></a> attribute set to <code>true</code>.</li>
                 <li>Elements that are a valid target of an <a href="https://w3c.github.io/aria/#aria-activedescendant" class="property-reference"><code>aria-activedescendant</code></a> attribute.</li>
               </ul>
 	        </li>
             <li>Elements that have an explicit role or a global <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attribute and do not have <a href="https://w3c.github.io/aria/#aria-hidden" class="state-reference"><code>aria-hidden</code></a> set to <code>true</code>. (See <a href="#tree_exclusion">Excluding Elements in the Accessibility Tree</a> for additional guidance on <a href="https://w3c.github.io/aria/#aria-hidden" class="state-reference"><code>aria-hidden</code></a>.)</li>
-            <li>Elements that are not <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-8">hidden</a> and have an ID that is referenced by another element via a <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property.
-            <div class="note" role="note" id="issue-container-generatedID-70"><div role="heading" class="note-title marker" id="h-note-70" aria-level="4"><span>Note</span></div><p class="">Text equivalents for <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-9">hidden</a> referenced objects can still be used in the <a href="https://w3c.github.io/accname/#mapping_additional_nd" class="accname">name and description computation</a> even when not included in the accessibility tree.</p></div>
+            <li>Elements that are not <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-9">hidden</a> and have an ID that is referenced by another element via a <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property.
+            <div class="note" role="note" id="issue-container-generatedID-71"><div role="heading" class="note-title marker" id="h-note-71" aria-level="4"><span>Note</span></div><p class="">Text equivalents for <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-10">hidden</a> referenced objects can still be used in the <a href="https://w3c.github.io/accname/#mapping_additional_nd" class="accname">name and description computation</a> even when not included in the accessibility tree.</p></div>
             </li>
           </ul>
 	</section>
@@ -13939,9 +13941,9 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 			<li>When these attributes appear in a document instance, the attributes will be processed as defined in this specification.</li>
 		</ul>
 		<p>		Host languages that support <cite><a href="https://www.w3.org/TR/2006/REC-xml-names-20060816/">XML Namespaces</a></cite> [<cite><a class="bibref" data-link-type="biblio" href="#bib-xml-names" title="Namespaces in XML 1.0 (Third Edition)">XML-NAMES</a></cite>] <strong><em class="rfc2119">MAY</em></strong> require that <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> attributes be used with a namespace. In this case, the namespace for <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes <strong><em class="rfc2119">MUST</em></strong> be <code>http://www.w3.org/ns/wai-aria/</code>. To use <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> in host languages that do not explicitly describe support for it, authors <strong><em class="rfc2119">SHOULD</em></strong> use this namespace as well, if the host language supports namespaces and there is expectation that user agents will recognize the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> namespace. The namespace prefix is not defined by this specification but generally is expected to be "<code>aria</code>". </p>
-		<div class="note" role="note" id="issue-container-generatedID-71"><div role="heading" class="note-title marker" id="h-note-71" aria-level="4"><span>Note</span></div><p class="">The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes have a naming convention such that they all begin with the string "<code>aria-</code>". This is <em>not</em> a namespace prefix, it is a part of the state or property name. Therefore, when using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties with namespace prefixes, the complete attribute name will be like "<code>aria:aria-foo</code>".</p></div>
+		<div class="note" role="note" id="issue-container-generatedID-72"><div role="heading" class="note-title marker" id="h-note-72" aria-level="4"><span>Note</span></div><p class="">The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes have a naming convention such that they all begin with the string "<code>aria-</code>". This is <em>not</em> a namespace prefix, it is a part of the state or property name. Therefore, when using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties with namespace prefixes, the complete attribute name will be like "<code>aria:aria-foo</code>".</p></div>
 		<p>Some host languages do not use namespaces with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes, either because the host language does not support namespaces or because the designers wish to incorporate <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> into the core feature set. In these host languages, the namespace name for these attributes has no value. The names of these attributes do not have a prefix offset by a colon; in the terms of namespaces they are unprefixed attribute names. The ECMAScript binding of the <abbr title="Document Object Model">DOM</abbr> interface <code>getAttributeNS</code> for example, treats the empty string (<code>""</code>) as representing this condition, so that both <code>getAttribute("aria-busy")</code> and <code>getAttributeNS("", "aria-busy")</code> access the same <a href="https://w3c.github.io/aria/#aria-busy" class="state-reference"><code>aria-busy</code></a> attribute in the <abbr title="Document Object Model">DOM</abbr>.</p>
-		<div class="note" role="note" id="issue-container-generatedID-72"><div role="heading" class="note-title marker" id="h-note-72" aria-level="4"><span>Note</span></div><p class="">According to the requirements of this section, some user agents recognize <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes <em>with</em> namespaces, some <em>without</em> namespaces, and some might recognize both. Authors are advised to be aware of which form is supported for the host language they are using. Unless the host language and supporting user agents explicitly indicate that the namespace is required, authors are advised to use the attribute without namespaces. Even user agents that support namespaces generally do not publish namespaced <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties to accessibility <abbr title="Application Programing Interfaces">APIs</abbr>. In particular, current implementations of <abbr title="Hypertext Markup Language">HTML</abbr>, including <abbr title="Extensible Hypertext Markup Language">XHTML</abbr>, do not support this namespace.</p></div>
+		<div class="note" role="note" id="issue-container-generatedID-73"><div role="heading" class="note-title marker" id="h-note-73" aria-level="4"><span>Note</span></div><p class="">According to the requirements of this section, some user agents recognize <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property attributes <em>with</em> namespaces, some <em>without</em> namespaces, and some might recognize both. Authors are advised to be aware of which form is supported for the host language they are using. Unless the host language and supporting user agents explicitly indicate that the namespace is required, authors are advised to use the attribute without namespaces. Even user agents that support namespaces generally do not publish namespaced <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties to accessibility <abbr title="Application Programing Interfaces">APIs</abbr>. In particular, current implementations of <abbr title="Hypertext Markup Language">HTML</abbr>, including <abbr title="Extensible Hypertext Markup Language">XHTML</abbr>, do not support this namespace.</p></div>
 	</section>
 	<section id="host_general_focus"><div class="header-wrapper"><h3 id="x8-3-focus-navigation"><bdi class="secno">8.3 </bdi>Focus Navigation</h3><a class="self-link" href="#host_general_focus" aria-label="Permalink for Section 8.3"></a></div>
 		
@@ -13994,7 +13996,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 	</section>
 	<section id="document-handling_css-selectors"><div class="header-wrapper"><h3 id="x8-7-css-selectors"><bdi class="secno">8.7 </bdi><abbr title="Cascading Style Sheets">CSS</abbr> Selectors</h3><a class="self-link" href="#document-handling_css-selectors" aria-label="Permalink for Section 8.7"></a></div>
 		
-		<div class="note" role="note" id="issue-container-generatedID-73"><div role="heading" class="note-title marker" id="h-note-73" aria-level="4"><span>Note</span></div><p class="">This section might be removed in a future version.</p></div>
+		<div class="note" role="note" id="issue-container-generatedID-74"><div role="heading" class="note-title marker" id="h-note-74" aria-level="4"><span>Note</span></div><p class="">This section might be removed in a future version.</p></div>
 		<p>Support for <a class="termref informative" data-type="dfn" href="https://dom.spec.whatwg.org/#concept-attribute">attribute</a> selectors <em class="rfc2119">MUST</em> include <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attributes. For example, <samp>.fooMenuItem[aria-haspopup="true"]</samp> would select all <a data-link-type="dfn|abstract-op" data-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">elements</a>  with class <code>fooMenuItem</code>, and <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property <a href="https://w3c.github.io/aria/#aria-haspopup" class="property-reference"><code>aria-haspopup</code></a> with value of <code>true</code>. The presentation <em class="rfc2119">MUST</em> be updated for dynamic changes to <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attributes. This allows authors to match styling with <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> <a href="#dfn-semantics" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-semantics-10">semantics</a>. </p>
 	</section>
 </section>
@@ -14048,7 +14050,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 				</li>
 				<li>Otherwise, ignore the value and treat the property as not present.</li>
 			</ul>
-			<div class="note" role="note" id="issue-container-generatedID-74"><div role="heading" class="note-title marker" id="h-note-74" aria-level="4"><span>Note</span></div><p class="">In <abbr title="User Interface Automation">UIA</abbr>, the user agent might leave the corresponding property set to "unsupported."</p></div>
+			<div class="note" role="note" id="issue-container-generatedID-75"><div role="heading" class="note-title marker" id="h-note-75" aria-level="4"><span>Note</span></div><p class="">In <abbr title="User Interface Automation">UIA</abbr>, the user agent might leave the corresponding property set to "unsupported."</p></div>
 			<p>User agents <em class="rfc2119">MUST NOT</em> expose <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attributes that reference unresolved IDs. For example:</p>
 			<ul>
 				<li>When the state or property has only one ID reference that cannot be resolved, treat as if the state or property is not present.</li>
@@ -14132,7 +14134,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 				</tr>
 			</tbody>
 		</table>
-		<div class="note" role="note" id="issue-container-generatedID-75"><div role="heading" class="note-title marker" id="h-note-75" aria-level="4"><span>Note</span></div><p class="">Implicit values for non-required states and properties appear in the characteristics table for each role. These are not considered fallback values so are not included here.</p></div>
+		<div class="note" role="note" id="issue-container-generatedID-76"><div role="heading" class="note-title marker" id="h-note-76" aria-level="4"><span>Note</span></div><p class="">Implicit values for non-required states and properties appear in the characteristics table for each role. These are not considered fallback values so are not included here.</p></div>
 	</section>
 	<section id="conflict_resolution_presentation_none"><div class="header-wrapper"><h3 id="x9-3-presentational-roles-conflict-resolution"><bdi class="secno">9.3 </bdi>Presentational Roles Conflict Resolution</h3><a class="self-link" href="#conflict_resolution_presentation_none" aria-label="Permalink for Section 9.3"></a></div>
 		
@@ -14223,7 +14225,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 			<li><p><var>idlAttribute</var> must <a data-link-type="dfn|abstract-op" data-type="dfn" href="https://html.spec.whatwg.org/multipage/common-dom-interfaces.html#reflect">reflect</a> <var>contentAttributeName</var> and support <a data-link-type="idl" data-lt="ElementInternals" data-type="interface" href="https://html.spec.whatwg.org/multipage/custom-elements.html#elementinternals"><code>ElementInternals</code></a>.</p></li>
 		</ol>
 
-		<div class="note" role="note" id="issue-container-generatedID-76"><div role="heading" class="note-title marker" id="h-note-76" aria-level="4"><span>Note</span></div><p class="">In practice, this means that, e.g., the <code>role</code> IDL attribute on <code>Element</code> reflects the <code>role</code> content attribute; the <code>ariaValueMin</code> IDL attribute reflects the <a href="https://w3c.github.io/aria/#aria-valuemin" class="property-reference"><code>aria-valuemin</code></a> content attribute; etc. Ambiguity clarifications (such as <code>ariaPosInSet</code>) are listed in <a href="#idl_attr_exceptions">IDL Attribute Name Notes or Exceptions</a>.</p></div>
+		<div class="note" role="note" id="issue-container-generatedID-77"><div role="heading" class="note-title marker" id="h-note-77" aria-level="4"><span>Note</span></div><p class="">In practice, this means that, e.g., the <code>role</code> IDL attribute on <code>Element</code> reflects the <code>role</code> content attribute; the <code>ariaValueMin</code> IDL attribute reflects the <a href="https://w3c.github.io/aria/#aria-valuemin" class="property-reference"><code>aria-valuemin</code></a> content attribute; etc. Ambiguity clarifications (such as <code>ariaPosInSet</code>) are listed in <a href="#idl_attr_exceptions">IDL Attribute Name Notes or Exceptions</a>.</p></div>
 	</section>
 
 	<section id="accessibilityroleandproperties-correspondence" class="normative" data-dfn-for="ARIAMixin" data-link-for="ARIAMixin"><div class="header-wrapper"><h3 id="x10-2-aria-attribute-correspondence"><bdi class="secno">10.2 </bdi>ARIA Attribute Correspondence</h3><a class="self-link" href="#accessibilityroleandproperties-correspondence" aria-label="Permalink for Section 10.2"></a></div>
@@ -14285,7 +14287,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 			<tr><td><dfn data-export="" data-dfn-type="attribute" id="dom-ariamixin-ariavaluenow" data-idl="attribute" data-title="ariaValueNow" data-dfn-for="ARIAMixin" data-type="DOMString" data-lt="ariaValueNow" data-local-lt="ARIAMixin.ariaValueNow" tabindex="0" aria-haspopup="dialog"><code>ariaValueNow</code></dfn></td><td><a href="https://w3c.github.io/aria/#aria-valuenow" class="property-reference"><code>aria-valuenow</code></a></td></tr>
 			<tr><td><dfn data-export="" data-dfn-type="attribute" id="dom-ariamixin-ariavaluetext" data-idl="attribute" data-title="ariaValueText" data-dfn-for="ARIAMixin" data-type="DOMString" data-lt="ariaValueText" data-local-lt="ARIAMixin.ariaValueText" tabindex="0" aria-haspopup="dialog"><code>ariaValueText</code></dfn></td><td><a href="https://w3c.github.io/aria/#aria-valuetext" class="property-reference"><code>aria-valuetext</code></a></td></tr>
 		</tbody></table>
-		<div class="note" role="note" id="issue-container-generatedID-77"><div role="heading" class="note-title marker" id="h-note-77" aria-level="4"><span>Note</span></div><p class="">Note: Attributes <a href="https://w3c.github.io/aria/#aria-dropeffect" class="property-reference"><code>aria-dropeffect</code></a> and <a href="https://w3c.github.io/aria/#aria-grabbed" class="state-reference"><code>aria-grabbed</code></a> were deprecated in ARIA 1.1 and do not have corresponding IDL attributes.</p></div>
+		<div class="note" role="note" id="issue-container-generatedID-78"><div role="heading" class="note-title marker" id="h-note-78" aria-level="4"><span>Note</span></div><p class="">Note: Attributes <a href="https://w3c.github.io/aria/#aria-dropeffect" class="property-reference"><code>aria-dropeffect</code></a> and <a href="https://w3c.github.io/aria/#aria-grabbed" class="state-reference"><code>aria-grabbed</code></a> were deprecated in ARIA 1.1 and do not have corresponding IDL attributes.</p></div>
 
 		<section class="informative" id="idl_attr_disambiguation"><div class="header-wrapper"><h4 id="x10-2-1-disambiguation-pattern"><bdi class="secno">10.2.1 </bdi>Disambiguation Pattern</h4><a class="self-link" href="#idl_attr_disambiguation" aria-label="Permalink for Section 10.2.1"></a></div><p><em>This section is non-normative.</em></p>
 			
@@ -14356,8 +14358,8 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 </section>
 <section class="informative appendix" id="typemapping"><div class="header-wrapper"><h2 id="a-mapping-wai-aria-value-types-to-languages"><bdi class="secno">A. </bdi>Mapping <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> Value types to languages</h2><a class="self-link" href="#typemapping" aria-label="Permalink for Appendix A."></a></div><p><em>This section is non-normative.</em></p>
 	
-	<div class="note" role="note" id="issue-container-generatedID-78"><div role="heading" class="note-title marker" id="h-note-78" aria-level="3"><span>Note</span></div><p class="">The <abbr title="Hypertext Markup Language">HTML</abbr> column of the table below is advisory. Guidance on use of <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> state and properties in <abbr title="Hypertext Markup Language">HTML</abbr> is provided in <a href="https://www.w3.org/TR/html-aria/#docconformance">Document conformance requirements for use of ARIA attributes in <abbr title="Hypertext Markup Language">HTML</abbr></a> ([<cite><a class="bibref" data-link-type="biblio" href="#bib-html-aria" title="ARIA in HTML">HTML-ARIA</a></cite>]).</p></div>
-	<div class="note" role="note" id="issue-container-generatedID-79"><div role="heading" class="note-title marker" id="h-note-79" aria-level="3"><span>Note</span></div><p class="">The suggested mappings for true/false values in <abbr title="Hypertext Markup Language">HTML</abbr> use <a href="https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#keywords-and-enumerated-attributes">Keyword and enumerated attributes</a> with allowed values of <code>true</code> and <code>false</code>, instead of using the <abbr title="Hypertext Markup Language">HTML</abbr> boolean value type. </p></div>
+	<div class="note" role="note" id="issue-container-generatedID-79"><div role="heading" class="note-title marker" id="h-note-79" aria-level="3"><span>Note</span></div><p class="">The <abbr title="Hypertext Markup Language">HTML</abbr> column of the table below is advisory. Guidance on use of <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> state and properties in <abbr title="Hypertext Markup Language">HTML</abbr> is provided in <a href="https://www.w3.org/TR/html-aria/#docconformance">Document conformance requirements for use of ARIA attributes in <abbr title="Hypertext Markup Language">HTML</abbr></a> ([<cite><a class="bibref" data-link-type="biblio" href="#bib-html-aria" title="ARIA in HTML">HTML-ARIA</a></cite>]).</p></div>
+	<div class="note" role="note" id="issue-container-generatedID-80"><div role="heading" class="note-title marker" id="h-note-80" aria-level="3"><span>Note</span></div><p class="">The suggested mappings for true/false values in <abbr title="Hypertext Markup Language">HTML</abbr> use <a href="https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#keywords-and-enumerated-attributes">Keyword and enumerated attributes</a> with allowed values of <code>true</code> and <code>false</code>, instead of using the <abbr title="Hypertext Markup Language">HTML</abbr> boolean value type. </p></div>
 	<p>The table below provides recommended mappings between <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> state and property types and attribute types from <cite><a data-matched-text="[[[HTML]]]" href="https://html.spec.whatwg.org/multipage/">HTML Standard</a></cite> and <cite><a data-matched-text="[[[XMLSCHEMA11-2]]]" href="https://www.w3.org/TR/xmlschema11-2/">W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes</a></cite>.</p>
 	<p>Languages not listed below might have appropriate value types defined in the language. If they do not, we recommend XML Schema Datatypes for general purpose XML languages. Documents using DTDs instead of schemas will not be able to validate automatically and require additional processing on <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attributes.</p>
 	<table>
@@ -14715,7 +14717,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
 <section id="references" class="appendix"><div class="header-wrapper"><h2 id="d-references"><bdi class="secno">D. </bdi>References</h2><a class="self-link" href="#references" aria-label="Permalink for Appendix D."></a></div><section id="normative-references"><div class="header-wrapper"><h3 id="d-1-normative-references"><bdi class="secno">D.1 </bdi>Normative references</h3><a class="self-link" href="#normative-references" aria-label="Permalink for Appendix D.1"></a></div>
     
     <dl class="bibliography"><dt id="bib-accname-1.2">[ACCNAME-1.2]</dt><dd>
-      <a href="https://www.w3.org/TR/accname-1.2/"><cite>Accessible Name and Description Computation 1.2</cite></a>. Bryan Garaventa; Melanie Sumner.  W3C. 3 April 2024. W3C Working Draft. URL: <a href="https://www.w3.org/TR/accname-1.2/">https://www.w3.org/TR/accname-1.2/</a>
+      <a href="https://www.w3.org/TR/accname-1.2/"><cite>Accessible Name and Description Computation 1.2</cite></a>. Bryan Garaventa; Melanie Sumner.  W3C. 29 April 2024. W3C Working Draft. URL: <a href="https://www.w3.org/TR/accname-1.2/">https://www.w3.org/TR/accname-1.2/</a>
     </dd><dt id="bib-core-aam">[CORE-AAM]</dt><dd>
       <a href="https://www.w3.org/TR/core-aam-1.1/"><cite>Core Accessibility API Mappings 1.1</cite></a>. Joanmarie Diggs; Joseph Scheuhammer; Richard Schwerdtfeger; Michael Cooper; Andi Snow-Weaver; Aaron Leventhal.  W3C. 14 December 2017. W3C Recommendation. URL: <a href="https://www.w3.org/TR/core-aam-1.1/">https://www.w3.org/TR/core-aam-1.1/</a>
     </dd><dt id="bib-core-aam-1.2">[CORE-AAM-1.2]</dt><dd>
@@ -14758,7 +14760,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
     </dd><dt id="bib-fingerprinting-guidance">[fingerprinting-guidance]</dt><dd>
       <a href="https://www.w3.org/TR/fingerprinting-guidance/"><cite>Mitigating Browser Fingerprinting in Web Specifications</cite></a>. Nick Doty.  W3C. 28 March 2019. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/fingerprinting-guidance/">https://www.w3.org/TR/fingerprinting-guidance/</a>
     </dd><dt id="bib-html-aria">[HTML-ARIA]</dt><dd>
-      <a href="https://www.w3.org/TR/html-aria/"><cite>ARIA in HTML</cite></a>. Scott O'Hara; Patrick Lauke.  W3C. 15 April 2024. W3C Recommendation. URL: <a href="https://www.w3.org/TR/html-aria/">https://www.w3.org/TR/html-aria/</a>
+      <a href="https://www.w3.org/TR/html-aria/"><cite>ARIA in HTML</cite></a>. Scott O'Hara; Patrick Lauke.  W3C. 30 April 2024. W3C Recommendation. URL: <a href="https://www.w3.org/TR/html-aria/">https://www.w3.org/TR/html-aria/</a>
     </dd><dt id="bib-iaccessible2">[IAccessible2]</dt><dd>
       <a href="https://wiki.linuxfoundation.org/accessibility/iaccessible2/"><cite>IAccessible2</cite></a>.  Linux Foundation. URL: <a href="https://wiki.linuxfoundation.org/accessibility/iaccessible2/">https://wiki.linuxfoundation.org/accessibility/iaccessible2/</a>
     </dd><dt id="bib-msaa">[MSAA]</dt><dd>
@@ -14975,9 +14977,9 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
     <li>
       <a href="#ref-for-dfn-hidden-1" title="§ 2. Important Terms">§ 2. Important Terms</a> <a href="#ref-for-dfn-hidden-2" title="Reference 2">(2)</a> 
     </li><li>
-      <a href="#ref-for-dfn-hidden-3" title="§ 6.8 Definitions of States and Properties (all aria-* attributes)">§ 6.8 Definitions of States and Properties (all aria-* attributes)</a> <a href="#ref-for-dfn-hidden-4" title="Reference 2">(2)</a> <a href="#ref-for-dfn-hidden-5" title="Reference 3">(3)</a> <a href="#ref-for-dfn-hidden-6" title="Reference 4">(4)</a> 
+      <a href="#ref-for-dfn-hidden-3" title="§ 6.8 Definitions of States and Properties (all aria-* attributes)">§ 6.8 Definitions of States and Properties (all aria-* attributes)</a> <a href="#ref-for-dfn-hidden-4" title="Reference 2">(2)</a> <a href="#ref-for-dfn-hidden-5" title="Reference 3">(3)</a> <a href="#ref-for-dfn-hidden-6" title="Reference 4">(4)</a> <a href="#ref-for-dfn-hidden-7" title="Reference 5">(5)</a> 
     </li><li>
-      <a href="#ref-for-dfn-hidden-7" title="§ 7.2 Including Elements in the Accessibility Tree">§ 7.2 Including Elements in the Accessibility Tree</a> <a href="#ref-for-dfn-hidden-8" title="Reference 2">(2)</a> <a href="#ref-for-dfn-hidden-9" title="Reference 3">(3)</a> 
+      <a href="#ref-for-dfn-hidden-8" title="§ 7.2 Including Elements in the Accessibility Tree">§ 7.2 Including Elements in the Accessibility Tree</a> <a href="#ref-for-dfn-hidden-9" title="Reference 2">(2)</a> <a href="#ref-for-dfn-hidden-10" title="Reference 3">(3)</a> 
     </li>
   </ul>
     </div><div class="dfn-panel" hidden="" role="dialog" aria-modal="true" id="dfn-panel-for-dfn-hide-from-all-users" aria-label="Links in this document to definition: Hidden From All Users">
