From ecea212f511eca984c9983ee085b12983bc0ff35 Mon Sep 17 00:00:00 2001
From: Sarah Higley <sarah.higley@microsoft.com>
Date: Thu, 14 Jul 2022 10:52:57 -0700
Subject: [PATCH 01/19] initial updates

---
 index.html | 51 ++++++++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 48 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index b887e641d..db368071b 100644
--- a/index.html
+++ b/index.html
@@ -1620,6 +1620,7 @@ <h2>Definition of Roles</h2>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -1909,6 +1910,7 @@ <h2>Definition of Roles</h2>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -2666,6 +2668,7 @@ <h2>Definition of Roles</h2>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -2755,6 +2758,7 @@ <h2>Definition of Roles</h2>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -3083,6 +3087,7 @@ <h2>Definition of Roles</h2>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -3427,6 +3432,7 @@ <h2>Definition of Roles</h2>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-brailleroledescription</pref></li>
 								<li><pref>aria-label</pref></li>
@@ -4067,6 +4073,7 @@ <h2>Definition of Roles</h2>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -4778,6 +4785,7 @@ <h2>Definition of Roles</h2>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -6213,6 +6221,7 @@ <h5>Presentational Role Inheritance</h5>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -8013,6 +8022,7 @@ <h5>Presentational Role Inheritance</h5>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -8172,6 +8182,7 @@ <h5>Presentational Role Inheritance</h5>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -8276,9 +8287,10 @@ <h5>Presentational Role Inheritance</h5>
 									<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 									<td class="role-disallowed">
 											<ul>
-													<li><pref>aria-braillelabel</pref></li>
-													<li><pref>aria-label</pref></li>
-													<li><pref>aria-labelledby</pref></li>
+												<li><pref>aria-actions</pref></li>	
+												<li><pref>aria-braillelabel</pref></li>
+												<li><pref>aria-label</pref></li>
+												<li><pref>aria-labelledby</pref></li>
 											</ul>
 									</td>
 							</tr>
@@ -8364,6 +8376,7 @@ <h5>Presentational Role Inheritance</h5>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -8921,6 +8934,7 @@ <h5>Presentational Role Inheritance</h5>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -9243,6 +9257,7 @@ <h5>Presentational Role Inheritance</h5>
 						<th class="role-disallowed-head" scope="row">Prohibited States and Properties:</th>
 						<td class="role-disallowed">
 							<ul>
+								<li><pref>aria-actions</pref></li>
 								<li><pref>aria-braillelabel</pref></li>
 								<li><pref>aria-label</pref></li>
 								<li><pref>aria-labelledby</pref></li>
@@ -10212,6 +10227,7 @@ <h3>Drag-and-Drop Attributes</h3>
 			<h3>Relationship Attributes</h3>
 			<p>This section lists [=attributes=] that indicate <a>relationships</a> or associations between [=elements=] which cannot be readily determined from the document structure.</p>
 			<ul>
+				<li><pref>aria-actions</pref></li>
 				<li><pref>aria-activedescendant</pref></li>
 				<li><pref>aria-colcount</pref></li>
 				<li><pref>aria-colindex</pref></li>
@@ -10241,6 +10257,35 @@ <h3>State change notification</h3>
 		<h2>Definitions of States and Properties (all aria-* attributes)</h2>
 		<p>Below is an alphabetical list of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a>states</a> and [=ARIA/properties=] to be used by authors. A detailed definition of each <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and [=ARIA/property=] follows this compact list.</p>
 		<p id="index_state_prop" class="placeholder">Placeholder for index of states and properties</p>
+		<div class="property" id="aria-actions">
+			<pdef>aria-actions</pdef>
+			<div class="property-description">
+				<p>Placeholder: text description of aria-actions</p>
+			</div>
+			<table class="property-features">
+				<caption>Characteristics:</caption>
+				<thead>
+					<tr>
+						<th scope="col">Characteristic</th>
+						<th scope="col">Value</th>
+					</tr>
+				</thead>
+				<tbody>
+					<tr>
+						<th class="property-applicability-head" scope="row">Used in Roles:</th>
+						<td class="property-applicability">All elements of the base markup except for some roles or elements that prohibit its use</td>
+					</tr>
+					<tr>
+						<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
+						<td class="property-descendants">Placeholder</td>
+					</tr>
+					<tr>
+						<th class="property-value-head" scope="row">Value:</th>
+						<td class="property-value"><a href="#valuetype_idref">ID reference</a></td>
+					</tr>
+				</tbody>
+			</table>
+		</div>
 		<div class="property" id="aria-activedescendant">
 			<pdef>aria-activedescendant</pdef>
 			<div class="property-description">

