From c969abc85ddd6fce36ba3f360b842f8a169632d0 Mon Sep 17 00:00:00 2001
From: Keith Cirkel Exposing HTML Features That Require a Minimum Role
require a minimum role be returned as the computed role for the element, prioritize the more specific role in the ARIA taxonomy.
+ An element contains plain content when the element and all of its + accessibility subtree descendants + have roles limited to: + `generic`, + `group`, + `paragraph`, + `img`, + `none`, + or text. +
++ Elements that contain any accessibility subtree + descendants with roles other than those listed above are considered to contain rich content. + This includes interactive elements (such as buttons, links, or form controls), semantic structures (such as tables, lists, or headings), + and landmark regions. +
+- User Agents MUST expose an `aria-details` relationship with the associated element (identified via the specified `commandfor` + User Agents MUST expose a relation with the associated element (identified via the specified `commandfor` attribute) except under the following conditions:
+ Author-provided `aria-describedby` or `aria-details` attributes on the invoking element take precedence over these implicit relations. +
A button that represents a submit button or is in the reset state with a [=button/form owner=] cannot invoke a command. @@ -13645,7 +13679,10 @@
ispopup: <value> where <value> reflects the popover type.
@@ -13655,14 +13692,18 @@ Relations: `RELATION_DETAILS_FOR` points to invoking element. See Comments.
+ Relations: + If `popover=hint` with plain content, `RELATION_DESCRIPTION_FOR`; + otherwise `RELATION_DETAILS_FOR` points to invoking element. + See Comments.ispopup: <value> where <value> reflects the popover type.
@@ -13679,7 +13720,7 @@ User agents MUST NOT expose a details relation between a `popover` and its invoking element under the following conditions:
+User agents MUST NOT expose a relation between a `popover` and its invoking element under the following conditions:
- There are no unique mappings for the different `popover` states. Any accessibility mapping changes for the popover element would be the responsibility of the author. e.g., using - different base HTML elements, attributes, or ARIA attributes to make such changes. -
- User Agents MUST expose an `aria-details` relation with the associated popover element except under the following - conditions: + User Agents MUST expose a relation with the associated popover element except under the following conditions:
+ Author-provided `aria-describedby` or `aria-details` attributes on the invoking element take precedence over these implicit relations. +
A button that represents a submit button with a [=button/form owner=] cannot invoke a popover.
- Author-provided `aria-describedby` or `aria-details` attributes on the invoking element take precedence over these implicit relations. + Author-provided `aria-describedby` or `aria-details` attributes on the invoking element take precedence over these implicit relations, + even if their value is the empty string.
A button that represents a submit button or is in the