<?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: Web standards checklist</title>
	<atom:link href="http://www.maxdesign.com.au/articles/checklist/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.maxdesign.com.au</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 22:31:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Russ</title>
		<link>http://www.maxdesign.com.au/articles/checklist/comment-page-1/#comment-3682</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Mon, 09 Aug 2010 02:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/?page_id=1090#comment-3682</guid>
		<description>Hi Emmanuel-Jelome

Good to hear from you. Thank you for the comments.

&lt;strong&gt;Re points 1 and 2:&lt;/strong&gt;
I presume you are talking about the longdesc attribute?
http://www.w3.org/TR/REC-html40/struct/objects.html#adef-longdesc-IMG

[img longdesc=&quot;URL&quot; alt=&quot;ALT text&quot; /]

We have found that although longdesc is great, it has two issues:
1. people stopped using them some time ago so it has died out as a practice
2. in all of our testing, blind users did not use these - they are bombarded by too much info anyway, and generally a good &quot;alt&quot; attribute was more than enough.

&lt;strong&gt;Re point 3:&lt;/strong&gt;
There is info on skip links above.

&lt;strong&gt;Re point 4:&lt;/strong&gt;
I am not a fan of adding values into input elements as a general. I think it is much more important to include a good label, with a &quot;for&quot; attribute that describes the input element. Labels are vital for blind users, and useful for everyone.

