Chore: Format files with Prettier

Author: github-actions[bot]

core-aam/index.html

@@ -56,7 +56,7 @@
             name: "Cynthia Shelly",
             company: "W3C Invited Expert",
             mailto: "[email protected]",
-            w3cid: 11897
+            w3cid: 11897,
           },
         ],
         formerEditors: [
@@ -196,7 +196,10 @@
           >comment archive</a
         >). In-progress updates to the document may be viewed in the <a href="http://w3c.github.io/core-aam/">publicly visible editors' draft</a>.
       </p>
-      <p><strong>Living specification</strong> &mdash; This document is maintained as a living specification. For the latest normative version, visit <a href="https://www.w3.org/TR/core-aam-1.2/">Core Accessibility API Mappings</a>.</p>
+      <p>
+        <strong>Living specification</strong> &mdash; This document is maintained as a living specification. For the latest normative version, visit
+        <a href="https://www.w3.org/TR/core-aam-1.2/">Core Accessibility API Mappings</a>.
+      </p>
     </section>
     <section id="intro" class="informative">
       <h2>Introduction</h2>
@@ -213,8 +216,8 @@ <h2>Introduction</h2>
         <li>
           <cite
             ><a href="https://www.w3.org/WAI/ARIA/apg/"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Authoring Practices Guide</a></cite
-          >, describes how web content developers can develop accessible rich internet applications using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>.
-          It provides detailed advice and examples directed primarily to web application developers, yet also useful to user agent and developers of assistive technologies.
+          >, describes how web content developers can develop accessible rich internet applications using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. It provides detailed
+          advice and examples directed primarily to web application developers, yet also useful to user agent and developers of assistive technologies.
         </li>
         <li>
           <cite
@@ -359,9 +362,7 @@ <h5>Accessible Names and Descriptions</h5>
       </section>
     </section>
     <section id="conformance">
-      <p>
-        Normative sections provide requirements that user agents and assistive technologies MUST follow for an implementation to conform to this specification.
-      </p>
+      <p>Normative sections provide requirements that user agents and assistive technologies MUST follow for an implementation to conform to this specification.</p>
       <p>
         Non-normative (informative) sections provide information useful to understanding the specification. Such sections may contain examples of recommended practice, but it is not required to follow
         such recommendations in order to conform to this specification.
@@ -545,15 +546,17 @@ <h2>Computed Role</h2>
           <p class="note">
             When an element has a role but is not contained in the required context (for example, an orphaned `listitem` without the required accessible parent of role `list`), this is an authoring
             error, but the user agent behavior is not specified as a single rule. For most roles, user agents can either recover the error by ignoring the role, or respect the author's intended role
-            in scenarios deemed by the implementation to be harmless. Please note that this permissiveness in how engines treat author role errors might be overridden in a language-specific mapping document such as [[HTML-AAM]].
+            in scenarios deemed by the implementation to be harmless. Please note that this permissiveness in how engines treat author role errors might be overridden in a language-specific mapping
+            document such as [[HTML-AAM]].
           </p>
           <aside class="example">
             <!-- ReSpec needs these examples to be unindented. -->
             <pre>
 &lt;div role="listitem"&gt; &lt;!-- Author error: orphaned listitem. computedrole is unspecified. --&gt;
 
 &lt;div role="list"&gt; &lt;!-- computedrole returns "list" --&gt;
-  &lt;div role="listitem"&gt; &lt;!-- computedrole returns "listitem" in the appropriate context. --&gt;</pre>
+  &lt;div role="listitem"&gt; &lt;!-- computedrole returns "listitem" in the appropriate context. --&gt;</pre
+            >
           </aside>
           <p>
             When host language elements do not have an exact or equivalent mapping to a valid, non-abstract role, the related Accessibilty API Mapping extension specification MAY specify a unique
@@ -10756,7 +10759,12 @@ <h3>Changes to document content or node visibility</h3>
               </tr>
             </tbody>
           </table>
-          <p>Fire the following events for node changes where the node in question is an element and has an <a class="termref">accessible object</a>. The <dfn data-export="" data-lt="accessibility subtree">accessibility subtree</dfn> of a node is its <a class="termref">accessible object</a> in the <a>accessibility tree</a> and all of it's <a>accessibility descendants</a>. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via <a class="specref" href="#aria-flowto">aria-flowto</a> unless those objects are also descendants in the <a>accessibility tree</a>.
+          <p>
+            Fire the following events for node changes where the node in question is an element and has an <a class="termref">accessible object</a>. The
+            <dfn data-export="" data-lt="accessibility subtree">accessibility subtree</dfn> of a node is its <a class="termref">accessible object</a> in the <a>accessibility tree</a> and all of it's
+            <a>accessibility descendants</a>. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via
+            <a class="specref" href="#aria-flowto">aria-flowto</a> unless those objects are also descendants in the <a>accessibility tree</a>.
+          </p>
           <table class="data">
             <caption>
               Table of document change scenarios and events to be fired in each

dpub-aam/index.html

@@ -164,7 +164,10 @@
     </section>
     <section id="sotd">
       <p>Future updates to this specification may incorporate <a href="https://www.w3.org/policies/process/20231103/#allow-new-features">new features</a>.</p>
-      <p><strong>Living specification</strong> &mdash; This document is maintained as a living specification. For the latest normative version, visit <a href="https://www.w3.org/TR/dpub-aam/">Digital Publishing Accessibility API Mappings</a>.</p>
+      <p>
+        <strong>Living specification</strong> &mdash; This document is maintained as a living specification. For the latest normative version, visit
+        <a href="https://www.w3.org/TR/dpub-aam/">Digital Publishing Accessibility API Mappings</a>.
+      </p>
     </section>
     <section id="intro" class="informative">
       <h2>Introduction</h2>
@@ -182,9 +185,7 @@ <h2>Introduction</h2>
       </p>
     </section>
     <section id="conformance" class="normative">
-      <p>
-        Normative sections provide requirements that user agents and assistive technologies MUST follow for an implementation to conform to this specification.
-      </p>
+      <p>Normative sections provide requirements that user agents and assistive technologies MUST follow for an implementation to conform to this specification.</p>
       <p>
         Non-normative (informative) sections provide information useful to understanding the specification. Such sections may contain examples of recommended practice, but it is not required to follow
         such recommendations in order to conform to this specification.