<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.townx.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>townx - Website launch - Comments</title>
 <link>http://www.townx.org/blog/elliot/website_launch</link>
 <description>Comments for &quot;Website launch&quot;</description>
 <language>en</language>
<item>
 <title>Website launch</title>
 <link>http://www.townx.org/blog/elliot/website_launch</link>
 <description>&lt;p&gt;I&#039;ve recently been building a website for a charity in Manchester (see &lt;a href=&quot;http://www.selfhelpservices.org.uk/&quot;&gt;Self Help Services&lt;/a&gt;), which I launched last week. I found out about the project through the &lt;a href=&quot;http://www.it4communities.org.uk&quot;&gt;IT4Communities website&lt;/a&gt;, which I recommend for anyone with IT skills who would like to do some charity work. I also got involved to improve my portfolio, when I was thinking about a career change and considering consultancy.&lt;/p&gt;
&lt;p&gt;One thing I&#039;m quite pleased about is that I designed it to the &lt;a href=&quot;http://www.w3.org/TR/WAI-WEBCONTENT/&quot;&gt;W3C Web Content  Accessibility Guidelines&lt;/a&gt;. As a consequence, when I tried the site through my new HP iPAQ PDA, it displayed very nicely, unlike 90% of sites on the web. I&#039;ve always maintained that building accessible sites would future-proof them: human-accessible = machine-accessible as a consequence. Nice to see it working in practice.&lt;/p&gt;
</description>
 <comments>http://www.townx.org/blog/elliot/website_launch#comments</comments>
 <pubDate>Thu, 28 Oct 2004 18:21:53 -0500</pubDate>
 <dc:creator>elliot</dc:creator>
 <guid isPermaLink="false">38 at http://www.townx.org</guid>
</item>
</channel>
</rss>
