Radio buttons are not a viable way to manage state for UIs.
-
Radio buttons are not a viable way to manage state for UIs. If you’re using radio buttons for anything other than forms, you’re opening yourself to risk and your users to hassle.
https://css-tricks.com/the-radio-state-machine/#comment-1884181 (link to my comment citing challenges)
-
Radio buttons are not a viable way to manage state for UIs. If you’re using radio buttons for anything other than forms, you’re opening yourself to risk and your users to hassle.
https://css-tricks.com/the-radio-state-machine/#comment-1884181 (link to my comment citing challenges)
I’ve added to my post “CSS-only Widgets Are Inaccessible”:
https://adrianroselli.com/2023/03/css-only-widgets-are-inaccessible.html#State (anchor link)You’ll see it looks very much like the ‘looper’ example I cited in 2024 from Chrome / Google.
-
I’ve added to my post “CSS-only Widgets Are Inaccessible”:
https://adrianroselli.com/2023/03/css-only-widgets-are-inaccessible.html#State (anchor link)You’ll see it looks very much like the ‘looper’ example I cited in 2024 from Chrome / Google.
A lesson here is that the Accessibility Law of Headlines also applies to sub-heads. Because “accessibility notes” rarely are noteworthy.
Accessibility Law of Headlines
Betteridge’s law of headlines states that any headline that ends in a question mark can be answered by the word no. For at least the digital accessibility landscape, I would like to amend it, fork it, whatever it: Any headline that asserts a thing is accessible is wrong. Yes, that…
Adrian Roselli (adrianroselli.com)
-
P pixelate@tweesecake.social shared this topic
