-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessability #7
Comments
Fully agree here, the UI components looks and feels amazing but as long as they're not accessible I won't consider using this. Radix UI/shadcn also looks and feels amazing, but the fact the components are also fully accessible is really the main reason for me why I use them and why they bring so much value to all kinds of projects. Also, really want to take the time to say that the work you guys have done with PinesUI so far is terrific! 👏 |
+1. Accessibility is really important. Exhibit A: https://www.accessibility.com/digital-lawsuits |
Even in the US, accessibility is a must, as someone who works on educational sites. |
Any update on this topic? |
Just stumbled on the same thing. Nav bar looks amazing but the drop down can't be accessed using a keyboard. |
Same feeling here: it looks like a really good alternative to Shadcn/ui for Laravel project (outside of Inertia), but without fully accessible components, I won't consider using it. |
I noticed that the components are Not following accessability principles. Since we (in Europe) will have to follows the european accessibility act this would be a necessary thing to work with it. Except of the reason that a good accessability would be good anyway.
The text was updated successfully, but these errors were encountered: