The very first exercise in this series, (Cat App) used a couple of forms that used label/input pairs. Every input element in that exercise has name and value attributes.
My question is, why does the Building a Registration Form exercise not use the same format? I understand there can be different methods of achieving a similar result, but in this case - specifically the account-type section - the input uses a name attribute but fails to use a value attribute. If the back-end server relies on name as an identifier, why is there no value attribute for the Personal or Business radio buttons?
Along the same lines, why does the T&C checkbox also lack a value attribute? Does the user checking the box constitute a value in itself?
Please clarify or tell me if I’ve not formed the question correctly.
Thanks!
-D