I don’t think you understand to intent of my post. It is about the gap that exists which really does need to be addressed for Phoenix to remain viable in an ecosystem that often must provide accessibility out of the box.
I am not complaining that the community hasn’t somehow meet all my needs which you continue to insinuate.
I have been using my own resources to experiment with web components to close the gap and will be providing some sample apps for others to follow if they wish to go down that path also. Thats me, not someone else.
So far I have experimented with Shoelace, Adobe Spectrum, and the most recent is Carbon Design System v11 which is by far the best so far and the front runner for a LiveView solution.
Carbon does accessibility very well as the framework has strong design principles. It also provides the essential navigation elements that all the web components lack.
Carbon web components gets as close to parity with a JS front end that LiveView is likely to get in terms of interactivity and accessibility currently, to the point it would likely be the same choice of components with JS Svelte or React or Vue as well.
I will be sharing a starter project on using Carbon with Liveview.