I believe a more semantically correct method would be to use strong:

<label for="details-email">
Email: <strong>(Required)</strong>
</label> 

Darren Lovelock
Munky Online Web Design
http://www.munkyonline.co.uk
T: +44 (0)20-8816-8893


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Thierry Koblentz
Sent: 26 February 2008 00:02
To: [email protected]
Subject: RE: [WSG] strong element being more semantical and accessible for
required field

> On Behalf Of russ - maxdesign
> Sent: Monday, February 25, 2008 1:37 PM
> To: Web Standards Group
> Subject: Re: [WSG] strong element being more semantical and accessible 
> for required field
> 
> > I can't speak for screen readers since I've never used one my self...
> > But would there be any reason you couldn't do both and please the 
> > client and the screen reader(assuming it does help them)? a simple
> > <strong>* First Name</strong>
> >
> > Just something I thought of :)
> 
> Interesting discussion. You could also use more meaningful flags like 
> the word "Required" instead of "*" and style this content in red/bold. 
> This means that everyone, including screen reader users understand the 
> implications much more clearly (as long as this information is 
> included inside the label element.
> 
> For example:
> 
> <label for="details-email">
>     Email <span class="required">(Required)</span>:
> </label>

What about using a fieldset with *legend* if the required fields can be
grouped together.
Because the legend (required fields) would be read aloud before each label.


--
Regards,
Thierry | http://www.TJKDesign.com







*******************************************************************
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]
*******************************************************************

Reply via email to