For those of us who do, time has told us again and again and again and again and again, and we're kinda sick of time telling us to just hold tight when everything we need is right there in the native frameworks.
Every project has to start somewhere and as you can tell from this comment page there are many groups of users who feel we have not met their expectations...
I imagine that level of criticism must be demoralizing. (That's why I didn't pile on, though I've been vocal about accessibility on similar threads about other toolkits.)
Just so I can understand where you're coming from, what's your motivation for developing yet another custom toolkit, despite all the challenges and all the table-stakes requirements that haven't yet been met? There must be some reason you feel this is a worthwhile use of your time, but I don't understand what it is.
Basically having seen the revolution in usability, software design and raised expectations on mobile it was frustrating that desktop had stagnated. Having a toolkit that was slim, easy to learn, cross platform and sweet looking seemed like a worthwhile challenge :).
I think you've inflated the expectations by creating a 1.0 release, that's a point where you'd expect things like accessibility to be included. Had it still been 0.x then you'd get a lot more leeway on missing features.
It would also be great to list these limitations on the main page, anyone that finds those limitation important can then avoid it, they'll be a lot less annoyed than someone who invested a lot of time learning to use Fyne only to discover the limitations.