Update from PR #1018 for nameFrom: heading #1860
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -617,9 +617,11 @@ <h3>Accessible Name Calculation</h3> | |
| <dd>One of the following values: | ||
| <ol> | ||
| <li>author: name comes from values provided by the author in explicit markup features such as the <pref>aria-label</pref> attribute, the <pref>aria-labelledby</pref> attribute, or the host language labeling mechanism, such as the <code>alt</code> or <code>title</code> attributes in <abbr title="Hypertext Markup Language">HTML</abbr>, with HTML <code>title</code> attribute having the lowest precedence for specifying a text alternative.</li> | ||
| <li>heading: name comes from the text value of the first descendant (i.e., depth first) <a>element</a> node with the role of <code>heading</code>. Although "heading" may be allowed in addition to "author" in some <a>roles</a>, "heading" is used in content only if higher priority "author" features are not provided.</li> | ||
| <li>contents: name comes from the text value of the <a>element</a> node. Although this may be allowed in addition to "author" in some <a>roles</a>, this is used in content only if higher priority "author" features are not provided.</li> | ||
| <li>prohibited: the element does not support name from author. Authors MUST NOT use the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attributes to name the element.</li> | ||
| </ol> | ||
| <p>Priority is defined by the <a href="#mapping_additional_nd_te" class="accname">accessible name and description computation</a> algorithm. [[ACCNAME-1.2]]<p> | ||
| </dd> | ||
| </dl> | ||
| <section id="namecomputation"> | ||
|
|
@@ -634,21 +636,22 @@ <h4>Description Computation</h4> | |
| <h4>Accessible Name and Description Computation</h4> | ||
| <p><a href="#mapping_additional_nd_te" class="accname">Accessible Name and Description Computation</a> is defined in the Accessible Name and Description specification.</p> | ||
| </section> | ||
| <section id="namefromauthor"> | ||
| <h4>Roles Supporting Name from Author</h4> | ||
| <div id="index_fromauthor"></div> | ||
| </section> | ||
| <section id="namefromheading"> | ||
| <h4>Roles Supporting Name from Heading</h4> | ||
| <div id="index_fromheading"></div> | ||
| </section> | ||
| <section id="namefromcontent"> | ||
| <h4>Roles Supporting Name from Content</h4> | ||
| <div id="index_fromcontent"></div> | ||
| </section> | ||
| <section id="namefromprohibited"> | ||
| <h4>Roles which cannot be named (Name prohibited)</h4> | ||
| <div id="index_fromprohibited"></div> | ||
| </section> | ||
| </section> | ||
| <section id="childrenArePresentational"> | ||
| <h3>Presentational Children</h3> | ||
|
|
@@ -988,7 +991,12 @@ <h2>Definition of Roles</h2> | |
| </tr> | ||
| <tr> | ||
| <th class="role-namefrom-head" scope="row">Name From:</th> | ||
| <td class="role-namefrom"> | ||
| <ul> | ||
| <li>author</li> | ||
| <li>heading</li> | ||
| </ul> | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <th class="role-namerequired-head" scope="row">Accessible Name Required:</th> | ||
|
|
@@ -1168,7 +1176,12 @@ <h2>Definition of Roles</h2> | |
| </tr> | ||
| <tr> | ||
| <th class="role-namefrom-head" scope="row">Name From:</th> | ||
| <td class="role-namefrom"> | ||
| <ul> | ||
| <li>author</li> | ||
| <li>heading</li> | ||
| </ul> | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <th class="role-namerequired-head" scope="row">Accessible Name Required:</th> | ||
|
|
@@ -3018,7 +3031,6 @@ <h2>Definition of Roles</h2> | |
| <div class="role-description"> | ||
| <p>A dialog is a descendant window of the primary window of a web application. For <abbr title="Hypertext Markup Language">HTML</abbr> pages, the primary application window is the entire web document, i.e., the <code>body</code> element.</p> | ||
| <p>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 <rref>alertdialog</rref>.</p> | ||
|
There was a problem hiding this comment. Note: This is an editorial removal. Not substantive. Accessible Name Required is defined as True below, so this normative requirement remains. I'm removing excessive duplication that will be resolved in the AccName spec with w3c/accname/issues/182. |
||
| <p>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.</p> | ||
| <p class="note">In the description of this role, the term "web application" does not refer to the <rref>application</rref> role, which specifies specific assistive technology behaviors.</p> | ||
| </div> | ||
|
|
@@ -3073,7 +3085,12 @@ <h2>Definition of Roles</h2> | |
| </tr> | ||
| <tr> | ||
| <th class="role-namefrom-head" scope="row">Name From:</th> | ||
| <td class="role-namefrom"> | ||
| <ul> | ||
| <li>author</li> | ||
| <li>heading</li> | ||
| </ul> | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <th class="role-namerequired-head" scope="row">Accessible Name Required:</th> | ||
|
|
@@ -6802,7 +6819,7 @@ <h5>Presentational Role Inheritance</h5> | |
| <div class="role-description"> | ||
| <p>A <rref>landmark</rref> 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.</p> | ||
| <p>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 <a href="#landmark_roles">landmark roles</a>, such as <rref>main</rref>, <rref>complementary</rref>, or <rref>navigation</rref>.</p> | ||
cookiecrook marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment. Note: This is an editorial removal. Not substantive. Accessible Name Required is defined as True below, so this normative requirement remains. I'm removing excessive duplication that will be resolved in the AccName spec with w3c/accname#182. |
||
| <p>Authors MUST give each element with a region role a brief label that describes the purpose of the region.</p> | ||
| <p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>region</code>. | ||
| [=User agents=] SHOULD treat elements with role <code>region</code> and have an accessible name as navigational <a>landmarks</a>. | ||
| [=User agents=] MAY enable users to quickly navigate to elements with role <code>region</code>.</p> | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is whitespace correction, which I would normally be opposed to in a substantive diff, but the spaces vs tab inconsistency was in a section that I had to modify anyway. I claim editorial discretion.