diff --git a/index.html b/index.html index ead4b3c60..096b0b432 100644 --- a/index.html +++ b/index.html @@ -662,9 +662,11 @@

Accessible Name Calculation

One of the following values:
  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. +
  2. heading: name comes from the text alternative of the first descendant element node matching the role of heading as defined in the AccName computation algorithm for nameFrom: heading. Although "heading" is allowed in addition to "author" in some roles, "heading" is used in content only if higher priority "author" features are not provided.
  3. contents: name comes from the text value of the element node. Although this might 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.2]].
  4. prohibited: the element does not support name from author. Authors MUST NOT use the aria-label or aria-labelledby attributes to name the element.
+

Priority is defined by the accessible name and description computation algorithm. [[ACCNAME-1.2]]

@@ -679,21 +681,22 @@

Description Computation

Accessible Name and Description Computation

Accessible Name and Description Computation is defined in the Accessible Name and Description specification.

-
-

Roles Supporting Name from Author

-
-
+
+

Roles Supporting Name from Author

+
-
-

Roles Supporting Name from Content

-
-
+
+

Roles Supporting Name from Heading

+
+
+
+

Roles Supporting Name from Content

+
-

Roles which cannot be named (Name prohibited)

-
-
-
+

Roles which cannot be named (Name prohibited)

+
+

Presentational Children

@@ -1033,7 +1036,12 @@

Definition of Roles

Name From: - author + + + Accessible Name Required: @@ -1213,7 +1221,12 @@

Definition of Roles

Name From: - author + + + Accessible Name Required: @@ -3059,7 +3072,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 MUST provide an accessible name for a dialog, 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.

@@ -3114,7 +3126,12 @@

Definition of Roles

Name From: - author + + + Accessible Name Required: @@ -3554,7 +3571,6 @@

Definition of Roles

A landmark region that contains a collection of items and objects that, as a whole, combine to create a form. See related search.

A form can contain a mix of host language form controls, scripted controls, and hyperlinks. Authors are reminded to use native host language semantics to create form controls whenever possible. If the purpose of a form is to submit search criteria, authors SHOULD use the search role instead of the generic form role.

-

Authors MUST give each element with role form a brief label that describes the purpose of the form. 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.

If an author uses a script to submit a form based on a user action that would otherwise not trigger an onsubmit event (for example, a form submission triggered by the user changing a form element's value), the author SHOULD provide the user with advance notification of the behavior.

Assistive technologies SHOULD enable users to quickly navigate to elements with role form. [=User agents=] SHOULD treat elements with role form and an accessible name as navigational landmarks. @@ -6879,7 +6895,6 @@

Presentational Role Inheritance

A landmark 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.

Assistive technologies SHOULD enable users to quickly navigate to elements with role region. [=User agents=] SHOULD treat elements with role region and an accessible name as navigational landmarks. [=User agents=] MAY enable users to quickly navigate to elements with role region.