Hi Steven, thanks for the two links.
I am replying in a new thread because, after reading the "Too much
accessibility - FIELDSET LEGENDS", I feel that it deserves to open a
new thread for a new, hopefully more thorough discussion on Fieldset
and Legend, and maybe to have a closer exmination that these two
attributes are like the tabindex, accesskeys and titles, more harmful
than useful.
The article was over 2 years old, while I am in full agreement with
these:
The right way is to choose LEGEND text that is:
• Concise: between 1 and 6 words.
• Relevant: to every single form field in the FIELDSET.
• Seamless: in that the words chosen for the LEGEND should make sense
when joined to each label phrase. This might take a bit more
explanation, so read on and you’ll see why.
W3C said: "The LEGEND element allows authors to assign a caption to a
FIELDSET"
No way in my right mind that I would ever think the legend will be
read out by each set of label atrribute repetitive.
Quote BIM: I don’t see that the W3c intention and the JAWS screen
reader implementation are necessarily at odds; JAWS has a “duty” to
keep users informed that they are in the same group, and this is one
way of achieving it.
Has a "duty" as being overly helpful that turns to absurdity and
annoyance?
Does BIM a memebr here too? I am sorry, but I think his logic and
reason are at fault.
An annoyance is an annoyance whether the legend is one word or 10
words long. One word of legend text, if repeated 10 times to me over
and over on every page I visit. It's an annoyance.
This leads me to take a closer look on how I use the fieldset and
legend; at a closer examination, I think I am going to remove fieldset
and legend in that 'get shipping estimation' form and I will stop
using fieldset and legend in forms that contain only a few inputs/
checkboxes/radio button.
tee
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
