From 64579bf08e32466b099d03f647b93261f5e79aee Mon Sep 17 00:00:00 2001
From: Sarah Higley <sarah.higley@microsoft.com>
Date: Wed, 15 Jul 2026 17:07:42 -0700
Subject: [PATCH] add aria-actions focus-handling wording to ARIA and Core AAM

---
 core-aam/index.html |  7 ++++++-
 index.html          | 15 ++++++++++++++-
 2 files changed, 20 insertions(+), 2 deletions(-)

diff --git a/core-aam/index.html b/core-aam/index.html
index c6c53de05..8b7704544 100644
--- a/core-aam/index.html
+++ b/core-aam/index.html
@@ -6461,7 +6461,12 @@ <h4>Not Mapped</h4>
             </p>
           </section>
           <h4 id="ariaActions"><code>aria-actions</code></h4>
-          <table aria-labelledby="ariaActions">
+          <p>
+            After an action is invoked, browsers MUST NOT fire the API's <a href="#focus_state_event_table">focus event</a> when the referenced action node receives focus.
+            The browser MUST subsequently return DOM focus to the referencing node also without firing an API <a href="#focus_state_event_table">focus event</a>,
+            unless focus is moved to a different node by a programmatic focus change or a user interaction.
+          </p>
+          <table class="data" aria-labelledby="ariaActions">
             <tbody>
               <tr>
                 <th>ARIA Specification</th>
diff --git a/index.html b/index.html
index 86e9a4cde..29f9192f7 100644
--- a/index.html
+++ b/index.html
@@ -12197,8 +12197,21 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
               <li>User Agents SHOULD use the accessible names of elements referenced by <code>aria-actions</code> to determine the names of actions that are exposed in a platform accessibility API.</li>
               <li>User Agents MUST NOT expose <code>aria-actions</code> if the Author MUST's are not followed.</li>
             </ul>
+            <p>In order to allow users to invoke actions while remaining on the referencing element, browsers MUST do the following steps to manage focus once an action is invoke via the <code>aria-actions</code> API:</p>
+            <ol>
+              <li>
+                 If the referenced action node is focusable and receives focus as a result of an <code>aria-actions</code> invocation:
+                <ul>
+                  <li>Allow the DOM focus events to fire on the referenced action node as a result of invoking it.</li>
+                  <li>Do not fire the <a>desktop focus event</a>.</li>
+                </ul>
+              </li>
+              <li>If focus is moved either programmatically or via a user interaction, handle that focus change as normal, and do not perform any further <code>aria-actions</code> focus steps.</li>
+              <li>If focus has not moved, the browser MUST move DOM focus back to the referencing element, again without firing a <a>desktop focus event</a>.</li>
+              <li>If the referencing element can no longer be focused, the browser MAY keep focus on the referenced action element and fire a <a>desktop focus event</a>.</li>
+            </ol>
           </div>
-          <table class="property-features">
+          <table class="def">
             <caption>Characteristics:</caption>
             <thead>
               <tr>