leolopes

Leonardo Baptista Lopes, [Strongway Webstudio](https://strongway.com.br) Here are two images. See what might fit best :)  

Today I started the document by making a list of references to all the concepts that remind of radio buttons in many design systems. After that I started a spreadsheet...

I think the radio button is more complex than the checkbox because the checkbox is "standalone", while the radio button represents an option amongst other options. I see the radio...

I updated the preliminary inventory with three other design systems: https://docs.google.com/spreadsheets/d/1addPff5gfeAIRvCeVTnT0GUD1IesCQYO8JmFzlum2Ug/edit?usp=sharing You can see there I divided the concepts between radio buttons and radio button groups. You can see by...

As I keep listing the design systems' options for Radio/RadioGroups, I only strenghten my belief that we should treat Radio Button Groups as the actual component, instead of Radio Buttons...

> the control and the indicator Hello @gregwhitworth, do you mean the actual radio input (the circle) and the label? > I would like that scoped anatomy What do you...

Let me rectify: a label for the whole group seems very important, thus: - Radio Button Group (the actual component) - Group Label - Radio Button (at least two required)...

I have finished the analisys of all the design systems' properties, and now I'm going to use both the WAI-ARIA specs and the recurrence of properties among the design systems...

Because of the need of tying the radio buttons together, I think the "Group Label" should be included in the basic anatomy, specially when we have more than one option....

Coming back after a while, I've been reading a bit further and found this: > A document must not contain an input element whose radio button group contains only that...