So then you might look up the documentation for the submit event on forms: https://html.spec.whatwg.org/multipage/form-control-infrastr...
And then realize that adding the onclick handler on the submit button handles one use case (clicking the button), but a more general solution would be to add the onclick handlers on the form itself.
Then maybe you start thinking, huh, what happens when someone tabs to a button and presses enter, does the onclick handler work there? And so on and so on...
So the answer for where it's written down, it's in the documentation. But most people these days can't be bothered with things like reading documentation and textbooks and reference manuals, so, uh, I guess you just need to have a little bit of experience combined with an attention to detail?
My email in profile if you’d like to check it out.
<input type="radio" id="factor-weight-4" name="score" value="4">
<label for="factor-weight-3">super important</label>
<br>
<input type="radio" id="factor-weight-3" name="score" value="3">
<label for="factor-weight-3">pretty important</label>[0] most people use JSON not XML so i prefer to call it AJAJ not AJAX
Most web applications I have seen opt to use the form element. The default form browser behaviour can be suppressed easily.