One key issue with adding a value into an input field is that it should be &quot;cleared&quot; before users start typing - otherwise it can cause all sorts of usability issues - agin, this affects sighted and blind users.</description>
		<content:encoded><![CDATA[<p>Hi Emmanuel-Jelome</p>
<p>Good to hear from you. Thank you for the comments.</p>
<p><strong>Re points 1 and 2:</strong><br />
I presume you are talking about the longdesc attribute?<br />
<a href="http://www.w3.org/TR/REC-html40/struct/objects.html#adef-longdesc-IMG" rel="nofollow">http://www.w3.org/TR/REC-html40/struct/objects.html#adef-longdesc-IMG</a></p>
<p>[img longdesc="URL" alt="ALT text" /]</p>
<p>We have found that although longdesc is great, it has two issues:<br />
1. people stopped using them some time ago so it has died out as a practice<br />
2. in all of our testing, blind users did not use these &#8211; they are bombarded by too much info anyway, and generally a good &#8220;alt&#8221; attribute was more than enough.</p>
<p><strong>Re point 3:</strong><br />
There is info on skip links above.</p>
<p><strong>Re point 4:</strong><br />
I am not a fan of adding values into input elements as a general. I think it is much more important to include a good label, with a &#8220;for&#8221; attribute that describes the input element. Labels are vital for blind users, and useful for everyone.</p>
<p>One key issue with adding a value into an input field is that it should be &#8220;cleared&#8221; before users start typing &#8211; otherwise it can cause all sorts of usability issues &#8211; agin, this affects sighted and blind users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emmanuel-Jelome</title>
		<link>http://www.maxdesign.com.au/articles/checklist/comment-page-1/#comment-3666</link>
		<dc:creator>Emmanuel-Jelome</dc:creator>
		<pubDate>Sat, 07 Aug 2010 04:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/?page_id=1090#comment-3666</guid>
		<description>Hello, this was a very useful checklist - 5 stars. ^^,

I&#039;m an extremist regarding web standards, although I&#039;m just an amateur in the f2e world (7 months old ^^), may I add some accessibility requirement from your list.

1. Image &#039;desc&#039;ription - although not mandatory in every images, you should at least put &#039;desc&#039; into your logo, in case the use wants to know what the logo is all about, it is the opposite of &#039;alt&#039;, which is the short version.

2. d-link - because &#039;desc&#039; is not majorly supported by browsers (even the major browsers), this will serve as the alternative to link to your &#039;desc&#039; file.

3. skip-link - You should give users (especially for blind users using assistive technology - e.g. screen reader) to be able to skip navigation links. Skip links help the user to jump immediately to content, rather than letting them wait to read out all the links of the page before even reaching the content.

4. default value for  input elements/tags - This is useful for forms and even search features of your web site. This allows the user to know what should be typed in the field.

Keep up the good work,
Kind regards, 
Jelome ^^,</description>
		<content:encoded><![CDATA[<p>Hello, this was a very useful checklist &#8211; 5 stars. ^^,</p>
<p>I&#8217;m an extremist regarding web standards, although I&#8217;m just an amateur in the f2e world (7 months old ^^), may I add some accessibility requirement from your list.</p>
<p>1. Image &#8216;desc&#8217;ription &#8211; although not mandatory in every images, you should at least put &#8216;desc&#8217; into your logo, in case the use wants to know what the logo is all about, it is the opposite of &#8216;alt&#8217;, which is the short version.</p>
<p>2. d-link &#8211; because &#8216;desc&#8217; is not majorly supported by browsers (even the major browsers), this will serve as the alternative to link to your &#8216;desc&#8217; file.</p>
<p>3. skip-link &#8211; You should give users (especially for blind users using assistive technology &#8211; e.g. screen reader) to be able to skip navigation links. Skip links help the user to jump immediately to content, rather than letting them wait to read out all the links of the page before even reaching the content.</p>
<p>4. default value for  input elements/tags &#8211; This is useful for forms and even search features of your web site. This allows the user to know what should be typed in the field.</p>
<p>Keep up the good work,<br />
Kind regards,<br />
Jelome ^^,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jabuke.Net</title>
		<link>http://www.maxdesign.com.au/articles/checklist/comment-page-1/#comment-3621</link>
		<dc:creator>Jabuke.Net</dc:creator>
		<pubDate>Mon, 02 Aug 2010 08:57:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/?page_id=1090#comment-3621</guid>
		<description>[...] How does the site perform in terms of speed/page size? [...]</description>
		<content:encoded><![CDATA[<p>[...] How does the site perform in terms of speed/page size? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Essential Website Launch Checklists &#124; Ekste</title>
		<link>http://www.maxdesign.com.au/articles/checklist/comment-page-1/#comment-3600</link>
		<dc:creator>Essential Website Launch Checklists &#124; Ekste</dc:creator>
		<pubDate>Sat, 31 Jul 2010 07:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/?page_id=1090#comment-3600</guid>
		<description>[...] Web Standards Checklist [...]</description>
		<content:encoded><![CDATA[<p>[...] Web Standards Checklist [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cheap web designer</title>
		<link>http://www.maxdesign.com.au/articles/checklist/comment-page-1/#comment-3532</link>
		<dc:creator>Cheap web designer</dc:creator>
		<pubDate>Sat, 24 Jul 2010 12:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/?page_id=1090#comment-3532</guid>
		<description>Very nice web design checklist.It is really useful when I will  start web designing it&#039;s great help me. thanks</description>
		<content:encoded><![CDATA[<p>Very nice web design checklist.It is really useful when I will  start web designing it&#8217;s great help me. thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Usability Guidelines &#171; Right4web&#39;s Blog</title>
		<link>http://www.maxdesign.com.au/articles/checklist/comment-page-1/#comment-3528</link>
		<dc:creator>Usability Guidelines &#171; Right4web&#39;s Blog</dc:creator>
		<pubDate>Fri, 23 Jul 2010 15:35:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/?page_id=1090#comment-3528</guid>
		<description>[...] http://www.maxdesign.com.au/articles/checklist/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.maxdesign.com.au/articles/checklist/" rel="nofollow">http://www.maxdesign.com.au/articles/checklist/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Não bata palmas para meias-verdades! ? Revolução Etc</title>
		<link>http://www.maxdesign.com.au/articles/checklist/comment-page-1/#comment-3490</link>
		<dc:creator>Não bata palmas para meias-verdades! ? Revolução Etc</dc:creator>
		<pubDate>Tue, 20 Jul 2010 16:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/?page_id=1090#comment-3490</guid>
		<description>[...] Recentemente se tem discutido muito sobre crit&#233;rios de avalia&#231;&#227;o de um trabalho web, se &#233; &quot;tableless&quot; ou n&#227;o, se &#233; &quot;webstandards&quot; ou n&#227;o e por a&#237; vai. Alguns defendem simplesmente trocar tabelas por divs outros defendem que apenas se o c&#243;digo estiver validado pelo validador da W3C &#233; que o trabalho ser&#225; webstandards. Navegando pelo site do Maujor, CSS para Web Design encontrei o CheckList para web standards que &#233; uma tradu&#231;&#227;o de um artigo do Russ Weakley. [...]</description>
		<content:encoded><![CDATA[<p>[...] Recentemente se tem discutido muito sobre crit&eacute;rios de avalia&ccedil;&atilde;o de um trabalho web, se &eacute; &quot;tableless&quot; ou n&atilde;o, se &eacute; &quot;webstandards&quot; ou n&atilde;o e por a&iacute; vai. Alguns defendem simplesmente trocar tabelas por divs outros defendem que apenas se o c&oacute;digo estiver validado pelo validador da W3C &eacute; que o trabalho ser&aacute; webstandards. Navegando pelo site do Maujor, CSS para Web Design encontrei o CheckList para web standards que &eacute; uma tradu&ccedil;&atilde;o de um artigo do Russ Weakley. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What Is The Last Thing You Do Before You Launch A Website? &#124; i know idea</title>
		<link>http://www.maxdesign.com.au/articles/checklist/comment-page-1/#comment-3450</link>
		<dc:creator>What Is The Last Thing You Do Before You Launch A Website? &#124; i know idea</dc:creator>
		<pubDate>Fri, 16 Jul 2010 12:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.maxdesign.com.au/?page_id=1090#comment-3450</guid>
		<description>[...] Web Standards Checklist  [...]</description>
		<content:encoded><![CDATA[<p>[...] Web Standards Checklist  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

