<?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: Information structures: The grouped table</title>
	<atom:link href="http://www.standards-schmandards.com/2004/information-structures-the-grouped-table/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.standards-schmandards.com/2004/information-structures-the-grouped-table/</link>
	<description>A pragmatic approach to web standards and accessibility</description>
	<pubDate>Mon, 01 Dec 2008 23:05:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Thomas</title>
		<link>http://www.standards-schmandards.com/2004/information-structures-the-grouped-table/#comment-150</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Mon, 20 Jun 2005 15:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=11#comment-150</guid>
		<description>&lt;p&gt;Interesting read. However, it is pretty well established at this point that Jabba is male, and since Luke and Leia are twins there seems to be some error in your table data for 'age'. Although hyperspace travel presumably would create some weird temporal effects, I think that the one doing more space travel (Leia in this example) would age less, not more, that the other one, according to the theory of relativity.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Interesting read. However, it is pretty well established at this point that Jabba is male, and since Luke and Leia are twins there seems to be some error in your table data for &#8216;age&#8217;. Although hyperspace travel presumably would create some weird temporal effects, I think that the one doing more space travel (Leia in this example) would age less, not more, that the other one, according to the theory of relativity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juan Carlos</title>
		<link>http://www.standards-schmandards.com/2004/information-structures-the-grouped-table/#comment-115</link>
		<dc:creator>Juan Carlos</dc:creator>
		<pubDate>Fri, 08 Apr 2005 15:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=11#comment-115</guid>
		<description>&lt;p&gt;Don't rely on Jaws alone. It might be the most popular, but it isn't necessarily that good. Furthermore, regardless of whether it is good or bad, other screen readers are quite different. It is hard to create HTML modified for screen reader optimization as that might impact your ideal semantics.&lt;/p&gt; &lt;p&gt;Your example suggests possibly the use of two &#60;thead&#62; tags.&lt;/p&gt; &lt;p&gt;Things like scope, and axis in theory will help users navigate the table much more easily, but that requires Jaws and others to get on board and support this stuff (I think Jaws has some limited support).&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Don&#8217;t rely on Jaws alone. It might be the most popular, but it isn&#8217;t necessarily that good. Furthermore, regardless of whether it is good or bad, other screen readers are quite different. It is hard to create HTML modified for screen reader optimization as that might impact your ideal semantics.</p>
<p>Your example suggests possibly the use of two &lt;thead&gt; tags.</p>
<p>Things like scope, and axis in theory will help users navigate the table much more easily, but that requires Jaws and others to get on board and support this stuff (I think Jaws has some limited support).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrick h. lauke</title>
		<link>http://www.standards-schmandards.com/2004/information-structures-the-grouped-table/#comment-66</link>
		<dc:creator>patrick h. lauke</dc:creator>
		<pubDate>Wed, 19 Jan 2005 01:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=11#comment-66</guid>
		<description>&lt;p&gt;the problem with approach #2 would be the navigability of the table with a screenreader like JAWS. splitting the table up into separate ones makes it that little bit more difficult to, say, just go down row by row while staying in a particular column.&lt;/p&gt; &lt;p&gt;not looked too hard at it, and don't have JAWS here at home, but it appears to be a classic example of a complex, multi-dimensional table where headers should be identified via headers/id (and possibly axis), rather than scope. &lt;a href="http://www.w3.org/TR/html401/struct/tables.html#multi-dimension"&gt;W3C HTML4.01 spec - Tables in HTML documents&lt;/a&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>the problem with approach #2 would be the navigability of the table with a screenreader like JAWS. splitting the table up into separate ones makes it that little bit more difficult to, say, just go down row by row while staying in a particular column.</p>
<p>not looked too hard at it, and don&#8217;t have JAWS here at home, but it appears to be a classic example of a complex, multi-dimensional table where headers should be identified via headers/id (and possibly axis), rather than scope. <a href="http://www.w3.org/TR/html401/struct/tables.html#multi-dimension">W3C HTML4.01 spec - Tables in HTML documents</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://www.standards-schmandards.com/2004/information-structures-the-grouped-table/#comment-58</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Wed, 05 Jan 2005 10:52:34 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=11#comment-58</guid>
		<description>&lt;p&gt;Joe, thank you for your comment. Using a definition list is not recommended. Jaws for example, reads definition lists as "Definition list of X items. [dt text] equals [dd text]". This would make a grouped table confusing for a screen reader user.&lt;/p&gt; &lt;p&gt;Using multiple tables creates the same issues as approach #2: repeated column headers and possible problems with column alignment.&lt;/p&gt; &lt;p&gt;Using headings could be an alternative in approach #1 if one makes sure those headings exist in a proper heading context.&lt;/p&gt; &lt;p&gt;Thhis article is meant as a starting point for a discusssion around a good solution. I have seen many web applications where this is an issue.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Joe, thank you for your comment. Using a definition list is not recommended. Jaws for example, reads definition lists as &#8220;Definition list of X items. [dt text] equals [dd text]&#8220;. This would make a grouped table confusing for a screen reader user.</p>
<p>Using multiple tables creates the same issues as approach #2: repeated column headers and possible problems with column alignment.</p>
<p>Using headings could be an alternative in approach #1 if one makes sure those headings exist in a proper heading context.</p>
<p>Thhis article is meant as a starting point for a discusssion around a good solution. I have seen many web applications where this is an issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://www.standards-schmandards.com/2004/information-structures-the-grouped-table/#comment-54</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Mon, 03 Jan 2005 19:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=11#comment-54</guid>
		<description>&lt;p&gt;I don't know why you can't just use headings; multiple tables with caption; or a definition list. Your example table seems too fictitious for us to really decide which is best, or at least which is least bad.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know why you can&#8217;t just use headings; multiple tables with caption; or a definition list. Your example table seems too fictitious for us to really decide which is best, or at least which is least bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://www.standards-schmandards.com/2004/information-structures-the-grouped-table/#comment-2</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Mon, 01 Nov 2004 23:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=11#comment-2</guid>
		<description>&lt;p&gt;Interesting article. This will be very helpful for a webapp we are developing right now.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Interesting article. This will be very helpful for a webapp we are developing right now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
