Caridy Patiño

@SiTaggart > Feels super weird that delegateFocus would be that vehicle. That's ok, maybe we can decouple this from focus, and just have a new configuration for shadow root that...

This is superseded by the proposal in https://github.com/WICG/aom/issues/169, which is a lot more coherent.

@cookiecrook @alice @minorninth do you have any preference on where to discuss the naming, type, default-value, etc for the new ARIA property reflection and names? We will like to help...

> I'm pretty concerned that if the polyfill catches on folks will begin to expect that behavior... The concern is not only CSS and query selectors (which I think it...

I'm very excited about this one, thanks @rniwa for taking the time to address this. We raised that concern in https://github.com/WICG/aom/issues/107 more than a year ago about programatic access to...

Overall, I do like @rniwa's proposal, aside from @robdodson's comment, which I think is very valid. But the part that is still concerning with respect to the 2nd bullet from...

@alice is the new convention for `myElement.aria*` properties specified somewhere? I know that this is the new direction, but I haven't seen any formalization of the convention in this repo.

@alice, in the example above, when you mention that `ariaActiveDescendantElement` overrides `ariaActiveDescendant`, are you referencing to the internal representation used by SR? If the answer to that question is "yes",...

By looking at what is specified today, it seems that the list of properties that will be related to this issue are: ```js partial interface Element { attribute DOMString ariaActiveDescendant;...

I can probably help with this.