4 ms·
If you're implementing a reasonably complex ui, the insane edge-cases that component-libraries must manage cannot be accomplished with CSS alone. Accessibility,
by SebastianKra 3y ago
If you're implementing a reasonably complex ui, the insane edge-cases that component-libraries must manage cannot be accomplished with CSS alone. Accessibility, Keyboard-Navigation, spec-conformance... The feature summaries from react-aria [1] illustrate this.
For example, did you know that it's not trivial to have a button inside an interactive list item, because none of the default html-interactive components can be nested?
As another example, DaisyUI recommends relying on the <dialog> element for a simple modal, which, as I recall, has flawed accessibility and excludes 7% of browsers.
[1]: https://react-spectrum.adobe.com/react-aria/useGridList.html https://react-spectrum.adobe.com/react-aria/useGridList.html