<?xml version="1.0" encoding="UTF-8"?>
<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 Accessibility Articles</title>
	<atom:link href="http://webaccessibilityguide.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://webaccessibilityguide.com/blog</link>
	<description>Articles and other information about web accessibility</description>
	<lastBuildDate>Mon, 07 Sep 2009 13:38:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Online Video Captioning &#8211; Repost</title>
		<link>http://webaccessibilityguide.com/blog/2009/09/07/online-video-captioning-repost/</link>
		<comments>http://webaccessibilityguide.com/blog/2009/09/07/online-video-captioning-repost/#comments</comments>
		<pubDate>Mon, 07 Sep 2009 13:38:44 +0000</pubDate>
		<dc:creator>Jen Rohrig</dc:creator>
				<category><![CDATA[Online Video Captioning]]></category>
		<category><![CDATA[Web Accessibility]]></category>

		<guid isPermaLink="false">http://webaccessibilityguide.com/blog/?p=143</guid>
		<description><![CDATA[My articles about being hard of hearing on the internet and the review of online videos by TV show Networks have been combined, and edited for reposting at Accessites. I&#8217;d like to thank Mel Pedley for her feedback on both the article in question and the redesign of the Web Accessibility Guide. 
Read &#8220;Online Video [...]]]></description>
			<content:encoded><![CDATA[<p>My articles about being hard of hearing on the internet and the review of online videos by TV show Networks have been combined, and edited for reposting at <a href="http://accessites.org/site/">Accessites</a>. I&#8217;d like to thank Mel Pedley for her feedback on both the article in question and the redesign of the Web Accessibility Guide. </p>
<p>Read &#8220;<a href="http://accessites.org/site/2009/09/online-video-captioning/">Online Video Captioning</a>&#8221; at Accessites. </p>
]]></content:encoded>
			<wfw:commentRss>http://webaccessibilityguide.com/blog/2009/09/07/online-video-captioning-repost/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessible JavaScript = Unobtrusive JavaScript</title>
		<link>http://webaccessibilityguide.com/blog/2008/11/16/accessible-javascript-unobtrusive-javascript/</link>
		<comments>http://webaccessibilityguide.com/blog/2008/11/16/accessible-javascript-unobtrusive-javascript/#comments</comments>
		<pubDate>Sun, 16 Nov 2008 15:47:12 +0000</pubDate>
		<dc:creator>Jen Rohrig</dc:creator>
				<category><![CDATA[Web Accessibility]]></category>

		<guid isPermaLink="false">http://jenrweb.com/?p=138</guid>
		<description><![CDATA[JavaScript is not my favorite topic –- I think it's over used and used badly by people who should know better. There are so many ways badly implemented JavaScript can cause problems for both users and search engines alike that I often feel that it's better to not use it at all.]]></description>
			<content:encoded><![CDATA[<p>JavaScript is not my favorite topic –- I think it&#8217;s over used and used badly by people who should know better. There are so many ways badly implemented JavaScript can cause problems for both users and search engines alike that I often feel that it&#8217;s better to not use it at all.</p>
<p><span id="more-138"></span></p>
<p>However, the reality of it is people like using JavaScript and there are actually some good uses for it. As I describe in the Web Accessibility Guide the key to Accessible JavaScript is Unobtrusive JavaScript. Unobtrusive JavaScript essentially means making sure the site will work without JavaScript enabled. All critical functions of the site must be usable without JavaScript – this includes navigation and form submission among other items.</p>
<p>Additionally, it&#8217;s important to learn how to create your own scripts and not depend on pre-made scripts available on any old web site. Most of the scripts available on those sites use out of date methods that can cause more harm than good. If you do need a pre-made script, find a recently created one from a reputable source and make sure you understand how it works. Also make sure the script has to two essential features:</p>
<ol>
<li>All functions and event handlers must be in a separate .js file – separating behavior from structure is the key to unobtrusive JavaScript.</li>
<li>All functions that use onMouseOver onMouseOut handlers must also use onFocus and onBlur handlers so that the script will work for keyboard users.</li>
</ol>
<p>Before creating a site it&#8217;s important to think deeply about what will be needed to do whatever it is that needs to be done. If JavaScript is absolutely necessary make sure it&#8217;s unobtrusive and as usable as it can be. Take the time and effort to use JavaScript correctly and test it thoroughly before letting the site go live. If there are problems fix them – don&#8217;t leave them and hope people won&#8217;t notice, because they will. There&#8217;s no point in having a site if people can&#8217;t use it and search engines can&#8217;t index it properly.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaccessibilityguide.com/blog/2008/11/16/accessible-javascript-unobtrusive-javascript/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SEO Made Accessible</title>
		<link>http://webaccessibilityguide.com/blog/2008/10/18/search-engine-optimization-made-accessible/</link>
		<comments>http://webaccessibilityguide.com/blog/2008/10/18/search-engine-optimization-made-accessible/#comments</comments>
		<pubDate>Sat, 18 Oct 2008 12:21:10 +0000</pubDate>
		<dc:creator>Jen Rohrig</dc:creator>
				<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://jenrweb.com/?p=132</guid>
		<description><![CDATA[As with Web Accessibility, Search Engine Optimization (SEO) works best when it's thought of at the beginning of the design process, not after the site has gone up. If a site is going to rank well, it's because it was designed to. Keywords should be chosen at the same time the content is being written. Page titles, descriptions, and keywords should be written at the same time the pages are created. For the coding of the site it is important to use valid code without unnecessary Flash or JavaScript that make indexing the site difficult, if not impossible.]]></description>
			<content:encoded><![CDATA[<p>As with Web Accessibility, Search Engine Optimization (SEO) works best when it&#8217;s thought of at the beginning of the design process, not after the site has gone up. If a site is going to rank well, it&#8217;s because it was designed to. Keywords should be chosen at the same time the content is being written. Page titles, descriptions, and keywords should be written at the same time the pages are created. For the coding of the site it is important to use valid code without unnecessary Flash or JavaScript that make indexing the site difficult, if not impossible.</p>
<p><span id="more-132"></span></p>
<p>This doesn&#8217;t mean that older sites can&#8217;t be optimized; just that it becomes exponentially harder to do the older the code is. The solution to this is to update the code as best as possible. Make sure there are no depreciated tags within the code. Pull any embedded and inline <abbr title="Cascading Style Sheet">CSS</abbr> out of the .html file and put it into an external .css file. Pull any JavaScript functions out of the .html and into an external .js file. Replace JavaScript navigation menus with CSS menus. Images should have descriptive alt text – especially if those images are part of the navigation or if the site&#8217;s header is an image. And finally add content to the site – the more text there is on the page the more there is for search engine crawlers to see.</p>
<p>Once the site is updated it&#8217;s time to do keyword research and update the title, description and keyword tags – and to do it correctly. Take the time to do extensive research on what keywords will work best for the site. When creating titles, descriptions and keywords make them relevant to each page. Don&#8217;t use a keyword on every individual page just for the sake of having it on a page. If the keyword is not used within the content don&#8217;t use it in the title, description or keyword tag.</p>
<p>Final step in SEO should be inbound linking – and in fact shouldn&#8217;t be considered until after all other updates to the code are completed. Yes, it&#8217;s true that inbound linking is probably the single most important part of SEO, but visitors still need to be able to use the site once they get to it. Rankings are all well and good but are pretty much worthless if the visitor can&#8217;t use the site. Make sure the site is usable before inviting visitors to see it. The site isn&#8217;t going to do anyone any good if the visitor – human or search engine spider alike &#8211; can&#8217;t get past the front door.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaccessibilityguide.com/blog/2008/10/18/search-engine-optimization-made-accessible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Makes A Good Web Site?</title>
		<link>http://webaccessibilityguide.com/blog/2008/09/14/what-makes-a-good-web-site/</link>
		<comments>http://webaccessibilityguide.com/blog/2008/09/14/what-makes-a-good-web-site/#comments</comments>
		<pubDate>Sun, 14 Sep 2008 13:14:12 +0000</pubDate>
		<dc:creator>Jen Rohrig</dc:creator>
				<category><![CDATA[Web Accessibility]]></category>

		<guid isPermaLink="false">http://jenrweb.com/?p=12</guid>
		<description><![CDATA[Having a good web site means making sure the site is easy to use and the information easy to find and understand. This can be accomplished with the basics (<abbr title="HyperText Markup Language">HTML</abbr>/<abbr title="Extensible Hypertext Markup Language">XHTML</abbr> and <abbr title="Cascading Style Sheet">CSS</abbr>). JavaScript should only be used where needed, not to just to do tricks that can be annoying at best, or -- at worst -- make the site impossible to use without it. Dynamic sites built with <abbr title="PHP Hypertext Preprocessor">PHP </abbr>or <abbr title="Active Server Pages">ASP</abbr>, and databases have their places; but it's still important that the site be easy to use and maintain.]]></description>
			<content:encoded><![CDATA[<p>Having a good web site means making sure the site is easy to use and the information easy to find and understand. This can be accomplished with the basics (<abbr title="HyperText Markup Language">HTML</abbr>/<abbr title="Extensible Hypertext Markup Language">XHTML</abbr> and <abbr title="Cascading Style Sheet">CSS</abbr>). JavaScript should only be used where needed, not to just to do tricks that can be annoying at best, or &#8212; at worst &#8212; make the site impossible to use without it. Dynamic sites built with <abbr title="PHP Hypertext Preprocessor">PHP </abbr>or <abbr title="Active Server Pages">ASP</abbr>, and databases have their places; but it&#8217;s still important that the site be easy to use and maintain.</p>
<p><span id="more-12"></span></p>
<p>When Web Accessibility is mentioned, people tend to focus on how it can help disabled people &#8212; without looking at the bigger picture. Accessible sites are better for everyone. Even those without disabilities may be having trouble using a web site. Maybe a Flash or JavaScript element is preventing the site from being indexed properly. Old, out-of-date code with depreciated tags could be causing more problems than people realize.</p>
<p>Often times JavaScript menus are hard to use and can become useless when JavaScript is turned off or otherwise unavailable. Using images for navigation without proper alt text only adds to the problems. Even worse is the use of Flash in the site navigation, which usually means users will have to install a Flash player just to navigate the site. These issues don&#8217;t just affect visitors, but search engines as well. The web crawlers used by search engines to index a site are essentially blind and cannot interpret images or JavaScript. Without any text to read, they cannot properly index a site.</p>
<p>Some may worry that these changes will take too much time, cost too much or mean that their entire site will need to change. This is not necessarily true. Updating the code is relatively easy and doesn&#8217;t have to mean changing the look of the site. Yes, the navigation might need to be changed and maybe some different colors would work better; but these are still small changes, relatively speaking. Some sites will, of course, need more drastic changes &#8212; but it all depends on what is there to start with.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaccessibilityguide.com/blog/2008/09/14/what-makes-a-good-web-site/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
