Been reading a few new articles on Web Components and accessibility, which lead me to re-read an old post I wrote: Notes on Web Components + ARIA. I noted the demo was broken, presumably as the web component syntax had changed since 2012. So I decided to make a few new tests:
What I found was that anything that relies upon an
id association between content in the DOM and Shadow DOM breaks (note need to run latest Chrome or Firefox Nightly ,with web components flag enabled, to test):
Some HTML examples:
- document fragment links (#blah) – if the link target is in the shadow or visa versa
- label for/id association in DOM for controls in the shadow DOM
Most ARIA relationship attributes:
will this be fixed?
Discussion is occurring in regards to the ARIA issues – ARIA relationships via selector
Would you want to use an id association across the DOM/ Shadow DOM boundary? Wouldn’t that rather negate the value of encapsulation?
hi bruce, I think that being able to link to a document fragment inside a component,
https://plauke.com/#ballsfor example, is a reasonable use case, but as I said on twitter I am not forming a value judgement, just flagging a potential issue, that people more knowledgeable than I, have been discussing in the dark corners of Googledom.