Editorial: Fix id value references and add h2s where appropriate (#2633)

daniel-montalvo · web-flow · commit edd33251bd35 · 2025-10-02T14:43:14.000+02:00
diff --git a/pdf-aam/index.html b/pdf-aam/index.html
@@ -139,13 +139,15 @@
   </head>
   <body>
     <section id="abstract">
+      <h2>Abstract</h2>
       <p>
         This document describes how [=user agents=] should expose semantics of PDF content to <a class="termref">accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a
         >. This helps users with disabilities to obtain and interact with information using <a class="termref">assistive technologies</a>. Documenting these mappings promotes interoperable exposure of
         roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.
       </p>
     </section>
     <section id="sotd">
+      <h2>Status of This Document</h2>
       <p>
         The Accessible Rich Internet Applications Working Group seeks feedback on any aspect of the specification. When submitting feedback, please consider issues in the context of the companion
         documents. To comment, <a href="https://github.com/w3c/pdf-aam/issues/new">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> pdf-aam GitHub repository</a>. If this is not
@@ -155,6 +157,7 @@
       </p>
     </section>
     <section id="Introduction">
+      <h2>Introduction</h2>
       <p>This section is non-normative.</p>
 
       <p>
@@ -194,7 +197,7 @@ <h2>PDF-specific Terms & Definitions</h2>
       </div>
     </section>
 
-    <section id="mapping-pdf-object to be named">
+    <section id="mapping-pdf-object-to-be-named">
       <h2>Mapping PDF-object to be named to Accessibility APIs</h2>
 
       <h3>General Rules for Exposing PDF Semantics via HTML or WAI-ARIA Semantics</h3>
