Chore: Format files with Prettier

Author: github-actions[bot]

pdf-aam/index.html

@@ -167,7 +167,9 @@ <h2>Introduction</h2>
       </p>
 
       <p>
-        This specification defines how PDF user agents (commonly referred to as “PDF processors” in ISO standards for PDF technology) respond to and expose <abbr title="PDF Logical Structure Items">PLSIs</abbr> (structure elements, structure attributes, or property lists associated with marked content, etc., as defined in ISO 32000-2 clauses 14.7–14.9).
+        This specification defines how PDF user agents (commonly referred to as “PDF processors” in ISO standards for PDF technology) respond to and expose
+        <abbr title="PDF Logical Structure Items">PLSIs</abbr> (structure elements, structure attributes, or property lists associated with marked content, etc., as defined in ISO 32000-2 clauses
+        14.7–14.9).
       </p>
 
       <p>
@@ -208,26 +210,29 @@ <h2>Mapping PDF Logical Structure Items to Accessibility APIs</h2>
 
       <h3>General Rules for Exposing PDF Semantics via HTML or WAI-ARIA Semantics</h3>
       <p>
-        Unless indicated otherwise, a <abbr title="PDF Logical Structure Items">PLSI</abbr> with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics MUST be exposed to the platform accessibility APIs according to
-        the relevant WAI-ARIA mappings defined in the
-        [[[Core-AAM-1.2]]] specification. Where a <abbr title="PDF Logical Structure Item">PLSI</abbr> has equivalent semantics to a WAI-ARIA role, user agents
-        MUST expose such semantic information to the platform for the WAI-ARIA accessibility APIs in a way that conforms to the WAI-ARIA semantics in the Core Accessibility API Mappings 1.2.
+        Unless indicated otherwise, a <abbr title="PDF Logical Structure Items">PLSI</abbr> with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics MUST be exposed to the platform
+        accessibility APIs according to the relevant WAI-ARIA mappings defined in the [[[Core-AAM-1.2]]] specification. Where a <abbr title="PDF Logical Structure Item">PLSI</abbr> has equivalent
+        semantics to a WAI-ARIA role, user agents MUST expose such semantic information to the platform for the WAI-ARIA accessibility APIs in a way that conforms to the WAI-ARIA semantics in the Core
+        Accessibility API Mappings 1.2.
       </p>
       <p>
-        In some cases, features present in a PDF may not map to a WAI-ARIA role specified in the
-        [[[Core-AAM-1.2]]]. In such cases a relevant HTML Accessibility API Mapping may exist. In those cases, a <abbr title="PDF Logical Structure Item">PLSI</abbr> is mapped to that
-        HTML Accessibility API. Where a PLSI has equivalent semantics to an HTML element, but not a WAI-ARIA role, user agents MUST expose such semantic information to the platform
-        for HTML accessibility APIs in a way that conforms to the <a href="https://www.w3.org/TR/html-aam-1.0/">HTML Accessibility API Mappings 1.0</a>.
+        In some cases, features present in a PDF may not map to a WAI-ARIA role specified in the [[[Core-AAM-1.2]]]. In such cases a relevant HTML Accessibility API Mapping may exist. In those cases,
+        a <abbr title="PDF Logical Structure Item">PLSI</abbr> is mapped to that HTML Accessibility API. Where a PLSI has equivalent semantics to an HTML element, but not a WAI-ARIA role, user agents
+        MUST expose such semantic information to the platform for HTML accessibility APIs in a way that conforms to the
+        <a href="https://www.w3.org/TR/html-aam-1.0/">HTML Accessibility API Mappings 1.0</a>.
       </p>
 
       <h3>Exposing <abbr title="PDF Logical Structure Items">PLSIs</abbr> That Do Not Directly Map to Accessibility APIs</h3>
-      <p>Where a <abbr title="PDF Logical Structure Items">PLSI</abbr> does not have any default HTML or WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification.</p>
+      <p>
+        Where a <abbr title="PDF Logical Structure Items">PLSI</abbr> does not have any default HTML or WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by
+        this specification.
+      </p>
 
       <h3>Exposing <abbr title="PDF Logical Structure Items">PLSIs</abbr> That Require a Minimum Role</h3>
 
       <p>
-        A minimum role is the equivalent WAI-ARIA role a <abbr title="PDF Logical Structure Item">PLSI</abbr> will map to if the element does not have a more specific implicit role or platform role mappings, e.g., a non-generic
-        role. Minimum roles help ensure that users of assistive technologies get the best possible experience for valid PLSIs where otherwise a role would not be exposed.
+        A minimum role is the equivalent WAI-ARIA role a <abbr title="PDF Logical Structure Item">PLSI</abbr> will map to if the element does not have a more specific implicit role or platform role
+        mappings, e.g., a non-generic role. Minimum roles help ensure that users of assistive technologies get the best possible experience for valid PLSIs where otherwise a role would not be exposed.
       </p>
 
       <p>A minimum role is provided when all of the following conditions are true:</p>
@@ -251,8 +256,8 @@ <h3>Exposing <abbr title="PDF Logical Structure Items">PLSIs</abbr> That Require
 
       <h3>PDF Element Role Mappings</h3>
       <p>
-        <abbr title="PDF Logical Structure Items">PLSIs</abbr> with implicit WAI-ARIA role semantics MUST be mapped to platform accessibility APIs according to the identified WAI-ARIA role mapping as defined in the
-        <a href="https://www.w3.org/TR/core-aam-1.2/">Core AAM 1.2</a> specification.
+        <abbr title="PDF Logical Structure Items">PLSIs</abbr> with implicit WAI-ARIA role semantics MUST be mapped to platform accessibility APIs according to the identified WAI-ARIA role mapping as
+        defined in the <a href="https://www.w3.org/TR/core-aam-1.2/">Core AAM 1.2</a> specification.
       </p>
       <p>
         Where a <abbr title="PDF Logical Structure Item">PLSI</abbr> is indicated as having “No corresponding (WAI-ARIA) role”, or is mapped to the generic role, user agents MUST NOT expose the