From a90aa06a7aab2df8afd86a14151b3118bdf87c4f Mon Sep 17 00:00:00 2001
From: Scott O'Hara <scottaohara@users.noreply.github.com>
Date: Mon, 15 Apr 2024 10:42:34 -0400
Subject: [PATCH 1/4] Addition: popovertarget guidance

Closes #513

the `aria-expanded` state is implicit when using the `popovertarget` attribute - and authors are not to use the ARIA attribute with this native HTML attribute.
---
 index.html | 57 +++++++++++++++++++++---------------------------------
 1 file changed, 22 insertions(+), 35 deletions(-)

diff --git a/index.html b/index.html
index 27ba149..43f2719 100644
--- a/index.html
+++ b/index.html
@@ -64,6 +64,10 @@
         the following substantive additions and/or corrections have been proposed:
       </p>
       <ul>
+        <!--<li>
+          <a href="https://github.com/w3c/html-aria/pull/...">15 April 2024 - Addition:</a>
+          Add author rules for the <a href="#att-popovertarget">`popovertarget`</a> attribute.
+        </li>-->
         <li>
           <a href="https://github.com/w3c/html-aria/pull/489">4 October 2023 - Addition:</a>
           Update the button element and input type=button,image,reset,submit elements to allow the `separator` role.
@@ -3618,10 +3622,6 @@ <h3 id="docconformance-attr">
               </td>
               <td>
                 <div class="correction">
-                  <p>
-                    Use the `checked` attribute on any element that is allowed the `checked` attribute in HTML. 
-                    Use the <a data-cite="html/input.html#dom-input-indeterminate">`indeterminate`</a> IDL attribute to indicate the "mixed" state for <a data-cite="html/input.html#checkbox-state-(type=checkbox)">`input type=checkbox`</a> elements.
-                  </p>
                   <p>
                     Authors MUST NOT use the <a data-cite="wai-aria-1.2#aria-checked">`aria-checked`</a> attribute on any element where the <a data-cite="html/form-control-infrastructure.html#concept-fe-checked">checkedness</a>, or the 
                     indeterminate checked value of the element can be in opposition to the current value of the `aria-checked` attribute.
@@ -3643,9 +3643,6 @@ <h3 id="docconformance-attr">
                 `aria-disabled="true"`
               </td>
               <td>
-                <p>
-                  Use the `disabled` attribute on any element that is allowed the `disabled` attribute in HTML.
-                </p>
                 <p>
                   Authors MAY use the <a data-cite="wai-aria-1.2#aria-disabled">`aria-disabled`</a> attribute on any element that is allowed the `disabled` attribute in HTML, or any element with a WAI-ARIA role which allows the `aria-disabled` attribute</a>.
                 </p>
@@ -3689,10 +3686,6 @@ <h3 id="docconformance-attr">
                 `aria-placeholder="..."`
               </td>
               <td>
-                <p>
-                  Use the `placeholder` attribute on any element that is allowed the
-                  `placeholder` attribute in HTML.
-                </p>
                 <p>
                   Authors MAY use the <a data-cite="wai-aria-1.2#aria-placeholder">`aria-placeholder`</a> attribute on any element that is allowed the `placeholder` attribute in HTML, or any element with a WAI-ARIA role which allows the `aria-placeholder` attribute.
                 </p>
@@ -3701,6 +3694,24 @@ <h3 id="docconformance-attr">
                 </p>
               </td>
             </tr>
+          <tr id="att-popovertarget" tabindex="-1">
+              <th>
+                Any element where the <a data-cite="html/popover.html#the-popover-target-attributes">`popovertarget`</a> attribute is allowed: 
+                [^button^], 
+                <a data-cite="html/input.html#button-state-(type=button)">`input type=button`</a>,
+                <a data-cite="html/input.html#button-state-(type=image)">`input type=image`</a>,
+                <a data-cite="html/input.html#reset-button-state-(type=reset)">`input type=reset`</a>
+                <a data-cite="html/input.html#submit-button-state-(type=submit)">`input type=submit`</a>
+              </th>
+              <td>
+                `aria-expanded="..."`
+              </td>
+              <td>
+                <p class="addition">
+                  Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `popovertarget` attribute.
+                </p>
+              </td>
+            </tr>
             <tr id="att-max" tabindex="-1">
               <th>
                 Any element where the `max` attribute is allowed: `meter` [^meter/max^], `progress` [^progress/max^], and `input` [^input/max^]
