Also wondering about ARIA element reflection (ariaDescribedByElements, ariaOwnsElements, etc.) ?
We already have an implementation of ARIA element reflection in Blink, but it isn't shipping yet, and has likely fallen into disrepair (for more info about that, I just added comment 25 <http://comment%2025> in the original feature bug). I feel like in order to ship the new exciting technique, we should also ship the original technique. Interested in hearing everyone's thoughts. Thanks, Aaron On Friday, September 22, 2023 at 7:35:09 PM UTC-4 Ben Howell wrote: > Contact emails > > sligh...@chromium.org, alexr...@microsoft.com, beho...@microsoft.com > > > Explainer > > https://github.com/WICG/aom/blob/gh-pages/exportid-explainer.md > > > Specification > > None > > > Summary > > Exported IDs are a way to refer to elements inside a shadow tree from an > ID reference attribute like `aria-labelledby` or `for`, while preserving > shadow DOM encapsulation. There is a new attribute `exportid` to mark an > element as having its ID exported from the shadow root, and a new syntax to > refer to the element from outside the shadow root: `for="host::id(child)"`. > There is also a new attribute `useids` to allow referring to elements > outside of the shadow tree. More details are in the explainer. Together > these features allow creating ARIA relationships across the shadow tree > boundary. > > > > > Blink component > > Blink>DOM>ShadowDOM > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EDOM%3EShadowDOM> > > > Motivation > > The Shadow DOM presents a problem for accessibility: there is not a way to > establish semantic relationships between elements on in different shadow > trees (such as aria-labelledby). This limits the ability to design web > components in a way that works with accessibility tools such as screen > readers. Exported IDs solve this problem by giving a way to create semantic > relationships between elements in a way that respects shadow DOM > encapsulation. The specifics of the proposal are detailed in the linked > explainer. > > > > > Initial public proposal > > https://github.com/WICG/aom/pull/204 > > > TAG review > > None > > > TAG review status > > Pending > > > Risks > > > > > Interoperability and Compatibility > > None > > > > *Gecko*: No signal > > *WebKit*: No signal > > *Web developers*: No signals > > *Other signals*: > > > WebView application risks > > *Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications?* > > None > > > > > Debuggability > > None > > > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? > > No > > > Flag name on chrome://flags > > None > > > Finch feature name > > None > > > Non-finch justification > > None > > > Requires code in //chrome? > > False > > > Estimated milestones > > No milestones specified > > > > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5188237101891584 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fcf759fe-ca23-47d3-8ed7-42bda450a19cn%40chromium.org.
