@knowler MDN accepts PRs…
I started working on https://github.com/Westbrook/axe-core-element-internals as a test bed for #ElementInternals usage for ace-core, but maybe more useful at large for these APIs. I accept PRs, too. 🤗
Also, we’re looking to reignite the push for community docs and guides for WCs in https://discord.gg/KzgaSbGc9q to clarify these sorts of things, as well.
Initial PR to #webPlatformTests to ensure that #elementInternals behaves the same x-browser in response to the above: https://github.com/web-platform-tests/wpt/pull/47233
How have you worked to make the web a better place today?
Yes, the inclusion of axe-core in Lighthouse testing is a great advancement for the #a11y coverage of the tool at large. However, the axe-core's inability to cover #elementInternals in #webComponents is gonna be a huge pain in that it will publish A LOT of false negatives. A test that is "always red" is a test that doesn't get looked at when it gets "more red".
Even if axe-core can't read element internals by default, can't we get a partnership between it and DevTool protocol in this context?
Do you use #elementInternals? A powerful set of APIs to support custom elements in behaving more like native ones.
Do you have thoughts on how we might approach the APIs from a #declarative standpoint? Declarativity is a key ingredient to SSR and low or no JS delivery of features.
We'd love to hear from you in the #webComponentsCG! Come join the conversation at https://discord.gg/YmrNQ4rYJz