@@ -3709,10 +3720,6 @@ <h3 id="docconformance-attr">
                 `aria-valuemax="..."`
               </td>
               <td>
-                <p>
-                  Use the `max` attribute on any element that is
-                  allowed the `max` attribute in HTML.
-                </p>
                 <p>
                   Authors MAY use the <a data-cite="wai-aria-1.2#aria-valuemax">`aria-valuemax`</a> attribute on any other element with a WAI-ARIA role which allows the `aria-valuemax` attribute.
                 </p>
@@ -3732,10 +3739,6 @@ <h3 id="docconformance-attr">
                 `aria-valuemin="..."`
               </td>
               <td>
-                <p>
-                  Use the `min` attribute on any element that is
-                  allowed the `min` attribute in HTML.
-                </p>
                 <p>
                   Authors MAY use the <a data-cite="wai-aria-1.2#aria-valuemax">`aria-valuemin`</a> attribute on any other element with a WAI-ARIA role which allows the `aria-valuemin` attribute.
                 </p>
@@ -3756,10 +3759,6 @@ <h3 id="docconformance-attr">
                 `aria-readonly="true"`
               </td>
               <td>
-                <p>
-                  Use the `readonly` attribute on any element that is
-                  allowed the `readonly` attribute in HTML.
-                </p>
                 <p>
                   Authors MAY use the <a data-cite="wai-aria-1.2#aria-readonly">`aria-readonly`</a> attribute on any element with a WAI-ARIA role which allows the attribute</a>.
                 </p>
@@ -3801,10 +3800,6 @@ <h3 id="docconformance-attr">
                 `aria-required="true"`
               </td>
               <td>
-                <p>
-                  Use the `required` attribute on any element
-                  that is allowed the `required` attribute in HTML.
-                </p>
                 <p>
                   Authors MAY use the <a data-cite="wai-aria-1.2#aria-required">`aria-required`</a> attribute on any element that is allowed the `required` attribute in HTML, or any element with a WAI-ARIA role which allows the `aria-required` attribute.
                 </p>
@@ -3824,10 +3819,6 @@ <h3 id="docconformance-attr">
                 `aria-colspan="..."`
               </td>
               <td>
-                <p>
-                  Use the `colspan` attribute on any element that is
-                  allowed the `colspan` attribute in HTML.
-                </p>
                 <!--
                   Removing per issue #338
                   Revised rules to be re-added
@@ -3852,10 +3843,6 @@ <h3 id="docconformance-attr">
                 `aria-rowspan="..."`
               </td>
               <td>
-                <p>
-                  Use the `rowspan` attribute on any element that is
-                  allowed the `rowspan` attribute in HTML.
-                </p>
                 <!--
                   Removing per issue #338
                   Revised rules to be re-added

From 5cb48c96be816a7a828c6339294ee8b6c1f43043 Mon Sep 17 00:00:00 2001
From: Scott O'Hara <scottaohara@users.noreply.github.com>
Date: Mon, 15 Apr 2024 11:46:14 -0400
Subject: [PATCH 2/4] Create popovertarget.html

adds test case for popovertarget author guidance
---
 tests/popovertarget.html | 99 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 99 insertions(+)
 create mode 100644 tests/popovertarget.html

