No I am not saying that. I am saying that when you are doing hobby projects anything will do but when you are doing commercial projects things like accessibility are table stakes, as in if you don’t meet basic accessibility requirements that are codified in various regulations you don’t get to play.
Elixir does not have a LiveView UI component library, not one that has any focus on meeting accessibility requirements. There is one in the making Doggo which I have encouraged as addressing a huge gap.
I am willing to pay and have evaluated a number of libraries including Tailwind UI which was also not a good fit for Phoenix as in there is a lot they don’t provide in the html version that which is addressed in their React components.
The petal components also don’t meet requirements so no I wouldn’t pay for something that is not headless semantic UI with first class consideration for web standards accessibility, keyboard navigation and themeable second.
I am not ok with not addressing a11y concerns and Phoenix has a gap that currently can only be addressed by solutions outside of its ecosystem which means a11y web components or building the UI with a JS framework.
