Merge pull request #2375 from w3c/popover-states-clarification

Update: minor popover clarification

html-aam/index.html

@@ -13415,10 +13415,11 @@ <h4 id="att-popover">`popover`</h4>
                 <p>User agents MUST NOT expose a details relation between a `popover` and its invoking element under the following conditions:</p>
                 <ul>
                   <li>when the `popover` is the next immediate accessibility sibling to the invoking element,</li>
-                  <li>when the element has a `popovertarget=hide` attribute value,</li>
+                  <li>when the element has a `popovertargetaction=hide` attribute value,</li>
                   <li>or when the element is a descendant of the `popover` and its `popovertarget` is the "`auto`" state.</li>
                 </ul>
-                <p>If specified on an element with an implicit role of `generic`, then the element's role instead maps to <a class="core-mapping" href="#role-map-group">`group`</a>.</p>
+                <p>If specified on an element with an implicit role of `generic`, then the element's role instead maps to <a class="core-mapping" href="#role-map-group">`group`</a> for all <a data-cite="html/popover.html#the-popover-attribute">`popover` states</a>.</p>
+                <p class="note">There are no unique mappings for the different `popover` states. Any accessibility mapping changes for the popover element would be the responsibility of the author. e.g., using different base HTML elements, attributes, or ARIA attributes to make such changes.</p>
               </td>
             </tr>
           </tbody>