<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: FIELDSET and LEGEND Tags in Web Design</title>
	<atom:link href="http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 11 Mar 2010 16:51:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Glen Finch</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-155</link>
		<dc:creator>Glen Finch</dc:creator>
		<pubDate>Tue, 24 Nov 2009 19:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-155</guid>
		<description>Oh forgot to add:
T-S - &quot;read&quot; W3C specifications before you preach.
http://www.w3.org/TR/html401/interact/forms.html (it&#039;s in the FORMs section, there&#039;s a clue!)

&quot;An HTML form is a section of a document containing normal content, markup, SPECIAL ELEMENTS CALLED CONTROLS (checkboxes, radio buttons, menus, etc.)
...

Adding structure to forms: the FIELDSET and LEGEND elements

The FIELDSET element allows authors to group thematically related CONTROLS and LABELS. Grouping controls makes it easier for users to understand their purpose while simultaneously facilitating tabbing navigation for visual user agents and speech navigation for speech-oriented user agents. The proper use of this element makes documents more accessible.

The LEGEND element allows authors to assign a caption to a FIELDSET. The legend improves accessibility when the FIELDSET is rendered non-visually.&quot;

Pretty damn clear to me - they&#039;re for FORM elements ONLY.

&quot;build for purpose... use the material for the purpose it was intended&quot;</description>
		<content:encoded><![CDATA[<p>Oh forgot to add:<br />
T-S &#8211; &#8220;read&#8221; W3C specifications before you preach.<br />
<a href="http://www.w3.org/TR/html401/interact/forms.html" rel="nofollow">http://www.w3.org/TR/html401/interact/forms.html</a> (it&#8217;s in the FORMs section, there&#8217;s a clue!)</p>
<p>&#8220;An HTML form is a section of a document containing normal content, markup, SPECIAL ELEMENTS CALLED CONTROLS (checkboxes, radio buttons, menus, etc.)<br />
&#8230;</p>
<p>Adding structure to forms: the FIELDSET and LEGEND elements</p>
<p>The FIELDSET element allows authors to group thematically related CONTROLS and LABELS. Grouping controls makes it easier for users to understand their purpose while simultaneously facilitating tabbing navigation for visual user agents and speech navigation for speech-oriented user agents. The proper use of this element makes documents more accessible.</p>
<p>The LEGEND element allows authors to assign a caption to a FIELDSET. The legend improves accessibility when the FIELDSET is rendered non-visually.&#8221;</p>
<p>Pretty damn clear to me &#8211; they&#8217;re for FORM elements ONLY.</p>
<p>&#8220;build for purpose&#8230; use the material for the purpose it was intended&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen Finch</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-154</link>
		<dc:creator>Glen Finch</dc:creator>
		<pubDate>Tue, 24 Nov 2009 19:18:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-154</guid>
		<description>Ouch - lively conversation. Lots of people have already said &quot;its against W3C standards&quot; and the response is &quot;so.. its still good&quot;. What seems to be missing is &#039;why standards are good&#039;.
The usual suspects are:

1) there are lots of people that rely on screen readers, using fieldset/legend this way is going to be REALLY frustrating for them... and before anyone comes back with &#039;but this is from a design perspective&#039; what you mean is a &#039;VISUAL&#039; design perspective - someone using a screen reader will tell you that &#039;your design&#039; sucks as they &#039;aurally experience&#039; your design. (Spring&#039;ed: be careful throwing the term &#039;design nazi&#039; around I think the visually impaired have much greater claim on that term for your approach which essentially says [in best German accent] &quot;you are inferior as you are unable to see our master design, we shall make you suffer bad UX&quot;)

2) If your doing this commercially they be aware that making accessible websites is law and at some point somebody&#039;s going to come along and start dishing out fines for not complying - just like not having a ramp instead as well as stairs. At that point you&#039;re going to look pretty silly as a professional.

If either of these doesn&#039;t convince you then hopefully the following will.

Back in the good &#039;ol days we had to use tables for layout - tables weren&#039;t intended for this, but we didn&#039;t have a proper set of tools for the job and browsers couldn&#039;t agree how to implement them.

Now if you want to go down the route of &quot;this isn&#039;t what the standards say and it wasn&#039;t meant to do this, but hell I can, so I will&quot; then you&#039;re thinking along the lines that Microsoft and Netscape did during the Browser wars - where each decided what tags they wanted to support and how to support them.

Standards are our friends - they&#039;ve helped us come a long way from bloated browser sniffers, alternate versions of sites for different browsers, horrible hacks, etc.

Sneer in the face of them and you will have nobody to blame when Microsoft turns back around and says &#039;to hell with this, we&#039;ll just do what we want then&#039; (and if you think there&#039;s no chance of that then you only have to look at Outlook 2003 which can only use Word&#039;s hideous HTML rendering engine, essentially making CSS impossible and setting html email design back about 5 years)

