<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: SEO and Accessibility Overlap</title>
	<atom:link href="http://www.communis.co.uk/blog/2009-08-06-seo-and-accessibility-overlap/feed" rel="self" type="application/rss+xml" />
	<link>http://www.communis.co.uk/blog/2009-08-06-seo-and-accessibility-overlap</link>
	<description>Notes from the sharp end of web accessiblity</description>
	<lastBuildDate>Tue, 13 Jul 2010 05:17:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Colin Hall</title>
		<link>http://www.communis.co.uk/blog/2009-08-06-seo-and-accessibility-overlap/comment-page-1#comment-37454</link>
		<dc:creator>Colin Hall</dc:creator>
		<pubDate>Tue, 13 Jul 2010 05:17:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.communis.co.uk/blog/?p=70#comment-37454</guid>
		<description>I started using a &#039;blind browser&#039; back in 2004, both for website building and because I also have limited close-up sight issues (now a Fire Vox user). I found that I instantly gained in search engine results and, because of the text value of the page, I was provided with a huge cross-section of long-tail keywords.

Points that I have found to be important in accessible page design are as follows:

1. All pictures must be properly described in their Alt text.
2. Text topics should be segmented into blocks
3. The first link on the page should be to a site synopsis .txt page, which completely describes your site and offers your blind visitors the opportunity to quickly contact the site managers and request help to find what they need directly.
4. Bookmarks are good.
5. links need to be easily read ( i.e. contact.html , not contact.php?blablabla )
6. Absolutely no repeated keywords or bulk packing of keywords. These are read really easily, but bore the living daylights out of your blind readers.

It&#039;s important to realise (as Liam has already written about above) that Search engine spiders work in the same way as a blind browser. So, if it&#039;s good for your blind readers, it&#039;s good for your SEO work too.

Another thing that I would like to see is a DMOZ style directory that lists only 100% accessible sites. Then I&#039;d like to see Google, Yahoo, etc. reward anyone who makes the grade with additional search engine trustrank.

Thanks for a very interesting article Liam. It&#039;s a subject that is often ignored, but it&#039;s also an area that reaps rewards if the time is taken.

All the best

Colin (Norwich)</description>
		<content:encoded><![CDATA[<p>I started using a &#8216;blind browser&#8217; back in 2004, both for website building and because I also have limited close-up sight issues (now a Fire Vox user). I found that I instantly gained in search engine results and, because of the text value of the page, I was provided with a huge cross-section of long-tail keywords.</p>
<p>Points that I have found to be important in accessible page design are as follows:</p>
<p>1. All pictures must be properly described in their Alt text.<br />
2. Text topics should be segmented into blocks<br />
3. The first link on the page should be to a site synopsis .txt page, which completely describes your site and offers your blind visitors the opportunity to quickly contact the site managers and request help to find what they need directly.<br />
4. Bookmarks are good.<br />
5. links need to be easily read ( i.e. contact.html , not contact.php?blablabla )<br />
6. Absolutely no repeated keywords or bulk packing of keywords. These are read really easily, but bore the living daylights out of your blind readers.</p>
<p>It&#8217;s important to realise (as Liam has already written about above) that Search engine spiders work in the same way as a blind browser. So, if it&#8217;s good for your blind readers, it&#8217;s good for your SEO work too.</p>
<p>Another thing that I would like to see is a DMOZ style directory that lists only 100% accessible sites. Then I&#8217;d like to see Google, Yahoo, etc. reward anyone who makes the grade with additional search engine trustrank.</p>
<p>Thanks for a very interesting article Liam. It&#8217;s a subject that is often ignored, but it&#8217;s also an area that reaps rewards if the time is taken.</p>
<p>All the best</p>
<p>Colin (Norwich)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liam McGee</title>
		<link>http://www.communis.co.uk/blog/2009-08-06-seo-and-accessibility-overlap/comment-page-#comment-37384</link>
		<dc:creator>Liam McGee</dc:creator>
		<pubDate>Wed, 30 Sep 2009 07:47:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.communis.co.uk/blog/?p=70#comment-37384</guid>
		<description>Nine years (feels like longer) working in the field of accessibility and coming on for five years working in the field of evidence-based SEO. If you have closer look at the article I provide a few references if you want to dig deeper. Thanks for reading!</description>
		<content:encoded><![CDATA[<p>Nine years (feels like longer) working in the field of accessibility and coming on for five years working in the field of evidence-based SEO. If you have closer look at the article I provide a few references if you want to dig deeper. Thanks for reading!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mantra SEO dan Aksesibilitas Web - Dani Iswara .Net</title>
		<link>http://www.communis.co.uk/blog/2009-08-06-seo-and-accessibility-overlap/comment-page-1#comment-37366</link>
		<dc:creator>Mantra SEO dan Aksesibilitas Web - Dani Iswara .Net</dc:creator>
		<pubDate>Sat, 05 Sep 2009 01:26:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.communis.co.uk/blog/?p=70#comment-37366</guid>
		<description>[...] mesin pencari Internet. Liam McGee mengulas keterkaitan SEO dan aksesibilitas web versi WCAG 2.0 di SEO and Accessibility Overlap (blog Accessibility Field Notes). Lebih rinci lagi poin demi [...]</description>
		<content:encoded><![CDATA[<p>[...] mesin pencari Internet. Liam McGee mengulas keterkaitan SEO dan aksesibilitas web versi WCAG 2.0 di SEO and Accessibility Overlap (blog Accessibility Field Notes). Lebih rinci lagi poin demi [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Captions tell the future - Accessible Rhetoric</title>
		<link>http://www.communis.co.uk/blog/2009-08-06-seo-and-accessibility-overlap/comment-page-1#comment-37359</link>
		<dc:creator>Captions tell the future - Accessible Rhetoric</dc:creator>
		<pubDate>Wed, 12 Aug 2009 18:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.communis.co.uk/blog/?p=70#comment-37359</guid>
		<description>[...] We don&#8217;t tend to talk about closed captions as providing, in some cases, a different (even advantageous) viewing experience over traditional, non-captioned ways of watching movies and TV shows. And yet I think that&#8217;s precisely what we need to talk about in order to bring closed captions closer to the mainstream. That&#8217;s what Web accessibility advocates do every time they discuss Web accessibility as benefiting everyone, not just users with disabilities. (Two quick examples: consider how Mobile Web Best Practices overlap with Web Accessibility Content Guidelines [e.g. see WAI], and how the practice of optimizing websites for search engines overlaps with the practice of making websites accessible [e.g. see McGee].) [...]</description>
		<content:encoded><![CDATA[<p>[...] We don&#8217;t tend to talk about closed captions as providing, in some cases, a different (even advantageous) viewing experience over traditional, non-captioned ways of watching movies and TV shows. And yet I think that&#8217;s precisely what we need to talk about in order to bring closed captions closer to the mainstream. That&#8217;s what Web accessibility advocates do every time they discuss Web accessibility as benefiting everyone, not just users with disabilities. (Two quick examples: consider how Mobile Web Best Practices overlap with Web Accessibility Content Guidelines [e.g. see WAI], and how the practice of optimizing websites for search engines overlaps with the practice of making websites accessible [e.g. see McGee].) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

