We don't have to enforce strings here. Let's make it any or unknown as in Tabs.

A hidden <input> is rendered for the whole RadioGroup root which requires the native DOM type:

{props.name && (
  <input type="hidden" name={props.name} value={checkedItem ?? ''} required={required} />
)}

So we can allow string or number. I don't think anything else needs to be allowed anyway?

Similarly to the Select, we can allow arbitrary values here and expose a prop to control how it's serialized.

What valid use cases are there for something other than a string or number?

@atomiks is Composite/CompositeItem intended to be a successor to the current useCompoundParent/Item?

At least for Slider I think this could be a completely replacement for it if we could pass arbitrary metadata into these parameters (for slider it's the id of the associated input element)

BTW the only other component also using useCompound is Tabs, which uses useCompound in a similar way that Accordion needs, I'll try using CompositeList/Item for Accordion first ~

Yes, it's a replacement for both them & FloatingList. It can be modified wherever necessary for different components