<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: The times they are a-changin&#8217;</title>
	<atom:link href="http://aralbalkan.com/1003/feed" rel="self" type="application/rss+xml" />
	<link>http://aralbalkan.com/1003</link>
	<description>Passionate geekisms.</description>
	<lastBuildDate>Fri, 19 Mar 2010 19:46:31 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: منتديات</title>
		<link>http://aralbalkan.com/1003/comment-page-1#comment-256232</link>
		<dc:creator>منتديات</dc:creator>
		<pubDate>Tue, 16 Jun 2009 18:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1003#comment-256232</guid>
		<description>Nice Info

Thanks</description>
		<content:encoded><![CDATA[<p>Nice Info</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: شات</title>
		<link>http://aralbalkan.com/1003/comment-page-1#comment-155269</link>
		<dc:creator>شات</dc:creator>
		<pubDate>Fri, 13 Jun 2008 03:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1003#comment-155269</guid>
		<description>Nice Info

Thanks</description>
		<content:encoded><![CDATA[<p>Nice Info</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vivek Gaikwad</title>
		<link>http://aralbalkan.com/1003/comment-page-1#comment-96914</link>
		<dc:creator>Vivek Gaikwad</dc:creator>
		<pubDate>Thu, 27 Dec 2007 06:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1003#comment-96914</guid>
		<description>Yes , you are right, &#039;Flash is not going away&#039;. We just need to make all the developers, designers and also ID&#039;s aware that flash can be made accessible.

After working on flash and accessibility for almost 2 years now, I feel we can do it easily if we are really willing to do it. It&#039;s pretty easy (revolving in certain properties of accessibility) but damn painful if our approach is wrong while implementing accessibility in flash.

peace, veiky</description>
		<content:encoded><![CDATA[<p>Yes , you are right, &#8216;Flash is not going away&#8217;. We just need to make all the developers, designers and also ID&#8217;s aware that flash can be made accessible.</p>
<p>After working on flash and accessibility for almost 2 years now, I feel we can do it easily if we are really willing to do it. It&#8217;s pretty easy (revolving in certain properties of accessibility) but damn painful if our approach is wrong while implementing accessibility in flash.</p>
<p>peace, veiky</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Just Flashing - Today&#8217;s Top Blog Posts on Flash - Powered by SocialRank</title>
		<link>http://aralbalkan.com/1003/comment-page-1#comment-74310</link>
		<dc:creator>Just Flashing - Today&#8217;s Top Blog Posts on Flash - Powered by SocialRank</dc:creator>
		<pubDate>Mon, 01 Oct 2007 09:03:18 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1003#comment-74310</guid>
		<description>[...] The times they are a-changin&#8217; at Aral Balkan [...]</description>
		<content:encoded><![CDATA[<p>[...] The times they are a-changin&#8217; at Aral Balkan [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thom Shannon</title>
		<link>http://aralbalkan.com/1003/comment-page-1#comment-66530</link>
		<dc:creator>Thom Shannon</dc:creator>
		<pubDate>Wed, 15 Aug 2007 10:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1003#comment-66530</guid>
		<description>how about &quot;Flash used badly sucks&quot;, we can all agree on that!

I like flash, and I spend most of time writing my best semantic, accessible degradable XHTML/JavaScript. I&#039;m in the middle of an email conversations with a clients &quot;technical advisor&quot; trying to explain to them how to use flash properly and it is a struggle.

Perhaps Adobe could do more to promote nicer ways of using it, but it wouldn&#039;t be good business practice since the right way to use it is sparingly.</description>
		<content:encoded><![CDATA[<p>how about &#8220;Flash used badly sucks&#8221;, we can all agree on that!</p>
<p>I like flash, and I spend most of time writing my best semantic, accessible degradable XHTML/JavaScript. I&#8217;m in the middle of an email conversations with a clients &#8220;technical advisor&#8221; trying to explain to them how to use flash properly and it is a struggle.</p>
<p>Perhaps Adobe could do more to promote nicer ways of using it, but it wouldn&#8217;t be good business practice since the right way to use it is sparingly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Arno</title>
		<link>http://aralbalkan.com/1003/comment-page-1#comment-66351</link>
		<dc:creator>David Arno</dc:creator>
		<pubDate>Tue, 14 Aug 2007 08:05:03 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1003#comment-66351</guid>
		<description>The Google Webmaster Central blog had a good piece on this issue recently:

http://googlewebmastercentral.blogspot.com/2007/07/best-uses-of-flash.html

Flash has its place, and steps can be taken to make it accessible, but it is just another browser plugin. When used to add &quot;rich content&quot; to web pages, it&#039;s great. When used to try and completely replace web pages, it&#039;s crap.</description>
		<content:encoded><![CDATA[<p>The Google Webmaster Central blog had a good piece on this issue recently:</p>
<p><a href="http://googlewebmastercentral.blogspot.com/2007/07/best-uses-of-flash.html" rel="nofollow">http://googlewebmastercentral.blogspot.com/2007/07/best-uses-of-flash.html</a></p>
<p>Flash has its place, and steps can be taken to make it accessible, but it is just another browser plugin. When used to add &#8220;rich content&#8221; to web pages, it&#8217;s great. When used to try and completely replace web pages, it&#8217;s crap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isofarro</title>
		<link>http://aralbalkan.com/1003/comment-page-1#comment-66246</link>
		<dc:creator>Isofarro</dc:creator>
		<pubDate>Mon, 13 Aug 2007 12:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/1003#comment-66246</guid>
		<description>ooops.... I didn&#039;t want the Flash Sucks piece to be the central part of my post - it was  just an indication that misinformation is still there but not as prevalent, and mainly down to mere personal opinion rather than fact - hence highlighting Steve Webster&#039;s comment in particular because its a fair reflection of the failures of both Flash and Ajax development.

But the core points of both our posts are clear - there&#039;s great work and progress happening because of HTML/CSS based developers working with and alongside Flash developers.

I&#039;ll note that the argument of Flash Sucks is based on a piece Jakob Nielsen wrote in 2000, one he himself largely refuted a year later.

To be honest, my gut feeling is that building an accessible Rich Internet Application is going to be easier with Flash than it is with the current range of Ajax techniques. Accessible Ajax in a practical sense is very much in its infancy.  Much of this is because with Flash you have to do a little extra to make sure that its accessible. With HTML and CSS its largely there, and we Ajax developers are expecting the same effort of &quot;don&#039;t do stupid things&quot; will be enough to have an accessible Ajax application. Its a developer mindset, the accessible Ajax developer has to start thinking like an accessible Flash developer - the accessible Flash developer is already there.

I will not be surprised if some of the leap-forwards in accessibility techniques come from, or have been previously used, in Flash applications. 

I&#039;d point to Niqui&#039;s Flash colour filter technique for alleviating colour-contrast issues (for both colour-blind and dyslexic visitors) as a recent example of where Flash developers can teach us web developers how to solve particular accessibility problems. Even larger than that - Niqui&#039;s demonstration should be taken up by browser manufacturers as a way of implementing browser-based colour filtering. I need to blog that example in particular.


Oh, happy plus-1000 posts!

Mike</description>
		<content:encoded><![CDATA[<p>ooops&#8230;. I didn&#8217;t want the Flash Sucks piece to be the central part of my post &#8211; it was  just an indication that misinformation is still there but not as prevalent, and mainly down to mere personal opinion rather than fact &#8211; hence highlighting Steve Webster&#8217;s comment in particular because its a fair reflection of the failures of both Flash and Ajax development.</p>
<p>But the core points of both our posts are clear &#8211; there&#8217;s great work and progress happening because of HTML/CSS based developers working with and alongside Flash developers.</p>
<p>I&#8217;ll note that the argument of Flash Sucks is based on a piece Jakob Nielsen wrote in 2000, one he himself largely refuted a year later.</p>
<p>To be honest, my gut feeling is that building an accessible Rich Internet Application is going to be easier with Flash than it is with the current range of Ajax techniques. Accessible Ajax in a practical sense is very much in its infancy.  Much of this is because with Flash you have to do a little extra to make sure that its accessible. With HTML and CSS its largely there, and we Ajax developers are expecting the same effort of &#8220;don&#8217;t do stupid things&#8221; will be enough to have an accessible Ajax application. Its a developer mindset, the accessible Ajax developer has to start thinking like an accessible Flash developer &#8211; the accessible Flash developer is already there.</p>
<p>I will not be surprised if some of the leap-forwards in accessibility techniques come from, or have been previously used, in Flash applications. </p>
<p>I&#8217;d point to Niqui&#8217;s Flash colour filter technique for alleviating colour-contrast issues (for both colour-blind and dyslexic visitors) as a recent example of where Flash developers can teach us web developers how to solve particular accessibility problems. Even larger than that &#8211; Niqui&#8217;s demonstration should be taken up by browser manufacturers as a way of implementing browser-based colour filtering. I need to blog that example in particular.</p>
<p>Oh, happy plus-1000 posts!</p>
<p>Mike</p>
]]></content:encoded>
	</item>
</channel>
</rss>
