<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Patrick Lauke on Ariadne</title>
    <link>http://www.ariadne.ac.uk/authors/patrick-lauke/</link>
    <description>Recent content in Patrick Lauke on Ariadne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 08 Feb 2006 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://www.ariadne.ac.uk/authors/patrick-lauke/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Accessibility Testing and Reporting With TAW3</title>
      <link>http://www.ariadne.ac.uk/issue/46/lauke/</link>
      <pubDate>Wed, 08 Feb 2006 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/46/lauke/</guid>
      <description>When it comes to assessing a Web site&#39;s accessibility, any Web designer should know by now that simply running the mark-up though an automated testing tool is not enough. Automated tools are limited, purely testing for syntax, easily ascertained &#34;yes or no&#34; situations and a set of (sometimes quite arbitrary) heuristics, which are often based on an interpretation of accessibility guidelines on the part of the tool&#39;s developers.
Nonetheless, automated checkers are a useful tool in the arsenal of accessibility-conscious designers, provided that their results are checked for false positives/negatives [1] and backed up by the necessary manual checks, carried out by a knowledgeable human tester who is familiar with any potential access issues and how they manifest themselves in a Web site.</description>
    </item>
    
    <item>
      <title>Evaluating Web Sites for Accessibility With Firefox</title>
      <link>http://www.ariadne.ac.uk/issue/44/lauke/</link>
      <pubDate>Fri, 29 Jul 2005 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/44/lauke/</guid>
      <description>In a previous issue of Ariadne [1], I gave a brief overview of Mozilla Firefox [2] and introduced a few of its most useful extensions. In this article, we will use one of these extensions, Chris Pederick&#39;s Web Developer toolbar [3], to aid us in a preliminary assessment of a web site&#39;s accessibility.
Although awareness of web accessibility has steadily increased in recent years, many web developers are still uncertain about how to evaluate their sites.</description>
    </item>
    
    <item>
      <title>Mozilla Firefox for Rapid Web Development and Testing</title>
      <link>http://www.ariadne.ac.uk/issue/42/lauke/</link>
      <pubDate>Sun, 30 Jan 2005 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/42/lauke/</guid>
      <description>Mozilla Firefox [1] is a free, open-source Web browser based on the Mozilla codebase.
Version 1.0 was recently released after two years of development, so now may be a good time to evaluate this browser&#39;s capabilities.
&#34;Out of the box&#34; Mozilla Firefox offers a variety of features catering to both occasional Web surfers and power users. The more advanced functionality can be particularly noted as a real time saver during the Web development process.</description>
    </item>
    
  </channel>
</rss>