You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.html
+47-20Lines changed: 47 additions & 20 deletions
Original file line number
Diff line number
Diff line change
@@ -617,9 +617,11 @@ <h3>Accessible Name Calculation</h3>
617
617
<dd>One of the following values:
618
618
<ol>
619
619
<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>
620
-
<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. Priority is defined by the <a href="#mapping_additional_nd_te" class="accname">accessible name and description computation</a> algorithm [[ACCNAME-1.2]].</li>
620
+
<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>
621
+
<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>
621
622
<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>
622
623
</ol>
624
+
<p>Priority is defined by the <a href="#mapping_additional_nd_te" class="accname">accessible name and description computation</a> algorithm. [[ACCNAME-1.3]]<p>
<h4>Accessible Name and Description Computation</h4>
635
637
<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>
636
638
</section>
637
-
<section id="namefromauthor">
638
-
<h4>Roles Supporting Name from Author</h4>
639
-
<div id="index_fromauthor">
640
-
</div>
639
+
<section id="namefromauthor">
640
+
<h4>Roles Supporting Name from Author</h4>
641
+
<div id="index_fromauthor"></div>
641
642
</section>
642
-
<section id="namefromcontent">
643
-
<h4>Roles Supporting Name from Content</h4>
644
-
<div id="index_fromcontent">
645
-
</div>
643
+
<section id="namefromheading">
644
+
<h4>Roles Supporting Name from Heading</h4>
645
+
<div id="index_fromheading"></div>
646
+
</section>
647
+
<section id="namefromcontent">
648
+
<h4>Roles Supporting Name from Content</h4>
649
+
<div id="index_fromcontent"></div>
646
650
</section>
647
651
<section id="namefromprohibited">
648
-
<h4>Roles which cannot be named (Name prohibited)</h4>
649
-
<div id="index_fromprohibited">
650
-
</div>
651
-
</section>
652
+
<h4>Roles which cannot be named (Name prohibited)</h4>
<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
@@ -3018,7 +3036,6 @@ <h2>Definition of Roles</h2>
3018
3036
<div class="role-description">
3019
3037
<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>
3020
3038
<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>
3021
-
<p>Authors MUST provide an accessible name for a dialog, which can be done with the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attribute.</p>
3022
3039
<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>
3023
3040
<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>
3024
3041
</div>
@@ -3073,7 +3090,12 @@ <h2>Definition of Roles</h2>
<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
@@ -6802,7 +6824,7 @@ <h5>Presentational Role Inheritance</h5>
6802
6824
<div class="role-description">
6803
6825
<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>
6804
6826
<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>
6805
-
<p>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 <pref>aria-labelledby</pref> 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 <rref>heading</rref>.</p>
6827
+
<p>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 <code>section</code>), authors would need to specify an explicit <code>role="region"</code> on the element to enable the nameFrom: heading technique.</p>
6806
6828
<p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>region</code>.
6807
6829
[=User agents=] SHOULD treat elements with role <code>region</code> and have an accessible name as navigational <a>landmarks</a>.
6808
6830
[=User agents=] MAY enable users to quickly navigate to elements with role <code>region</code>.</p>
@@ -6858,7 +6880,12 @@ <h5>Presentational Role Inheritance</h5>
0 commit comments