From a429ab9ce9442a6f155e21b3c8382ca9ab7ffb60 Mon Sep 17 00:00:00 2001
From: James Craig <jcraig@apple.com>
Date: Thu, 19 Jan 2023 01:32:05 -0800
Subject: [PATCH 02/19] proposed attribute description and requirements for
 aria-actions

---
 index.html | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index db368071b..ec08e92ae 100644
--- a/index.html
+++ b/index.html
@@ -10260,7 +10260,16 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 		<div class="property" id="aria-actions">
 			<pdef>aria-actions</pdef>
 			<div class="property-description">
-				<p>Placeholder: text description of aria-actions</p>
+				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger behaviors or operations relevant to the current element.</p>
+				<p>The <code>aria-actions</code> attribute provides an element to other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message may reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
+				<ul>
+					<li>Authors MUST ensure that related action elements have a label.</li>
+					<li>Authors MUST ensure that related action elements accept a <code>click</code> event handler or default activation behavior.</li>
+					<li>Authors MUST ensure that related action events are not limited to a modality-specific activation such as the <code>keyup</code> or <code>touchend</code> event handlers.</li>
+					<li>Authors SHOULD ensure that related actions elements have subclass role of <rref>command</rref> such as <rref>button</rref> or <rref>link</rref>. [Todo: What about the "activatable" <rref>input</rref> subclass roles like <rref>checkbox</rref> and <rref>switch</rref><rref>? I think UAs could make those work by combining label and status: action name could be "uncheck 'subscribe to marketing emails'". -jc]</li>
+					<li>Authors SHOULD ensure that related actions elements are visible and activatable when the current element is focused by the user agent or assistive technology.</li>
+					<li>User Agents SHOULD use the label of each associated element to determine the label of the action in a platform accessibility API mapping.</li>
+				</ul>
 			</div>
 			<table class="property-features">
 				<caption>Characteristics:</caption>

From 7fabd092349249c081741542c2db1200c27675b5 Mon Sep 17 00:00:00 2001
From: James Craig <cookiecrook@users.noreply.github.com>
Date: Thu, 19 Jan 2023 01:37:25 -0800
Subject: [PATCH 03/19] m. resolving ambiguity re: action name vs element label

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index ec08e92ae..b55956515 100644
--- a/index.html
+++ b/index.html
@@ -10268,7 +10268,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 					<li>Authors MUST ensure that related action events are not limited to a modality-specific activation such as the <code>keyup</code> or <code>touchend</code> event handlers.</li>
 					<li>Authors SHOULD ensure that related actions elements have subclass role of <rref>command</rref> such as <rref>button</rref> or <rref>link</rref>. [Todo: What about the "activatable" <rref>input</rref> subclass roles like <rref>checkbox</rref> and <rref>switch</rref><rref>? I think UAs could make those work by combining label and status: action name could be "uncheck 'subscribe to marketing emails'". -jc]</li>
 					<li>Authors SHOULD ensure that related actions elements are visible and activatable when the current element is focused by the user agent or assistive technology.</li>
-					<li>User Agents SHOULD use the label of each associated element to determine the label of the action in a platform accessibility API mapping.</li>
+					<li>User Agents SHOULD use the label of each associated element to determine the name of the action in a platform accessibility API mapping.</li>
 				</ul>
 			</div>
 			<table class="property-features">

From 9f40c25b6a6ae3dede9fa53d7a9406b4af44ae1e Mon Sep 17 00:00:00 2001
From: James Craig <cookiecrook@users.noreply.github.com>
Date: Thu, 19 Jan 2023 01:53:03 -0800
Subject: [PATCH 04/19] m. typo

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index b55956515..51f29f02c 100644
--- a/index.html
+++ b/index.html
@@ -10261,7 +10261,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 			<pdef>aria-actions</pdef>
 			<div class="property-description">
 				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger behaviors or operations relevant to the current element.</p>
-				<p>The <code>aria-actions</code> attribute provides an element to other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message may reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
+				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message may reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
 				<ul>
 					<li>Authors MUST ensure that related action elements have a label.</li>
 					<li>Authors MUST ensure that related action elements accept a <code>click</code> event handler or default activation behavior.</li>

From 80421d2f0ab16ab0ec111e2ae460aafb42ce5883 Mon Sep 17 00:00:00 2001
From: James Craig <cookiecrook@users.noreply.github.com>
Date: Tue, 7 Feb 2023 13:26:59 -0800
Subject: [PATCH 05/19] Pulling out the overly prescriptive context rule I
 initially proposed.

---
 index.html | 1 -
 1 file changed, 1 deletion(-)

