Skip to content

Commit b4b8ceb

Browse files
authored
Update: minor popover clarification
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.
1 parent 83872bf commit b4b8ceb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

html-aam/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13368,7 +13368,7 @@ <h4 id="att-popover">`popover`</h4>
1336813368
<li>when the element has a `popovertarget=hide` attribute value,</li>
1336913369
<li>or when the element is a descendant of the `popover` and its `popovertarget` is the "`auto`" state.</li>
1337013370
</ul>
13371-
<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>
13371+
<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>
1337213372
</td>
1337313373
</tr>
1337413374
</tbody>

0 commit comments

Comments
 (0)