<?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 for LearnAccessibility.org</title>
	<atom:link href="http://learnaccessibility.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://learnaccessibility.org</link>
	<description>This is a platform to learn about Accessibility</description>
	<lastBuildDate>Mon, 24 Jan 2011 18:49:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on A quick Web Accessibility Checklist by Tweets that mention A quick Web Accessibility Checklist « LearnAccessibility.org -- Topsy.com</title>
		<link>http://learnaccessibility.org/2010/07/a-quick-web-accessibility-checklist/comment-page-1/#comment-448</link>
		<dc:creator>Tweets that mention A quick Web Accessibility Checklist « LearnAccessibility.org -- Topsy.com</dc:creator>
		<pubDate>Mon, 24 Jan 2011 18:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=81#comment-448</guid>
		<description>[...] This post was mentioned on Twitter by Copious Ltd, LearnAccessibility. LearnAccessibility said: Thanks everyone for valuable feedback! we have updated the post &quot;A quick Accessibility Checklist&quot;. Please read and com…http://lnkd.in/h72Q36 [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Copious Ltd, LearnAccessibility. LearnAccessibility said: Thanks everyone for valuable feedback! we have updated the post &quot;A quick Accessibility Checklist&quot;. Please read and com…http://lnkd.in/h72Q36 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A quick Web Accessibility Checklist by Web Axe</title>
		<link>http://learnaccessibility.org/2010/07/a-quick-web-accessibility-checklist/comment-page-1/#comment-446</link>
		<dc:creator>Web Axe</dc:creator>
		<pubDate>Mon, 24 Jan 2011 04:17:26 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=81#comment-446</guid>
		<description>Great updates, looks solid now!</description>
		<content:encoded><![CDATA[<p>Great updates, looks solid now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A quick Web Accessibility Checklist by WebAdmin</title>
		<link>http://learnaccessibility.org/2010/07/a-quick-web-accessibility-checklist/comment-page-1/#comment-444</link>
		<dc:creator>WebAdmin</dc:creator>
		<pubDate>Sun, 23 Jan 2011 15:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=81#comment-444</guid>
		<description>Thanks everyone for feedback! Now, we have updated the check list. Please view and write to us again with your valuable comments! Thanks for being on our portal!</description>
		<content:encoded><![CDATA[<p>Thanks everyone for feedback! Now, we have updated the check list. Please view and write to us again with your valuable comments! Thanks for being on our portal!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Common mistakes of that a web developers make by offshore banking</title>
		<link>http://learnaccessibility.org/2010/10/common-mistakes-of-that-a-web-developers-make/comment-page-1/#comment-443</link>
		<dc:creator>offshore banking</dc:creator>
		<pubDate>Sun, 23 Jan 2011 14:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=93#comment-443</guid>
		<description>.....An accessible website doesnt exclude anyone because they have a .....visual impairment or another disability or because they are older .....or because they have a slow internet connection of lack the latest .....software...........It means that everyone can understand it navigate around it .....contribute to it and use its interactive services. When a website reaches a .....certain level it can display a symbol from one of the organisations .....that set the standards......The Parkway Green website has many features that help make it as .....accessible as possible - Look out for the ..... external site symbol and the link on many of .....our pages........... The site avoids unnecessary frills or techniques that need .....technical know-how to use.</description>
		<content:encoded><![CDATA[<p>&#8230;..An accessible website doesnt exclude anyone because they have a &#8230;..visual impairment or another disability or because they are older &#8230;..or because they have a slow internet connection of lack the latest &#8230;..software&#8230;&#8230;&#8230;..It means that everyone can understand it navigate around it &#8230;..contribute to it and use its interactive services. When a website reaches a &#8230;..certain level it can display a symbol from one of the organisations &#8230;..that set the standards&#8230;&#8230;The Parkway Green website has many features that help make it as &#8230;..accessible as possible &#8211; Look out for the &#8230;.. external site symbol and the link on many of &#8230;..our pages&#8230;&#8230;&#8230;.. The site avoids unnecessary frills or techniques that need &#8230;..technical know-how to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A quick Web Accessibility Checklist by Australia Web Development</title>
		<link>http://learnaccessibility.org/2010/07/a-quick-web-accessibility-checklist/comment-page-1/#comment-426</link>
		<dc:creator>Australia Web Development</dc:creator>
		<pubDate>Mon, 17 Jan 2011 02:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=81#comment-426</guid>
		<description>Thanks for sharing your thoughts. What I like about iFrame is that it&#039;s easy to implement. You only need to add a few lines of code to your web page to begin syndicating content from other sites or provide the iFrame code for visitors to syndicate content from your site to theirs.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing your thoughts. What I like about iFrame is that it&#8217;s easy to implement. You only need to add a few lines of code to your web page to begin syndicating content from other sites or provide the iFrame code for visitors to syndicate content from your site to theirs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A quick Web Accessibility Checklist by WebAdmin</title>
		<link>http://learnaccessibility.org/2010/07/a-quick-web-accessibility-checklist/comment-page-1/#comment-409</link>
		<dc:creator>WebAdmin</dc:creator>
		<pubDate>Wed, 12 Jan 2011 03:33:13 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=81#comment-409</guid>
		<description>Thanks WebAxe for inputs. We will update the post soon. Continue to help us.</description>
		<content:encoded><![CDATA[<p>Thanks WebAxe for inputs. We will update the post soon. Continue to help us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A quick Web Accessibility Checklist by Web Axe</title>
		<link>http://learnaccessibility.org/2010/07/a-quick-web-accessibility-checklist/comment-page-1/#comment-396</link>
		<dc:creator>Web Axe</dc:creator>
		<pubDate>Mon, 10 Jan 2011 06:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=81#comment-396</guid>
		<description>I&#039;ve posted comments about this post on my blog: http://weba.im/commquick</description>
		<content:encoded><![CDATA[<p>I&#8217;ve posted comments about this post on my blog: <a href="http://weba.im/commquick" rel="nofollow">http://weba.im/commquick</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A quick Web Accessibility Checklist by WebAdmin</title>
		<link>http://learnaccessibility.org/2010/07/a-quick-web-accessibility-checklist/comment-page-1/#comment-19</link>
		<dc:creator>WebAdmin</dc:creator>
		<pubDate>Sun, 08 Aug 2010 17:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=81#comment-19</guid>
		<description>@Sanvin - Totally agree with you. Also, my intention is not to say these options are mandatory. Only reason, I prefer developer to provide these options are, not many user are aware of existing accessibility options provided by browser and OS. In fact, not many are aware of using CTRL Plus and Control Minus to increase and decrease font size. But your point is very much valid and thanks for being on my site.</description>
		<content:encoded><![CDATA[<p>@Sanvin &#8211; Totally agree with you. Also, my intention is not to say these options are mandatory. Only reason, I prefer developer to provide these options are, not many user are aware of existing accessibility options provided by browser and OS. In fact, not many are aware of using CTRL Plus and Control Minus to increase and decrease font size. But your point is very much valid and thanks for being on my site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A quick Web Accessibility Checklist by sanvin</title>
		<link>http://learnaccessibility.org/2010/07/a-quick-web-accessibility-checklist/comment-page-1/#comment-18</link>
		<dc:creator>sanvin</dc:creator>
		<pubDate>Sun, 08 Aug 2010 16:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=81#comment-18</guid>
		<description>Good checklist !
But, I&#039;m not so sure for “Color options” “Font re-size option” that you can put them at the same level of priority compared with image alternative for example. Now with the modern browsers functions as zoom, no need to give Font-size option, and if you need complex color changes, you need specific software. They are not so important web site accessibility features !</description>
		<content:encoded><![CDATA[<p>Good checklist !<br />
But, I&#8217;m not so sure for “Color options” “Font re-size option” that you can put them at the same level of priority compared with image alternative for example. Now with the modern browsers functions as zoom, no need to give Font-size option, and if you need complex color changes, you need specific software. They are not so important web site accessibility features !</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Writing accessible HTML forms by Tweets that mention Writing accessible HTML forms &#124; LearnAccessibility.org - This is a platform to learn about Accessibility -- Topsy.com</title>
		<link>http://learnaccessibility.org/2010/08/writing-accessible-html-forms/comment-page-1/#comment-16</link>
		<dc:creator>Tweets that mention Writing accessible HTML forms &#124; LearnAccessibility.org - This is a platform to learn about Accessibility -- Topsy.com</dc:creator>
		<pubDate>Sun, 08 Aug 2010 10:57:02 +0000</pubDate>
		<guid isPermaLink="false">http://learnaccessibility.org/?p=83#comment-16</guid>
		<description>[...] This post was mentioned on Twitter by LearnAccessibility, Srinivasu. Srinivasu said: An example of inaccessible form and tips to make HTML forms accessible - http://bit.ly/9jyPpD #accessibility #aria #html #yui [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by LearnAccessibility, Srinivasu. Srinivasu said: An example of inaccessible form and tips to make HTML forms accessible &#8211; <a href="http://bit.ly/9jyPpD" rel="nofollow">http://bit.ly/9jyPpD</a> #accessibility #aria #html #yui [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