diff --git a/index.html b/index.html
index 51f29f02c..c7031fbac 100644
--- a/index.html
+++ b/index.html
@@ -10266,7 +10266,6 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 					<li>Authors MUST ensure that related action elements have a label.</li>
 					<li>Authors MUST ensure that related action elements accept a <code>click</code> event handler or default activation behavior.</li>
 					<li>Authors MUST ensure that related action events are not limited to a modality-specific activation such as the <code>keyup</code> or <code>touchend</code> event handlers.</li>
-					<li>Authors SHOULD ensure that related actions elements have subclass role of <rref>command</rref> such as <rref>button</rref> or <rref>link</rref>. [Todo: What about the "activatable" <rref>input</rref> subclass roles like <rref>checkbox</rref> and <rref>switch</rref><rref>? I think UAs could make those work by combining label and status: action name could be "uncheck 'subscribe to marketing emails'". -jc]</li>
 					<li>Authors SHOULD ensure that related actions elements are visible and activatable when the current element is focused by the user agent or assistive technology.</li>
 					<li>User Agents SHOULD use the label of each associated element to determine the name of the action in a platform accessibility API mapping.</li>
 				</ul>

From 0e03c4b64370ea34963efff5b6750c73541889dd Mon Sep 17 00:00:00 2001
From: James Craig <cookiecrook@users.noreply.github.com>
Date: Wed, 8 Feb 2023 11:29:48 -0800
Subject: [PATCH 06/19] Review feedback from @mcking65

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index c7031fbac..ba40cf592 100644
--- a/index.html
+++ b/index.html
@@ -10260,7 +10260,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 		<div class="property" id="aria-actions">
 			<pdef>aria-actions</pdef>
 			<div class="property-description">
-				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger behaviors or operations relevant to the current element.</p>
+				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger a behavior or operation relevant to the referencing user interface object, such as the close button for a dialog, or a reply button relevant to the specific email message in focus.</p>
 				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message may reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
 				<ul>
 					<li>Authors MUST ensure that related action elements have a label.</li>

From 0f232188bde70ac3a34dc435074ecad2e5acb0d8 Mon Sep 17 00:00:00 2001
From: James Craig <cookiecrook@users.noreply.github.com>
Date: Wed, 8 Feb 2023 15:57:17 -0800
Subject: [PATCH 07/19] review suggestion from smhigley; combine author MUST
 statements

Co-authored-by: Sarah Higley <smhigley@users.noreply.github.com>
---
 index.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/index.html b/index.html
index ba40cf592..0e3ef6ef2 100644
--- a/index.html
+++ b/index.html
@@ -10264,8 +10264,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message may reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
 				<ul>
 					<li>Authors MUST ensure that related action elements have a label.</li>
-					<li>Authors MUST ensure that related action elements accept a <code>click</code> event handler or default activation behavior.</li>
-					<li>Authors MUST ensure that related action events are not limited to a modality-specific activation such as the <code>keyup</code> or <code>touchend</code> event handlers.</li>
+					<li>Authors MUST ensure that related action elements respond to a <code>click</code> event and are not limited to modality-specific activation such as the <code>keyup</code> or <code>touchend</code> events.</li>
 					<li>Authors SHOULD ensure that related actions elements are visible and activatable when the current element is focused by the user agent or assistive technology.</li>
 					<li>User Agents SHOULD use the label of each associated element to determine the name of the action in a platform accessibility API mapping.</li>
 				</ul>

From 2d2e4447fa61a419b4e85d00c8efe7ec8cd19c03 Mon Sep 17 00:00:00 2001
From: James Craig <cookiecrook@users.noreply.github.com>
Date: Fri, 10 Feb 2023 10:26:26 -0800
Subject: [PATCH 08/19] m. review feedback from Matt King re: label versus name

Co-authored-by: Matt King <a11yThinker@Gmail.com>
---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 0e3ef6ef2..3aee0f3ad 100644
--- a/index.html
+++ b/index.html
@@ -10266,7 +10266,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 					<li>Authors MUST ensure that related action elements have a label.</li>
 					<li>Authors MUST ensure that related action elements respond to a <code>click</code> event and are not limited to modality-specific activation such as the <code>keyup</code> or <code>touchend</code> events.</li>
 					<li>Authors SHOULD ensure that related actions elements are visible and activatable when the current element is focused by the user agent or assistive technology.</li>
-					<li>User Agents SHOULD use the label of each associated element to determine the name of the action in a platform accessibility API mapping.</li>
+					<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>
 				</ul>
 			</div>
 			<table class="property-features">

From 6b40469a3c5640fb3fe8b02dc6f463f5084561a4 Mon Sep 17 00:00:00 2001
From: James Craig <cookiecrook@users.noreply.github.com>
Date: Fri, 10 Feb 2023 10:33:01 -0800
Subject: [PATCH 09/19] m. more review feedback from Matt King re: label versus
 name

