It is possible but unusual and not normally considered either sensible or accessible not using the LABEL for radio buttons. Because without a LABEL you cannot easily access the radio buttons themselves. Losing the benefits of the LABEL element which is a form control that explicitly associates and the group of radio button(s) with the specific control in question. Using some CSS instead to position might be a solution if it’s purely presentational layout. In either case why drop the LABEL you could use it in a TABLE anyway it makes little sense dropping LABEL because the columns themselves have a different purpose to the buttons. It would only complicate matters and make extra work without the associated labels.
Furthermore if you require an ‘unselected state’ a checkbox might be more appropriate. Since to “unsubscribe” you’d already have to be subscribed. To subscribe you may just want to check a single box or leave blank in the case of not wanting to subscribe. Plus in that demo you’d be making the assumption the user possibly wants to alter the state of all 4 items. Obviously depending on “default” radio ‘checked’ state, which of course if you were already subscribed would have to begin with that checked state. If not it would be the opposite ‘default’ state of; “not subscribed already”.
It’s perfectly possible (and valid HTML) to have radio buttons without labels … but as Robert says, it’s got problems associated with it. The first is that people then have to click the radio button itself, which is a smaller target and may be difficult for people with poor motor control or those using mobile devices. The second is that screen readers and other accessibility software will usually ignore HTML elements within a <form> that are not form controls (ie inputs, legends and labels), so while an HTML table would be semantically appropriate, it wouldn’t be properly accessible. A more accessible option would just be to have a single check box by each article name, make the name into the <label> and do away with the <table> altogether.
[font=verdana]Changing it to a single check box for each row, I would code it as a <ul>, but if you want to code it as a <table> that isn’t a problem. The difference is that you’re not relying on the column headings to convey essential information, which you are with label-less radio buttons – without the column headings of Subscribe/Unsubscribe, those radio buttons are meaningless, but a check box still makes sense.
There’s no problem with including an <img> tag within the <label> if you want to retain the thumbnail.[/font]
It’s a form, so <legend> would give a suitable heading (eg “Subscribe to…”) and then wrap the legend and the checkbox list in a <fieldset>. You can style these to get rid of the default border on the <fieldset>.