<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Words &#187; Accessibility</title>
	<atom:link href="http://wizardev.ca/web-words/category/accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://wizardev.ca</link>
	<description>Web development resources</description>
	<lastBuildDate>Fri, 04 Feb 2011 02:30:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>10 Reasons Clients Don&#8217;t Care About Accessibility (Digital Web)</title>
		<link>http://wizardev.ca/10-reasons-clients-dont-care-about-accessibility-digital-web/</link>
		<comments>http://wizardev.ca/10-reasons-clients-dont-care-about-accessibility-digital-web/#comments</comments>
		<pubDate>Fri, 04 Nov 2005 14:12:59 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/?p=41</guid>
		<description><![CDATA[Working as an accessibility consultant in an IT company is a very frustrating job right now. Highly publicized lawsuits and deep-rooted accessibility myths leave us with a lot to explain when the final product does not really help visitors. Clients simply don’t care about accessibility as much as we’d like them to, and there are [...]]]></description>
			<content:encoded><![CDATA[<p>Working as an accessibility consultant in an IT company is a very frustrating job right now. Highly publicized lawsuits and deep-rooted accessibility myths leave us with a lot to explain when the final product does not really help visitors. Clients simply don’t care about accessibility as much as we’d like them to, and there are several reasons for that. <small>(Article dated: September 12, 2005)</small></p>
<p><a href="http://www.digital-web.com/articles/ten_reasons_clients_dont_care_about_accessibility/" rel="external">Read the Article&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/10-reasons-clients-dont-care-about-accessibility-digital-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>7 Usability Guidelines for Web Sites on Mobile Devices (Web Credibles)</title>
		<link>http://wizardev.ca/7-usability-guidelines-for-web-sites-on-mobile-devices-web-credibles/</link>
		<comments>http://wizardev.ca/7-usability-guidelines-for-web-sites-on-mobile-devices-web-credibles/#comments</comments>
		<pubDate>Fri, 12 Oct 2007 12:51:39 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/7-usability-guidelines-for-web-sites-on-mobile-devices-web-credibles</guid>
		<description><![CDATA[More and more mobile phones users are browsing and searching the Internet on their handsets. These 7 guidelines are based on actual user research conducted with mobile phone users. Users were asked to carry out typical tasks on popular websites using a mobile phone browser. The issues they encountered were used to produce these guidelines. [...]]]></description>
			<content:encoded><![CDATA[<p>More and more mobile phones users are browsing and searching the Internet on their handsets. These 7 guidelines are based on actual user research conducted with mobile phone users. Users were asked to carry out typical tasks on popular websites using a mobile phone browser. The issues they encountered were used to produce these guidelines.</p>
<p>Read <a href="http://www.webcredible.co.uk/user-friendly-resources/web-usability/mobile-guidelines.shtml" rel="external">7 Usability Guidelines for Web Sites on Mobile Devices</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/7-usability-guidelines-for-web-sites-on-mobile-devices-web-credibles/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Journey Through Accessibility (Juicy Studios)</title>
		<link>http://wizardev.ca/a-journey-through-accessibility-juicy-studios/</link>
		<comments>http://wizardev.ca/a-journey-through-accessibility-juicy-studios/#comments</comments>
		<pubDate>Tue, 16 May 2006 14:07:40 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/?p=103</guid>
		<description><![CDATA[From &#8220;tag generation&#8221; to the &#8220;WYSIWOYS generation&#8221;. Roberto Scano identifies web accessibility problems throughout the web generations, and summarises where we are now, and what we can expect for the future. (Article dated: March 27, 2006) Read the Article&#8230;]]></description>
			<content:encoded><![CDATA[<p>From &#8220;tag generation&#8221; to the &#8220;WYSIWOYS generation&#8221;. Roberto Scano identifies web accessibility problems throughout the web generations, and summarises where we are now, and what we can expect for the future.  <small>(Article dated: March 27, 2006)</small></p>
<p><a href="http://juicystudio.com/article/journey-through-accessibility.php" rel="external">Read the Article&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/a-journey-through-accessibility-juicy-studios/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessibility First! A New Approach to Web Design</title>
		<link>http://wizardev.ca/accessibility-first-a-new-approach-to-web-design/</link>
		<comments>http://wizardev.ca/accessibility-first-a-new-approach-to-web-design/#comments</comments>
		<pubDate>Mon, 20 Mar 2006 16:31:43 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/accessibility-first-a-new-approach-to-web-design</guid>
		<description><![CDATA[Prepared by: Brian J. Rosmaita, Department of Computer Science, Hamilton College This paper proposes an accessibility first pedogogy for web design, in which the course is organized around the requirement of implementing web pages accessible to visually impaired computer users. This approach and its advantages are discussed in detail. (Paper dated: March 3, 2006) Read [...]]]></description>
			<content:encoded><![CDATA[<p>Prepared by:  Brian J. Rosmaita, Department of Computer Science, Hamilton College</p>
<p>This paper proposes an <strong>accessibility first</strong> pedogogy for web design, in which the course is organized around the requirement of implementing web pages accessible to visually impaired computer users. This approach and its advantages are discussed in detail.  <small>(Paper dated: March 3, 2006)</small></p>
<p><a href="http://academics.hamilton.edu/computer_science/brosmait/talks/2006-03-03/fp166-rosmaita.html" rel="external">Read the Paper&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/accessibility-first-a-new-approach-to-web-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessibility of CAPTCHA (Juicy Studios)</title>
		<link>http://wizardev.ca/accessibility-of-captcha-juicy-studios/</link>
		<comments>http://wizardev.ca/accessibility-of-captcha-juicy-studios/#comments</comments>
		<pubDate>Mon, 25 Sep 2006 20:54:44 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/accessibility-of-captcha-juicy-studios</guid>
		<description><![CDATA[Completely Automated Public Turing test to Tell Computers and Humans Apart (CAPTCHA) is a technique that attempts to differentiate between humans and machines on ability alone. (Article dated: September 10, 2006) Read the Article&#8230;]]></description>
			<content:encoded><![CDATA[<p>Completely Automated Public Turing test to Tell Computers and Humans Apart (CAPTCHA) is a technique that attempts to differentiate between humans and machines on ability alone. <small>(Article dated: September 10, 2006)</small></p>
<p><a href="http://juicystudio.com/article/accessibility-of-captcha.php" rel="external">Read the Article&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/accessibility-of-captcha-juicy-studios/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adobe&#8217;s Accessibility Resource Center</title>
		<link>http://wizardev.ca/adobes-accessibility-resource-center/</link>
		<comments>http://wizardev.ca/adobes-accessibility-resource-center/#comments</comments>
		<pubDate>Wed, 03 Jan 2007 13:43:58 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/adobes-accessibility-resource-center</guid>
		<description><![CDATA[Create Accessible PDF Documents with Adobe Acrobat [PDF] Best practices for accessible Flash design [PDF] Accessibility Resource Center]]></description>
			<content:encoded><![CDATA[<ul>
<li><a href="http://www.adobe.com/enterprise/accessibility/pdfs/acro7_pg_ue.pdf" rel="external">Create Accessible PDF Documents with Adobe Acrobat</a> [PDF]</li>
<li><a href="http://www.adobe.com/resources/accessibility/best_practices/best_practices_acc_flash.pdf" rel="external">Best practices for accessible Flash design</a> [PDF]</li>
<li><a href="http://www.adobe.com/accessibility/index.html" rel="external">Accessibility Resource Center</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/adobes-accessibility-resource-center/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AJAX, accessibility and the user</title>
		<link>http://wizardev.ca/ajax-accessibility-and-the-user/</link>
		<comments>http://wizardev.ca/ajax-accessibility-and-the-user/#comments</comments>
		<pubDate>Tue, 16 Oct 2007 21:03:08 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Web Tech]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/ajax-accessibility-and-the-user</guid>
		<description><![CDATA[One on the myths of accessibility is that it suppresses creativity and progress. People mistakenly think you can’t use innovative new technologies and your web sites have to remain flat and boring. This is not the case as accessibility is one part of the design process and works alongside, not against, innovative design. The only [...]]]></description>
			<content:encoded><![CDATA[<p>One on the myths of accessibility is that it suppresses creativity and progress. People mistakenly think you can’t use innovative new technologies and your web sites have to remain flat and boring. This is not the case as accessibility is one part of the design process and works alongside, not against, innovative design. The only difference is that you need to keep all users in mind and build to standards. <small>(Article dated: October 1, 2007)</small></p>
<p>Read <a href="http://www.rnib.org.uk/wacblog/javascript/ajax-accessibility-and-the-user/" rel="external">AJAX, accessibility and the user</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/ajax-accessibility-and-the-user/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AJAX, JavaScript Support and Screen Reader Accessibility (456 Berea Street)</title>
		<link>http://wizardev.ca/ajax-javascript-support-and-screen-reader-accessibility-456-berea-street/</link>
		<comments>http://wizardev.ca/ajax-javascript-support-and-screen-reader-accessibility-456-berea-street/#comments</comments>
		<pubDate>Wed, 24 May 2006 12:04:09 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Tech]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/?p=109</guid>
		<description><![CDATA[Making websites and web based applications that use a lot of JavaScript accessible isn&#8217;t as easy as just making sure that there is a non-JavaScript fallback. Yes, you always need to make sure that your site degrades gracefully in user agents that do not support JavaScript. But that isn&#8217;t always enough. (Article dated: May 18, [...]]]></description>
			<content:encoded><![CDATA[<p>Making websites and web based applications that use a lot of JavaScript accessible isn&#8217;t as easy as just making sure that there is a non-JavaScript fallback. Yes, you always need to make sure that your site degrades gracefully in user agents that do not support JavaScript. But that isn&#8217;t always enough. <small>(Article dated: May 18, 2006)</small></p>
<p><a href="http://www.456bereastreet.com/archive/200605/ajax_javascript_support_and_screen_reader_accessibility/" rel="external">Read the Article&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/ajax-javascript-support-and-screen-reader-accessibility-456-berea-street/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beware the Automated Accessibility Tool Trap (SitePoint)</title>
		<link>http://wizardev.ca/beware-the-automated-accessibility-tool-trap-sitepoint/</link>
		<comments>http://wizardev.ca/beware-the-automated-accessibility-tool-trap-sitepoint/#comments</comments>
		<pubDate>Tue, 03 Jan 2006 00:50:59 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/beware-the-automated-accessibility-tool-trap-sitepoint</guid>
		<description><![CDATA[Being a piece of software, an automated accessibility testing tool doesn&#8217;t have much in the way of common sense. It will interpret each and every accessibility guideline literally, without giving any thought to what other things are happening on the page. (Article dated: December 15, 2005) Read the Article&#8230;]]></description>
			<content:encoded><![CDATA[<p>Being a piece of software, an automated accessibility testing tool doesn&#8217;t have much in the way of common sense. It will interpret each and every accessibility guideline literally, without giving any thought to what other things are happening on the page.   <small>(Article dated: December 15, 2005)</small></p>
<p><a href="http://www.sitepoint.com/article/automated-accessibility-trap" rel="external">Read the Article&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/beware-the-automated-accessibility-tool-trap-sitepoint/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Beyond Guidelines &#8211; Advanced Accessibility Techniques (WebCredible)</title>
		<link>http://wizardev.ca/beyond-guidelines-advanced-accessibility-techniques-webcredible/</link>
		<comments>http://wizardev.ca/beyond-guidelines-advanced-accessibility-techniques-webcredible/#comments</comments>
		<pubDate>Tue, 01 Aug 2006 13:14:34 +0000</pubDate>
		<dc:creator>Mishka</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://wizardev.ca/web-words/beyond-guidelines-advanced-accessibility-techniques-webcredible</guid>
		<description><![CDATA[When creating accessible websites, most Web developers and Web managers tend to follow the W3C accessibility guidelines. The W3C accessibility guidelines, or Web Content Accessibility Guidelines as they&#8217;re officially known, could go slightly further however. (Article dated: July 14, 2006) Read the Article&#8230;]]></description>
			<content:encoded><![CDATA[<p>When creating accessible websites, most Web developers and Web managers tend to follow the W3C accessibility guidelines. The W3C accessibility guidelines, or Web Content Accessibility Guidelines as they&#8217;re officially known, could go slightly further however.  <small>(Article dated: July 14, 2006)</small></p>
<p><a href="http://www.webcredible.co.uk/user-friendly-resources/web-accessibility/beyond-guidelines.shtml" rel="external">Read the Article&#8230;</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wizardev.ca/beyond-guidelines-advanced-accessibility-techniques-webcredible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

