Want to provide a nice experience for screen reader users but don't enjoy messing with the DOM to add live refions? Use this simple utility for screen reader announcements https://t.co/SVVgkSLE4V
@syntaxfm@radix_ui@tan_stack@shoelace_style@shadcn@daisyui_ Hey guys, awesome episode as always. Just got a shameless plug for a UI lib I'm working on: https://t.co/spoppOmrKs. it uses light-dom web component with CSS variables, I think @stolinski is gonna like it. Grateful if you'd check it out and let me know your thoughts.
@buildWithKris Depend on the users interaction. If it behaves like the native radio btns then I feel like C would introduce a more jarring exp. for keyboard users as they use the arrows to select, but at the same time it allows more possibly for focus state, so B (with focus) is a safer choice
@_davideast Why not both? For simple use case like this, we could provide the props as an easy way for devs to follow our "heading group" standard, but if they need to break the rules, they still can
If you would wave a magic wand 🪄and invent anything new in CSS (and magically get implemented in every browser at once)… What would you come up with?
No limits. Any superpower you want added to CSS.
What do you wish were possible in graphic design on the web???