diff --git a/index.html b/index.html index 3cdf223bd..6665be29a 100644 --- a/index.html +++ b/index.html @@ -358,7 +358,11 @@

Important Terms

Usable by users in ways they can control. References in this document relate to WCAG 2.1 Principle 2: Content must be operable [[WCAG21]]. See Keyboard Accessible.

-
Owned Element
+
Accessibility child
+
+

An 'accessibility child' is a DOM child of the element, a descendant of the element with only elements of role generic or none intervening, a child specified via an aria-owns relationship to the element, or a descendant of an element with role generic or none specified via aria-owns with only elements of role generic or none intervening.

+
+
Owned Element

An 'owned element' is any DOM descendant of the element, any element specified as a child via aria-owns, or any DOM descendant of the owned child.

@@ -366,6 +370,10 @@

Important Terms

An 'owning element' is any DOM ancestor of the element, or any element with an aria-owns attribute which references the ID of the element.

+
Accessibility parent
+
+

An 'accessibility parent' is a DOM parent of the element, an ancestor of the element with only elements of role generic or none intervening, any element with an owned child specified via aria-owns, or an ancestor of an owned element with only elements of role generic or none intervening.

+
Perceivable

Presentable to users in ways they can sense. References in this document relate to WCAG 2.1 Principle 1: Content must be perceivable [[WCAG21]].

@@ -600,18 +608,51 @@

Prohibited States and Properties

A host language attribute with the appropriate implicit WAI-ARIA semantic would also prohibit a state or property in this section.

-

Required Owned Elements

-

Any element that will be [=ARIA/owned=] by the element with this role. For example, an element with the role list will own at least one element with the role listitem.

-

When multiple roles are specified as required owned elements for a role, at least one instance of one required [=ARIA/owned=] element is expected. This specification does not require an instance of each of the listed owned roles. For example, a menu should have at least one instance of a menuitem, menuitemcheckbox, or menuitemradio. The menu role does not require one instance of each.

-

There might be times that required [=ARIA/owned=] elements are missing, for example, while editing or while loading a data set. When a widget is missing required owned elements due to script execution or loading, authors MUST mark a containing element with aria-busy equal to true. For example, until a page is fully initialized and complete, an author could mark the document element as busy.

-

A role that has 'required owned elements' does not imply the reverse relationship. While processing of a role might be incomplete without elements of given roles present as descendants, elements with roles in this list do not always have to be found within elements of the given role. See required context role for requirements about the context where elements of a given role will be contained.

-

An element with a subclass role of the 'required owned element' does not fulfill this requirement. For example, the listbox role requires ownership of an element using the option or group role. Although the group role is the superclass of row, adding an [=ARIA/owned=] element with a role of row will not fulfill the requirement that listbox owns an option or a group.

+

Allowed Accessibility Child Roles

+

A list of roles which are allowed on an accessibility child (simplified as "child") of the element with this role. Authors MUST only add child element with allowed roles. For example, an element with the role list can own child elements with the role listitem, but cannot own elements with the role option.

+

To determine whether an element is the child of an element, user agents MUST ignore any intervening elements with the role generic or none.

+

Descendants which are not children of an element ancestor are not constrained by allowed accessibility child roles. For example, an image is not an allowed child of a list, but it is a valid descendant if it is also a descendant of the list's allowed child listitem.

+

A role that has 'allowed accessibility child roles' does not imply the reverse relationship. Elements with roles in this list do not always have to be found within elements of the given role. See required accessibility parent roles for requirements about the context where elements of a given role will be contained.

+

An element with a subclass role of the 'allowed accessibility child role' does not fulfill this requirement. For example, the listbox role allows a child element using the option or group role. Although the group role is the superclass of row, adding a child element with a role of row will not fulfill the requirement that listbox allows children with option or group roles.

An element with the appropriate implicit WAI-ARIA semantic fulfills this requirement.

+

+ Examples of valid ways to mark up allowed accessibility child roles include: +

    +
  1. Direct DOM child: + +
    <div role="listbox">
+	<div role="option">option text</div>
+</div>
    +
    2. +
  2. DOM child with generics intervening: + +
    <div role="listbox">
+	<div>
+		<div role="option">option text</div>
+	</div>
+</div>
    +
    3. +
  3. Direct aria-owns relationship: + +
    <div role="listbox" aria-owns="id1"></div>
+<div role="option" id="id1">option text</div>
    +
    4. +
  4. aria-owns relationship with generics intervening: + +
    <div role="listbox" aria-owns="id1"></div>
+<div id="id1">
+	<div>
+		<div role="option">option text</div>
+	</div>
+</div>
    +
    5. +
+

-

Required Context Role

-

The required context role defines the owning container where this role is allowed. If a role has a required context, authors MUST ensure that an element with the role is contained inside (or [=ARIA/owned=] by) an element with the required context role. For example, an element with role listitem is only meaningful when contained inside (or [=ARIA/owned=] by) an element with role list.

-

A role that has 'required context role' does not imply the reverse relationship. While an element with the given role needs to appear within an element of the listed role(s) in order to be meaningful, elements of the listed roles do not always need descendant elements of the given role in order to be meaningful. See required owned elements for requirements about elements that require presence of a given descendant to be processed properly.

+

Required Accessibility Parent Role

+

The required accessibility parent (simplified as "parent") role defines the container where this role is allowed. If a role has a required accessibility parent, authors MUST ensure that an element with the role is an accessibility child of an element with the required accessibility parent role. For example, an element with role listitem is only meaningful when it is a child of an element with role list.

+

To determine whether an element has a parent with the required role, user agents MUST ignore any elements with the role generic or none.

An element with the appropriate implicit WAI-ARIA semantic fulfills this requirement.

@@ -879,11 +920,11 @@

Definition of Roles

- Required Context Role: + Required Accessibility Parent Roles:   - Required Owned Elements: + Allowed Accessibility Child Roles:   @@ -971,11 +1012,11 @@

Definition of Roles

- Required Context Role: + Required Accessibility Parent Roles:   - Required Owned Elements: + Allowed Accessibility Child Roles:   @@ -1057,11 +1098,11 @@

Definition of Roles

- Required Context Role: + Required Accessibility Parent Roles:   - Required Owned Elements: + Allowed Accessibility Child Roles:   @@ -1146,11 +1187,11 @@

Definition of Roles

<[^article^]> in HTML - Required Context Role: + Required Accessibility Parent Roles:   - Required Owned Elements: + Allowed Accessibility Child Roles:   @@ -1238,11 +1279,11 @@

Definition of Roles

  - Required Context Role: + Required Accessibility Parent Roles:   - Required Owned Elements: + Allowed Accessibility Child Roles: