Components are not accessible by screen readers.
the most of components are not accessible by screen readers, so we can revisit every component and check it and make it accessible.
I can help with that but we need to discuss the way to revisit components and how acceptable changes we can do to avoid any compatibility issue with current users.
Thanks for the issue @Muhnad ! We are definitely open to making changes to make the components more accessible.
In general, my approach would be to value accessibility over making breaking changes to the API. In other words, we are open to making breaking API changes if it makes the components more accessible.
Cross-referencing this with #253 . One of the goals before the v1.0.0 release is to improve accessibility.