editorial: tidying up "Characteristics of Roles"

Replaces #1733
Resolves #1263

Author: pkra

index.html

@@ -1131,10 +1131,6 @@ <h2>Characteristics of Roles</h2>
         <p>Roles define the following characteristics.</p>
         <section id="isAbstract">
           <h3>Abstract Roles</h3>
-          <dl class="runin">
-            <dt>Values</dt>
-            <dd>Boolean</dd>
-          </dl>
           <p>
             Abstract <a>roles</a> are the foundation upon which all other <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles are built. Authors MUST NOT use abstract roles
             because they are not implemented in the <abbr title="Application Programming Interface">API</abbr> binding. User agents MUST NOT map abstract roles to the standard role mechanism of the
@@ -1256,38 +1252,23 @@ <h3>Required Accessibility Parent Role</h3>
           <p class="note">An element with the appropriate <a href="#implicit_semantics">implicit WAI-ARIA semantic</a> fulfills this requirement.</p>
         </section>
         <section id="namecalculation">
-          <h3>Accessible Name Calculation</h3>
-          <dl class="runin">
-            <dt>Values</dt>
-            <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 HTML, with HTML <code>title</code> attribute having the lowest precedence for
-                  specifying a text alternative.
-                </li>
-                <li>
-                  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 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>
-                <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>
-            </dd>
-          </dl>
-          <section id="namecomputation">
-            <h4>Name Computation</h4>
-            <p><a href="#mapping_additional_nd_name" class="accname">Name Computation</a> is defined in the Accessible Name and Description specification.</p>
-          </section>
-          <section id="descriptioncomputation">
-            <h4>Description Computation</h4>
-            <p><a href="#mapping_additional_nd_description" class="accname">Description Computation</a> is defined in the Accessible Name and Description specification.</p>
-          </section>
-          <section id="textalternativecomputation">
-            <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>
+          <h3>Name From</h3>
+          <p>
+            Determines which content contributes to the <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite> [[ACCNAME-1.2]].
+          </p>
+          <p>One of the following values:</p>
+          <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>
+              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
+              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]].
+            </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>
           <section id="namefromauthor">
             <h4>Roles Supporting Name from Author</h4>
             <div id="index_fromauthor"></div>
@@ -1302,15 +1283,9 @@ <h4>Roles which cannot be named (Name prohibited)</h4>
           </section>
         </section>
         <section id="childrenArePresentational">
-          <h3>Presentational Children</h3>
-          <dl class="runin">
-            <dt>Values</dt>
-            <dd>
-              <p>Boolean (<code>true</code> | <code>false</code>)</p>
-            </dd>
-          </dl>
+          <h3>Children Presentational</h3>
           <p>
-            The <abbr title="Document Object Model">DOM</abbr> descendants are presentational. [=user agents=] SHOULD NOT expose descendants of this <a>element</a> through the platform
+            Indicates whether DOM descendants are presentational. [=user agents=] SHOULD NOT expose descendants of this <a>element</a> through the platform
             <a>accessibility <abbr title="Application Programming Interface">API</abbr></a
             >. If [=user agents=] do not hide the descendant nodes, some information might be read twice.
           </p>
@@ -13382,10 +13357,10 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
             </ul>
 
             <p>
-              Unlike elements referenced by <code>aria-describedby</code>, elements referenced by <code>aria-details</code> are not used in the Accessible
-              <a href="#mapping_additional_nd_description" class="accname">Description Computation</a> as defined in the Accessible Name and Description specification. Thus, the content of elements
-              referenced by <code>aria-details</code> are not flattened to a string when presented to assistive technology users. This makes <code>aria-details</code> particularly useful when
-              converting the information to a string would cause a loss of information or make the extended information more difficult to understand.
+              Unlike elements referenced by <code>aria-describedby</code>, elements referenced by <code>aria-details</code> are not used in the Accessible Description Computation as defined in the
+              <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite> [[ACCNAME-1.2]]. Thus, the content of elements referenced by <code>aria-details</code> are not
+              flattened to a string when presented to assistive technology users. This makes <code>aria-details</code> particularly useful when converting the information to a string would cause a
+              loss of information or make the extended information more difficult to understand.
             </p>
             <p>
               The <code>aria-details</code> property supports referring to multiple elements. For example, a paragraph in a document editor might reference multiple comments that are not related to
@@ -14286,10 +14261,9 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
               Most host languages provide an attribute that could be used to name the element (e.g., the <code>[^html-global/title^]</code> attribute in HTML), yet this could present a browser
               tooltip. In the cases where DOM content or a tooltip is undesirable, authors MAY set the accessible name of the element using <pref>aria-label</pref>, if the element does not
               <a href="#prohibitedattributes">prohibit</a> use of the attribute. If the label text is available in the DOM (i.e. typically visible text content), authors SHOULD use
-              <pref>aria-labelledby</pref> and SHOULD NOT use <pref>aria-label</pref>. There might be instances where the name of an element cannot be determined programmatically from the DOM, and
+              <pref>aria-labelledby</pref> and SHOULD NOT use <pref>aria-label</pref>. There might be instances where the name of an element cannot be determined programmatically from the DOM, and 
               there are cases where referencing DOM content is not the desired user experience. Authors MUST NOT specify <code>aria-label</code> on an element which has an explicit or implicit
-              WAI-ARIA role where <code>aria-label</code> is <a href="#prohibitedattributes">prohibited</a>. As required by the
-              <a href="#textalternativecomputation">accessible name and description computation</a>, user agents give precedence to <pref>aria-labelledby</pref> over <pref>aria-label</pref> when
+              WAI-ARIA role where <code>aria-label</code> is <a href="#prohibitedattributes">prohibited</a>. As required by the <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite> [[ACCNAME-1.2]], user agents give precedence to <pref>aria-labelledby</pref> over <pref>aria-label</pref> when
               computing the accessible name property.
             </p>
           </div>
@@ -14334,7 +14308,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
             <p>
               If the interface is such that it is not possible to have a visible label on the screen, authors SHOULD use <pref>aria-label</pref> and SHOULD NOT use <pref>aria-labelledby</pref>.
               Authors MUST NOT specify <code>aria-labelledby</code> on an element which has an explicit or implicit WAI-ARIA role where <code>aria-labelledby</code> is
-              <a href="#prohibitedattributes">prohibited</a>. As required by the <a href="#textalternativecomputation">accessible name and description computation</a>, user agents give precedence to
+              <a href="#prohibitedattributes">prohibited</a>. As required by the <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite> [[ACCNAME-1.2]], user agents give precedence to
               <pref>aria-labelledby</pref> over <pref>aria-label</pref> when computing the accessible name property.
             </p>
             <p>
@@ -15151,7 +15125,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
             </p>
             <p>
               When text changes are denoted as relevant, user agents MUST monitor any descendant node change that affects the
-              <a href="#textalternativecomputation">accessible name and description computation</a> of the live region as if the accessible name were determined from contents (<a
+              <cite><a href="" class="accname">Accessible Name and Description Computation</a></cite> [[ACCNAME-1.2]] of the live region as if the accessible name were determined from contents (<a
                 href="#namecalculation"
                 >nameFrom: contents</a
               >). For example, a text change would be triggered if the HTML <code>alt</code> attribute of a contained image changed. However, no change would be triggered if there was a text change to