<?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: 6 Accessibility Tips</title>
	<atom:link href="http://divitodesign.com/accesibility/6-accessibility-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://divitodesign.com/accesibility/6-accessibility-tips/</link>
	<description>Articles, Tutorials and Resources for the Webdesigner</description>
	<lastBuildDate>Thu, 02 Feb 2012 15:35:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: jinny</title>
		<link>http://divitodesign.com/accesibility/6-accessibility-tips/comment-page-1/#comment-54741</link>
		<dc:creator>jinny</dc:creator>
		<pubDate>Tue, 28 Jun 2011 12:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/blog/2007/10/6-accessibility-tips/#comment-54741</guid>
		<description>thanks for the great article I have been learning to develop site on my own and your articles are helping get to my goals....</description>
		<content:encoded><![CDATA[<p>thanks for the great article I have been learning to develop site on my own and your articles are helping get to my goals&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unisonlogix &#187; Blog Archive &#187; How-to: DropDown CSS Menu</title>
		<link>http://divitodesign.com/accesibility/6-accessibility-tips/comment-page-1/#comment-8310</link>
		<dc:creator>Unisonlogix &#187; Blog Archive &#187; How-to: DropDown CSS Menu</dc:creator>
		<pubDate>Sat, 25 Oct 2008 08:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/blog/2007/10/6-accessibility-tips/#comment-8310</guid>
		<description>[...] To learn more about accessibility in a CSS menu, you should read my past tips regarding accessibility here. [...]</description>
		<content:encoded><![CDATA[<p>[...] To learn more about accessibility in a CSS menu, you should read my past tips regarding accessibility here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How-to: DropDown CSS Menu &#187; DivitoDesign - Webdesign Blog</title>
		<link>http://divitodesign.com/accesibility/6-accessibility-tips/comment-page-1/#comment-5404</link>
		<dc:creator>How-to: DropDown CSS Menu &#187; DivitoDesign - Webdesign Blog</dc:creator>
		<pubDate>Tue, 09 Sep 2008 18:53:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/blog/2007/10/6-accessibility-tips/#comment-5404</guid>
		<description>[...] To learn more about accessibility in a CSS menu, you should read my past tips regarding accessibility here. [...]</description>
		<content:encoded><![CDATA[<p>[...] To learn more about accessibility in a CSS menu, you should read my past tips regarding accessibility here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Make your weblog more user friendly » divitodesign.com</title>
		<link>http://divitodesign.com/accesibility/6-accessibility-tips/comment-page-1/#comment-1402</link>
		<dc:creator>Make your weblog more user friendly » divitodesign.com</dc:creator>
		<pubDate>Sat, 23 Feb 2008 18:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/blog/2007/10/6-accessibility-tips/#comment-1402</guid>
		<description>[...] Important part. Not all visitors use the same device, computer, browser, and/or settings. Maybe, your weblog is not visualized the way you or your designer wanted to. Some users might have disabled images or JavaScript, some might have a 800×600 resolution. You should prepare for this, make sure they can read the content and view the site as good as possible. Remember, you are publishing for all users and it should be your goal to let everyone read your content. Read more accessibility tips. [...]</description>
		<content:encoded><![CDATA[<p>[...] Important part. Not all visitors use the same device, computer, browser, and/or settings. Maybe, your weblog is not visualized the way you or your designer wanted to. Some users might have disabled images or JavaScript, some might have a 800×600 resolution. You should prepare for this, make sure they can read the content and view the site as good as possible. Remember, you are publishing for all users and it should be your goal to let everyone read your content. Read more accessibility tips. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michiel</title>
		<link>http://divitodesign.com/accesibility/6-accessibility-tips/comment-page-1/#comment-1291</link>
		<dc:creator>Michiel</dc:creator>
		<pubDate>Mon, 07 Jan 2008 14:38:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/blog/2007/10/6-accessibility-tips/#comment-1291</guid>
		<description>I have to agree with you on that one, for content images you could use something like that. It is more noticeable when you put a &#039;-&#039; before and after the text.

An other technique I saw on the W3 website:

Travel Expense Report table as rendered by a visual user agent.

Instead of this image: http://www.w3.org/TR/WCAG10-HTML-TECHS/techimages/table1.gif

to be found above: http://www.w3.org/TR/WCAG10-HTML-TECHS/#tables-layout

Notice the text behind the description. This is also a good technique if the image isn&#039;t in the middle of the text (because then it would just be a weird sentence).

So depending on where the image is, you could use any of these techniques.</description>
		<content:encoded><![CDATA[<p>I have to agree with you on that one, for content images you could use something like that. It is more noticeable when you put a &#8216;-&#8217; before and after the text.</p>
<p>An other technique I saw on the W3 website:</p>
<p>Travel Expense Report table as rendered by a visual user agent.</p>
<p>Instead of this image: <a href="http://www.w3.org/TR/WCAG10-HTML-TECHS/techimages/table1.gif" rel="nofollow">http://www.w3.org/TR/WCAG10-HTML-TECHS/techimages/table1.gif</a></p>
<p>to be found above: <a href="http://www.w3.org/TR/WCAG10-HTML-TECHS/#tables-layout" rel="nofollow">http://www.w3.org/TR/WCAG10-HTML-TECHS/#tables-layout</a></p>
<p>Notice the text behind the description. This is also a good technique if the image isn&#8217;t in the middle of the text (because then it would just be a weird sentence).</p>
<p>So depending on where the image is, you could use any of these techniques.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Vervoort</title>
		<link>http://divitodesign.com/accesibility/6-accessibility-tips/comment-page-1/#comment-1284</link>
		<dc:creator>Stefan Vervoort</dc:creator>
		<pubDate>Fri, 04 Jan 2008 19:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/blog/2007/10/6-accessibility-tips/#comment-1284</guid>
		<description>Thank you Michiel. 

You are right; navigation images should have ALT-texts to point the direction the visitor are going. But what to do with images inside the content? 

Example: You are using ALT-text &#039;Dog&#039; when displaying a image of a dog. This image will not be shown in some browsers where images are turned off, the ALT-text is. The readers will scan the text and does not recognize an image in the content. When you have used something like this: -- DOG --, the &#039;strange text&#039; will fall out and you have more changes to make this ALT-text will be seen. Far more changes as &#039;Dog&#039; only. 

What do you think?</description>
		<content:encoded><![CDATA[<p>Thank you Michiel. </p>
<p>You are right; navigation images should have ALT-texts to point the direction the visitor are going. But what to do with images inside the content? </p>
<p>Example: You are using ALT-text &#8216;Dog&#8217; when displaying a image of a dog. This image will not be shown in some browsers where images are turned off, the ALT-text is. The readers will scan the text and does not recognize an image in the content. When you have used something like this: &#8212; DOG &#8211;, the &#8216;strange text&#8217; will fall out and you have more changes to make this ALT-text will be seen. Far more changes as &#8216;Dog&#8217; only. </p>
<p>What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michiel</title>
		<link>http://divitodesign.com/accesibility/6-accessibility-tips/comment-page-1/#comment-1283</link>
		<dc:creator>Michiel</dc:creator>
		<pubDate>Fri, 04 Jan 2008 08:41:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/blog/2007/10/6-accessibility-tips/#comment-1283</guid>
		<description>Nice article! There&#039;s some good stuff in there.

Although I don&#039;t agree on the ALT-text part. Your ALT-text should display whats on the image, or where it links to. So an image used in a navigation that looks like this:

---------
&#124; Home  &#124;
---------

Should have an ALT-text like: &#039;Home&#039; or &#039;Go to home&#039;, or something like it. This way people will recognize it as navigation rater than content.</description>
		<content:encoded><![CDATA[<p>Nice article! There&#8217;s some good stuff in there.</p>
<p>Although I don&#8217;t agree on the ALT-text part. Your ALT-text should display whats on the image, or where it links to. So an image used in a navigation that looks like this:</p>
<p>&#8212;&#8212;&#8212;<br />
| Home  |<br />
&#8212;&#8212;&#8212;</p>
<p>Should have an ALT-text like: &#8216;Home&#8217; or &#8216;Go to home&#8217;, or something like it. This way people will recognize it as navigation rater than content.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

