mark custom elements missing an open shadow for needs review if it fails a rule

If a custom element is picked up by a rule it can fail under two cases which probably shouldn’t:

1. the element isn’t defined in the CustomElementRegistry
2. the element is defined but uses a closed shadow root

It would be nice if axe-core detected these two cases and marked the element as needs review rather than fail it for any rule it fails.

We can easily detect the first case by using CustomElement.get to see if the element name has been defined. For the 2nd case, it might be safe enough to assume that if the element is defined but does not have content or an open shadow root, it has a closed shadow root and we should mark it for needs review as we can’t tell for certain anything about the node.

[dbjorge]

+1 for case 2; we just hit a case today where an Accessibility Insights user contacted us about a false positive in the aria-required-parent rule where a custom element of form <custom-tree-item role="treeitem" /> is slotted into a <div role="group"> that is hidden behind a closed shadow root. Repro codepen

[straker]

@brennanyoung until AOM is adopted and supported, custom element won’t expose any accessibility semantics by themselves. So a user would have to add all that information themselves to the DOM.