Co-authored-by: Matt King <a11yThinker@Gmail.com>
---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 3aee0f3ad..871639650 100644
--- a/index.html
+++ b/index.html
@@ -10263,7 +10263,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger a behavior or operation relevant to the referencing user interface object, such as the close button for a dialog, or a reply button relevant to the specific email message in focus.</p>
 				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message may reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
 				<ul>
-					<li>Authors MUST ensure that related action elements have a label.</li>
+					<li>Authors MUST ensure that elements referenced by <code>aria-actions</code> have an accessible name.</li>
 					<li>Authors MUST ensure that related action elements respond to a <code>click</code> event and are not limited to modality-specific activation such as the <code>keyup</code> or <code>touchend</code> events.</li>
 					<li>Authors SHOULD ensure that related actions elements are visible and activatable when the current element is focused by the user agent or assistive technology.</li>
 					<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>

From 02a94e5a837fea431cb90e5f609c105ed85e7ebc Mon Sep 17 00:00:00 2001
From: Sarah Higley <sarah.higley@microsoft.com>
Date: Fri, 19 Apr 2024 15:41:50 -0400
Subject: [PATCH 10/19] added 4.3.1 wording, fixed idref list value, wording
 tweaks

---
 index.html | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index 871639650..f5ab7a6f5 100644
--- a/index.html
+++ b/index.html
@@ -506,7 +506,8 @@ <h3>Information for Authors</h3>
 	      <li><rref>treegrid</rref></li>
 	      <li><rref>tablist</rref></li>
 	    </ul>
-	    <p>User agents that support <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> expand the usage of host language mechanisms such as <code>tabindex</code>, <code>focus</code>, and <code>blur</code> to allow them on all [=elements=]. Where the host language supports it, authors MAY add any element such as a <code>div</code>, <code>span</code>, or <code>img</code> to the default tab order by setting <code>tabindex=&quot;0&quot;</code>. In addition, any item with <code>tabindex</code> equal to a negative integer is focusable via script or a mouse click, but is not part of the default tab order. This is supported in both [[HTML]] and [[SVG2]].</p>
+		<p>Authors MUST also ensure any elements referenced by <pref>aria-actions</pref> are either in the tab order, accessible through managed focus as part of a composite widget container, or have a documented alternative method to achieve their function while focus is on the referencing element.</p>	    
+		<p>User agents that support <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> expand the usage of host language mechanisms such as <code>tabindex</code>, <code>focus</code>, and <code>blur</code> to allow them on all [=elements=]. Where the host language supports it, authors MAY add any element such as a <code>div</code>, <code>span</code>, or <code>img</code> to the default tab order by setting <code>tabindex=&quot;0&quot;</code>. In addition, any item with <code>tabindex</code> equal to a negative integer is focusable via script or a mouse click, but is not part of the default tab order. This is supported in both [[HTML]] and [[SVG2]].</p>
 	    <p>Authors MAY use <pref>aria-activedescendant</pref> to inform <a>assistive technologies</a> which descendant of a <rref>widget</rref> element is treated as having keyboard focus in the user interface if the role of the widget element supports <code>aria-activedescendant</code>.
         This is often a more convenient way of providing keyboard navigation within widgets, such as a <rref>listbox</rref>, where the widget occupies only one stop in the page <kbd>Tab</kbd> sequence and other keys, typically arrow keys, are used to focus elements inside the widget.</p>
 	    <p>Typically, the author will use host language <a>semantics</a> to put the widget in the <kbd>Tab</kbd> sequence (e.g., <code>tabindex="0"</code> in HTML) and <code>aria-activedescendant</code> to point to the ID of the currently active descendant. The author, not the user agent, is responsible for styling the currently active descendant to show it has keyboard focus. The author cannot use <code>:<span class="css-selector">focus</span></code> to style the currently active descendant since the actual focus is on the container.</p>
@@ -10260,11 +10261,12 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 		<div class="property" id="aria-actions">
 			<pdef>aria-actions</pdef>
 			<div class="property-description">
-				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger a behavior or operation relevant to the referencing user interface object, such as the close button for a dialog, or a reply button relevant to the specific email message in focus.</p>
+				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger a behavior or operation relevant to the referencing user interface object, such as the close button for a dialog, or a reply button relevant to the email message that references it.</p>
 				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message may reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
 				<ul>
 					<li>Authors MUST ensure that elements referenced by <code>aria-actions</code> have an accessible name.</li>
 					<li>Authors MUST ensure that related action elements respond to a <code>click</code> event and are not limited to modality-specific activation such as the <code>keyup</code> or <code>touchend</code> events.</li>
+					<li>Authors MUST ensure the secondary action is either directly navigable with the keyboard, or that there is a keyboard shortcut to directly activate it when focus is on the referencing element.</li>
 					<li>Authors SHOULD ensure that related actions elements are visible and activatable when the current element is focused by the user agent or assistive technology.</li>
 					<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>
 				</ul>
