<![CDATA[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)

]]>https://board.circlewithadot.net/topic/48529ade-cd3d-4c5b-9be6-d5714d4bab78/radio-buttons-are-not-a-viable-way-to-manage-state-for-uis.RSS for NodeThu, 14 May 2026 21:39:59 GMTTue, 21 Apr 2026 17:50:44 GMT60<![CDATA[Reply to Radio buttons are not a viable way to manage state for UIs. on Tue, 21 Apr 2026 17:56:08 GMT]]>A lesson here is that the Accessibility Law of Headlines also applies to sub-heads. Because “accessibility notes” rarely are noteworthy.

Link Preview Image
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…

favicon

Adrian Roselli (adrianroselli.com)

]]>https://board.circlewithadot.net/post/https://toot.cafe/users/aardrian/statuses/116443982642923570https://board.circlewithadot.net/post/https://toot.cafe/users/aardrian/statuses/116443982642923570Tue, 21 Apr 2026 17:56:08 GMT<![CDATA[Reply to Radio buttons are not a viable way to manage state for UIs. on Tue, 21 Apr 2026 17:53:37 GMT]]>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.

]]>https://board.circlewithadot.net/post/https://toot.cafe/users/aardrian/statuses/116443972707691701https://board.circlewithadot.net/post/https://toot.cafe/users/aardrian/statuses/116443972707691701Tue, 21 Apr 2026 17:53:37 GMT