diff --git a/aria-practices.html b/aria-practices.html index 8ebda53687..92c06a609b 100644 --- a/aria-practices.html +++ b/aria-practices.html @@ -106,7 +106,7 @@

Principle 2: ARIA Can Both Cloak and Enhance, Creating Both Power and Danger

On the other hand, some uses of ARIA are more like suspenders or belts; they add meaning that provides essential support to the original content.


         <button aria-pressed="false">Mute</button>
-
+

This is the power of ARIA. It enables authors to describe nearly any user interface component in ways that assistive technologies can reliably interpret, thus making components accessible to assistive technology users. @@ -3742,7 +3742,7 @@

What ARE Accessible Names and Descriptions?

For example, a switch button named Mute Conversation in the off state could be announced as Mute Conversation switch button off. Because descriptions are optional strings that are usually significantly longer than names, they are presented last, sometimes after a slight delay. For example, Mute Conversation Switch button off, Silences alerts and notifications about activity in this conversation. - To reduce verbosity, some screen readers do not announce descriptions by default but instead inform users of their presence so that users can press a key that will announce the description. + To reduce verbosity, some screen readers do not announce descriptions by default but instead inform users of their presence so that users can press a key that will announce the description.

@@ -4074,7 +4074,7 @@
Naming Tables and Figures with Captions
</figure>

Like with table elements, if a figure is not named using aria-label or aria-labelledby, the content of the figcaption element will be used as the accessible name. - However unlike table elements, if the figcaption element is not used for the name, it does not become an accessible description unless it is referenced by aria-describedby. + However unlike table elements, if the figcaption element is not used for the name, it does not become an accessible description unless it is referenced by aria-describedby. Nevertheless, assistive technologies will render the content of a figcaption regardless of whether it is used as a name, description, or neither.

Using the caption element to name a table element, or a figcaption element to name a figure element, satisfies Rule 2: Prefer Visible Text and Rule 3: Prefer Native Techniques.

@@ -6279,6 +6279,149 @@

Indicating sort order with aria-sort

+
+

Describing Hierarchical Structure with aria-level

+

+ When elements have a hierarchical relationship, such as headers of sections or data in tree structures, aria-level is used to communicate the hierarchy between elements to assistive technologies. + The value of aria-level is numeric, with 1 indicating the top level of the structure. + The number increases for each level of nesting. +

+

Do not use aria-level when the DOM structure already accurately represents the elements' hierarchical relationships.

+

The aria-level attribute can be used on the following roles:

+ +
+

heading Role

+

+ Used together, the aria-level attribute and heading role will be treated the same by assistive technologies as the native HTML header elements: h1, h2, h3, h4, h5 and h6. + Do not use attribute aria-level and heading when a native HTML element can be used. +

+

+ This example uses the heading role and aria-level attribute to communicate levels of headings for a graph created with an SVG. + The headings "Deciduous Trees" and "Evergreen Trees" are both subheadings to "Total Trees". +

+ 
<svg width="1000" height="1000">
+  <text x="10" y="10" role="header" aria-level="1">Total Trees:</text>
+  <text x="10" y="100" role="header" aria-level="2">Deciduous Trees:</text>
+  <text x="10" y="200" role="header" aria-level="2">Evergreen Trees:</text>
+  ...
+</svg>
+
+ +
+

Remediation Uses Cases

+

+ In rare scenarios, legacy code cannot be converted to using HTML header elements. + In these cases, the aria-level attribute and the heading role can be added to the website's header elements to communicate to assitive technologies that those elements should be treated like a native HTML section heading element. +

+

For example, "Definition of a Room" is a subsection of "Housing Specification":

+ 
<div role="heading" aria-level="1" class="header-big">Housing Specification</div>
+<div role="section" aria-labelledby="room-definition">
+  <div role="heading" aria-level="2" id="room-definition" class="header-small">Definition of a Room</div>
+  ...
+</div>
+
+

Equivalent (and preferred) HTML:

+ 
<h1>Housing Specification</h1>
+<section aria-labelledby="room-definition">
+  <h2 id="room-definition">Definition of a Room</h2>
+  ...
+</section>
+
+
+
+ +
+

listitem role

+

+ The aria-level attribute can be used on elements with listitem role to represent list subitems when the structure of the DOM tree does not imply the intended level of nesting. + For example, to quote a item in a nested to-do list, use the 'aria-level' attribute on the list items. +

+ 
<blockquote>
+<ul>
+  <li aria-level="2">Wash Dishes</li>
+</ul>
+</blockquote>
+<p>I can do this item, but I can't do the other clean up items.</p>
+
+
+ +
+

treeitem role

+

The attribute aria-level can be used on elements with role treeitem to explicitly set the level of items within the Tree View Design Pattern.

+

+ The computed aria-level of a treeitem within a tree is based on the number of 'group' role elements in the ancestor chain between the treeitem and the tree role, where the top level treeitems are aria-level 1. + In the following example of a discussion board with nested replies, the top level post "What color should we paint the bike shed?" has an implicit aria-level='1'. + The first reply has an implicit aria-level='2', the response to that first reply has an implicit aria-level='3'. +

+ 
<ul role='tree'>
+  <li role='treeitem'>
+  What color should we paint the bike shed?
+  <ul role='group'>
+    <li role='treeitem''>
+    Green.
+    <ul role='group'>
+      <li role='treeitem'>
+      Green is boring, let's do purple.
+      </li>
+    </ul>
+    </li>
+  </ul>
+  </li>
+</ul>
+
+

To override the aria-level calculated from the number of group role parents, set aria-level explicitly. Setting aria-level explictly might be necessary if only part of a tree is loaded and the implicity calculations cannot account for the missing part of the tree.

+ 
<ul role='tree'>
+  <li role='treeitem' aria-level='1'>
+  What color should we paint the bike shed?
+  <button>Show 98 hidden replies</button>
+  <ul role='group'>
+    <li role='treeitem' aria-level='100'>
+    I disagree with all 98 people who have replied before me, it should be rainbow colored.
+    </li>
+  </ul>
+  </li>
+</ul>
+
+
+ +
+

row Role

+

+ The aria-level attribute can be used on an element with row role to describe nesting of rows in a treegrid, as is explained in the treegrid pattern. + In this example, the DOM tree does not represent the hierarchical relationship between rows. + Each email is in a tr element, which are siblings in the DOM tree, therefore aria-level is necessary to communicate that the emails form a tree structure. +

+ 
<table role='treegrid'>
+  <tr>
+  <th>From:</th>
+  <th>Subject:</th>
+  </tr>
+  <tr aria-level='1'>
+  <td>Laura</td>
+  <td>We should definitely cover the bike shed in rainbows.</td>
+  </tr>
+  <tr aria-level='2'>
+  <td>Fred</td>
+  <td>Re: We should definitely cover the bike shed in rainbows.</td>
+  </tr>
+</table>
+
+

Do not use aria-level on rows that are in a grid or a table because only rows in a treegrid table are expected to have a hierarchical relationship.

+
+ +
+

grid Role

+

The attribute aria-level can be used on elements with role grid to represent nested grids but it is not recommended.

+
+ +
+

Intentionally Hiding Semantics with the presentation Role