<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Disability and Internet Use</title>
	<atom:link href="http://pjaywebdisability.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://pjaywebdisability.wordpress.com</link>
	<description>Information and discussion about technology and methods to improve internet accessibility.</description>
	<lastBuildDate>Mon, 31 Aug 2009 14:09:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='pjaywebdisability.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Disability and Internet Use</title>
		<link>http://pjaywebdisability.wordpress.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://pjaywebdisability.wordpress.com/osd.xml" title="Disability and Internet Use" />
	<atom:link rel='hub' href='http://pjaywebdisability.wordpress.com/?pushpress=hub'/>
		<item>
		<title>Web Design for the Ageing Population</title>
		<link>http://pjaywebdisability.wordpress.com/2009/08/31/web-design-for-the-ageing-population/</link>
		<comments>http://pjaywebdisability.wordpress.com/2009/08/31/web-design-for-the-ageing-population/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 14:02:25 +0000</pubDate>
		<dc:creator>Penny</dc:creator>
				<category><![CDATA[Web Usability]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[accessibility guidelines]]></category>
		<category><![CDATA[Ageing]]></category>
		<category><![CDATA[w3]]></category>
		<category><![CDATA[Web Design for the Ageing Population]]></category>

		<guid isPermaLink="false">http://pjaywebdisability.wordpress.com/?p=32</guid>
		<description><![CDATA[According to reports written by members of the WAI-AGE Project, older people with dexterity issues suffer from steadiness of hand which makes it difficult to move in the desired direction causing issues with navigation and sliding off dynamic, drop-down or multilevel menus. Many of the guiding principles outlined in most reports follow those of the [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pjaywebdisability.wordpress.com&amp;blog=8659580&amp;post=32&amp;subd=pjaywebdisability&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>According to reports written by members of the <acronym>WAI-AGE</acronym> Project, older people with dexterity issues suffer from steadiness of hand which makes it difficult to move in the desired direction causing issues with navigation and sliding off dynamic, drop-down or multilevel menus. Many of the guiding principles outlined in most reports follow those of the basic accessibility guidelines; however, when dealing with older people and web design, there are some further points to be considered.</p>
<p><strong>“Parallels to WAI guidelines</strong></p>
<ul>
<li>contrast      &#8211; most of the guidelines reviewed recommended high contrast</li>
<li>clear      presentation</li>
<li>clear      writing</li>
<li>clear      navigation</li>
<li>clarity      of links</li>
<li>augmentation      with images”</li>
</ul>
<p>Andrew Arch and Shadi Abou-Zhara 2004<br />
“How Web Accessibility Guidelines Apply to Design for the Ageing Population”<br />
<a href="http://www.w3.org/WAI/WAI-AGE/">http://www.w3.org/WAI/WAI-AGE/</a><br />
Accessed 31 August 2009</p>
<p>The ability to view web content, although not a dexterity issue is relevant as it is a major issue for many older people. It is also relevant as many web designers use text as links. This is an issue for people with dexterity problems as small text can be extremely difficult to click on.</p>
<p><strong>“Presentation and writing</strong></p>
<ul>
<li>font      use &#8211; generally recommending sans serif fonts</li>
<li>white      space – increases readability</li>
<li>Text      size &#8211; 12pt was recommended as a minimum by several authors. However, WCAG      1.0 and WCAG 2.0 both require text that be resized to suit the user’s      needs.</li>
<li>text      spacing &#8211; often recommending spacing greater than the browser default”</li>
</ul>
<p>Andrew Arch and Shadi Abou-Zhara 2004<br />
“How Web Accessibility Guidelines Apply to Design for the Ageing Population”<br />
<a href="http://www.w3.org/WAI/WAI-AGE/">http://www.w3.org/WAI/WAI-AGE/</a><br />
Accessed 31 August 2009</p>
<p><strong> </strong></p>
<p>There are many other age related issues which have some relevance to dexterity, such as minimising the need to click or double click on a page, removing flashing or moving clickable parts of a site and removing advertisements from sites. (These last two points relate also to the issue of information overload and visual confusion.)<br />
The most interesting point of these reports is that all of the requirements are extremely simple to implement. It is sad and unfortunate that all designers do not see the validity of keeping these simple things in mind when designing sites. If I were looking for a designer, I would question prospective companies to find out if they followed these guidelines or instead, left out a huge portion of the population. Is it worth your while to put into practice these small changes?<br />
To view our site designed for accessibility, go to <a title="www.pjayweb.com" href="http://www.pjayweb.com" target="_blank">www.pjayweb.com</a></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/pjaywebdisability.wordpress.com/32/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/pjaywebdisability.wordpress.com/32/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/pjaywebdisability.wordpress.com/32/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/pjaywebdisability.wordpress.com/32/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/pjaywebdisability.wordpress.com/32/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/pjaywebdisability.wordpress.com/32/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/pjaywebdisability.wordpress.com/32/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/pjaywebdisability.wordpress.com/32/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/pjaywebdisability.wordpress.com/32/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/pjaywebdisability.wordpress.com/32/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/pjaywebdisability.wordpress.com/32/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/pjaywebdisability.wordpress.com/32/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/pjaywebdisability.wordpress.com/32/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/pjaywebdisability.wordpress.com/32/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pjaywebdisability.wordpress.com&amp;blog=8659580&amp;post=32&amp;subd=pjaywebdisability&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://pjaywebdisability.wordpress.com/2009/08/31/web-design-for-the-ageing-population/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/517452c141b16e5cf038e28ecaf002f7?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Penny</media:title>
		</media:content>
	</item>
		<item>
		<title>Web Content Accessibility Guidelines</title>
		<link>http://pjaywebdisability.wordpress.com/2009/08/25/web-content-accessibility-guidelines/</link>
		<comments>http://pjaywebdisability.wordpress.com/2009/08/25/web-content-accessibility-guidelines/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 09:47:06 +0000</pubDate>
		<dc:creator>Penny</dc:creator>
				<category><![CDATA[Web Usability]]></category>
		<category><![CDATA[accessibility guidelines]]></category>
		<category><![CDATA[internet usability]]></category>
		<category><![CDATA[w3]]></category>

		<guid isPermaLink="false">http://pjaywebdisability.wordpress.com/?p=28</guid>
		<description><![CDATA[The Web Content Accessibility Guidelines according to W3. For more information or greater detail go to http://www.w3.org/TR/WCAG10/#Guidelines Web Content Accessibility Guidelines 1. Provide equivalent alternatives to auditory and visual content. Provide content that, when presented to the user, conveys essentially the same function or purpose as auditory or visual content. 2. Don&#8217;t rely on colour [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pjaywebdisability.wordpress.com&amp;blog=8659580&amp;post=28&amp;subd=pjaywebdisability&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>The Web Content Accessibility Guidelines according to W3. For more information or greater detail go to</p>
<p><a title="http://www.w3.org/TR/WCAG10/#Guidelines" href="http://www.w3.org/TR/WCAG10/#Guidelines">http://www.w3.org/TR/WCAG10/#Guidelines</a></p>
<p><strong>Web Content Accessibility Guidelines</strong></p>
<p>1. Provide equivalent alternatives to auditory and visual content.</p>
<p><em>Provide content that, when presented to the user, conveys essentially the same function or purpose as auditory or visual content.</em></p>
<p>2. Don&#8217;t rely on colour alone.</p>
<p><em>Ensure that text and graphics are understandable when viewed without colour.</em></p>
<p>3. Use markup and style sheets and do so properly.</p>
<p><em>Mark up documents with the proper structural elements. Control presentation with style sheets rather than with presentation elements and attributes.</em></p>
<p>4. Clarify natural language usage</p>
<p><em>Use markup that facilitates pronunciation or interpretation of abbreviated or foreign text.</em></p>
<p>5. Create tables that transform gracefully.</p>
<p><em>Ensure that tables have necessary markup to be transformed by accessible browsers and other user agents.</em></p>
<p>6. Ensure that pages featuring new technologies transform gracefully.</p>
<p><em>Ensure that pages are accessible even when newer technologies are not supported or are turned off.</em></p>
<p>7. Ensure user control of time-sensitive content changes.</p>
<p><em>Ensure that moving, blinking, scrolling, or auto-updating objects or pages may be paused or stopped.</em></p>
<p>8. Ensure direct accessibility of embedded user interfaces.</p>
<p><em>Ensure that the user interface follows principles of accessible design: device-independent access to functionality, keyboard operability, self-voicing, etc.</em></p>
<p><em> </em></p>
<p>9. Design for device-independence.</p>
<p><em>Use features that enable activation of page elements via a variety of input devices.</em></p>
<p>10. Use interim solutions.</p>
<p><em>Use interim accessibility solutions so that assistive technologies and older browsers will operate correctly.</em></p>
<p>11. Use W3C technologies and guidelines.</p>
<p><em>Use W3C technologies (according to specification) and follow accessibility guidelines. Where it is not possible to use a W3C technology, or doing so results in material that does not transform gracefully, provide an alternative version of the content that is accessible.</em></p>
<p>12. Provide context and orientation information.</p>
<p><em>Provide context and orientation information to help users understand complex pages or elements.</em></p>
<p>13. Provide clear navigation mechanisms.</p>
<p><em>Provide clear and consistent navigation mechanisms &#8212; orientation information, navigation bars, a site map, etc. &#8212; to increase the likelihood that a person will find what they are looking for at a site.</em></p>
<p>14. Ensure that documents are clear and simple.</p>
<p><em>Ensure that documents are clear and simple so they may be more easily understood.</em></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/pjaywebdisability.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/pjaywebdisability.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/pjaywebdisability.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/pjaywebdisability.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/pjaywebdisability.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/pjaywebdisability.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/pjaywebdisability.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/pjaywebdisability.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/pjaywebdisability.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/pjaywebdisability.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/pjaywebdisability.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/pjaywebdisability.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/pjaywebdisability.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/pjaywebdisability.wordpress.com/28/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pjaywebdisability.wordpress.com&amp;blog=8659580&amp;post=28&amp;subd=pjaywebdisability&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://pjaywebdisability.wordpress.com/2009/08/25/web-content-accessibility-guidelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/517452c141b16e5cf038e28ecaf002f7?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Penny</media:title>
		</media:content>
	</item>
		<item>
		<title>Who needs Accessibility?</title>
		<link>http://pjaywebdisability.wordpress.com/2009/08/25/who-needs-accessibility/</link>
		<comments>http://pjaywebdisability.wordpress.com/2009/08/25/who-needs-accessibility/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 09:22:38 +0000</pubDate>
		<dc:creator>Penny</dc:creator>
				<category><![CDATA[Web Usability]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[Ageing]]></category>
		<category><![CDATA[arthritis]]></category>

		<guid isPermaLink="false">http://pjaywebdisability.wordpress.com/?p=24</guid>
		<description><![CDATA[Internet Accessibility is an issue with growing validity for web designers and developers; as the average age of the population increases, the population of those with accessibility issues increases also. “This issue is compounding because the world’s population is living longer with a disproportionate number of people soon to be elderly as compared with any [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pjaywebdisability.wordpress.com&amp;blog=8659580&amp;post=24&amp;subd=pjaywebdisability&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Internet Accessibility is an issue with growing validity for web designers and developers; as the average age of the population increases, the population of those with accessibility issues increases also.</p>
<p><em>“This issue is compounding because the world’s population is living longer with a disproportionate number of people soon to be elderly as compared with any other period in human history. The United Nations (<acronym>UN</acronym>) estimates that by 2050 one out of every five people will be over 60 years, and by 2150, one third of the people in the world are expected to be 60 years of age or older [<a href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#un2007"><cite>UN 2007</cite></a>; <a href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#un1998"><cite>UN 1998</cite></a>]. In Europe in the near future, it is estimated that the <acronym>EU-25</acronym> countries will experience a demographic shift from 2000 when 15.7% of the population was over 64, to an estimated older population of 17.6% in 2010 and 20.7% in 2020 [<cite><a href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#ec2007a">EC 2007a</a></cite>].”</em></p>
<p>Andrew Arch (W3C). “Web Accessibility for Older Users: A Literature Review”.  <a href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/">http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/</a><br />
Accessed 11 Aug 2009.</p>
<p>Whilst many would consider the problem to be irrelevant, several recent court cases would suggest otherwise. In Australia and the UK there have been several instances of anti-discrimination lawsuits focused on the discrimination against disabled internet users and the breach of anti-discrimination laws. If this is the future of the internet, accessibility and usability should be a priority for all web designers and developers.</p>
<p>The older internet user is not necessarily one who has major disabilities, yet minor disabilities can also cause large accessibility problems. Vision decline, Hearing loss, Motor skill diminishment and Cognition effects are experienced by many older people in varying degrees. The causes of these are also varied so any one solution may not apply to all sections of the population, creating a need for basic accessibility standards across the entire internet.</p>
<p>The least aggressive seeming of these difficulties would be motor skills diminishment, this issue however, affects a large area of the population, with many diseases, age related or not, causing various issues with motor skills.</p>
<p><em>“Arthritis is a major cause of mobility issues for the elderly and Wikipedia [<a href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#wikimsd"><cite>Wiki MSD</cite></a>] reports that arthritis is the leading cause of disability in people older than 55 years. The <acronym>US</acronym>-based Arthritis Foundation reports that 50% of Americans over 65 experience arthritis [<a href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#arthritisfndn2008"><cite>Arthritis Foundation 2008</cite></a>] , while Arthritis Care in the <acronym>UK</acronym> report that 20% of all adults in the <acronym>UK</acronym> are affected [<a href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/#arthritiscare2007"><cite>Arthritis Care 2007</cite></a>].”</em></p>
<p>Andrew Arch (W3C). “Web Accessibility for Older Users: A Literature Review”.  <a href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/">http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/</a><br />
Accessed 11 Aug 2009.</p>
<p>Problems with motor skills range from the mild, being difficulties in typing for long periods of time and accuracy with a mouse; to complete lack of motor function resulting in the complete inability to use any standard input hardware. Many companies, both large and small, have devised methods for increased usability for physically impaired people, aged or otherwise. Microsoft itself has developed both hardware and software for many years, including within ‘Windows Control Panel’ the facility to change the  ‘Accessibility Options’ of ‘Keyboard’, ‘Sound’, ‘Display’, and ‘Mouse’.</p>
<p><em>“A lot of the IT adaptations that disabled people need are already available in off-the-peg hardware and software. Accessibility is often just a matter of ensuring that particular features have not been turned off and helping users to set them up. For example, a feature such as sticky keys, which enables a user to press the Shift, Ctrl, Alt and Windows keys one at a time rather than all at once (to create a capital letter, for example), is great for people who lack the dexterity to press these commonly used keys together.<br />
Many of the assistive aids disabled people need are very simple. For example, oversized keyboards for those with an uncertain touch; key guards to guide fingers onto keys; big switches the size of yo-yos to control software.&#8221;<br />
</em></p>
<p><a href="http://www.microsoft.com/enable/default.aspx">http://www.microsoft.com/enable/default.aspx</a><br />
Accessed 11 Aug 2009.</p>
<p>With the average age of our population increasing, it is imperative for the industry, that all designers of computer related equipment, hardware and software, take into consideration the difficulties faced at a basic level by large sections of the market.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/pjaywebdisability.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/pjaywebdisability.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/pjaywebdisability.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/pjaywebdisability.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/pjaywebdisability.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/pjaywebdisability.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/pjaywebdisability.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/pjaywebdisability.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/pjaywebdisability.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/pjaywebdisability.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/pjaywebdisability.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/pjaywebdisability.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/pjaywebdisability.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/pjaywebdisability.wordpress.com/24/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pjaywebdisability.wordpress.com&amp;blog=8659580&amp;post=24&amp;subd=pjaywebdisability&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://pjaywebdisability.wordpress.com/2009/08/25/who-needs-accessibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/517452c141b16e5cf038e28ecaf002f7?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Penny</media:title>
		</media:content>
	</item>
		<item>
		<title>So, is your web site accessible?</title>
		<link>http://pjaywebdisability.wordpress.com/2009/08/04/so-is-your-web-site-accessible/</link>
		<comments>http://pjaywebdisability.wordpress.com/2009/08/04/so-is-your-web-site-accessible/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 11:29:20 +0000</pubDate>
		<dc:creator>Penny</dc:creator>
				<category><![CDATA[Web Usability]]></category>

		<guid isPermaLink="false">http://pjaywebdisability.wordpress.com/2009/08/04/so-is-your-web-site-accessible/</guid>
		<description><![CDATA[With the average age of the population increasing, and the number of businesses and individuals dependant on the web, isn’t it worth your while to make your site accessible to everyone, regardless of ability? There are a growing number of people with disabilities, impairments and problems with web use. Is your web site able to [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pjaywebdisability.wordpress.com&amp;blog=8659580&amp;post=13&amp;subd=pjaywebdisability&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>With the average age of the population increasing, and the number of businesses and individuals dependant on the web, isn’t it worth your while to make your site accessible to everyone, regardless of ability?<br />
There are a growing number of people with disabilities, impairments and problems with web use.<br />
Is your web site able to deal with these people? Or will they click out of your site before they have had a chance to see what it is you have to offer?<br />
Many accessibility issues are simple to deal with and require little in the way of extra design time.<br />
There are some simple things that you can do to enable more users access to your site. I will begin on the general basics and work my way up to focus on the more specific issue of mobility and dexterity. There are many ways in which you can make your site user friendly, seeing it as an issue to begin with, is a huge step forward.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/pjaywebdisability.wordpress.com/13/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/pjaywebdisability.wordpress.com/13/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/pjaywebdisability.wordpress.com/13/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/pjaywebdisability.wordpress.com/13/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/pjaywebdisability.wordpress.com/13/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/pjaywebdisability.wordpress.com/13/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/pjaywebdisability.wordpress.com/13/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/pjaywebdisability.wordpress.com/13/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/pjaywebdisability.wordpress.com/13/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/pjaywebdisability.wordpress.com/13/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/pjaywebdisability.wordpress.com/13/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/pjaywebdisability.wordpress.com/13/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/pjaywebdisability.wordpress.com/13/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/pjaywebdisability.wordpress.com/13/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=pjaywebdisability.wordpress.com&amp;blog=8659580&amp;post=13&amp;subd=pjaywebdisability&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://pjaywebdisability.wordpress.com/2009/08/04/so-is-your-web-site-accessible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/517452c141b16e5cf038e28ecaf002f7?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Penny</media:title>
		</media:content>
	</item>
	</channel>
</rss>