diff --git a/tests/popovertarget.html b/tests/popovertarget.html
new file mode 100644
index 0000000..e68f269
--- /dev/null
+++ b/tests/popovertarget.html
@@ -0,0 +1,99 @@
+<!DOCTYPE html>
+<html lang="en"><head>
+	<meta charset="UTF-8">
+	<title>ARIA in HTML - Test Cases</title>
+    <link rel="stylesheet" href="../results/styles.css">
+	<style>
+		body{
+			font-size: 1em;
+		}
+		.roleTest {
+			border: 2px solid black;
+			width: 1em;
+			height: 1em;
+			margin: 5px;
+		}
+		.flex {
+			display: flex;
+			flex-wrap: wrap;
+			align-items: stretch;
+		}
+		.widgetDemo {
+			border: 1px solid #EEE;
+			margin: .5em;
+			padding: 5px;
+			flex: 1 0 0;
+			min-width: calc(300px - 1em);
+		}
+		.widgetDemo p {
+			color: #696969;
+			font-size: 1.125em;
+			padding: 0;
+			margin: .75em 0;
+		}
+		.testcase {
+			margin: 2em 0;
+		}
+		h3{
+			margin: .5em 0;
+			border: 0;
+			padding: 0;
+		}
+		h2 {font-size:2em}
+	</style>
+</head>
+<body>
+
+	<header>
+	<h1>ARIA in HTML - test cases for <code>popovertarget</code> and <code>aria-expanded</code></h1>
+	<p>last updated 15 April 2024</p>
+	<p>
+		<a href="https://html.spec.whatwg.org/multipage/popover.html#the-popover-target-attributes"><code>popovertarget</code></a> is allowed on 
+    <a href="https://html.spec.whatwg.org/multipage/forms.html#concept-button"><code>button</code> elements</a>.
+	</p>
+	</header>
+	<main>
+		<h2>Tests:</h2>
+
+		<div class="flex">
+			<div class="widgetDemo">
+				<h3>Test 1</h3>
+				<p>
+          Authors MUST NOT use the <code>aria-expanded</code> attribute on any element which also has a <code>popovertarget</code> attribute.</p>
+
+				<div class="testcase">
+					<button popovertarget=f aria-expanded="false">test 1</button>
+          <div id=f popover>test 1 popover</div>
+				</div>
+
+				<p><strong>Expected result:</strong>
+				<br> error for inappropriate use of <code>aria-expanded</code> when element has <code>popovertarget</code> 
+          attribute which implicitly handles <code>aria-expanded</code> states.</p>
+			</div>
+
+			<div class="widgetDemo">
+				<h3>Test 2</h3>
+				<p>
+          Authors MUST NOT use the <code>aria-expanded</code> attribute on any element which will have a <code>popovertarget</code> attribute
+          set due to adding it via the <code>popoverTargetElement</code> IDL attribute.</p>
+
+				<p>The first <code>th</code> and <code>td</code> each have an <code>aria-colspan="1"</code> and <code>colspan="1"</code> attribute</p>
+
+				<div class="testcase">
+					<button aria-expanded=false id=t2>test 2</button>
+          <div id=g popover>test 2 popover</div>
+          <script>
+            const b = document.getElementById('t2');
+            const p = document.getElementById('g');
+            b.popoverTargetElement = p;
+          </script>
+				</div>
+
+				<p><strong>Expected result:</strong>
+				<br> error for inappropriate use of <code>aria-expanded</code> when element has <code>popovertarget</code> 
+          attribute which implicitly handles <code>aria-expanded</code> states.</p>
+			</div>
+		</div>
+	</main>
+</body>
+</html>

From 99010339756168ad16c87b1d15a2c75c5c1d0197 Mon Sep 17 00:00:00 2001
From: Scott O'Hara <scottaohara@users.noreply.github.com>
Date: Fri, 4 Apr 2025 17:14:33 -0400
Subject: [PATCH 3/4] adjust attributes table content.  add command attr rules

the various lines of "authors may use [ attribute name ]" were unnecessary for the scope of this spec.

listing out what elements the HTML attributes are used with was also unnecessary / and would require upkeep that adds extra maintenance to this spec.

adds rules for command attribute, and adds aria-details allowances for popovertarget.
---
 index.html | 155 ++++++++++++++++++++++++-----------------------------
 1 file changed, 69 insertions(+), 86 deletions(-)

diff --git a/index.html b/index.html
index 3036d8e..cfdee9c 100644
--- a/index.html
+++ b/index.html
@@ -3626,7 +3626,7 @@ <h3 id="docconformance-attr">
               </th>
               <th>
                 <p id="implicit-attr">
-                  Implicit ARIA semantics
+                  Implicit ARIA semantics 
                 </p>
               </th>
               <th>
@@ -3645,15 +3645,61 @@ <h3 id="docconformance-attr">
               <td>
                 <div class="correction">
                   <p>
-                    Authors MUST NOT use the <a data-cite="wai-aria-1.2#aria-checked">`aria-checked`</a> attribute on any element where the <a data-cite="html/form-control-infrastructure.html#concept-fe-checked">checkedness</a>, or the 
+                    Authors MUST NOT use the <a data-cite="wai-aria-1.2#aria-checked">`aria-checked`</a> attribute on any element where the 
+                    <a data-cite="html/form-control-infrastructure.html#concept-fe-checked">checkedness</a>, or the 
                     indeterminate checked value of the element can be in opposition to the current value of the `aria-checked` attribute.
                   </p>
                 </div>
+              </td>
+            </tr>
+            <tr id="att-command" tabindex="-1">
+              <th>
                 <p>