@@ -10288,7 +10290,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 					</tr>
 					<tr>
 						<th class="property-value-head" scope="row">Value:</th>
-						<td class="property-value"><a href="#valuetype_idref">ID reference</a></td>
+						<td class="property-value"><a href="#valuetype_idref_list">ID reference list</a></td>
 					</tr>
 				</tbody>
 			</table>

From 6794aef6d394aa74b44210e43cfe78b10dcc0177 Mon Sep 17 00:00:00 2001
From: Sarah Higley <sarah.higley@microsoft.com>
Date: Thu, 2 May 2024 13:06:52 -0700
Subject: [PATCH 11/19] remove errant lower-case may

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index f5ab7a6f5..8d6d8f60f 100644
--- a/index.html
+++ b/index.html
@@ -10262,7 +10262,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 			<pdef>aria-actions</pdef>
 			<div class="property-description">
 				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger a behavior or operation relevant to the referencing user interface object, such as the close button for a dialog, or a reply button relevant to the email message that references it.</p>
-				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message may reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
+				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message could reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
 				<ul>
 					<li>Authors MUST ensure that elements referenced by <code>aria-actions</code> have an accessible name.</li>
 					<li>Authors MUST ensure that related action elements respond to a <code>click</code> event and are not limited to modality-specific activation such as the <code>keyup</code> or <code>touchend</code> events.</li>

From e2fcd7113e44eb73a0cd801dcaf636330a9fd32b Mon Sep 17 00:00:00 2001
From: Sarah Higley <smhigley@users.noreply.github.com>
Date: Fri, 31 May 2024 13:50:32 -0700
Subject: [PATCH 12/19] Apply wording suggestions from code review

Co-authored-by: Matt King <a11yThinker@Gmail.com>
---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 8d6d8f60f..e451530ae 100644
--- a/index.html
+++ b/index.html
@@ -10262,11 +10262,11 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 			<pdef>aria-actions</pdef>
 			<div class="property-description">
 				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger a behavior or operation relevant to the referencing user interface object, such as the close button for a dialog, or a reply button relevant to the email message that references it.</p>
-				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the current element. For example, in a web mail application, the currently selected email message could reference action elements such as the <em>message-specific</em> Reply, Forward, and Delete buttons. Actions are triggered by mainstream pointer events (click, tap) or by simulated pointer events from assistive technology.</p>
+				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the referencing element. For example, in a web mail application, the selected email message could reference buttons that perform actions on that email, such as Reply, Forward, and Delete. Actions are triggered by pointer events (click, tap) that can be simulated by assistive technologies.</p>
 				<ul>
 					<li>Authors MUST ensure that elements referenced by <code>aria-actions</code> have an accessible name.</li>
 					<li>Authors MUST ensure that related action elements respond to a <code>click</code> event and are not limited to modality-specific activation such as the <code>keyup</code> or <code>touchend</code> events.</li>
-					<li>Authors MUST ensure the secondary action is either directly navigable with the keyboard, or that there is a keyboard shortcut to directly activate it when focus is on the referencing element.</li>
+					<li>Authors MUST ensure each referenced action element is either directly navigable with the keyboard or that there is a keyboard shortcut to directly activate it when focus is on the referencing element.</li>
 					<li>Authors SHOULD ensure that related actions elements are visible and activatable when the current element is focused by the user agent or assistive technology.</li>
 					<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>
 				</ul>

From 84667d394d7b2f89d6473020a0d4482a3c62a34c Mon Sep 17 00:00:00 2001
From: Sarah Higley <sarah.higley@microsoft.com>
Date: Wed, 11 Sep 2024 14:55:34 -0700
Subject: [PATCH 13/19] pull core aam mappings into the main PR

---
 core-aam/index.html | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)

diff --git a/core-aam/index.html b/core-aam/index.html
index fa74f9282..2842cefad 100644
--- a/core-aam/index.html
+++ b/core-aam/index.html
@@ -5711,6 +5711,44 @@ <h4>Not Mapped</h4>
               >. Its absence not only indicates that the accessible object is not grabbed, but further defines it as not grab-able. These cases are marked as "Not mapped" without an asterisk.
             </p>
           </section>
