Re:Shadcn: Components that you can copy-paste into your apps
by ecuaflo on Saturday January 13, 2024 @05:22AM
(#38978644)
Can you add ariakit?
Re:Shadcn: Components that you can copy-paste into your apps
by darekkay on Saturday January 13, 2024 @01:39PM
(#38983048)
Ariakit is a Reakit successor, which already got the full score in my post. Ariakit looks as accessible as Reakit. I've updated my post accordingly.
Re:Shadcn: Components that you can copy-paste into your apps
by gmarcus on Tuesday January 16, 2024 @02:47AM
(#39010590)
Great compilation. Thanks for putting that together.
Curious what your take is on these UI libraries that "claim" they are accessible:
https://mantine.dev - "Build fully functional accessible web applications faster than ever" https://nextui.org - "NextUI components are built on top of React Aria ensuring exceptional accessibility support as a top priority."
Re:Shadcn: Components that you can copy-paste into your apps
by darekkay on Wednesday January 17, 2024 @11:50AM
(#39030191)
You can always get a first impression by checking a website with Chrome Lightroom. For Mantine, Lightroom returns a few ARIA and a lot of contrast ratio issues. NextUI is built upon React Aria, which indeed puts accessibility first. Nonetheless, NextUI includes some contrast ratio issues as well. I think that claims like "fully accessible" or "exceptional accessibility" give a false sense of security to people using those UI frameworks. Accessibility is not something a UI framework can guarantee for your app or website.
EDIT: I've added Mantine to my post. I've left out NextUI, being more of a "skin" over React Aria.
> Is it accessible? Yes. It adheres to the WAI-ARIA design patterns.
I've only checked the Tab component (as one of the more complex one from accessibility perspective), but the WAI-ARIA patterns are well implemented.
However, WAI-ARIA patterns are a necessary but not a sufficient condition. E.g., the Tab component has _detectable_ issues, i.e., run Lightroom in Chrome and you will find some problems (like contrast ratio issues). Finally, a manual test is necessary, which will show things like the insufficient focus ring in the "New York" style.
I've updated my post, where I compare different UI libraries on a subset of accessibility criteria, to include shadcn: https://darekkay.com/blog/accessible-ui-frameworks/