Justin French wrote:
Honestly, the most logical way I can see to do this is to have them in
three cells of a table row, since at least they'll be associated in a
row. fieldset's would also be nice, but they're intended for
groupings of form elements, and using them for each text input seems
Lee Roberts wrote:
First Labels should not wrap the input. The elements within the Label tag become the label. By wrapping the input with the Label you are stating the input is part of its own Label. That's wrong.
Sorry, but that's wrong. Enclosing the input within the label is a
prescribed
Hi all,
I'm trying to decide on a nice semantic way to mark-up a short (usually
only a few words) block of help text in the context of a web form. I
currently use a label to label the input, and a paragraph or div to
mark-up the help text:
form...
div class='formitem'
label
-Original Message-
From: Justin French [mailto:[EMAIL PROTECTED]
Sent: 22 July 2004 15:25
To: [EMAIL PROTECTED]
Subject: [WSG] semantic way to mark up form help?
Hi all,
I'm trying to decide on a nice semantic way to mark-up a short (usually
only a few words) block of help text in the context
-Original Message-
From: Justin French [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 22, 2004 7:25 AM
To: [EMAIL PROTECTED]
Subject: [WSG] semantic way to mark up form help?
Hi all,
I'm trying to decide on a nice semantic way to mark-up a short (usually
only a few words) block of help text
-Original Message-
From: Justin French
Sent: 22 July 2004 15:25
To: [EMAIL PROTECTED]
Subject: [WSG] semantic way to mark up form help?
Hi all,
I'm trying to decide on a nice semantic way to mark-up a
short (usually
only a few words) block of help text in the context of a web form
: Thursday, July 22, 2004 10:15 AM
To: [EMAIL PROTECTED]
Subject: RE: [WSG] semantic way to mark up form help?
Maybe a slight stretch, but how about wrapping these
related elements (label, input, etc) up in their own
fieldset, and using the legend for that text (thus
associating it with the (input
There are a number of things that need to be considered:
1. title attribute content is not accessible to users who cannot use a
mouse (as the tool tip only appears on mouseover not onfocus)
2. the title attribute content is only available to a subset of screen
reading software (latest versions of
a class on the label to visually identify the presence of a title tag, for instance a dotted bottom border or a simple underline.
Ted
-Original Message-
From: Justin French [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 22, 2004 7:25 AM
To: [EMAIL PROTECTED]
Subject: [WSG] semantic way to mark
4:13 PM
To: [EMAIL PROTECTED]
Subject: Re: [WSG] semantic way to mark up form help?
There are a number of things that need to be considered:
1. title attribute content is not accessible to users who cannot use a
mouse (as the tool tip only appears on mouseover not onfocus)
2. the title attribute
Thanks to everyone for their input, especially Steven insight into the
world of screen readers. My summation of all this is that the elements
need to appear in this order:
Label Text
Extended help
Input or widgets
I really like the idea of wrapping the label tag around the whole lot,
so that
First Labels should not wrap the input. The elements
within the Label tag become the label. By wrapping the
input with the Label you are stating the input is part of
its own Label. That's wrong.
Using heading tags for font declarations is poor form and
fails to meet the standards. DIV is a
12 matches
Mail list logo
