diff --git a/index.html b/index.html index 0c37baa..2f6f0d3 100644 --- a/index.html +++ b/index.html @@ -196,6 +196,15 @@

HTML Element Role Mappings

  • "Not mapped" means the element does not need to be exposed via an accessibility API. This is usually because the element is not displayed as part of the user interface. However, authors can force some of these elements to be rendered. For instance, by overriding user agent styles to render elements that would have been otherwise set to `display: none`. In these cases, the user agent SHOULD map such elements to the role of `generic`.
  • Where applicable, how an element participates in the computation of its own or another element's accessible name and/or accessible description is described in the Accessible Name and Description Computation section of this document.
  • Where an element is indicated as having "No corresponding (WAI-ARIA) role", or is mapped to the `generic` role, user agents MUST NOT expose the `aria-roledescription` property value in the accessibility tree unless the element has an explicit, conforming `role` attribute value which [[WAI-ARIA-1.2]] does not prohibit the use of `aria-roledescription`.
    • +
  • + When HTML elements do not have an exact or equivalent mapping to a valid, non-abstract WAI-ARIA role, a unique `computedrole` string has been specified to serve as the return value for interoperability testing purposes. For instance, the `video` element MAY be exposed with a `computedrole` of "`html-video`". Authors MUST NOT use any `html-`prefixed computed role string in the role attribute (such as `html-video`). User Agents MUST ignore any abstract or invalid role token. +
    + + <video> <!-- computedrole returns 'html-video' --> + <main role="html-video"> <!-- Author error. computed role returns 'main' --> + +
    +
  • IAccessible2: