Merge branch 'main' into htmlaam-571

Author: scottaohara

.github/workflows/prettier.yaml

@@ -12,7 +12,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
         with:
           ref: ${{github.event.pull_request.head.ref}}
           repository: ${{github.event.pull_request.head.repo.full_name}}
@@ -24,9 +24,10 @@ jobs:
 
       - name: Prettify code
         id: prettify
-        uses: creyD/prettier_action@v4.3
+        uses: creyD/prettier_action@v4.5
         with:
-          prettier_options: --write **/index.html --print-width 200
+          prettier_options: --write "**/index.html" "!index.html" --print-width 200
+          only_changed: True
           commit_message: "chore: prettier"
         continue-on-error: true
 

accname/index.html

@@ -536,8 +536,8 @@ <h4>Computation steps</h4>
                         <li id="comp_labelledby_set_current">
                           <span id="step2B.ii.a"><!-- Don't link to this legacy numbered ID. --></span>Set the <code>current node</code> to the node referenced by the IDREF.
                         </li>
-                        <li id="comp_labelledby_recursion">
-                          <span id="step2B.ii.b"><!-- Don't link to this legacy numbered ID. --></span><em>LabelledBy Recursion:</em> Compute the text alternative of the
+                        <li id="comp_labelledby_traversal">
+                          <span id="step2B.ii.b"><!-- Don't link to this legacy numbered ID. --></span><em>LabelledBy Traversal:</em> Compute the text alternative of the
                           <code>current node</code> beginning with the overall <a href="#comp_computation">Computation</a> step. Set the <code>result</code> to that text alternative.
                         </li>
                         <li id="comp_labelledby_append">
@@ -551,7 +551,7 @@ <h4>Computation steps</h4>
                   </ol>
                   <div>
                     <p>
-                      The result of <a href="#comp_labelledby_recursion">LabelledBy Recursion</a> in combination with <a href="#comp_hidden_not_referenced">Hidden Not Referenced</a> means that
+                      The result of <a href="#comp_labelledby_traversal">LabelledBy Traversal</a> in combination with <a href="#comp_hidden_not_referenced">Hidden Not Referenced</a> means that
                       <a class="termref">user agents</a> MUST include all nodes in the subtree as part of the <a class="termref">accessible name</a> or <a class="termref">accessible description</a>,
                       when the node referenced by <code>aria-labelledby</code> or <code>aria-describedby</code> is hidden.
                     </p>
@@ -612,8 +612,8 @@ <h4>Computation steps</h4>
                   <code>aria-label</code> [=attribute=] whose value is not undefined, not the empty string, nor, when trimmed of [=ascii whitespace|whitespace=], is not the empty string:
                   <ol class="acc-ol">
                     <li>
-                      If traversal of the <code>current node</code> is due to recursion <strong>and</strong> the <code>current node</code> is an embedded control, ignore <code>aria-label</code> and
-                      skip to rule <a href="#comp_embedded_control">Embedded Control</a>.
+                      If traversal of the <code>current node</code> is due to <a href="#comp_name_from_content_for_each_child">Name From Content descendant node recursion</a> <strong>and</strong> the
+                      <code>current node</code> is an embedded control, ignore <code>aria-label</code> and skip to rule <a href="#comp_embedded_control">Embedded Control</a>.
                     </li>
                     <li>Otherwise, return the value of <code>aria-label</code>.</li>
                   </ol>
@@ -665,8 +665,13 @@ <h4>Computation steps</h4>
                       <span id="step2F.ii"><!-- Don't link to this legacy numbered ID. --></span><em>Name From Generated Content:</em> Check for
                       <abbr title="Cascading Style Sheets">CSS</abbr> generated textual content associated with the <code>current node</code> and include it in the <code>accumulated text</code>. The
                       <abbr title="Cascading Style Sheets">CSS</abbr> <a href="https://www.w3.org/TR/selectors-3/#gen-content"><code>::before</code> and <code>::after</code></a> pseudo elements
