If you do switch what would you switch to?
All of our components are built for keyboard / screenreader support and accessibility was one of our primary goals since the beginning. We take it serious and it's baked into our review process. It's fairly mature and is now two and a half years old with a solid team working on it full time. At the very least you might find some ideas for your projects. It's also TypeScript-backed and themable through a Sass layer with native dark mode support.
We welcome contributions and if there's any students out there thinking about hacking on a component library for summer of code you can find some projects over here[3].
Other projects out there similar to ours that are pretty mature are Microsoft's Fabric[4] and Atalassian's Atlas Kit[5]. Both of which are open source as well. Generally we tend to have more features, and they might be a little easier to theme or modularize. Chakra UI[6] is a new comer that is smaller, but people seem to like as well. There are a lot of options these days and most of them are tailored towards a certain use case, since it's hard to target everything.
I research this stuff a lot so if anyone has any questions about component libs give a yell.
[1]: https://github.com/elastic/eui [2]: https://elastic.github.io/eui/#/ [3]: https://github.com/elastic/gsoc [4]: https://developer.microsoft.com/en-us/fabric#/ [5]: https://atlaskit.atlassian.com/ [6]: https://chakra-ui.com/
I'm intrigued by Tailwind UI though, it looks like it might be the right balance between feature set and brand agnosticism.