+          <h4 id="ariaActions"><code>aria-actions</code></h4>
+          <table aria-labelledby="ariaActions">
+            <tbody>
+              <tr>
+                <th>ARIA Specification</th>
+                <td>
+                  <a class="property-reference" href="#aria-actions"><code>aria-actions</code></a>
+                </td>
+              </tr>
+              <tr>
+                <th>MSAA + IAccessible2</th>
+                <td>
+                  <span class="property">Interface: <code>IAccessibleAction</code>, using the accessible nodes matching `aria-actions` IDREFs, if the referenced objects are in the accessibility tree</span><br />
+                  <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
+                </td>
+              </tr>
+              <tr>
+                <th><abbr title="User Interface Automation">UIA</abbr></th>
+                <td>
+                  <span class="property">Custom Property: <code>AccessibleActions</code>: element array of accessible nodes matching IDREFs, if the referenced objects are in the accessibility tree</span><br />
+                  <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
+                </td>
+              </tr>
+              <tr>
+                <th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology-Service Provider Interface">AT-SPI</abbr></th>
+                <td>
+                  <span class="relation">Relation: <code>RELATION_DETAILS</code> points to accessible nodes matching IDREFs, if the referenced objects are in the accessibility tree</span><br />
+                  <span class="relation">Reverse Relation: <code>RELATION_DETAILS_FOR</code> points to element</span>
+                </td>
+              </tr>
+              <tr>
+                <th><abbr title="macOS Accessibility Protocol">AX API</abbr></th>
+                <td>
+                  <span class="property">Implement as <a href="https://developer.apple.com/documentation/uikit/uiaccessibilitycustomaction">custom action</a></span>
+                </td>
+              </tr>
+            </tbody>
+          </table>
           <h4 id="ariaActiveDescendant"><code>aria-activedescendant</code></h4>
           <table aria-labelledby="ariaActiveDescendant">
             <tbody>

From 4119f0b363c7a1cf8f24888413f6c70de27e7f94 Mon Sep 17 00:00:00 2001
From: smhigley <smhigley@users.noreply.github.com>
Date: Wed, 11 Sep 2024 21:57:32 +0000
Subject: [PATCH 14/19] chore: prettier

---
 core-aam/index.html | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/core-aam/index.html b/core-aam/index.html
index 2842cefad..613cdb730 100644
--- a/core-aam/index.html
+++ b/core-aam/index.html
@@ -5723,14 +5723,18 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
               <tr>
                 <th>MSAA + IAccessible2</th>
                 <td>
-                  <span class="property">Interface: <code>IAccessibleAction</code>, using the accessible nodes matching `aria-actions` IDREFs, if the referenced objects are in the accessibility tree</span><br />
+                  <span class="property"
+                    >Interface: <code>IAccessibleAction</code>, using the accessible nodes matching `aria-actions` IDREFs, if the referenced objects are in the accessibility tree</span
+                  ><br />
                   <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
                 </td>
               </tr>
               <tr>
                 <th><abbr title="User Interface Automation">UIA</abbr></th>
                 <td>
-                  <span class="property">Custom Property: <code>AccessibleActions</code>: element array of accessible nodes matching IDREFs, if the referenced objects are in the accessibility tree</span><br />
+                  <span class="property"
+                    >Custom Property: <code>AccessibleActions</code>: element array of accessible nodes matching IDREFs, if the referenced objects are in the accessibility tree</span
+                  ><br />
                   <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
                 </td>
               </tr>

From 7e139a07dcb0afb1d463b0f36fe95c6cbc1aed54 Mon Sep 17 00:00:00 2001
From: Sarah Higley <sarah.higley@microsoft.com>
Date: Mon, 23 Sep 2024 11:32:16 -0700
Subject: [PATCH 15/19] address PR comments

---
 core-aam/index.html | 20 +++++++++++++++-----
 1 file changed, 15 insertions(+), 5 deletions(-)

diff --git a/core-aam/index.html b/core-aam/index.html
index 613cdb730..b0919d943 100644
--- a/core-aam/index.html
+++ b/core-aam/index.html
@@ -5723,9 +5723,14 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
               <tr>
                 <th>MSAA + IAccessible2</th>
                 <td>
-                  <span class="property"
-                    >Interface: <code>IAccessibleAction</code>, using the accessible nodes matching `aria-actions` IDREFs, if the referenced objects are in the accessibility tree</span
-                  ><br />
+                  <span class="property">
+                    Interface: <code>IAccessibleAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The interface methods should be mapped as follows:
+                    <ul>
+                      <li>`name`: return the DOM id of the corresponding target node.</li>
+                      <li>`localizedName`: return the corresponding target node's accessible name.</li>
+                      <li>`doAction`: behave as if `doAction(0)` were called on the corresponding target accessible node.</li>
+                    </ul>
+                  </span><br />
                   <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
                 </td>
               </tr>
@@ -5741,8 +5746,13 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
               <tr>
                 <th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology-Service Provider Interface">AT-SPI</abbr></th>
                 <td>
