
<?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: Accessibility of pre-filled input fields</title>
	<atom:link href="http://www.cssglance.com/news/accessibility-of-pre-filled-input-fields/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cssglance.com/news/accessibility-of-pre-filled-input-fields/</link>
	<description>CssGlance is the first italian website focused on providing a gallery of well designed and innovative CSS based websites from all around the world.</description>
	<lastBuildDate>Thu, 10 Nov 2011 19:49:21 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrea - CSSGlance Staff</title>
		<link>http://www.cssglance.com/news/accessibility-of-pre-filled-input-fields/comment-page-1/#comment-557</link>
		<dc:creator>Andrea - CSSGlance Staff</dc:creator>
		<pubDate>Wed, 08 Apr 2009 08:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssglance.com/?p=2882#comment-557</guid>
		<description>Hi Larry, thanks for your interesting reply. 

Adding a default text onload using JavaScript might be a possible solution indeed, especially in those cases where you cannot actually use a label because you don&#039;t have enough space. I&#039;m thinking of inline fields, put in a single line one after the other, like month and day.

On the other hand, as far as I know, some screen readers might have problems handling this kind of pre-filled text, even if JavaScript is turned on. This because they might not clean up the field properly when onfocus. 

I&#039;m really keen to hear the opinion of someone who has made or can run some tests with different screen readers.. they might have the answer!

Andrea</description>
		<content:encoded><![CDATA[<p>Hi Larry, thanks for your interesting reply. </p>
<p>Adding a default text onload using JavaScript might be a possible solution indeed, especially in those cases where you cannot actually use a label because you don&#8217;t have enough space. I&#8217;m thinking of inline fields, put in a single line one after the other, like month and day.</p>
<p>On the other hand, as far as I know, some screen readers might have problems handling this kind of pre-filled text, even if JavaScript is turned on. This because they might not clean up the field properly when onfocus. </p>
<p>I&#8217;m really keen to hear the opinion of someone who has made or can run some tests with different screen readers.. they might have the answer!</p>
<p>Andrea</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Roth</title>
		<link>http://www.cssglance.com/news/accessibility-of-pre-filled-input-fields/comment-page-1/#comment-556</link>
		<dc:creator>Larry Roth</dc:creator>
		<pubDate>Wed, 08 Apr 2009 05:50:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssglance.com/?p=2882#comment-556</guid>
		<description>Great analysis. I agree with your point. At first, I was thinking of arguing back that pre-filled fields can aid usability, but your comment about making more descriptive labels helps solve that.

One thought...If you use Javascript to empty the text field, you can use javascript to populate it in the first place. This would be more onerous on the developer, but  you wouldn&#039;t have to worry about screen readers or people with JavaScript turned off. Right?</description>
		<content:encoded><![CDATA[<p>Great analysis. I agree with your point. At first, I was thinking of arguing back that pre-filled fields can aid usability, but your comment about making more descriptive labels helps solve that.</p>
<p>One thought&#8230;If you use Javascript to empty the text field, you can use javascript to populate it in the first place. This would be more onerous on the developer, but  you wouldn&#8217;t have to worry about screen readers or people with JavaScript turned off. Right?</p>
]]></content:encoded>
	</item>
</channel>
</rss>



