-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
relationship between native semantics of HTML popover feature and ARIA might need to be normalized. #513
Comments
Nothing specifically for the popover attribute itself popovertarget on a button should not have an aria-expanded declared with it. |
Might
And there's also |
It doesn’t have an implicit aria-controls. popovertargetaction doesn’t add any a11y semantics |
I think maybe we cannot safely exclude (at least in any case) the possibility of an implicit
That is to say, it might be proper to have an implicit |
Being that I helped spec what was to be implemented for popover and its related attributes, I'm very confident that aria-controls is not used, nor is it going to be implicitly used. It'd be very rare to have a popover as a child of the popovertarget - since that attribute is only valid on buttons. In the few cases where that could happen, an aria-controls relationship would be useless (beyond the fact that aria-controls is already pretty useless outside of with comboboxes). |
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.
The current spec hasn't mentioned anything about
popover
, which is a new HTML feature.The relationship between native semantics of HTML
popover
feature and ARIA might need to be normalized.The text was updated successfully, but these errors were encountered: