Re: [webcomponents] Closed flag proposal breaks ability to audit and automate tests of web pages (#354)

@annevk apology accepted!

Actually, this proposal will break the internal auditing tools of at least Mozilla and Chrome.

Currently our aXe extension is the de-facto accessibility auditing tool for Firefox and will break with these changes. We have not started work on web components support, in part because we want to see how the spec shakes out.

Chrome's current implementation relies on traversing the shadowRoot https://github.com/GoogleChrome/accessibility-developer-tools/blob/master/src/js/DOMUtils.js#L121. And while I know there is some work ongoing to get this extension into the standard dev tools and not make it a separate extension, it is not clear that that work will circumvent/solve the problem.

I would like to contribute to the solution, here are some proposals:

1. If there is a publicly available implementation of the closed flag, I could attempt to use @rniwa's proposed circumvention and see how that pans out for the use cases I know of (testing and auditing)
2. I could take the use cases referenced here https://wiki.whatwg.org/wiki/Component_Model_Use_Cases and try to analyze them from a rigorous problem solution perspective
3. I could try to formally gather from the group members the specific examples of use cases that have caused trouble and document these so we can analyze/discuss them

thoughts?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/354#issuecomment-188061942