Undoubtedly it's the cleanest way to achieve the required functionality, and there are fewer accessibility issues.
However, it is less easy for a user to quickly review their answers because they have to read the text rather than just look at the physical position of the selected radio button. Also it doesn't give an indication of the trend, although this will not always be relevant. For most users it will take longer to fill in a form using <select> rather than radio buttons; at least two actions compared with one. Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Lo Sent: 03 December 2007 23:51 To: [email protected] Subject: Re: [WSG] Accessible likert scale (disagree/agree/strongly agree/etc) forms > The problem with the code below is that the content of the <legend> > will be read before every <label>. That makes it very difficult for a > screen reader user to read it fast. I would just have the question in > a <p> or possibly even a header element. > > Once the user has read through a few questions and realises that the > structure is consistent, they won't need to listen to the whole of > each label and they can very quickly skip through the form. What is your opinion on the idea of using SELECT mentioned by Patrick? Nick ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
