Open mrego opened 1 year ago
What do you mean by "provided implicitly"? Does this overlap with ElementInternals
?
Probably @bkardell can clarify, as this is a question from him in the original issue.
Yeah, I just meant that you could have something like
<label for="x">Favorite Quote</label>
<rich-text id="x">
(ShadowRoot)
(Some stuff)
(The actual area that should have a label)
</rich-text>
and if you are literally just delegating attributes down the tree that doesn't help all of the native built-in roles/relationships I guess?
Is this the same as reflection/exporting? In your example, the for
IDref is pointing down into the shadow root. (As opposed to delegation/importing, where it points out of a shadow root.)
Also related: #13 (since for
is not technically ARIA).
WCCG had their spring F2F in which this was discussed. You can read the full notes of the discussion (https://github.com/WICG/webcomponents/issues/978#issuecomment-1516897276) in which this was discussed, heading entitled "ARIA Mixin & Cross Root ARIA" - where this issue was specifically discussed.
In the meeting, present members of WCCG reached a consensus to discuss further in breakout sessions. I'd like to call out that https://github.com/WICG/webcomponents/issues/1005 is the tracking issue for that breakout, in which this will likely be discussed.
This is a separated issue extracted from https://github.com/leobalter/cross-root-aria-delegation/issues/7.
What should happen if you delegate something and it isn't provided? Could it be provided implicitly somehow?
Example: