A set of user interface objects which are not intended to be included in a page summary or table of contents by assistive technologies.
Contrast with region which is a grouping of user interface objects that will be included in a page summary or table of contents.
Authors SHOULD use a group to form logical collection of items in a widget such as children in a tree widget forming a collection of siblings in a hierarchy, or a collection of items having the same container in a directory. However, when a group is used in the context of list, authors MUST limit its children to listitem elements. Therefore, proper handling of group by authors and assistive technologies is determined by the context in which it is provided.
Authors MAY nest group elements. If a section is significant enough to warrant inclusion in the web page’s table of contents, the author SHOULD assign the section a role of region or a standard landmark role.
<figure aria-labelledby="operahouse_1" role="group">
<img src="/operahousesteps.jpg" alt="The Sydney Opera House">
<figcaption id="operahouse_1">We saw the opera <cite>Barber of Seville</cite> here!</figcaption>
HTML Example 2
- HTML fieldset
Supported States and Properties
Inherited States and Properties
- aria-busy (state)
- aria-current (state)
- aria-disabled (state)
- aria-expanded (state)
- aria-grabbed (state)
- aria-hidden (state)
- aria-invalid (state)
No HTML element equivalent.