-                  Authors MAY use the `aria-checked` attribute on any other element with a WAI-ARIA role which allows the attribute.
+                  Element with [^html-global/contenteditable^]`=true`
+                  or
+                  element without `contenteditable` attribute whose closest
+                  ancestor with a `contenteditable` attribute has
+                  `contenteditable="true"`.
+                </p>
+                <p class="note">
+                  This is equivalent to the <a data-cite="html/interaction.html#dom-iscontenteditable">`isContentEditable`</a>
+                  IDL attribute.
+                </p>
+              </th>
+              <td>
+                `aria-expanded="..."`, `aria-details`
+              </td>
+              <td>
+                <p>
+                  Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `command` attribute.
+                </p>
+                <p>
+                  Authors MAY use `aria-details` to modify whether or how the element exposes a details relationship 
+                  with its associated element or other relevant elements.
                 </p>
               </td>
             </tr>
+            <tr id="att-contenteditable" tabindex="-1">
+              <th>
+                <p>
+                  Element with [^html-global/contenteditable^]`=true`
+                  or
+                  element without `contenteditable` attribute whose closest
+                  ancestor with a `contenteditable` attribute has
+                  `contenteditable="true"`.
+                </p>
+                <p class="note">
+                  This is equivalent to the <a data-cite="html/interaction.html#dom-iscontenteditable">`isContentEditable`</a>
+                  IDL attribute.
+                </p>
+              </th>
+              <td>
+                `aria-readonly="false"`
+              </td>
+              <td>
+                Authors MUST NOT set `aria-readonly="true"` on an element that has `isContentEditable="true"`.
+              </td>
+            </tr>
             <tr id="att-disabled" tabindex="-1">
               <th>
                 Any element where the [^input/disabled^]
@@ -3665,13 +3711,6 @@ <h3 id="docconformance-attr">
                 `aria-disabled="true"`
               </td>
               <td>
-                <p>
-                  Use the `disabled` attribute on any element that is allowed the `disabled` attribute in HTML.
-                </p>
-                <p>
-                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-disabled">`aria-disabled`</a> attribute on any element that is allowed the `disabled` attribute in HTML, 
-                  or any element with a WAI-ARIA role which allows the `aria-disabled` attribute</a>.
-                </p>
                 <p>
                   Authors SHOULD NOT use `aria-disabled="true"` on any element which also has a `disabled` attribute.
                 </p>
@@ -3689,21 +3728,23 @@ <h3 id="docconformance-attr">
               </td>
               <td>
                 <p>
-                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-hidden">`aria-hidden`</a> attribute on any HTML element that allows <a data-cite="wai-aria-1.2#global_states">global `aria-*` attributes</a> to 
-                  be specified, with the exception of focusable elements and the <a href="#el-body">`body`</a> element.
+                  It is generally NOT RECOMMENDED for authors to use `aria-hidden="true"` on any element which also has the `hidden` attribute specified. 
+                  Authors MUST NOT use `aria-hidden="true"` on any element which also has the `hidden` attribute specified in the `until-found` state.
                 </p>
                 <p>
-                  It is generally NOT RECOMMENDED for authors to use `aria-hidden="true"` on any element which also has the `hidden` attribute specified. However, authors MUST NOT use `aria-hidden="true"` on any element which also has the `hidden` attribute specified in the `until-found` state.
+                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-hidden">`aria-hidden`</a> attribute on any HTML element that allows 
+                  <a data-cite="wai-aria-1.2#global_states">global `aria-*` attributes</a> to 
+                  be specified, with the exception of focusable elements. The attribute MUST NOT be used on the <a href="#el-body">`body`</a> and <a href="#el-html">`html`</a> elements.
                 </p>
                 <div class="note">
                   A focusable element is any element which can be focused by use of keyboard or pointer device. Focusable elements are not always elements which
-                  can be tabbed to via a keyboard. For instance, an element with `tabindex="-1"` is focusable but is not a tabbable element.
+                  can be tabbed to with a keyboard. For instance, an element with `tabindex="-1"` is focusable but is not a tabbable element.
                 </div>
                 <div class="note">
                   Using `aria-hidden="true"` on an element that has the `hidden` attribute is at best an unnecessary redundancy. At worst its usage can 
                   prevent access to the content if the `hidden` attribute's default UA style of `display: none` has been purposeuflly overwritten by an author or user style sheet.
