Hi Matt, I think
<label for="name">Name <span class="required">(required)</span></label> <input name="name" ... /> is the best way of representing required fields, It is what I implemented for Griffith University. (see it in action: http://www.griffith.edu.au/cgi-bin/feedbackform.cgi ) Thinking further on the subject, if I was to redo the Styling I would probably have used a <strong> declaration instead of the <span>. Kind Regards, Kane Tapping Web Standards Developer Web and Content Management Services Griffith University. 4111. Australia. [EMAIL PROTECTED] Phone: +61 (0)7 3735 7630 "Matt Fellows" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 26/02/2008 01:14 PM Please respond to wsg@webstandardsgroup.org To wsg@webstandardsgroup.org cc Subject Re: [WSG] strong element being more semantical and accessible for required field > In some cases that's an excellent solution (what I've been using for a > while) but unfortunately power users will dial down verbosity so much that > they will quiet legends as well. > > A blind power user I know told me * is best. He also told me nothing else is > needed, but he's a person and that part my be his opinion. For all-around > safety, one of these might be best: Thanks Mike that's really interesting. I would argue, based on the anecdotal evidence you've given, that the following legend is superflous and prevents logical grouping. > <fieldset> > <legend>Required</legend> > <label for="name">Name (required) <input name="name"> > <label for="email">Email (required) <input name="email"> > </fieldset> I am definitely leaning toward the following: <fieldset> <legend>Personal Details</legend> <label for="name">Name <span class="required">(required)</span></label> <input name="name"> <label for="email">Email <span class="required">(required)</span></label> <input name="email"> <label for="phone">Phone</label> <input name="phone"> ... </fieldset> Giving in to other's suggestions perhaps the <span class="required"> could become <strong class="required"> :) The benefits here are: * Easily scannable for the regular user * Will be read out for screen readers * Semantically intact * Inputs can be grouped logically * No need for annoying legends Does this seem to be a combination of the general consensus? ******************************************************************* 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] *******************************************************************
