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: accname/index.html
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -646,6 +646,10 @@ <h4>Computation steps</h4>
646
646
</p>
647
647
</div>
648
648
</li>
649
+
<liid="comp_name_from_heading">
650
+
<em>Name From Heading:</em> Otherwise, if the <code>current node</code> has a role that supports <aclass="specref" href="#namefromheading">nameFrom: heading</a>,
651
+
return the text alternative of the first descendant <a>element</a> node matching the role of <code>heading</code> in an <em>depth-first search.</em>
652
+
</li>
649
653
<liid="comp_name_from_content">
650
654
<spanid="step2F"><!-- Don't link to this legacy numbered ID. --></span><em>Name From Content:</em> Otherwise, if the <code>current node's</code><aclass="termref">role</a> allows
651
655
<aclass="specref" href="#namefromcontent">name from content</a>, or if the <code>current node</code> is referenced by <code>aria-labelledby</code>, <code>aria-describedby</code>, or
Copy file name to clipboardExpand all lines: index.html
+48-14Lines changed: 48 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -1265,15 +1265,27 @@ <h3>Name From</h3>
1265
1265
having the lowest precedence for specifying a text alternative.
1266
1266
</li>
1267
1267
<li>
1268
-
contents: name comes from the text value of the <a>element</a> node. Although this might be allowed in addition to "author" in some <a>roles</a>, this is used in content only if higher
1269
-
priority "author" features are not provided. Priority is defined by the <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite> [[ACCNAME-1.2]].
1268
+
heading: name comes from the text alternative of the first descendant <a>element</a> node (depth first search) matching the role of <code>heading</code> as defined in the AccName
1269
+
computation algorithm for nameFrom: heading. Although "namefrom: heading" is allowed in addition to "namefrom: author" in some <a>roles</a>, "namefrom: heading" is used in content only
1270
+
if higher priority "namefrom: author" features are not provided. Priority is defined by the <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite>
1271
+
[[ACCNAME-1.2]].
1270
1272
</li>
1273
+
<li>
1274
+
contents: name comes from the text value of the <a>element</a> node. Although this might be allowed in addition to "namefrom: author" or "namefrom:heading" in some <a>roles</a>, this
1275
+
is used in content only if higher priority "namefrom: author" or "namefrom: heading" features are not provided. Priority is defined by the <cite><a href="" class="accname">Accessible
1276
+
Name and Description Computation</a></cite> [[ACCNAME-1.2]].
1277
+
</li>
1278
+
<li>Priority is defined by the <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite> [[ACCNAME-1.2]].</li>
1271
1279
<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>
1272
1280
</ol>
1273
1281
<section id="namefromauthor">
1274
1282
<h4>Roles Supporting Name from Author</h4>
1275
1283
<div id="index_fromauthor"></div>
1276
1284
</section>
1285
+
<section id="namefromheading">
1286
+
<h4>Roles Supporting Name from Heading</h4>
1287
+
<div id="index_fromheading"></div>
1288
+
</section>
1277
1289
<section id="namefromcontent">
1278
1290
<h4>Roles Supporting Name from Content</h4>
1279
1291
<div id="index_fromcontent"></div>
@@ -1670,7 +1682,12 @@ <h2>Definition of Roles</h2>
<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
@@ -3631,7 +3653,7 @@ <h2>Definition of Roles</h2>
3631
3653
focus to dialogs. See the <a href="https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/">WAI-ARIA Authoring Practices: Dialog (modal) pattern</a> for additional details on implementing
3632
3654
modal dialog design patterns.
3633
3655
</p>
3634
-
<p>Authors SHOULD provide an accessible name for a dialog, which can be done with the <pref>aria-label</pref> or <pref>aria-labelledby</pref> attribute.</p>
3656
+
<p>Authors SHOULD provide an accessible name for a dialog, using either <a href="#namecalculation">namefrom</a>: author or <a href="#namecalculation">namefrom</a>: heading.</p>
3635
3657
<p>
3636
3658
Authors SHOULD ensure that all dialogs (both modal and non-modal) have at least one <a>focusable</a> descendant element. Authors SHOULD focus an element in the modal dialog when it is
3637
3659
displayed, and authors SHOULD constrain keyboard focus to focusable elements within a modal dialog, until dismissed.
@@ -3721,7 +3743,12 @@ <h2>Definition of Roles</h2>
<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
@@ -4254,9 +4281,8 @@ <h2>Definition of Roles</h2>
4254
4281
possible. If the purpose of a form is to submit search criteria, authors SHOULD use the <rref>search</rref> role instead of the generic <code>form</code> role.
4255
4282
</p>
4256
4283
<p>
4257
-
Authors SHOULD give each element with role <code>form</code> a brief label that describes the purpose of the form. Authors SHOULD reference a visible label with
4258
-
<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
4259
-
language heading element or an instance of an element with role <rref>heading</rref>.
4284
+
Authors SHOULD give each element with role <code>form</code> a label that describes the purpose of the form, using either <a href="#namecalculation">namefrom</a>: author or
4285
+
<a href="#namecalculation">namefrom</a>: heading.
4260
4286
</p>
4261
4287
<p>
4262
4288
If an author uses a script to submit a form based on a user action that would otherwise not trigger an <code>onsubmit</code> event (for example, a form submission triggered by the user
@@ -4320,7 +4346,12 @@ <h2>Definition of Roles</h2>
<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
@@ -7984,9 +8015,7 @@ <h5>Presentational Role Inheritance</h5>
7984
8015
<a href="#landmark_roles">landmark roles</a>, such as <rref>main</rref>, <rref>complementary</rref>, or <rref>navigation</rref>.
7985
8016
</p>
7986
8017
<p>
7987
-
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
7988
-
<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
7989
-
language heading element or an instance of an element with role <rref>heading</rref>.
8018
+
Authors MUST give each element with role region a label that describes the purpose of the content in the region, using either <a href="#namecalculation">namefrom</a>: author or <a href="#namecalculation">namefrom</a>: heading.
7990
8019
</p>
7991
8020
<p>
7992
8021
<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
@@ -8046,7 +8075,12 @@ <h5>Presentational Role Inheritance</h5>
0 commit comments