diff --git a/common/script/aria.js b/common/script/aria.js index b0d6cf3a2..871e74df4 100644 --- a/common/script/aria.js +++ b/common/script/aria.js @@ -267,6 +267,7 @@ require(["core/pubsubhub"], function( respecEvents ) { var fromContent = ""; var fromEncapsulation = ""; var fromLegend = ""; + var fromHeading = ""; var fromProhibited = ""; $.each(document.querySelectorAll("rdef"), function(i,item) { @@ -363,7 +364,10 @@ require(["core/pubsubhub"], function( respecEvents ) { } if (node.textContent.indexOf("legend") !== -1) { fromLegend += "
  • " + content + "" + req + "
    • "; - } + } + if (node.textContent.indexOf("heading") !== -1) { + fromHeading += "
  • " + content + "" + req + "
    • "; + } }); } if (container.nodeName.toLowerCase() == "div") { @@ -562,6 +566,16 @@ require(["core/pubsubhub"], function( respecEvents ) { parentNode.replaceChild(list, node); } + node = document.getElementById("index_fromheading"); + if (node) { + parentNode = node.parentNode; + list = document.createElement("ul"); + list.id = "index_fromheading"; + list.className = "compact"; + list.innerHTML = fromHeading; + parentNode.replaceChild(list, node); + } + node = document.getElementById("index_fromprohibited"); if (node) { parentNode = node.parentNode; diff --git a/index.html b/index.html index 04e3c2191..84fdb6bf1 100644 --- a/index.html +++ b/index.html @@ -532,8 +532,7 @@

    Accessible Name Calculation

    1. author: name comes from values provided by the author in explicit markup features such as the aria-label attribute, the aria-labelledby attribute, or the host language labeling mechanism, such as the alt or title attributes in HTML, with HTML title attribute having the lowest precedence for specifying a text alternative.
    2. contents: name comes from the text value of the element node. Although this may be allowed in addition to "author" in some roles, this is used in content only if higher priority "author" features are not provided. Priority is defined by the accessible name and description computation algorithm. [[ACCNAME-1.1]]
      3. -
    3. encapsulation: name comes from the text value of the element node with role label that is the closest ancestor. Although "encapsulation" may be allowed in addition to "author" and "contents" in some roles, "encapsulation" is used only if higher priority "author" features are not provided. Priority is defined by the accessible name and description computation algorithm. [[ACCNAME-1.1]]
      4. -
    4. legend: name comes from the text value of the first descendant element node with the role of legend. Although "legend" may be allowed in addition to "author" in some roles, "legend" is used in content only if higher priority "author" features are not provided. Priority is defined by the accessible name and description computation algorithm. [[ACCNAME-1.1]]
      5. +
    5. heading: name comes from the text value of the first descendant (i.e., depth first) element node with the role of heading. Although "heading" may be allowed in addition to "author" in some roles, "heading" is used in content only if higher priority "author" features are not provided. Priority is defined by the accessible name and description computation algorithm. [[ACCNAME-1.1]]
    6. prohibited: the element has no name. Authors MUST NOT use the aria-label or aria-labelledby attributes to name the element.
    @@ -564,6 +563,11 @@

    Roles Supporting Name from Encapsulation

    +
    +

    Roles Supporting Name from Heading

    +
    +
    +

    Roles Supporting Name from Legend

    @@ -915,7 +919,12 @@

    Definition of Roles

    Name From: - author + + + Accessible Name Required: @@ -1091,7 +1100,12 @@

    Definition of Roles

    Name From: - author + + + Accessible Name Required: @@ -2361,7 +2375,12 @@

    Definition of Roles

    Name From: - author + + + Accessible Name Required: @@ -2697,7 +2716,6 @@

    Definition of Roles

    A dialog is a descendant window of the primary window of a web application. For HTML pages, the primary application window is the entire web document, i.e., the body element.

    Dialogs are most often used to prompt the user to enter or respond to information. A dialog that is designed to interrupt workflow is usually modal. See related alertdialog.

    -

    Authors SHOULD provide a dialog label, which can be done with the aria-label or aria-labelledby attribute.

    Authors SHOULD ensure that all dialogs (both modal and non-modal) have at least one focusable descendant element. Authors SHOULD focus an element in the modal dialog when it is displayed, and authors SHOULD manage focus of modal dialogs.

    In the description of this role, the term "web application" does not refer to the application role, which specifies specific assistive technology behaviors.

    @@ -2752,7 +2770,12 @@

    Definition of Roles

    Name From: - author + + + Accessible Name Required: @@ -5644,7 +5667,12 @@

    Plain HTML or Polyfill DOM Result of the MathML Quadratic Formula

    Name From: - author + + + Accessible Name Required: @@ -6549,7 +6577,7 @@
    Presentational Roles Conflict Resolution

    A perceivable section containing content that is relevant to a specific, author-specified purpose and sufficiently important that users will likely want to be able to navigate to the section easily and to have it listed in a summary of the page. Such a page summary could be generated dynamically by a user agent or assistive technology.

    Authors SHOULD limit use of the region role to sections containing content with a purpose that is not accurately described by one of the other landmark roles, such as main, complementary, or navigation.

    -

    Authors MUST give each element with role region a brief label that describes the purpose of the content in the region. Authors SHOULD reference a visible label with aria-labelledby if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host language heading element or an instance of an element with role heading.

    +

    Authors MUST give each element with a region role a brief label that describes the purpose of the region. For host languages that support elements with the default role of region (e.g., HTML section), authors would need to specify an explicit role="region" on the element to enable the nameFrom: heading technique.

    Assistive technologies SHOULD enable users to quickly navigate to elements with role region. Mainstream user agents MAY enable users to quickly navigate to elements with role region.

    @@ -6605,7 +6633,12 @@
    Presentational Roles Conflict Resolution
    - +
    Name From:author +
      +
    • author
      • +
    • heading
      • +
    +
    Accessible Name Required: