Hi Thierry,
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.
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:
<label>* denotes required field</label>
<fieldset>
<legend>Required</legend>
<label for="name">Name * <input name="name">
<label for="email">Email * <input name="email">
</fieldset>
<fieldset>
<legend>Required</legend>
<label for="name">Name (required) <input name="name">
<label for="email">Email (required) <input name="email">
</fieldset>
<fieldset>
<legend>Required</legend>
<label for="name">Name <img src="star-pic" alt="required"></label> <input
name="name">
<label for="email">Email <img src="star-pic" alt="required"></label> <input
name="email">
</fieldset>
No mention was made about strong tags from this user.
Cheers.
Mike Cherim
----- Original Message -----
From: "Thierry Koblentz" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, February 25, 2008 7:01 PM
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]
*******************************************************************
