<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kevin Carey on Ariadne</title>
    <link>http://www.ariadne.ac.uk/authors/kevin-carey/</link>
    <description>Recent content in Kevin Carey on Ariadne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 29 Jul 2005 23:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://www.ariadne.ac.uk/authors/kevin-carey/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Accessibility: The Current Situation and New Directions</title>
      <link>http://www.ariadne.ac.uk/issue/44/carey/</link>
      <pubDate>Fri, 29 Jul 2005 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/44/carey/</guid>
      <description>Accessibility and UsabilityBefore embarking on the major strands of my argument it would be as well to consider definitions.
There is now a fine old Pharisaic, or perhaps we might better say Scholastic, discussion about the delineation of accessibility - the capability of a system to cater for the needs of disabled people - as a highly specific segment in the usability - the capability of a system to behave in a way which most closely accords with human behaviour - sector as a whole.</description>
    </item>
    
  </channel>
</rss>