<?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>Bristol Web Designer &#187; Accessibility</title>
	<atom:link href="http://www.imaker.co.uk/blog/category/accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.imaker.co.uk/blog</link>
	<description>Website design Blog</description>
	<lastBuildDate>Fri, 13 Jan 2012 15:10:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Accessible web design</title>
		<link>http://www.imaker.co.uk/blog/accessible-web-design/</link>
		<comments>http://www.imaker.co.uk/blog/accessible-web-design/#comments</comments>
		<pubDate>Mon, 05 Jun 2006 09:23:56 +0000</pubDate>
		<dc:creator>imaker</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://www.imaker.co.uk/blog/?p=19</guid>
		<description><![CDATA[When displaying images when should you use ALT and TITLE attributes? I was recently asked this and it got me thinking about the what and why. According to the W3C the ALT attribute is required, but the TITLE attribute is &#8230; <a href="http://www.imaker.co.uk/blog/accessible-web-design/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>When displaying images when should you use ALT and TITLE attributes?  I was recently asked this and it got me thinking about the what and why.</p>
<p>According to the W3C the ALT attribute is required, but the TITLE attribute is not. <span id="more-19"></span></p>
<p>The <span style="font-weight: bold">ALT</span> attribute is used as a text equivalent of the image, i.e. it should convey the same information as the image, and is used by screen readers to give and audio instead of visual representation of a web page.  ALT is supposed to be shown only when the image itself is not displayed, for example if you turn off images in your browser. IE/Win shows the ALT text as a tool-tip, but that&#8217;s not the correct behaviour according to the spec.</p>
<p>When using the ALT attribute you should be using no more than one or two sentences, if you need more then you can use the LONGDESC attribute to point to a longer description.</p>
<p>The <span style="font-weight: bold">TITLE</span> attribute is an &#8216;advisory title&#8217; which you can use to convey additional information. TITLE is shown by browsers that support it, even when the image is visible, and even IE uses TITLE instead of ALT, if it&#8217;s specified.</p>
<p>It is rarely useful to have the same text in ALT and in TITLE. They are meant for very different purposes.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.imaker.co.uk/blog/accessible-web-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is accessibility enough?</title>
		<link>http://www.imaker.co.uk/blog/is-accessibility-enough/</link>
		<comments>http://www.imaker.co.uk/blog/is-accessibility-enough/#comments</comments>
		<pubDate>Mon, 21 Nov 2005 14:25:44 +0000</pubDate>
		<dc:creator>imaker</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://www.imaker.co.uk/blog/?p=9</guid>
		<description><![CDATA[If you hunt around our site enough you should find a link that says it has passed the W3C guidelines on accessibility. However Jacob Nielsen, who is one of the leading usability experts, has just published an article with the &#8230; <a href="http://www.imaker.co.uk/blog/is-accessibility-enough/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>If you hunt around our site enough you should find a link that says it has passed the W3C <a href="http://www.imaker.co.uk/about.html">guidelines on accessibility</a>. However <a href="http://www.imaker.co.uk/web-design/nielsen.html">Jacob Nielsen</a>, who is one of the leading usability experts, has just published an article with the title of &#8216;<a href="http://www.useit.com/alertbox/accessibility.html">Accessibility Is Not Enough</a>&#8216;. It raises some worthwhile points and is well worth the read, summarised as &#8220;A strict focus on accessibility as a scorecard item doesn&#8217;t help users with disabilities. To help these users accomplish critical tasks, you must adopt a usability perspective&#8221;. You can find the article by following the title link.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.imaker.co.uk/blog/is-accessibility-enough/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessibility and your website, why bother?</title>
		<link>http://www.imaker.co.uk/blog/accessibility-and-your-website-why-bother/</link>
		<comments>http://www.imaker.co.uk/blog/accessibility-and-your-website-why-bother/#comments</comments>
		<pubDate>Sat, 29 Oct 2005 11:54:19 +0000</pubDate>
		<dc:creator>imaker</dc:creator>
				<category><![CDATA[Accessibility]]></category>

		<guid isPermaLink="false">http://www.imaker.co.uk/blog/?p=6</guid>
		<description><![CDATA[Accessibility is about everyone being able to access content online regardless of any physical impairment they may have. There are statutes that compel all web sites to be accessible. iMaker endeavour to build your website to be as accessible as &#8230; <a href="http://www.imaker.co.uk/blog/accessibility-and-your-website-why-bother/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Accessibility is about everyone being able to access content online regardless of any physical impairment they may have. There are statutes that compel all web sites to be accessible. iMaker endeavour to build your website to be as accessible as possible, but that means more work for us, so how does it benefit you, the client?</p>
<p><strong>Better search rankings</strong>. Search engines find it easier to catalogue web sites that are written for accessibility. As the majority of people find things on the internet using search engines, the easier you can make the engines job, the better for you.</p>
<p><strong>Long term Cost</strong>. Building an accessible web site means separating content from presentation to produce a content (xhtml) page and a presentation (css) page. These two files combine to provide the browser with the whole web page for display. There could be many thousands of html files in your site but only one css file. If you want to change the layout for your site you just need to change the one css file, that will change the layout for the entire site!</p>
<p><strong>Compatibility</strong>. Again building an accessible site should mean that your site looks the same in any browser, certainly the most popular, such as Internet explorer, Opera, Firefox and Safari. All your users will see the website as you do.</p>
<p><strong>Speed</strong>. A website built for accessibility will load much quicker than one that hasn&#8217;t and so keep your visitors happy and hopefully interested.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.imaker.co.uk/blog/accessibility-and-your-website-why-bother/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

