<?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"
	>
<channel>
	<title>Comments on: Video Accessibility Problems</title>
	<atom:link href="http://www.joedolson.com/articles/2007/02/video-accessibility-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2007/02/video-accessibility-problems/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<pubDate>Sat, 11 Oct 2008 17:45:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2007/02/video-accessibility-problems/#comment-8958</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 20 Feb 2007 15:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2007/02/video-accessibility-problems/#comment-8958</guid>
		<description>That's certainly one of the issues which slows people from retrofitting a site! It's true; once the initial hurdle of discovering and learning accessible development methods is passed, the generalities of designing an accessible website are fairly minor. 

Creating accessible content, once you've gone beyond plain HTML text, is a much more time consuming process --- and, specifically, it's always going to be time consuming.  You don't learn how to do it then find it easy, because it's not replacing a previous task.  Making multimedia content accessible is an additive task to the other processes of content creation.

Thanks, Adrian!</description>
		<content:encoded><![CDATA[<p>That&#8217;s certainly one of the issues which slows people from retrofitting a site! It&#8217;s true; once the initial hurdle of discovering and learning accessible development methods is passed, the generalities of designing an accessible website are fairly minor. </p>
<p>Creating accessible content, once you&#8217;ve gone beyond plain <acronym title="HyperText Markup Language">HTML</acronym> text, is a much more time consuming process&thinsp;&#8212;&thinsp;- and, specifically, it&#8217;s always going to be time consuming.  You don&#8217;t learn how to do it then find it easy, because it&#8217;s not replacing a previous task.  Making multimedia content accessible is an additive task to the other processes of content creation.</p>
<p>Thanks,&nbsp;Adrian!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://www.joedolson.com/articles/2007/02/video-accessibility-problems/#comment-8912</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Tue, 20 Feb 2007 10:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/2007/02/video-accessibility-problems/#comment-8912</guid>
		<description>I think the biggest actual problem that comes up here is time.
We always talk about making it as easy as possible for someone to use a web site, we praise apps like Wordpress for making it easier for people to set up their own blog etc....

So we know people are kind of lazy, and though they may come out with things like 'oh blind people aren't our audience' or whatever, but that's mainly trying to justify the fact that they don't want to add extra time and complexity to the process of adding video to a web site.

I think there's a lot more chance of getting people to use accessible HTML code than there is to get them to create accessible content all the time.</description>
		<content:encoded><![CDATA[<p>I think the biggest actual problem that comes up here is time.<br />
We always talk about making it as easy as possible for someone to use a web site, we praise apps like Wordpress for making it easier for people to set up their own blog etc&#8230;.</p>
<p>So we know people are kind of lazy, and though they may come out with things like &#8216;oh blind people aren&#8217;t our audience&#8217; or whatever, but that&#8217;s mainly trying to justify the fact that they don&#8217;t want to add extra time and complexity to the process of adding video to a web site.</p>
<p>I think there&#8217;s a lot more chance of getting people to use accessible <acronym title="HyperText Markup Language">HTML</acronym> code than there is to get them to create accessible content all the&nbsp;time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
