search

leobalter / cross-root-aria-delegation

Explainer for the Cross-root ARIA delegation proposal
https://leobalter.github.io/cross-root-aria-delegation/
25 stars 3 forks source link

Delegate something that isn't provided #21

Open mrego opened 1 year ago

mrego commented 1 year ago

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:

<x-foo>
  <template shadowroot="closed" shadowrootdelegatesariaattributes="aria-label">
    <input id="input" delegatedariaattributes="aria-label" />
  </template>
</x-foo>
nolanlawson commented 1 year ago

What do you mean by "provided implicitly"? Does this overlap with ElementInternals?

mrego commented 1 year ago

Probably @bkardell can clarify, as this is a question from him in the original issue.

bkardell commented 1 year ago

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?

nolanlawson commented 1 year ago

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).

keithamus commented 1 year ago

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.