<?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: Form Design And The Fallacy Of The Required Field</title>
	<atom:link href="http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/</link>
	<description>Usability, User Experience, Social Media, and Content Management</description>
	<lastBuildDate>Tue, 07 Sep 2010 00:56:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Twitted by pixelsavvy</title>
		<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/comment-page-1/#comment-1587</link>
		<dc:creator>Twitted by pixelsavvy</dc:creator>
		<pubDate>Tue, 24 Nov 2009 03:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=1844#comment-1587</guid>
		<description>[...] This post was Twitted by pixelsavvy [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by pixelsavvy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caroline Jarrett</title>
		<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/comment-page-1/#comment-1585</link>
		<dc:creator>Caroline Jarrett</dc:creator>
		<pubDate>Thu, 19 Nov 2009 23:58:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=1844#comment-1585</guid>
		<description>I agree with you that designers fret too much about the required field indicator. In testing, I&#039;ve seen that some web-savvy people (e.g. designers) do notice the required field indicators and do make some decisions about what to fill in based on them. Other web-savvy people don&#039;t care, and ordinary users don&#039;t notice them and make their decisions about what to answer in other ways.

I do very much like, and recommend, using the entire word &#039;optional&#039; to show which fields are optional - but, as Cam pointed out, putting the &#039;optional&#039; on the right-hand side may not be the best position. 

In the end, though, it&#039;s not the *indication* of required or optional that creates difficulties for users, it&#039;s the selection of what is required or optional and the way that the validations are handled. Being forced to answer a question for which you don&#039;t have an answer, just because it is required, really does create a lot of hassle. 

There&#039;s more discussion of this in our book: &quot;Forms that work: Designing web forms for usability&quot; www.formsthatwork.com</description>
		<content:encoded><![CDATA[<p>I agree with you that designers fret too much about the required field indicator. In testing, I&#8217;ve seen that some web-savvy people (e.g. designers) do notice the required field indicators and do make some decisions about what to fill in based on them. Other web-savvy people don&#8217;t care, and ordinary users don&#8217;t notice them and make their decisions about what to answer in other ways.</p>
<p>I do very much like, and recommend, using the entire word &#8216;optional&#8217; to show which fields are optional &#8211; but, as Cam pointed out, putting the &#8216;optional&#8217; on the right-hand side may not be the best position. </p>
<p>In the end, though, it&#8217;s not the *indication* of required or optional that creates difficulties for users, it&#8217;s the selection of what is required or optional and the way that the validations are handled. Being forced to answer a question for which you don&#8217;t have an answer, just because it is required, really does create a lot of hassle. </p>
<p>There&#8217;s more discussion of this in our book: &#8220;Forms that work: Designing web forms for usability&#8221; <a href="http://www.formsthatwork.com" rel="nofollow">http://www.formsthatwork.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-11-19 &#171; News, Software and All you need</title>
		<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/comment-page-1/#comment-1584</link>
		<dc:creator>links for 2009-11-19 &#171; News, Software and All you need</dc:creator>
		<pubDate>Thu, 19 Nov 2009 22:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=1844#comment-1584</guid>
		<description>[...] Form Design And The Fallacy Of The Required Field &#124; Usability Counts &#124; User Experience, Social Media &quot;Standards are wonderful, but if I asked my mom what is the international symbol for a required field, she would look at me like I was on drugs&quot; (tags: design usability forms) [...]</description>
		<content:encoded><![CDATA[<p>[...] Form Design And The Fallacy Of The Required Field | Usability Counts | User Experience, Social Media &quot;Standards are wonderful, but if I asked my mom what is the international symbol for a required field, she would look at me like I was on drugs&quot; (tags: design usability forms) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Real-Time Business Analytics: Talking Operational Intelligence &#8230; &#124; Management Business Wisdom</title>
		<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/comment-page-1/#comment-1583</link>
		<dc:creator>Real-Time Business Analytics: Talking Operational Intelligence &#8230; &#124; Management Business Wisdom</dc:creator>
		<pubDate>Thu, 19 Nov 2009 12:27:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=1844#comment-1583</guid>
		<description>[...] Form Design And The Fallacy Of The Required Field &#124; Usability &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Form Design And The Fallacy Of The Required Field | Usability &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by violetile</title>
		<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/comment-page-1/#comment-1582</link>
		<dc:creator>Twitted by violetile</dc:creator>
		<pubDate>Thu, 19 Nov 2009 02:49:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=1844#comment-1582</guid>
		<description>[...] This post was Twitted by violetile [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by violetile [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Neeman</title>
		<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/comment-page-1/#comment-1581</link>
		<dc:creator>Patrick Neeman</dc:creator>
		<pubDate>Thu, 19 Nov 2009 02:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=1844#comment-1581</guid>
		<description>That could be handled through presentation and CSS, right? Separation of presentation and content?</description>
		<content:encoded><![CDATA[<p>That could be handled through presentation and CSS, right? Separation of presentation and content?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cam</title>
		<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/comment-page-1/#comment-1580</link>
		<dc:creator>Cam</dc:creator>
		<pubDate>Thu, 19 Nov 2009 00:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=1844#comment-1580</guid>
		<description>Quote: &quot;...the word Optional was placed to the right of the field...&quot;

Potential issues for users of screen readers here? Reading out the word &#039;optional&#039; after they have already entered text into the field? Do they then associate the word &#039;optional&#039; with the next entry field?</description>
		<content:encoded><![CDATA[<p>Quote: &#8220;&#8230;the word Optional was placed to the right of the field&#8230;&#8221;</p>
<p>Potential issues for users of screen readers here? Reading out the word &#8216;optional&#8217; after they have already entered text into the field? Do they then associate the word &#8216;optional&#8217; with the next entry field?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by jeffkraemer</title>
		<link>http://www.usabilitycounts.com/2009/11/18/form-design-and-the-fallacy-of-the-required-field/comment-page-1/#comment-1579</link>
		<dc:creator>Twitted by jeffkraemer</dc:creator>
		<pubDate>Wed, 18 Nov 2009 18:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=1844#comment-1579</guid>
		<description>[...] This post was Twitted by jeffkraemer [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by jeffkraemer [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.265 seconds -->