-                  Finally, if the `hidden` attribute has the value of `until-found`, the use of `aria-hidden=true` will prevent this content from being discoverable to users of assistive
-                  technology when it is found via a browser's in-page find feature and visually rendered to users.
+                  Additionally, if the `hidden` attribute has the value of `until-found`, the use of `aria-hidden=true` will prevent this content from being discoverable to 
+                  users of assistive technology when it is found via a browser's in-page find feature and visually rendered to users.
                 </div>
               </td>
             </tr>
@@ -3715,14 +3756,6 @@ <h3 id="docconformance-attr">
                 `aria-placeholder="..."`
               </td>
               <td>
-                <p>
-                  Use the `placeholder` attribute on any element that is allowed the
-                  `placeholder` attribute in HTML.
-                </p>
-                <p>
-                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-placeholder">`aria-placeholder`</a> attribute on any element that is allowed the `placeholder` attribute in HTML, 
-                  or any element with a WAI-ARIA role which allows the `aria-placeholder` attribute.
-                </p>
                 <p>
                   Authors MUST NOT use the `aria-placeholder` attribute on any element which also has a `placeholder` attribute.
                 </p>
@@ -3730,33 +3763,29 @@ <h3 id="docconformance-attr">
             </tr>
           <tr id="att-popovertarget" tabindex="-1">
               <th>
-                Any element where the <a data-cite="html/popover.html#the-popover-target-attributes">`popovertarget`</a> attribute is allowed: 
-                [^button^], 
-                <a data-cite="html/input.html#button-state-(type=button)">`input type=button`</a>,
-                <a data-cite="html/input.html#button-state-(type=image)">`input type=image`</a>,
-                <a data-cite="html/input.html#reset-button-state-(type=reset)">`input type=reset`</a>
-                <a data-cite="html/input.html#submit-button-state-(type=submit)">`input type=submit`</a>
+                Any element where the <a data-cite="html/popover.html#the-popover-target-attributes">`popovertarget`</a> attribute is allowed
               </th>
               <td>
-                `aria-expanded="..."`
+                `aria-expanded="..."`, `aria-details`
               </td>
               <td>
-                <p class="addition">
+                <p>
                   Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `popovertarget` attribute.
                 </p>
+                <p>
+                  Authors MAY use `aria-details` to modify whether or how the element exposes a details relationship 
+                  with its associated `popover` or other relevant elements.
+                </p>
               </td>
             </tr>
             <tr id="att-max" tabindex="-1">
               <th>
-                Any element where the `max` attribute is allowed: `meter` [^meter/max^], `progress` [^progress/max^], and `input` [^input/max^]
+                Any element where the `max` attribute is allowed
               </th>
               <td>
                 `aria-valuemax="..."`
               </td>
               <td>
-                <p>
-                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-valuemax">`aria-valuemax`</a> attribute on any other element with a WAI-ARIA role which allows the `aria-valuemax` attribute.
-                </p>
                 <p>
                   Authors SHOULD NOT use `aria-valuemax` on any element which allows the `max` attribute. Use the `max` attribute instead.
                 </p>
@@ -3767,15 +3796,12 @@ <h3 id="docconformance-attr">
             </tr>
             <tr id="att-min" tabindex="-1">
               <th>
-                Any element where the `min` attribute is allowed: `meter` [^meter/min^] and `input` [^input/min^]
+                Any element where the `min` attribute is allowed
               </th>
               <td>
                 `aria-valuemin="..."`
               </td>
               <td>
-                <p>
-                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-valuemax">`aria-valuemin`</a> attribute on any other element with a WAI-ARIA role which allows the `aria-valuemin` attribute.
-                </p>
                 <p>
                   Authors SHOULD NOT use `aria-valuemin` on any element which allows the `min` attribute. Use the `min` attribute instead.
                 </p>
@@ -3786,16 +3812,12 @@ <h3 id="docconformance-attr">
             </tr>
             <tr id="att-readonly" tabindex="-1">
               <th>
-                Any element which allows the `readonly` attribute:
-                `input` [^input/readonly^], `textarea` [^textarea/readonly^] and <a>form-associated custom element</a> which allows [^form-associated custom elements/readonly^]
+                Any element which allows the `readonly` attribute
               </th>
               <td>
                 `aria-readonly="true"`
               </td>
               <td>
-                <p>
-                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-readonly">`aria-readonly`</a> attribute on any element with a WAI-ARIA role which allows the attribute</a>.
-                </p>
                 <p>
                   Authors SHOULD NOT use the `aria-readonly="true"` on any element which also has a `readonly` attribute.
                 </p>
