Editorial: Rename PDF-Object to be named

pdf-aam/index.html

@@ -167,8 +167,7 @@ <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 PDF-object to be named (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 PDF Logical Structure Items (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>
@@ -189,7 +188,7 @@ <h2>Introduction</h2>
       <h2>PDF-specific Terms & Definitions</h2>
       <div>
         <dl class="termlist">
-          <dt><dfn data-export="">PDF-object to be named</dfn></dt>
+          <dt><dfn data-export="">PDF Logical Structure Item (PLSI)</dfn></dt>
           <dd>
             <p>can represent any or all of the following: Structure Element, Structure Attribute, Property list associated with marked content, or Associated File(s)</p>
           </dd>
@@ -198,30 +197,30 @@ <h2>PDF-specific Terms & Definitions</h2>
     </section>
 
     <section id="mapping-pdf-object-to-be-named">
-      <h2>Mapping PDF-object to be named to Accessibility APIs</h2>
+      <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 PDF-object to be named with default Accessible Rich Internet Applications (WAI-ARIA) 1.2 semantics MUST be exposed to the platform accessibility APIs according to
+        Unless indicated otherwise, a PLSI 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
-        <a href="https://www.w3.org/TR/core-aam-1.2/">Core Accessibility API Mappings 1.2</a> specification. Where a PDF-object to be named has equivalent semantics to a WAI-ARIA role, user agents
+        <a href="https://www.w3.org/TR/core-aam-1.2/">Core Accessibility API Mappings 1.2</a> specification. Where a PLSI 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
-        <a href="https://www.w3.org/TR/core-aam-1.2/">Core AAM 1.2</a>. In such cases a relevant HTML Accessibility API Mapping may exist. In those cases, a PDF-object to be named is mapped to that
-        HTML Accessibility API. Where a PDF-object to be named has equivalent semantics to an HTML element, but not a WAI-ARIA role, user agents MUST expose such semantic information to the platform
+        <a href="https://www.w3.org/TR/core-aam-1.2/">Core AAM 1.2</a>. In such cases a relevant HTML Accessibility API Mapping may exist. In those cases, a PLSI 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 PDF-object to be named That Do Not Directly Map to Accessibility APIs</h3>
-      <p>Where a PDF-object to be named 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 PLSIs That Do Not Directly Map to Accessibility APIs</h3>
+      <p>Where a PLSI 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 PDF-object to be named That Require a Minimum Role</h3>
+      <h3>Exposing PLSIs That Require a Minimum Role</h3>
 
       <p>
-        A minimum role is the equivalent WAI-ARIA role a PDF-object to be named 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 PDF-object to be named where otherwise a role would not be exposed.
+        A minimum role is the equivalent WAI-ARIA role a PLSI 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>
@@ -245,11 +244,11 @@ <h3>Exposing PDF-object to be named That Require a Minimum Role</h3>
 
       <h3>PDF Element Role Mappings</h3>
       <p>
-        PDF-object to be named 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
+        PLSIs 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 PDF-object to be named is indicated as having “No corresponding (WAI-ARIA) role”, or is mapped to the generic role, user agents MUST NOT expose the
+        Where a PLSI is indicated as having “No corresponding (WAI-ARIA) role”, or is mapped to the generic role, user agents MUST NOT expose the
         <code>aria-roledescription</code> property value in the accessibility tree unless the element has an explicit, conforming role attribute value which
         <a href="https://www.w3.org/TR/wai-aria-1.2/">WAI-ARIA 1.2</a> does not prohibit the use of <code>aria-roledescription</code>.
       </p>