-                  <span class="relation">Relation: <code>RELATION_DETAILS</code> points to accessible nodes matching IDREFs, if the referenced objects are in the accessibility tree</span><br />
-                  <span class="relation">Reverse Relation: <code>RELATION_DETAILS_FOR</code> points to element</span>
+                  <span class="relation">Interface: <code>AtkAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The instance methods should be mapped as follows:</span>
+                  <ul>
+                    <li>`get_n_actions`: return the number of accessible nodes referenced by `aria-actions` that are exposed in the accessibility tree</li>
+                    <li>`get_name`: return the non-localized string 'click'.</li>
+                    <li>`get_localized_name`: return the corresponding target node's accessible name.</li>
+                    <li>`do_action`: behave as if `do_action` were called on the corresponding target accessible node.</li>
+                  </ul>
                 </td>
               </tr>
               <tr>

From 060790c51fc93001897d3a9596d91e150ec1db83 Mon Sep 17 00:00:00 2001
From: smhigley <smhigley@users.noreply.github.com>
Date: Mon, 23 Sep 2024 18:37:15 +0000
Subject: [PATCH 16/19] chore: prettier

---
 core-aam/index.html | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/core-aam/index.html b/core-aam/index.html
index b0919d943..912a60cc0 100644
--- a/core-aam/index.html
+++ b/core-aam/index.html
@@ -5724,13 +5724,14 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
                 <th>MSAA + IAccessible2</th>
                 <td>
                   <span class="property">
-                    Interface: <code>IAccessibleAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The interface methods should be mapped as follows:
+                    Interface: <code>IAccessibleAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The interface methods
+                    should be mapped as follows:
                     <ul>
                       <li>`name`: return the DOM id of the corresponding target node.</li>
                       <li>`localizedName`: return the corresponding target node's accessible name.</li>
                       <li>`doAction`: behave as if `doAction(0)` were called on the corresponding target accessible node.</li>
-                    </ul>
-                  </span><br />
+                    </ul> </span
+                  ><br />
                   <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
                 </td>
               </tr>
@@ -5746,7 +5747,10 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
               <tr>
                 <th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology-Service Provider Interface">AT-SPI</abbr></th>
                 <td>
-                  <span class="relation">Interface: <code>AtkAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The instance methods should be mapped as follows:</span>
+                  <span class="relation"
+                    >Interface: <code>AtkAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The instance methods should
+                    be mapped as follows:</span
+                  >
                   <ul>
                     <li>`get_n_actions`: return the number of accessible nodes referenced by `aria-actions` that are exposed in the accessibility tree</li>
                     <li>`get_name`: return the non-localized string 'click'.</li>

From 6c2d8be10ac8fe90693a84c58b76a13de3d4ead8 Mon Sep 17 00:00:00 2001
From: Sarah Higley <sarah.higley@microsoft.com>
Date: Mon, 23 Sep 2024 11:47:02 -0700
Subject: [PATCH 17/19] remove errant should, small wording fix

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

diff --git a/core-aam/index.html b/core-aam/index.html
index 912a60cc0..f0604e515 100644
--- a/core-aam/index.html
+++ b/core-aam/index.html
@@ -5724,14 +5724,13 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
                 <th>MSAA + IAccessible2</th>
                 <td>
                   <span class="property">
-                    Interface: <code>IAccessibleAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The interface methods
-                    should be mapped as follows:
+                    Interface: <code>IAccessibleAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The interface methods are mapped as follows:
                     <ul>
                       <li>`name`: return the DOM id of the corresponding target node.</li>
                       <li>`localizedName`: return the corresponding target node's accessible name.</li>
                       <li>`doAction`: behave as if `doAction(0)` were called on the corresponding target accessible node.</li>
-                    </ul> </span
-                  ><br />
+                    </ul>
+                  </span><br />
                   <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
                 </td>
               </tr>
@@ -5747,16 +5746,15 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
               <tr>
                 <th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology-Service Provider Interface">AT-SPI</abbr></th>
                 <td>
-                  <span class="relation"
-                    >Interface: <code>AtkAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The instance methods should
-                    be mapped as follows:</span
-                  >
-                  <ul>
-                    <li>`get_n_actions`: return the number of accessible nodes referenced by `aria-actions` that are exposed in the accessibility tree</li>
-                    <li>`get_name`: return the non-localized string 'click'.</li>
-                    <li>`get_localized_name`: return the corresponding target node's accessible name.</li>
-                    <li>`do_action`: behave as if `do_action` were called on the corresponding target accessible node.</li>
-                  </ul>
+                  <span class="relation">
+                    Interface: <code>AtkAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The instance methods are mapped as follows:
+                    <ul>
+                      <li>`get_n_actions`: return the number of accessible nodes referenced by `aria-actions` that are exposed in the accessibility tree</li>
+                      <li>`get_name`: return the non-localized string 'click'.</li>
+                      <li>`get_localized_name`: return the corresponding target node's accessible name.</li>
+                      <li>`do_action`: behave as if `do_action` were called on the corresponding target accessible node.</li>
+                    </ul>
+                  </span>
                 </td>
               </tr>
               <tr>
