Tomasz Jakut

@annevk @snuggs AFAIK `[property]` is defined as a [part of RDFa standard](https://www.w3.org/TR/rdfa-primer/#h-using-the-content-attribute).

According to the ARIA spec, elements with the `row` role (and [`` elements have it by default](https://w3c.github.io/html-aria/#:~:text=or%20aria%2D*%20attributes-,tr,role%3Drow,-If%20the%20ancestor)) can only contain [children with the `cell` role](https://w3c.github.io/aria/#row:~:text=Accessibility%20Child%20Roles%3A-,cell,rowheader,-Supported%20States%20and). However, due to how we...

What screen reader did you test? VoiceOver? It would be better to test it in English and to also test JAWS and NVDA. > It works, but it stopped announcing...

If you have a control over the custom element itself, there is no issue with getting its owner document, so you have full access to the `body`. However I'm not...

And now it's good again ;) https://jsfiddle.net/pp7z788w/2/ Maybe the use of `position: fixed` and positioning against visible viewport (not the whole page) could be a way to go?

> BTW, @Comandeer, do you know the place in the CSS spec clarifying why position:fixed behaves differently that position:absolute in this case? :D [Of course](https://drafts.csswg.org/css-position/#fixed-pos): > Fixed positioning is similar...

> For this case it's hard for me to imagine the custom element application, because you actually want to make an existing, normal element, an editor. Look into my demo...

Back in December, Safari had totally different implementation of Shadow DOM than Chrome – it lacked Selection on shadow root. Because of that experimental plugin for CKEditor 4 with Shadow...

It shouldn't violate WCAG as a focus indicator is needed only for keyboard navigation.