@@ -3804,28 +3826,6 @@ <h3 id="docconformance-attr">
                 </p>
               </td>
             </tr>
-            <tr id="att-contenteditable" tabindex="-1">
-              <th>
-                <p>
-                  Element with [^html-global/contenteditable^]`=true`
-                  or
-                  element without `contenteditable` attribute whose closest
-                  ancestor with a `contenteditable` attribute has
-                  `contenteditable="true"`.
-                </p>
-                <p class="note">
-                  This is equivalent to the <a data-cite=
-                  "html/interaction.html#dom-iscontenteditable">`isContentEditable`</a>
-                  IDL attribute.
-                </p>
-              </th>
-              <td>
-                `aria-readonly="false"`
-              </td>
-              <td>
-                Authors MUST NOT set `aria-readonly="true"` on an element that has `isContentEditable="true"`.
-              </td>
-            </tr>
             <tr id="att-required" tabindex="-1">
               <th>
                 Any element where the `required` attribute is allowed: `input` [^input/required^], `textarea` [^textarea/required^], and `select` [^select/required^]
@@ -3834,9 +3834,6 @@ <h3 id="docconformance-attr">
                 `aria-required="true"`
               </td>
               <td>
-                <p>
-                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-required">`aria-required`</a> attribute on any element that is allowed the `required` attribute in HTML, or any element with a WAI-ARIA role which allows the `aria-required` attribute.
-                </p>
                 <p>
                   Authors SHOULD NOT use the `aria-required="true"` on any element which also has a `required` attribute.
                 </p>
@@ -3853,18 +3850,11 @@ <h3 id="docconformance-attr">
                 `aria-colspan="..."`
               </td>
               <td>
-                <!--
-                  Removing per issue #338
-                  Revised rules to be re-added
-                <p>
-                  Authors MAY use the `aria-colspan` attribute on any element that is allowed the `colspan` attribute in HTML, or any element with a WAI-ARIA role which allows the <a data-cite="wai-aria-1.2#aria-colspan">`aria-colspan` attribute</a>.
-                </p>
-                -->
                 <p>
                   Authors SHOULD NOT use the `aria-colspan` attribute on any element which also has a `colspan` attribute.
                 </p>
                 <p>
-                  Authors MUST NOT use `aria-colspan` on any element which also has a `colspan` attribute, and the values of each attribute do not match.
+                  Authors MUST NOT use `aria-colspan` on any element which also has a `colspan` attribute.
                 </p>
               </td>
             </tr>
@@ -3877,18 +3867,11 @@ <h3 id="docconformance-attr">
                 `aria-rowspan="..."`
               </td>
               <td>
-                <!--
-                  Removing per issue #338
-                  Revised rules to be re-added
-                <p>
-                  Authors MAY use the `aria-rowspan` attribute on any element that is allowed the `rowspan` attribute in HTML, or any element with a WAI-ARIA role which allows the <a data-cite="wai-aria-1.2#aria-rowspan">`aria-rowspan` attribute</a>.
-                </p>
-                -->
                 <p>
                   Authors SHOULD NOT use the `aria-rowspan` attribute on any element which also has a `rowspan` attribute.
                 </p>
                 <p>
-                  Authors MUST NOT use `aria-rowspan` on any element which also has a `rowspan` attribute, and the values of each attribute do not match.
+                  Authors MUST NOT use `aria-rowspan` on any element which also has a `rowspan` attribute.
                 </p>
               </td>
             </tr>

From 4dbf1a45d3c11490da0ec6aee25626c3e334ac4d Mon Sep 17 00:00:00 2001
From: Scott O'Hara <scottaohara@users.noreply.github.com>
Date: Wed, 9 Apr 2025 09:38:55 -0400
Subject: [PATCH 4/4] finish command guidance

update the first column which had copied the `contenteditable` content to the correct `command` related content.

update the allowances for aria-expanded to only be applicable to the toggle/show/hide popover states - since that's where the implicit conflict would come into play.

other wording fixes for the attribute table cleanup that i was doing in this PR as well - for better/worse since that arguably should have been another PR... but the work is done so here it is...
---
 index.html | 63 ++++++++++++++++++++++++------------------------------
 1 file changed, 28 insertions(+), 35 deletions(-)

