Skip to content

Commit

Permalink
Aria-relevant clarifications for #1048
Browse files Browse the repository at this point in the history
  • Loading branch information
jnurthen committed Aug 25, 2022
1 parent ece14a1 commit 49230a3
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -12572,14 +12572,14 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
<div class="property" id="aria-relevant">
<pdef>aria-relevant</pdef>
<div class="property-description">
<p><a>Indicates</a> what notifications the user agent will trigger when the accessibility tree within a live region is modified. See related <pref>aria-atomic</pref>.</p>
<p><a>Indicates</a> what notifications the user agent will trigger when the <a>accessibility tree</a> within a live region is modified. See related <pref>aria-atomic</pref>.</p>
<p>The <a>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>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>event</a>. In that case <pref>aria-relevant</pref> will be set to <code>all</code>. When the <pref>aria-relevant</pref> 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>
<p class="note"><pref>aria-relevant</pref> 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>
<p class="note">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 <pref>aria-relevant</pref> value, the text addition ('bar') would be spoken, but the text removal ('foo') would not.</p>
<p><pref>aria-relevant</pref> is an optional attribute of live regions. This is a suggestion to <a>assistive technologies</a>, but assistive technologies are not required to present changes of all the relevant types.</p>
<p>When <pref>aria-relevant</pref> 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 MUST 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 HTML <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 <pref>aria-labelledby</pref>) by an element contained in the live region.</p>
<p>When text changes are denoted as relevant, user agents MUST 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 of the live region itself were determined from contents (<a href="#namecalculation">nameFrom: contents</a>). For example, a text change would be triggered if the HTML <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 <pref>aria-labelledby</pref>) by an element contained in the live region.</p>
</div>
<table class="property-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -12619,7 +12619,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
<tbody>
<tr>
<th class="value-name" scope="row">additions</th>
<td class="value-description">Element nodes are added to the accessibility tree within the live region.</td>
<td class="value-description">Element nodes are added to the <a>accessibility tree</a> within the live region.</td>
</tr>
<tr>
<th class="value-name" scope="row"><strong class="default">additions text (default)</strong></th>
Expand All @@ -12631,11 +12631,11 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
</tr>
<tr>
<th class="value-name" scope="row">removals</th>
<td class="value-description">Text content, a text alternative, or an element node within the live region is removed from the accessibility tree.</td>
<td class="value-description">Text content, a text alternative, or an element node within the live region is removed from the <a>accessibility tree</a>.</td>
</tr>
<tr>
<th class="value-name" scope="row">text</th>
<td class="value-description">Text content or a text alternative is added to any descendant in the accessibility tree of the live region.</td>
<td class="value-description">Text content or a text alternative is added to any descendant in the <a>accessibility tree</a> of the live region.</td>
</tr>
</tbody>
</table>
Expand Down

0 comments on commit 49230a3

Please sign in to comment.