<?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: HTML 5, microformats and testing accessibility</title>
	<atom:link href="http://www.brucelawson.co.uk/2007/html5-microformats-accessibility-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brucelawson.co.uk/2007/html5-microformats-accessibility-testing/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 14:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: bruce</title>
		<link>http://www.brucelawson.co.uk/2007/html5-microformats-accessibility-testing/comment-page-1/#comment-152940</link>
		<dc:creator>bruce</dc:creator>
		<pubDate>Sun, 10 Jun 2007 08:37:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2007/a-rant-html5-microformats-and-testing-accessibility/#comment-152940</guid>
		<description>Thanks Laura.

I like this sentence from the WAI/ PFWG statement:

&lt;blockquote&gt;Some commentors have suggested that in order to sustain a small language there have to be some screening factors, and frequency of use in the as-is Web is the screening factor to use.

The WAI position on this is roughly &quot;that is like saying that the builder of a high-rise building should decide whether or not to include fire-stairs based on whether the previous buildings at that street address had burned down or not.&quot;&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>Thanks Laura.</p>
<p>I like this sentence from the WAI/ PFWG statement:</p>
<blockquote><p>Some commentors have suggested that in order to sustain a small language there have to be some screening factors, and frequency of use in the as-is Web is the screening factor to use.</p>
<p>The WAI position on this is roughly &#8220;that is like saying that the builder of a high-rise building should decide whether or not to include fire-stairs based on whether the previous buildings at that street address had burned down or not.&#8221;</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura</title>
		<link>http://www.brucelawson.co.uk/2007/html5-microformats-accessibility-testing/comment-page-1/#comment-152212</link>
		<dc:creator>Laura</dc:creator>
		<pubDate>Sat, 09 Jun 2007 16:41:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2007/a-rant-html5-microformats-and-testing-accessibility/#comment-152212</guid>
		<description>On May 27, I asked for advice from WAI and the PFWG on the &quot;headers&quot; issue:
http://lists.w3.org/Archives/Public/public-html/2007May/1208.html

This is their resulting statement:
http://lists.w3.org/Archives/Public/public-html/2007Jun/0145.html

Then as the editor requested, 
http://lists.w3.org/Archives/Public/public-html/2007Jun/0003.html 

