Re:Future CSS: State Container Queries
by ughitsaaron on Wednesday June 28, 2023 @06:46PM
(#36513721)
I had no idea about these elements or their APIs. Maybe one downside to living in JSX all the time is that it can encourage ignorance of the foundation it’s built on.
[ Parent
| on HN ]
Re:Future CSS: State Container Queries
by jakelazaroff on Wednesday June 28, 2023 @08:27PM
(#36514732)
You can use these within JSX! I use <details> and <summary> all the time. Not so much <dialog> — since there are still accessibility issues by default, I’d rather use a library that wraps it. If and when <selectmenu> drops you can bet I’ll be ditching Radix for the native solution.
I've been exploring using dialog for modals - what a11y issues does it have?
There is currently a debate about these supposed a11y issues. Some are about what happens to focus after dismissal, some are about related elements and announcements, some are about buggy implementations and non support from screen readers.
However it is my belief that these were mostly true 2-3 years ago but the myth has remained. And people still belief there are issues.
I've heard from actual screen reader users that these supposed issues are mostly non-issue. And pale in comparison from people implementing their own.
Re:Future CSS: State Container Queries
by jakelazaroff on Friday June 30, 2023 @08:41AM
(#36533827)
* * *
> I still would be careful using it! MDN has a section on accessibility considerations
In fact, it seems pretty unequivocal: “The native HTML <dialog> element should be used in creating modal dialogs”