You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.html
+48-5
Original file line number
Diff line number
Diff line change
@@ -10761,8 +10761,8 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
10761
10761
<div class="property" id="aria-describedby">
10762
10762
<pdef>aria-describedby</pdef>
10763
10763
<div class="property-description">
10764
-
<p>Identifies the <a>element</a> (or elements) that describes the <a>object</a>. See related <pref>aria-labelledby</pref>.</p>
10765
-
<p>The <pref>aria-labelledby</pref> attribute is similar to the <pref>aria-describedby</pref> in that both reference other elements to calculate a text alternative, but a label should be concise, where a description is intended to provide more verbose information.</p>
10764
+
<p>Identifies the <a>element</a> (or elements) that describes the <a>object</a>. See related <pref>aria-labelledby</pref> and <pref>aria-description</pref>.</p>
10765
+
<p>The <pref>aria-labelledby</pref> attribute is similar to <pref>aria-describedby</pref> in that both reference other elements to calculate a text alternative, but a label should be concise, where a description is intended to provide more verbose information.</p>
10766
10766
<!-- keep previous sentence synced with the associated description in #aria-labelledby -->
10767
10767
<p>The element or elements referenced by the aria-describedby comprise the entire description. Include ID references to multiple elements if necessary, or enclose a set of elements (e.g., paragraphs) with the element referenced by the ID.</p>
10768
10768
</div>
@@ -10800,7 +10800,47 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
10800
10800
</tbody>
10801
10801
</table>
10802
10802
</div>
10803
-
<div class="property" id="aria-details">
10803
+
<div class="property" id="aria-description">
10804
+
<pdef>aria-description</pdef>
10805
+
<div class="property-description">
10806
+
<p>Defines a string value that describes or annotates the current element. See related <pref>aria-describedby</pref>.</p>
10807
+
<p>The <pref>aria-description</pref> attribute is similar to <pref>aria-label</pref> in that both provide a flat string to associate with the element, but a label should be concise, whereas a description is intended to provide more verbose information.</p>
10808
+
<p>The purpose of <pref>aria-description</pref> is the same as that of <pref>aria-describedby</pref>. It provides the user with additional descriptive text for the object. The most common <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> mapping for a description is the <a>accessible description</a> property. User agents MUST give precedence to <pref>aria-describedby</pref> over <pref>aria-description</pref> when computing the accessible description property.</p>
10809
+
<p>In cases where providing a visible description is not the desired user experience, authors MAY set the accessible description of the element using <pref>aria-description</pref>. However, if the description text is available in the DOM, authors SHOULD NOT use <pref>aria-description</pref>, but should use one of the following instead:</p>
10810
+
<ul>
10811
+
<li>Authors SHOULD use <pref>aria-describedby</pref> when the related description or annotation elements contain a simple, small description that is best experienced as a flat string, rather than by having the user navigate to them.</li>
10812
+
<li>Authors SHOULD use <pref>aria-details</pref> when the related description or annotation elements contain useful semantics or structure, or there is a lot of content within them, making it difficult to experience as a flat string. Using <pref>aria-details</pref> will allow assistive technology users to visit the structured content and provide additional navigation commands, making it easier to understand the structure, or to experience the information in smaller pieces.</li>
<td class="property-related"><code>title</code> attribute in [[HTML]]</td>
11507
+
<td class="property-related"></td>
11468
11508
</tr>
11469
11509
<tr>
11470
11510
<th class="property-applicability-head" scope="row">Used in Roles:</th>
@@ -11484,7 +11524,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
11484
11524
<div class="property" id="aria-labelledby">
11485
11525
<pdef>aria-labelledby</pdef>
11486
11526
<div class="property-description">
11487
-
<p>Identifies the <a>element</a> (or elements) that labels the current element. See related <pref>aria-describedby</pref>.</p>
11527
+
<p>Identifies the <a>element</a> (or elements) that labels the current element. See related <pref>aria-label</pref> and <pref>aria-describedby</pref>.</p>
11488
11528
<p>The purpose of <pref>aria-labelledby</pref> is the same as that of <pref>aria-label</pref>. It provides the user with a recognizable name of the object. The most common <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> mapping for a label is the <a>accessible name</a> property.</p>
11489
11529
<p>If the interface is such that it is not possible to have a visible label on the screen, authors SHOULD use <pref>aria-label</pref> and SHOULD NOT use <pref>aria-labelledby</pref>. As required by the <a href="#textalternativecomputation">accessible name and description computation</a>, user agents give precedence to <pref>aria-labelledby</pref> over <pref>aria-label</pref> when computing the accessible name property.</p>
11490
11530
<p>The <pref>aria-labelledby</pref> attribute is similar to <pref>aria-describedby</pref> in that both reference other elements to calculate a text alternative, but a label should be concise, where a description is intended to provide more verbose information.</p>
@@ -12987,6 +13027,7 @@ <h2>Conflicts with Host Language Semantics</h2>
12987
13027
<p>Certain ARIA features are critical to building a complete model in the accessibility API. Such features are not expected to conflict with native host language semantics (though they may complement them). Therefore, host languages MUST NOT declare strong native semantics that prevent use of the following ARIA features:</p>
0 commit comments