Manuel MatuzovićMay 19

Last week I stumbled upon yet another accessibility testing tool that doesn't support shadow DOM (an extension called taba11y). Web components are getting more popular, which means that confusing testing results may become more frequent if you're using the wrong tool.

PS: I contacted the developer and they replied quickly and friendly and told me that they'll try to find a solution.

https://www.matuzo.at/blog/2024/automated-testing-tools-and-web-components

Not all automated testing tools support Shadow DOM in web components - Manuel Matuzovic

I'm a frontend developer in Graz, specialized in HTML, accessibility, and CSS layout and architecture.

Manuel Matuzovic
Show threadwestbrook

@matuzo Shadow DOM isn’t the only part of the platform that #webComponent popularity is adding pressure on automated tools to support. Things like Element Internals are getting left off the menu in many places, like https://github.com/dequelabs/axe-core/issues/4259, just as they and soon things like Reference Targets start to expand as well. 🥺

#webDev #a11y #testTheWebForward

Custom Elements using `ElementInternals` to set `role` are flagged when `aria-label` is provided · Issue #4259 · dequelabs/axe-core

Product axe-core Product Version 4.8.2 Latest Version I have tested the issue with the latest version of the product Issue Description We are currently migrating our Web Component library to use th...

GitHub
May 19 at 8:13amWeb