Hi Nick,
The sample code on this page you link to does not look ideal. As has been
mentioned on this list a few times, title attributes are often ignored by
screen readers. And the use of a table element to lay out the form is a
little odd.
Unless I am missing something, I'd say it would be much better if it marked
up with standard form elements. For example (warning - code below thrown
together very quickly):
<form action="#" method="get">
<fieldset>
<legend>The product is a good value for the dollar</legend>
<label for="strongly-agree"><input name="likert" id="strongly-agree"
type="radio" />strongly agree</label>
<label for="agree"><input name="likert" id="agree" type="radio"
/>agree</label>
<label for="disagree"><input name="likert" id="disagree"
type="radio" />disagree</label>
<label for="undecided"><input name="likert" id="undecided"
type="radio" />undecided</label>
<label for="strongly-disagree"><input name="likert"
id="strongly-disagree" type="radio" />strongly disagree</label>
<input name="submit" id="submit" type="submit" value="Submit" />
</fieldset>
</form>
You can then use CSS (and a hammer if needed) to position these form
elements exactly as you want.
HTH
Russ
> Hello All,
>
> I'm working on a Likert scale questionnaire (Strongly Agree/Agree/
> Undecided/Disagree/Strongly Disagree) with 20 questions and some
> Googling came up with the following approach...
>
> http://www.enterpriseaccessibility.com/articles/
> AccessibleRadioButtons.html
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
