Skip to content

Commit

Permalink
Update: minor popover clarification
Browse files Browse the repository at this point in the history
to acknowledge there are different popover states (manual, auto/empty-string, and the proposed hint) this minor update clarifies that the minimum role of group applies to all popover states.

Is it worth also adding this note, or something like it?

There are no unique mappings for different popover states. Any additional accessibility mapping changes would be the responsibility of the author. e.g, using different base HTML elements, attributes, or ARIA attributes to make such changes.
  • Loading branch information
scottaohara authored Nov 15, 2024
1 parent 83872bf commit b4b8ceb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion html-aam/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -13368,7 +13368,7 @@ <h4 id="att-popover">`popover`</h4>
<li>when the element has a `popovertarget=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>
</td>
</tr>
</tbody>
Expand Down

0 comments on commit b4b8ceb

Please sign in to comment.