<?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"
	>
<channel>
	<title>Comments on: Accessible Table Markup Demonstration</title>
	<atom:link href="http://marcamos.com/accessible-table-markup-demonstration/feed/" rel="self" type="application/rss+xml" />
	<link>http://marcamos.com/accessible-table-markup-demonstration/</link>
	<description>&#60;love&#62;&#60;/love&#62;</description>
	<pubDate>Fri, 21 Nov 2008 02:30:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Chris Bloom</title>
		<link>http://marcamos.com/accessible-table-markup-demonstration/#comment-50</link>
		<dc:creator>Chris Bloom</dc:creator>
		<pubDate>Fri, 22 Aug 2008 17:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/accessible-table-markup-demonstration/#comment-50</guid>
		<description>	&lt;p&gt;Whoops, I overlooked the &#8220;write a long description&#8221; vs, &#8220;write a short description&#8221; in the source code. That seems like it should be the other way around though &#8211; the attribute should be the short value and the tagset should contain the long value, at least from a semantic standpoint.&lt;/p&gt;

	&lt;p&gt;Anyway, adjust my initial question in my previous comment to &#8220;Is the summary attribute used differently/separately from the caption tag by screen readers and co.?&#8221; &lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Whoops, I overlooked the &#8220;write a long description&#8221; vs, &#8220;write a short description&#8221; in the source code. That seems like it should be the other way around though &#8211; the attribute should be the short value and the tagset should contain the long value, at least from a semantic standpoint.</p>
<p>Anyway, adjust my initial question in my previous comment to &#8220;Is the summary attribute used differently/separately from the caption tag by screen readers and co.?&#8221; </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Bloom</title>
		<link>http://marcamos.com/accessible-table-markup-demonstration/#comment-49</link>
		<dc:creator>Chris Bloom</dc:creator>
		<pubDate>Fri, 22 Aug 2008 16:57:27 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/accessible-table-markup-demonstration/#comment-49</guid>
		<description>	&lt;p&gt;Like haku, I appreciate seeing a real-world example of this. The w3c documentation on accessible tables is just too much to digest. &lt;/p&gt;

	&lt;p&gt;Is there a difference between the table summary attribute and the caption tag? Perhaps you could expand on this article by explaining &lt;span class="caps"&gt;WHY&lt;/span&gt; the scope attribute matters and how an accessibility program would use all of this.&lt;/p&gt;

	&lt;p&gt;Also, one thing I learned the other day &#8211; It doesn&#8217;t matter in what order the thead, tbody and tfoot tags appear in your &lt;span class="caps"&gt;HTML&lt;/span&gt; &#8211; the header will always appear at the top, the footer at the bottom and the table body in between. Not sure how this order is handled by screen readers, et. al. though.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Like haku, I appreciate seeing a real-world example of this. The w3c documentation on accessible tables is just too much to digest. </p>
<p>Is there a difference between the table summary attribute and the caption tag? Perhaps you could expand on this article by explaining <span class="caps">WHY</span> the scope attribute matters and how an accessibility program would use all of this.</p>
<p>Also, one thing I learned the other day &#8211; It doesn&#8217;t matter in what order the thead, tbody and tfoot tags appear in your <span class="caps">HTML</span> &#8211; the header will always appear at the top, the footer at the bottom and the table body in between. Not sure how this order is handled by screen readers, et. al. though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Thompson</title>
		<link>http://marcamos.com/accessible-table-markup-demonstration/#comment-52</link>
		<dc:creator>Kevin Thompson</dc:creator>
		<pubDate>Fri, 04 Jul 2008 15:46:44 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/accessible-table-markup-demonstration/#comment-52</guid>
		<description>	&lt;p&gt;Lookin good, but I was going to recommend you look into Geshi. There&#8217;s several plugins for Textpattern (never tried any of them though), and it generates the code formatting server side.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Lookin good, but I was going to recommend you look into Geshi. There&#8217;s several plugins for Textpattern (never tried any of them though), and it generates the code formatting server side.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angelo</title>
		<link>http://marcamos.com/accessible-table-markup-demonstration/#comment-2</link>
		<dc:creator>Angelo</dc:creator>
		<pubDate>Sun, 13 Jan 2008 20:18:33 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/accessible-table-markup-demonstration/#comment-2</guid>
		<description>	&lt;p&gt;Thanks for clearing up the difference between caption and summary.&lt;/p&gt;

	&lt;p&gt;I usually get those confused, as intuitively I&#8217;d put the longer description in the element and leave the short snippet for the attribute. &lt;/p&gt;

	&lt;p&gt;anyhow, much appreciated.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Thanks for clearing up the difference between caption and summary.</p>
<p>I usually get those confused, as intuitively I&#8217;d put the longer description in the element and leave the short snippet for the attribute. </p>
<p>anyhow, much appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: haku</title>
		<link>http://marcamos.com/accessible-table-markup-demonstration/#comment-3</link>
		<dc:creator>haku</dc:creator>
		<pubDate>Fri, 11 Jan 2008 13:04:46 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/accessible-table-markup-demonstration/#comment-3</guid>
		<description>	&lt;p&gt;Nice Marc. Honestly, That&#8217;s exactly the kind of thing I need to see. I wan&#8217;t to program nice semantic code like that, but without seeing it it&#8217;s all hit and miss. I will definitely follow this model in the future.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Nice Marc. Honestly, That&#8217;s exactly the kind of thing I need to see. I wan&#8217;t to program nice semantic code like that, but without seeing it it&#8217;s all hit and miss. I will definitely follow this model in the future.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
