I believe what you want is the value attribute of the radio buttons. Something like this.
Code:
<ul>
<li>
<input type="radio" name="SelectPages" id="SelectPagesPageA" value="PageA" />
<label for="SelectPagesPageA">Page A</label>
</li>
<li>
<input type="radio" name="SelectPages" id="SelectPagesPageB" value="PageB" />
<label for="SelectPagesPageB">Page B</label>
</li>
</ul>
The label tag uses the for attribute to tie the descriptive text "Page A" to the correct form control. The name attribute of the radio button is the text you look for in the request object on the server side to determine what the user selected. In order to get the classic radio button behavior (where users can only select one button), you must apply the same
name to each radio button in the set. If you give a different name to a radio button, it will be in a different set. When you ask the Request object for the name, it will return the value to you (in this case "PageA" or "PageB". Based on that value you can write whatever code you need to cover each case.
You'll note that I like to combine the name and value together to create a quick and easy id. Usually I like the name and id to be the same in form elements but for radio buttons that's just not possible; the name values must be identical where ids are always unique. This is just one of the annoying inconsistencies of form elements. So I stay as close as I can by using the name in my ids, but adding the radio value as well to ensure that the id is unique. You can also see that as closely as possible, my values are identical to the descriptive text. My feeling is, if it's a good way to describe it to your users, it's a good way to identify it to yourself in code (and vice versa).