If you&#039;re still not convinced then look up and get a copy of Jeffery Zeldman&#039;s &quot;Designing With Web Standards&quot; - he&#039;s more convincing than me to be fair.</description>
		<content:encoded><![CDATA[<p>Ouch &#8211; lively conversation. Lots of people have already said &#8220;its against W3C standards&#8221; and the response is &#8220;so.. its still good&#8221;. What seems to be missing is &#8216;why standards are good&#8217;.<br />
The usual suspects are:</p>
<p>1) there are lots of people that rely on screen readers, using fieldset/legend this way is going to be REALLY frustrating for them&#8230; and before anyone comes back with &#8216;but this is from a design perspective&#8217; what you mean is a &#8216;VISUAL&#8217; design perspective &#8211; someone using a screen reader will tell you that &#8216;your design&#8217; sucks as they &#8216;aurally experience&#8217; your design. (Spring&#8217;ed: be careful throwing the term &#8216;design nazi&#8217; around I think the visually impaired have much greater claim on that term for your approach which essentially says [in best German accent] &#8220;you are inferior as you are unable to see our master design, we shall make you suffer bad UX&#8221;)</p>
<p>2) If your doing this commercially they be aware that making accessible websites is law and at some point somebody&#8217;s going to come along and start dishing out fines for not complying &#8211; just like not having a ramp instead as well as stairs. At that point you&#8217;re going to look pretty silly as a professional.</p>
<p>If either of these doesn&#8217;t convince you then hopefully the following will.</p>
<p>Back in the good &#8216;ol days we had to use tables for layout &#8211; tables weren&#8217;t intended for this, but we didn&#8217;t have a proper set of tools for the job and browsers couldn&#8217;t agree how to implement them.</p>
<p>Now if you want to go down the route of &#8220;this isn&#8217;t what the standards say and it wasn&#8217;t meant to do this, but hell I can, so I will&#8221; then you&#8217;re thinking along the lines that Microsoft and Netscape did during the Browser wars &#8211; where each decided what tags they wanted to support and how to support them.</p>
<p>Standards are our friends &#8211; they&#8217;ve helped us come a long way from bloated browser sniffers, alternate versions of sites for different browsers, horrible hacks, etc.</p>
<p>Sneer in the face of them and you will have nobody to blame when Microsoft turns back around and says &#8216;to hell with this, we&#8217;ll just do what we want then&#8217; (and if you think there&#8217;s no chance of that then you only have to look at Outlook 2003 which can only use Word&#8217;s hideous HTML rendering engine, essentially making CSS impossible and setting html email design back about 5 years)</p>
<p>If you&#8217;re still not convinced then look up and get a copy of Jeffery Zeldman&#8217;s &#8220;Designing With Web Standards&#8221; &#8211; he&#8217;s more convincing than me to be fair.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spring'ed</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-153</link>
		<dc:creator>Spring'ed</dc:creator>
		<pubDate>Fri, 29 May 2009 20:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-153</guid>
		<description>@T-S My man! I was surprised to see so many &quot;design nazis&quot; here bashing a genuine author of this article. And regarding the fieldset, yes I use it in my website design to show a report. Multiple reports in multiple fieldsets and the report heading in the legend. Of course the report is read only.</description>
		<content:encoded><![CDATA[<p>@T-S My man! I was surprised to see so many &#8220;design nazis&#8221; here bashing a genuine author of this article. And regarding the fieldset, yes I use it in my website design to show a report. Multiple reports in multiple fieldsets and the report heading in the legend. Of course the report is read only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T-S</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-152</link>
		<dc:creator>T-S</dc:creator>
		<pubDate>Thu, 07 May 2009 22:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-152</guid>
		<description>Yes, this thought that everything HAVE to bee CSS web20 based is a flop. Just like that everything must be .NET, php, MySQL etc. based.

Old saying says &quot;Keep it simple&quot;.. or we just say &quot;Keep IT simple&quot;... and keep in mind &quot;Build for purpose!&quot;</description>
		<content:encoded><![CDATA[<p>Yes, this thought that everything HAVE to bee CSS web20 based is a flop. Just like that everything must be .NET, php, MySQL etc. based.</p>
<p>Old saying says &#8220;Keep it simple&#8221;.. or we just say &#8220;Keep IT simple&#8221;&#8230; and keep in mind &#8220;Build for purpose!&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T-S</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-151</link>
		<dc:creator>T-S</dc:creator>
		<pubDate>Thu, 07 May 2009 22:54:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-151</guid>
		<description>Its a missunderstanding that the fieldset/legend can or should NOT be used for other functions than in forms.

The only purpose for the fieldset/legend tags is to define &quot;somthing&quot; inside it. So if its a formfield, text, an image etc. it does not &quot;harm&quot; the validity of the code.

As long as you can; Somethinglorem ipsum

There are NO arguments that say you can NOT;
As long as you can; Somethinglorem ipsum

I use fieldset/legend to just as many none form stuff as for forms. And I will continue to...

;-)

/T-S
Communications &amp; Control Systems Specialist</description>
		<content:encoded><![CDATA[<p>Its a missunderstanding that the fieldset/legend can or should NOT be used for other functions than in forms.</p>
<p>The only purpose for the fieldset/legend tags is to define &#8220;somthing&#8221; inside it. So if its a formfield, text, an image etc. it does not &#8220;harm&#8221; the validity of the code.</p>
<p>As long as you can; Somethinglorem ipsum</p>
<p>There are NO arguments that say you can NOT;<br />
As long as you can; Somethinglorem ipsum</p>
<p>I use fieldset/legend to just as many none form stuff as for forms. And I will continue to&#8230;<br />
 <img src='http://www.graphicrating.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>/T-S<br />
Communications &amp; Control Systems Specialist</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karel</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-150</link>
		<dc:creator>Karel</dc:creator>
		<pubDate>Thu, 16 Apr 2009 01:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-150</guid>
		<description>I am trying to redesign one of my forms using CSS rather than tables. I am trying to utilize FIELDSET, LEGEND, and LABEL tags as well as CSS. My CSS skills are average at best and FIELDSET, LEGEND, and LABEL tags are somewhat new to me as well. The form I am redesigning looks great in tables but I&#039;m starting it off now with very little style and just trying to get things to line up and put it together from the beginning using some best practices. Basically just getting it to work before we make it look pretty.

If I can see how the *correct* way of putting this type of form together I will learn from it and be able to move on in the future making forms in this way. However things that seemed easy in tables are having me pull my hair out now.</description>
		<content:encoded><![CDATA[<p>I am trying to redesign one of my forms using CSS rather than tables. I am trying to utilize FIELDSET, LEGEND, and LABEL tags as well as CSS. My CSS skills are average at best and FIELDSET, LEGEND, and LABEL tags are somewhat new to me as well. The form I am redesigning looks great in tables but I&#8217;m starting it off now with very little style and just trying to get things to line up and put it together from the beginning using some best practices. Basically just getting it to work before we make it look pretty.</p>
<p>If I can see how the *correct* way of putting this type of form together I will learn from it and be able to move on in the future making forms in this way. However things that seemed easy in tables are having me pull my hair out now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lebisol</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-149</link>
		<dc:creator>lebisol</dc:creator>
		<pubDate>Thu, 11 Dec 2008 18:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-149</guid>
		<description>WP ate my snip...2nd try
Title
blah blah..image and all</description>
		<content:encoded><![CDATA[<p>WP ate my snip&#8230;2nd try<br />
Title<br />
blah blah..image and all</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lebisol</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-148</link>
		<dc:creator>lebisol</dc:creator>
		<pubDate>Thu, 11 Dec 2008 18:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-148</guid>
		<description>less markup?
[code]
Title
 blah blah..image and all
[/code]
and use negative top or bottom (respectively) margin on one of the classes.

What is next? Using read-only form fields because they make a &#039;cool looking box&#039;?


On the other hand Andy deserves some credit for the article for pointing out the visuals effect of it. Only it should have been geared towards &#039;form design&#039; more so than &#039;layout design&#039;.
All the best!</description>
		<content:encoded><![CDATA[<p>less markup?<br />
[code]<br />
Title<br />
 blah blah..image and all<br />
[/code]<br />
and use negative top or bottom (respectively) margin on one of the classes.</p>
<p>What is next? Using read-only form fields because they make a &#8216;cool looking box&#8217;?</p>
<p>On the other hand Andy deserves some credit for the article for pointing out the visuals effect of it. Only it should have been geared towards &#8216;form design&#8217; more so than &#8216;layout design&#8217;.<br />
All the best!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Budji</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-147</link>
		<dc:creator>Budji</dc:creator>
		<pubDate>Fri, 21 Nov 2008 18:46:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-147</guid>
		<description>Bunchasheeps! Could someone then please, for crissakes, post a code that will output the same visual structure with less markup?!</description>
		<content:encoded><![CDATA[<p>Bunchasheeps! Could someone then please, for crissakes, post a code that will output the same visual structure with less markup?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry Roberts</title>
		<link>http://www.graphicrating.com/2008/11/17/fieldset-legend-tags-in-web-design/comment-page-1/#comment-146</link>
		<dc:creator>Harry Roberts</dc:creator>
		<pubDate>Wed, 19 Nov 2008 12:08:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.graphicrating.com/?p=995#comment-146</guid>
		<description>I agree, those tags are only for forms. Any other use is not semantic and goes against web standards guidelines.</description>
		<content:encoded><![CDATA[<p>I agree, those tags are only for forms. Any other use is not semantic and goes against web standards guidelines.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