diff --git a/index.html b/index.html
index cfdee9c..1f59bf0 100644
--- a/index.html
+++ b/index.html
@@ -3655,15 +3655,7 @@ <h3 id="docconformance-attr">
             <tr id="att-command" tabindex="-1">
               <th>
                 <p>
-                  Element with [^html-global/contenteditable^]`=true`
-                  or
-                  element without `contenteditable` attribute whose closest
-                  ancestor with a `contenteditable` attribute has
-                  `contenteditable="true"`.
-                </p>
-                <p class="note">
-                  This is equivalent to the <a data-cite="html/interaction.html#dom-iscontenteditable">`isContentEditable`</a>
-                  IDL attribute.
+                  Any element where the <a data-cite="html/form-elements.html#attr-button-command">`command`</a> attribute is allowed
                 </p>
               </th>
               <td>
@@ -3671,7 +3663,7 @@ <h3 id="docconformance-attr">
               </td>
               <td>
                 <p>
-                  Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `command` attribute.
+                  Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `command` attribute in the <strong>Toggle popover</strong>, <strong>Show popover</strong> or <strong>Hide popover</strong> state. E.g., `command=toggle-popover`, `command=show-popover` or `command=hide-popover`.
                 </p>
                 <p>
                   Authors MAY use `aria-details` to modify whether or how the element exposes a details relationship 
@@ -3703,9 +3695,7 @@ <h3 id="docconformance-attr">
             <tr id="att-disabled" tabindex="-1">
               <th>
                 Any element where the [^input/disabled^]
-                attribute is allowed, including
-                `option` [^option/disabled^] and
-                `optgroup` [^optgroup/disabled^]
+                attribute is allowed
               </th>
               <td>
                 `aria-disabled="true"`
@@ -3732,16 +3722,16 @@ <h3 id="docconformance-attr">
                   Authors MUST NOT use `aria-hidden="true"` on any element which also has the `hidden` attribute specified in the `until-found` state.
                 </p>
                 <p>
-                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-hidden">`aria-hidden`</a> attribute on any HTML element that allows 
+                  Authors MAY use the <a data-cite="wai-aria-1.2#aria-hidden">`aria-hidden`</a> attribute on an element that allows 
                   <a data-cite="wai-aria-1.2#global_states">global `aria-*` attributes</a> to 
                   be specified, with the exception of focusable elements. The attribute MUST NOT be used on the <a href="#el-body">`body`</a> and <a href="#el-html">`html`</a> elements.
                 </p>
                 <div class="note">
-                  A focusable element is any element which can be focused by use of keyboard or pointer device. Focusable elements are not always elements which
+                  A focusable element is an element which can be focused by use of keyboard or pointer device. Focusable elements are not always elements which
                   can be tabbed to with a keyboard. For instance, an element with `tabindex="-1"` is focusable but is not a tabbable element.
                 </div>
                 <div class="note">
-                  Using `aria-hidden="true"` on an element that has the `hidden` attribute is at best an unnecessary redundancy. At worst its usage can 
+                  Using `aria-hidden="true"` on an element that has the `hidden` attribute is at best an unnecessary redundancy. At worst, its usage can 
                   prevent access to the content if the `hidden` attribute's default UA style of `display: none` has been purposeuflly overwritten by an author or user style sheet.
                   Additionally, if the `hidden` attribute has the value of `until-found`, the use of `aria-hidden=true` will prevent this content from being discoverable to 
                   users of assistive technology when it is found via a browser's in-page find feature and visually rendered to users.
@@ -3757,7 +3747,7 @@ <h3 id="docconformance-attr">
               </td>
               <td>
                 <p>
-                  Authors MUST NOT use the `aria-placeholder` attribute on any element which also has a `placeholder` attribute.
+                  Authors MUST NOT use the `aria-placeholder` attribute on an element which also has a `placeholder` attribute.
                 </p>
               </td>
             </tr>
@@ -3770,10 +3760,10 @@ <h3 id="docconformance-attr">
               </td>
               <td>
                 <p>
-                  Authors MUST NOT use the `aria-expanded` attribute on any element which also has a `popovertarget` attribute.
+                  Authors MUST NOT use the `aria-expanded` attribute on an element which also has a `popovertarget` attribute.
                 </p>
                 <p>
-                  Authors MAY use `aria-details` to modify whether or how the element exposes a details relationship 
+                  Authors MAY use `aria-details` to modify whether or how an element exposes a details relationship 
                   with its associated `popover` or other relevant elements.
                 </p>
               </td>
