I don't have a problem with companies explicitly choosing not to make the apps accessible, unless I'm forced to use them, or they were accessible and it's hard

I don't have a problem with companies explicitly choosing not to make the apps accessible, unless I'm forced to use them, or they were accessible and it's hard to switch now. I have a problem with UI toolkit developers dismissing accessibility entirely and then companies using those "cool things" to build apps. If you build an inaccessible web app and you want to add a11y later on, you reasonably can. It might be hard, but it's usually doable. If you use a toolkit like this though, you're completely, hopelessly screwed. You can't do anything without rewriting half of the toolkit to support an alternative DOM representation, which will probably affect your performance. I've never seen that done. Either the companies just give up or moan about the shitload of money they've wasted and rebuild the app using normal web components, or build an alternative. Sometimes the law just forces them to, and the toolkit forces them not to. Imagine the sums of money you can waste on this.