-                      [[!CSS2]] can provide textual content for [=element|elements=] that have a content model.
+                      [[!CSS2]] can provide textual content for [=element|elements=] that have a content model, in addition to the
+                      <a href="https://www.w3.org/TR/css-pseudo-4/#selectordef-marker"><code>::marker</code></a> pseudo element.
                       <ol class="acc-ol">
+                        <li id="comp_name_from_content_pseudo_element_marker">
+                          For <code>::marker</code> pseudo elements, <a class="termref">User agents</a> MUST append <abbr title="Cascading Style Sheets">CSS</abbr> textual content, without a space, to
+                          the textual content of the <code>current node</code> if the <code>current node</code> supports <code>::marker</code>.
+                        </li>
                         <li id="comp_name_from_content_pseudo_element_before">
                           For <code>::before</code> pseudo elements, <a class="termref">User agents</a> MUST prepend <abbr title="Cascading Style Sheets">CSS</abbr> textual content, without a space,
                           to the textual content of the <code>current node</code>.

documentation/tests.md

@@ -72,5 +72,7 @@ Many of the automated tests in listed above started as a [Accessibility Investig
 
 ### Running (and writing) WPT Tests for ARIA and Related Specs
 
-Start with [Running the WPT Tests for ARIA and Related Specs](./wpt.md)
+Start with [Running the WPT Tests for ARIA and Related Specs](./wpt.md).
+
+For detailed guidance on writing tests for the purposes of accessibility interoperability, please visit: [Accessibility Interop Project Overview and Contribution Guidelines](https://github.com/web-platform-tests/interop-accessibility/wiki/Accessibility-Interop-Project-Overview-and-Contribution-Guidelines).
 

dpub-aam/index.html

@@ -13,13 +13,12 @@
 
         // specification status (e.g., WD, LC, NOTE, etc.). If in doubt use ED.
         specStatus: "WD",
-        crEnd: "2023-07-29",
-        //perEnd:               "2013-07-23",
+        //crEnd: "2023-07-29",
+        //prEnd:               "2025-04-21",
+        //errata: "https://www.w3.org/WAI/ARIA/1.1/errata/dpub",
         // the specifications short name, as in http://www.w3.org/TR/short-name/
         shortName: "dpub-aam-1.1",
-        implementationReportURI: "https://www.w3.org/2021/04/wpt-fyi-snapshot.html?filter=dpub-aam&date=2025-03-06",
-        // if you wish the publication date to be other than today, set this
-        // publishDate:  "2009-08-06",
+        implementationReportURI: "https://www.w3.org/2021/04/wpt-fyi-snapshot.html",
         copyrightStart: "2015",
         license: "w3c-software-doc",
 
@@ -61,7 +60,7 @@
             companyURL: "https://www.igalia.com",
             w3cid: 68182,
           },
-          { name: "Richard Schwerdtfeger", mailto: "[email protected]", company: "Knowbility", companyURL: "https://www.knowbility.org/", w3cid: 2460 },
+          { name: "Richard Schwerdtfeger", mailto: "[email protected]", company: "Knowbility", companyURL: "https://knowbility.org/", w3cid: 2460 },
         ],
         // authors, add as many as you like.
         // This is optional, uncomment if you have authors as well as editors.
@@ -165,30 +164,27 @@
   <body>
     <section id="abstract">
       <p>
-        The Digital Publishing Accessibility API Mappings (DPub-AAM) defines how [=user agents=] map the Digital Publishing WAI-ARIA Module [[dpub-aria-1.1]] markup to platform
+        Digital Publishing Accessibility API Mappings (DPUB-AAM) defines how [=user agents=] map the Digital Publishing WAI-ARIA Module [[dpub-aria-1.1]] markup to platform
         <a class="termref">accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a
-        >. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing.
+        >. It is intended for developers who are responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing.
       </p>
     </section>
     <section id="sotd">