I put together an issues page in the HTML 5 working group&#039;s wiki on the subject.
http://esw.w3.org/topic/HTML/IssueTableHeaders</description>
		<content:encoded><![CDATA[<p>On May 27, I asked for advice from WAI and the PFWG on the &#8220;headers&#8221; issue:<br />
<a href="http://lists.w3.org/Archives/Public/public-html/2007May/1208.html" rel="nofollow">http://lists.w3.org/Archives/Public/public-html/2007May/1208.html</a></p>
<p>This is their resulting statement:<br />
<a href="http://lists.w3.org/Archives/Public/public-html/2007Jun/0145.html" rel="nofollow">http://lists.w3.org/Archives/Public/public-html/2007Jun/0145.html</a></p>
<p>Then as the editor requested,<br />
<a href="http://lists.w3.org/Archives/Public/public-html/2007Jun/0003.html" rel="nofollow">http://lists.w3.org/Archives/Public/public-html/2007Jun/0003.html</a> </p>
<p>I put together an issues page in the HTML 5 working group&#8217;s wiki on the subject.<br />
<a href="http://esw.w3.org/topic/HTML/IssueTableHeaders" rel="nofollow">http://esw.w3.org/topic/HTML/IssueTableHeaders</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alan bowers</title>
		<link>http://www.brucelawson.co.uk/2007/html5-microformats-accessibility-testing/comment-page-1/#comment-151611</link>
		<dc:creator>alan bowers</dc:creator>
		<pubDate>Sat, 09 Jun 2007 00:25:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2007/a-rant-html5-microformats-and-testing-accessibility/#comment-151611</guid>
		<description>HTML 5 authors follow a double standard. They claim that the spec is driven by the real world and what current browsers are capable of rendering. Then, they completely ignore the capabilities of screen readers and other assistive technology. The Web is not just for Web browsers!

But the biggest problem with HTML 5 is not fixing the accessibility flaws of HTML 4. Specifically support for numbered headings that nobody uses correctly. Mr Hickson, don&#039;t be afraid to borrow a little from XHTML 2. Don&#039;t worry, you won&#039;t get contaminated.</description>
		<content:encoded><![CDATA[<p>HTML 5 authors follow a double standard. They claim that the spec is driven by the real world and what current browsers are capable of rendering. Then, they completely ignore the capabilities of screen readers and other assistive technology. The Web is not just for Web browsers!</p>
<p>But the biggest problem with HTML 5 is not fixing the accessibility flaws of HTML 4. Specifically support for numbered headings that nobody uses correctly. Mr Hickson, don&#8217;t be afraid to borrow a little from XHTML 2. Don&#8217;t worry, you won&#8217;t get contaminated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.brucelawson.co.uk/2007/html5-microformats-accessibility-testing/comment-page-1/#comment-149332</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Wed, 06 Jun 2007 11:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2007/a-rant-html5-microformats-and-testing-accessibility/#comment-149332</guid>
		<description>Nice work, Steve. Let&#039;s hope Mr Hickson takes it into account.</description>
		<content:encoded><![CDATA[<p>Nice work, Steve. Let&#8217;s hope Mr Hickson takes it into account.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve faulkner</title>
		<link>http://www.brucelawson.co.uk/2007/html5-microformats-accessibility-testing/comment-page-1/#comment-148368</link>
		<dc:creator>steve faulkner</dc:creator>
		<pubDate>Tue, 05 Jun 2007 13:15:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2007/a-rant-html5-microformats-and-testing-accessibility/#comment-148368</guid>
		<description>Hi bruce, 
I joined the HTML WG last week to comment on the headers issue primarily. I have been doing some testing with JAWS and Window Eyes to see if the headers attribute is supported JAWS 6.2 test http://lists.w3.org/Archives/Public/public-html/2007Jun/0072.html and Window Eyes 6.0 test http://lists.w3.org/Archives/Public/public-html/2007Jun/0114.html

The tests indicate that for complex irregular data tables, JAWS and Window Eyes make use of  id/headers to correctly interpret the headers associated with a data cell, whereas the scope attribute in this case was not up to the job.</description>
		<content:encoded><![CDATA[<p>Hi bruce,<br />
I joined the HTML WG last week to comment on the headers issue primarily. I have been doing some testing with JAWS and Window Eyes to see if the headers attribute is supported JAWS 6.2 test <a href="http://lists.w3.org/Archives/Public/public-html/2007Jun/0072.html" rel="nofollow">http://lists.w3.org/Archives/Public/public-html/2007Jun/0072.html</a> and Window Eyes 6.0 test <a href="http://lists.w3.org/Archives/Public/public-html/2007Jun/0114.html" rel="nofollow">http://lists.w3.org/Archives/Public/public-html/2007Jun/0114.html</a></p>
<p>The tests indicate that for complex irregular data tables, JAWS and Window Eyes make use of  id/headers to correctly interpret the headers associated with a data cell, whereas the scope attribute in this case was not up to the job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Drake</title>
		<link>http://www.brucelawson.co.uk/2007/html5-microformats-accessibility-testing/comment-page-1/#comment-143355</link>
		<dc:creator>Ted Drake</dc:creator>
		<pubDate>Tue, 29 May 2007 15:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/index.php/2007/a-rant-html5-microformats-and-testing-accessibility/#comment-143355</guid>
		<description>Headers and summary are two attributes that suffer horribly from ignorance.  I strongly feel that they&#039;d be used more often if most programmers actually knew they existed. 

The table summary is an especially helpful attribute for screen readers. 

Here&#039;s an &lt;a href=&quot;http://tech.yahoo.com/pc/1994298603,1994298640,1994303193,1994236700,1991688186?full=yes#ytprodspecdiv&quot; rel=&quot;nofollow&quot;&gt;example of a complicated set of tables&lt;/a&gt; on Yahoo! Tech that use headers to make a product comparison grid usable for screen readers. It uses the headers and summary attributes.

I built this page originally. It wasn&#039;t easy but I feel the result was worth the effort.</description>
		<content:encoded><![CDATA[<p>Headers and summary are two attributes that suffer horribly from ignorance.  I strongly feel that they&#8217;d be used more often if most programmers actually knew they existed. </p>
<p>The table summary is an especially helpful attribute for screen readers. </p>
<p>Here&#8217;s an <a href="http://tech.yahoo.com/pc/1994298603,1994298640,1994303193,1994236700,1991688186?full=yes#ytprodspecdiv" rel="nofollow">example of a complicated set of tables</a> on Yahoo! Tech that use headers to make a product comparison grid usable for screen readers. It uses the headers and summary attributes.</p>
<p>I built this page originally. It wasn&#8217;t easy but I feel the result was worth the effort.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