@@ -3787,10 +3777,11 @@ <h3 id="docconformance-attr">
               </td>
               <td>
                 <p>
-                  Authors SHOULD NOT use `aria-valuemax` on any element which allows the `max` attribute. Use the `max` attribute instead.
+                  Authors SHOULD NOT use `aria-valuemax` on an element which allows the `max` attribute. 
+                  Use the `max` attribute instead.
                 </p>
                 <p>
-                  Authors MUST NOT use `aria-valuemax` on any element which also has a `max` attribute.
+                  Authors MUST NOT use `aria-valuemax` on an element which also has a `max` attribute.
                 </p>
               </td>
             </tr>
@@ -3803,10 +3794,11 @@ <h3 id="docconformance-attr">
               </td>
               <td>
                 <p>
-                  Authors SHOULD NOT use `aria-valuemin` on any element which allows the `min` attribute. Use the `min` attribute instead.
+                  Authors SHOULD NOT use `aria-valuemin` on an element which allows the `min` attribute. 
+                  Use the `min` attribute instead.
                 </p>
                 <p>
-                  Authors MUST NOT use `aria-valuemin` on any element which also has a `min` attribute.
+                  Authors MUST NOT use `aria-valuemin` on an element which also has a `min` attribute.
                 </p>
               </td>
             </tr>
@@ -3819,59 +3811,60 @@ <h3 id="docconformance-attr">
               </td>
               <td>
                 <p>
-                  Authors SHOULD NOT use the `aria-readonly="true"` on any element which also has a `readonly` attribute.
+                  Authors SHOULD NOT use the `aria-readonly="true"` on an element which also has a `readonly` attribute.
                 </p>
                 <p>
-                  Authors MUST NOT use `aria-readonly="false"` on any element which also has a `readonly` attribute.
+                  Authors MUST NOT use `aria-readonly="false"` on an element which also has a `readonly` attribute.
                 </p>
               </td>
             </tr>
             <tr id="att-required" tabindex="-1">
               <th>
-                Any element where the `required` attribute is allowed: `input` [^input/required^], `textarea` [^textarea/required^], and `select` [^select/required^]
+                Any element where the `required` attribute is allowed
               </th>
               <td>
                 `aria-required="true"`
               </td>
               <td>
                 <p>
-                  Authors SHOULD NOT use the `aria-required="true"` on any element which also has a `required` attribute.
+                  Authors SHOULD NOT use the `aria-required="true"` on an element which also has a `required` attribute.
                 </p>
                 <p>
-                  Authors MUST NOT use `aria-required="false"` on any element which also has a `required` attribute.
+                  Authors MUST NOT use `aria-required="false"` on an element which also has a `required` attribute.
                 </p>
               </td>
             </tr>
             <tr id="att-colspan" tabindex="-1">
               <th>
-                Any element where the [^th/colspan^] attribute is allowed: `td` and `th`
+                Any element where the [^th/colspan^] attribute is allowed
               </th>
               <td>
                 `aria-colspan="..."`
               </td>
               <td>
                 <p>
-                  Authors SHOULD NOT use the `aria-colspan` attribute on any element which also has a `colspan` attribute.
+                  Authors SHOULD NOT use `aria-colspan` on an element which allows the `colspan` attribute. 
+                  Use the `colspan` attribute instead.
                 </p>
                 <p>
-                  Authors MUST NOT use `aria-colspan` on any element which also has a `colspan` attribute.
+                  Authors MUST NOT use `aria-colspan` on an element which also has a `colspan` attribute.
                 </p>
               </td>
             </tr>
             <tr id="att-rowspan" tabindex="-1">
               <th>
-                Any element where the [^th/rowspan^] attribute is allowed:
-                `td` and `th`
+                Any element where the [^th/rowspan^] attribute is allowed
               </th>
               <td>
                 `aria-rowspan="..."`
               </td>
               <td>
                 <p>
-                  Authors SHOULD NOT use the `aria-rowspan` attribute on any element which also has a `rowspan` attribute.
+                  Authors SHOULD NOT use the `aria-rowspan` attribute on an element which allows the `rowspan` attribute. 
+                  Use the `rowspan` attribute instead.
                 </p>
                 <p>
-                  Authors MUST NOT use `aria-rowspan` on any element which also has a `rowspan` attribute.
+                  Authors MUST NOT use `aria-rowspan` on an element which also has a `rowspan` attribute.
                 </p>
               </td>
             </tr>