<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Forms markup and CSS - Revisited</title>
	<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/</link>
	<description>Musings on design, web standards and free software from a Sri Lankan geek</description>
	<pubDate>Sun, 20 Jul 2008 00:12:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: Ryan Thrash</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5566</link>
		<author>Ryan Thrash</author>
		<pubDate>Wed, 06 Dec 2006 16:14:43 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5566</guid>
					<description>Great take on forms and thank you. Quick question:
Why a span.label in the .controlset as opposed to just using a label?</description>
		<content:encoded><![CDATA[<p>Great take on forms and thank you. Quick question:<br />
Why a span.label in the .controlset as opposed to just using a label?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Prabhath</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5567</link>
		<author>Prabhath</author>
		<pubDate>Wed, 06 Dec 2006 16:27:25 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5567</guid>
					<description>Thanks Ryan. 

The reason for using &lt;code&gt;span.label&lt;/code&gt; is because a label can't be explicitly associated with the inputs in the controlset, which have their own labels. I wasn't sure if an orphaned label was OK to use.</description>
		<content:encoded><![CDATA[<p>Thanks Ryan. </p>
<p>The reason for using <code>span.label</code> is because a label can&#8217;t be explicitly associated with the inputs in the controlset, which have their own labels. I wasn&#8217;t sure if an orphaned label was OK to use.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ryan Thrash</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5568</link>
		<author>Ryan Thrash</author>
		<pubDate>Wed, 06 Dec 2006 16:40:43 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5568</guid>
					<description>I think it is, but I'm probably wrong there. You could add name="" to the radios/checks, but those are also basically deprecated. Brings up an interesting question though!</description>
		<content:encoded><![CDATA[<p>I think it is, but I&#8217;m probably wrong there. You could add name=&#8221;" to the radios/checks, but those are also basically deprecated. Brings up an interesting question though!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Prabhath</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5569</link>
		<author>Prabhath</author>
		<pubDate>Wed, 06 Dec 2006 16:56:15 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5569</guid>
					<description>I've done &lt;a href="http://nidahas.com/sandbox/form_template_2.html" rel="nofollow"&gt;another variation of the template&lt;/a&gt; that uses &lt;code&gt;label.controlset&lt;/code&gt; instead of &lt;code&gt;span.label&lt;/code&gt;.

This is why comments are a great idea ;-)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve done <a href="http://nidahas.com/sandbox/form_template_2.html" rel="nofollow">another variation of the template</a> that uses <code>label.controlset</code> instead of <code>span.label</code>.</p>
<p>This is why comments are a great idea ;-)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jonathan Schemoul</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5570</link>
		<author>Jonathan Schemoul</author>
		<pubDate>Thu, 07 Dec 2006 09:55:49 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5570</guid>
					<description>Great ideas about form accessibility and css styling...

(btw, I prefer the label.controlset solution too. :-))</description>
		<content:encoded><![CDATA[<p>Great ideas about form accessibility and css styling&#8230;</p>
<p>(btw, I prefer the label.controlset solution too. :-))</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Apple</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5571</link>
		<author>Apple</author>
		<pubDate>Thu, 07 Dec 2006 10:37:16 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5571</guid>
					<description>Very nice form markup. Maybe in future you can provide a complete PHP script using this form markup. 

I have been looking long for free (XHTML) PHP contact forms but couldn't find any. Maybe a good chance to get a lot of visitors and links.</description>
		<content:encoded><![CDATA[<p>Very nice form markup. Maybe in future you can provide a complete PHP script using this form markup. </p>
<p>I have been looking long for free (XHTML) PHP contact forms but couldn&#8217;t find any. Maybe a good chance to get a lot of visitors and links.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Daniel</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5572</link>
		<author>Daniel</author>
		<pubDate>Thu, 07 Dec 2006 16:57:47 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5572</guid>
					<description>Very nice visually, also in terms of accessibility for screen readers, the checkboxes and radio buttons themselves should be further enclosed in  fieldset/legends...</description>
		<content:encoded><![CDATA[<p>Very nice visually, also in terms of accessibility for screen readers, the checkboxes and radio buttons themselves should be further enclosed in  fieldset/legends&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Bart</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5573</link>
		<author>Bart</author>
		<pubDate>Thu, 07 Dec 2006 17:07:54 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5573</guid>
					<description>Good stuff! Simple and clean. What do you think of putting the controlset inside of an unordered list?</description>
		<content:encoded><![CDATA[<p>Good stuff! Simple and clean. What do you think of putting the controlset inside of an unordered list?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Prabhath</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5574</link>
		<author>Prabhath</author>
		<pubDate>Thu, 07 Dec 2006 17:20:39 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5574</guid>
					<description>@Apple: The &lt;a href="http://sahana.lk/" rel="nofollow"&gt;Sahana project&lt;/a&gt; which uses the earlier version of this template has a script for generating forms. If you're looking for a contact form that could be integrated to WordPress, check out &lt;a href="http://codex.wordpress.org/Plugins/Mail" rel="nofollow"&gt;this list&lt;/a&gt; from the codex.

@Daniel: Thanks for the suggestion :-) I guess that could be easily achieved by limiting the scope of the fieldsets in the template to wrap each control set.

@Bart: If you look at the &lt;a href="http://nidahas.com/2006/01/12/forms-markup-and-css/" rel="nofollow"&gt;earlier version&lt;/a&gt; of this template you'd notice that it started off using an unordered list for check boxes and radios. However, as explained in &lt;a href="http://nidahas.com/2006/01/12/forms-markup-and-css/#comment-7" rel="nofollow"&gt;this comment&lt;/a&gt;, it was probably a case of going overboard with semantics. </description>
		<content:encoded><![CDATA[<p>@Apple: The <a href="http://sahana.lk/" rel="nofollow">Sahana project</a> which uses the earlier version of this template has a script for generating forms. If you&#8217;re looking for a contact form that could be integrated to WordPress, check out <a href="http://codex.wordpress.org/Plugins/Mail" rel="nofollow">this list</a> from the codex.</p>
<p>@Daniel: Thanks for the suggestion :-) I guess that could be easily achieved by limiting the scope of the fieldsets in the template to wrap each control set.</p>
<p>@Bart: If you look at the <a href="http://nidahas.com/2006/01/12/forms-markup-and-css/" rel="nofollow">earlier version</a> of this template you&#8217;d notice that it started off using an unordered list for check boxes and radios. However, as explained in <a href="http://nidahas.com/2006/01/12/forms-markup-and-css/#comment-7" rel="nofollow">this comment</a>, it was probably a case of going overboard with semantics.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: links for 2006-12-07 &#124; SridhaReena</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5576</link>
		<author>links for 2006-12-07 &#124; SridhaReena</author>
		<pubDate>Thu, 07 Dec 2006 23:22:12 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5576</guid>
					<description>[...] Nidahas » Forms markup and CSS - Revisited A CSS-based Form Template (tags: css forms webdesign) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Nidahas » Forms markup and CSS - Revisited A CSS-based Form Template (tags: css forms webdesign) [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ash Haque</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5578</link>
		<author>Ash Haque</author>
		<pubDate>Mon, 11 Dec 2006 02:34:13 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5578</guid>
					<description>Great looking template, clean markup too!</description>
		<content:encoded><![CDATA[<p>Great looking template, clean markup too!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Daniel</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5579</link>
		<author>Daniel</author>
		<pubDate>Mon, 11 Dec 2006 05:42:51 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5579</guid>
					<description>I am not sure what you are saying, but I think that is correct ... as it stands ... someone smarter should probably confirm .. the screen reader will read the legend for the fieldset with each form element .. which is perfect .. except when you get to something like the preferences section... let's use preferred location...

instead of saying 
preferences &#62; preferred location &#62; option1
preferences &#62; preferred location &#62; option2
preferences &#62; preferred location &#62; option3

it will say
preferences &#62; option1
preferences &#62; option2
preferences &#62; option3

Again I am no accessibility effort, but I think this is correct

... and let me re-iterate ... GREAT WORK ....</description>
		<content:encoded><![CDATA[<p>I am not sure what you are saying, but I think that is correct &#8230; as it stands &#8230; someone smarter should probably confirm .. the screen reader will read the legend for the fieldset with each form element .. which is perfect .. except when you get to something like the preferences section&#8230; let&#8217;s use preferred location&#8230;</p>
<p>instead of saying<br />
preferences &gt; preferred location &gt; option1<br />
preferences &gt; preferred location &gt; option2<br />
preferences &gt; preferred location &gt; option3</p>
<p>it will say<br />
preferences &gt; option1<br />
preferences &gt; option2<br />
preferences &gt; option3</p>
<p>Again I am no accessibility effort, but I think this is correct</p>
<p>&#8230; and let me re-iterate &#8230; GREAT WORK &#8230;.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: watchingnow &#187; Blog Archive &#187; links for 2006-12-08</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5580</link>
		<author>watchingnow &#187; Blog Archive &#187; links for 2006-12-08</author>
		<pubDate>Tue, 12 Dec 2006 02:45:44 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5580</guid>
					<description>[...] Nidahas » Forms markup and CSS - Revisited Creating CSS and standards-based forms (tags: css design forms development) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Nidahas » Forms markup and CSS - Revisited Creating CSS and standards-based forms (tags: css design forms development) [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steve</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5581</link>
		<author>Steve</author>
		<pubDate>Wed, 13 Dec 2006 15:53:50 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5581</guid>
					<description>While not strictly a CSS issue you may want to make the list of form errors a link that moves the input cursor to the appropriate filed or to the label for that field so the label ios read). This makes it easier for screen reader users and those with manual dexterity issues.</description>
		<content:encoded><![CDATA[<p>While not strictly a CSS issue you may want to make the list of form errors a link that moves the input cursor to the appropriate filed or to the label for that field so the label ios read). This makes it easier for screen reader users and those with manual dexterity issues.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Wilco</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5583</link>
		<author>Wilco</author>
		<pubDate>Thu, 14 Dec 2006 08:26:55 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5583</guid>
					<description>Great work! I've been looking at a simular problem myself for a while but I never got this far. 

I found a little problem with it. When a label extends to a second line things go wrong. You can't always prevent this from happening since users decide on their own font size.

Is there a way to break with the common label rule so you can put a number of checkboxes under eachother. with the label to the right of it. I would suggest holding it outside the div with the input element inside the label.</description>
		<content:encoded><![CDATA[<p>Great work! I&#8217;ve been looking at a simular problem myself for a while but I never got this far. </p>
<p>I found a little problem with it. When a label extends to a second line things go wrong. You can&#8217;t always prevent this from happening since users decide on their own font size.</p>
<p>Is there a way to break with the common label rule so you can put a number of checkboxes under eachother. with the label to the right of it. I would suggest holding it outside the div with the input element inside the label.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Prabhath</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5584</link>
		<author>Prabhath</author>
		<pubDate>Thu, 14 Dec 2006 14:07:03 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5584</guid>
					<description>Thanks Wilco.

I think what you want can already be done with this template. You have to use the &lt;code&gt;.controlset&lt;/code&gt; set of classes. There's an example of such a set of checkboxes under the "Preferences" fieldset.</description>
		<content:encoded><![CDATA[<p>Thanks Wilco.</p>
<p>I think what you want can already be done with this template. You have to use the <code>.controlset</code> set of classes. There&#8217;s an example of such a set of checkboxes under the &#8220;Preferences&#8221; fieldset.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Smith Data Processing Services &#187; Blog Archive &#187; links for 2006-12-18</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5585</link>
		<author>Smith Data Processing Services &#187; Blog Archive &#187; links for 2006-12-18</author>
		<pubDate>Mon, 18 Dec 2006 05:19:51 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5585</guid>
					<description>[...] Nidahas » Forms markup and CSS - Revisited (tags: css forms) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Nidahas » Forms markup and CSS - Revisited (tags: css forms) [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Chris Curtis dot Org: Random Musings of Chris Curtis and Co.</title>
		<link>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5589</link>
		<author>Chris Curtis dot Org: Random Musings of Chris Curtis and Co.</author>
		<pubDate>Sat, 23 Dec 2006 21:27:55 +0000</pubDate>
		<guid>http://nidahas.com/2006/12/06/forms-markup-and-css-revisited/#comment-5589</guid>
					<description>[...] Unfortunately, I can&#8217;t actually recall where I came across this since I&#8217;ve had it open and waiting to blog about for several days now.&#160; However, a post over on the Nidahas blog covers some very nice ways to make simple, accessible forms.&#160; All the CSS and such is in the source code for that page, so just dig in there and see how the markup and CSS work together to create a semantic and accessible form that&#8217;s easy to use.  0 Comments, 0 Trackbacks, 0 Pingbacks &#183; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Unfortunately, I can&#8217;t actually recall where I came across this since I&#8217;ve had it open and waiting to blog about for several days now.&nbsp; However, a post over on the Nidahas blog covers some very nice ways to make simple, accessible forms.&nbsp; All the CSS and such is in the source code for that page, so just dig in there and see how the markup and CSS work together to create a semantic and accessible form that&#8217;s easy to use.  0 Comments, 0 Trackbacks, 0 Pingbacks &middot; [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