-      <p>
-        The primary change since the First Public Working Draft was to update the Mac AX API mappings to add the AXCustomContent fields for announcing roles. Feedback on any aspect of the
-        specification is encouraged. A list of all substantive changes is available in the <a href="#changelog">change log</a>.
-      </p>
+      <p>Future updates to this specification may incorporate <a href="https://www.w3.org/policies/process/20231103/#allow-new-features">new features</a>.</p>
     </section>
     <section id="intro" class="informative">
       <h2>Introduction</h2>
 
       <p>
-        The implementation of this specification in user agents enables authors to produce more accessible e-books, by conveying structural book constructs used by the digital publishing industry to
-        assistive technologies. It does this by extending the <cite><a href="https://www.w3.org/TR/core-aam-1.1/">Core Accessibility API Mappings 1.1</a></cite> [[CORE-AAM-1.1]] and the
-        <cite><a href="https://www.w3.org/TR/accname-1.2/">Accessible Name and Description: Computation 1.2</a></cite> [[ACCNAME-1.2]] specifications for user agents. It provides Accessibility API
-        Mapping guidance for the roles defined in the Digital Publish WAI-ARIA Module.
+        The implementation of this specification in user agents enables authors to produce more accessible e-books by conveying structural book constructs that are used by the digital publishing
+        industry to assistive technologies. It does this by extending the <cite><a href="https://www.w3.org/TR/core-aam-1.1/">Core Accessibility API Mappings 1.1</a></cite> [[CORE-AAM-1.1]] and the
+        <cite><a href="https://www.w3.org/TR/accname-1.2/">Accessible Name and Description Computation 1.2</a></cite> [[ACCNAME-1.2]] specifications for user agents. It provides Accessibility API
+        Mapping guidance for the roles defined in the Digital Publishing WAI-ARIA Module.
       </p>
 
       <p>
-        The DPub-AAM is part of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> suite described in the
-        <a href="https://www.w3.org/WAI/intro/aria.php"><abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> Overview</a>.
+        The DPUB-AAM is part of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> suite that is described in the
+        <a href="https://www.w3.org/WAI/standards-guidelines/aria/"><abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> Overview</a>.
       </p>
     </section>
     <section id="conformance" class="normative">
@@ -2555,8 +2551,9 @@ <h4 id="role-map-toc"><code>doc-toc</code></h4>
       <h2>Translatable Values</h2>
 
       <p>
-        The HTML specification states that other specifications can define <a data-cite="html#translatable-attributes">translatable attributes</a> [[html]]. The language and directionality of each
-        attribute value is the same as the <a data-cite="html#language">language</a> and <a data-cite="html#the-directionality">directionality</a> of the element [[html]].
+        The HTML specification states that other specifications can define <a href="https://html.spec.whatwg.org/multipage/dom.html#translatable-attributes">translatable attributes</a> [[html]]. The
+        language and directionality of each attribute value is the same as the [=Node/language=] and <a href="https://html.spec.whatwg.org/multipage/dom.html#the-directionality">directionality</a> of
+        the element [[html]].
       </p>
 
       <p>To be understandable by assistive technology users, the following <code>role</code> mapping values intended for human consumption SHOULD be translated when a page is localized:</p>
@@ -2654,7 +2651,7 @@ <h3>Substantive changes since the <a href="https://www.w3.org/TR/2021/WD-dpub-aa
         </section>
 
         <section id="older-changes">
-          <h4>Other substantive changes since <a href="https://www.w3.org/TR/2017/REC-dpub-aam-1.0-20171214//">Digital Publishing Accessibility API Mappings 1.0</a></h4>
+          <h4>Other substantive changes since <a href="https://www.w3.org/TR/2017/REC-dpub-aam-1.0-20171214/">Digital Publishing Accessibility API Mappings 1.0</a></h4>
           <ul>
             <li>20-Sep-2021: Added mappings for doc-pageheader and doc-pagefooter roles.</li>
           </ul>