diff --git a/index.html b/index.html
index e451530ae..22acf1267 100644
--- a/index.html
+++ b/index.html
@@ -10262,7 +10262,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 			<pdef>aria-actions</pdef>
 			<div class="property-description">
 				<p><a>Identifies</a> a related element or elements whose primary activation (<code>click</code> event) will trigger a behavior or operation relevant to the referencing user interface object, such as the close button for a dialog, or a reply button relevant to the email message that references it.</p>
-				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions on the referencing element. For example, in a web mail application, the selected email message could reference buttons that perform actions on that email, such as Reply, Forward, and Delete. Actions are triggered by pointer events (click, tap) that can be simulated by assistive technologies.</p>
+				<p>The <code>aria-actions</code> attribute allows an element to reference other interactive elements which trigger actions related to the referencing element. For example, in a web mail application, the selected email message could reference buttons that perform actions on that email, such as Reply, Forward, and Delete. Actions are triggered by pointer events (click, tap) that can be simulated by assistive technologies.</p>
 				<ul>
 					<li>Authors MUST ensure that elements referenced by <code>aria-actions</code> have an accessible name.</li>
 					<li>Authors MUST ensure that related action elements respond to a <code>click</code> event and are not limited to modality-specific activation such as the <code>keyup</code> or <code>touchend</code> events.</li>

From 3b9b4b86e0bcb2d7289d558604f3236e59026023 Mon Sep 17 00:00:00 2001
From: smhigley <smhigley@users.noreply.github.com>
Date: Mon, 23 Sep 2024 18:49:57 +0000
Subject: [PATCH 18/19] chore: prettier

---
 core-aam/index.html | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/core-aam/index.html b/core-aam/index.html
index f0604e515..68f34c6b1 100644
--- a/core-aam/index.html
+++ b/core-aam/index.html
@@ -5724,13 +5724,14 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
                 <th>MSAA + IAccessible2</th>
                 <td>
                   <span class="property">
-                    Interface: <code>IAccessibleAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The interface methods are mapped as follows:
+                    Interface: <code>IAccessibleAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The interface methods
+                    are mapped as follows:
                     <ul>
                       <li>`name`: return the DOM id of the corresponding target node.</li>
                       <li>`localizedName`: return the corresponding target node's accessible name.</li>
                       <li>`doAction`: behave as if `doAction(0)` were called on the corresponding target accessible node.</li>
-                    </ul>
-                  </span><br />
+                    </ul> </span
+                  ><br />
                   <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
                 </td>
               </tr>
@@ -5747,7 +5748,8 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
                 <th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology-Service Provider Interface">AT-SPI</abbr></th>
                 <td>
                   <span class="relation">
-                    Interface: <code>AtkAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The instance methods are mapped as follows:
+                    Interface: <code>AtkAction</code>, adding one action for each accessible node referenced by `aria-actions` that is exposed in the accessibility tree. The instance methods are
+                    mapped as follows:
                     <ul>
                       <li>`get_n_actions`: return the number of accessible nodes referenced by `aria-actions` that are exposed in the accessibility tree</li>
                       <li>`get_name`: return the non-localized string 'click'.</li>

From 9d0397fd72c961f976df8e529a34a62bc3854aad Mon Sep 17 00:00:00 2001
From: Sarah Higley <sarah.higley@microsoft.com>
Date: Mon, 28 Oct 2024 14:29:20 -0700
Subject: [PATCH 19/19] aria-actions attribute mapping is an empty string, not
 the value

---
 core-aam/index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/core-aam/index.html b/core-aam/index.html
index 68f34c6b1..7d5f3dd31 100644
--- a/core-aam/index.html
+++ b/core-aam/index.html
@@ -5732,7 +5732,7 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
                       <li>`doAction`: behave as if `doAction(0)` were called on the corresponding target accessible node.</li>
                     </ul> </span
                   ><br />
-                  <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
+                  <span class="property">Object Attribute: <code>aria-actions: ""</code></span>
                 </td>
               </tr>
               <tr>
@@ -5741,7 +5741,7 @@ <h4 id="ariaActions"><code>aria-actions</code></h4>
                   <span class="property"
                     >Custom Property: <code>AccessibleActions</code>: element array of accessible nodes matching IDREFs, if the referenced objects are in the accessibility tree</span
                   ><br />
-                  <span class="property">Object Attribute: <code>aria-actions</code> &lt;value&gt;</span>
+                  <span class="property">Object Attribute: <code>aria-actions: ""</code></span>
                 </td>
               </tr>
               <tr>