<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-16786627.post116517181757473434..comments</id><updated>2009-06-23T21:23:01.454-07:00</updated><title type='text'>Comments on Web Axe - Practical Web Design Accessibility Tips - Podcast and Blog: Podcast #36: Complex Data Tables</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://webaxe.blogspot.com/feeds/116517181757473434/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/16786627/116517181757473434/comments/default'/><link rel='alternate' type='text/html' href='http://webaxe.blogspot.com/2006/12/podcast-36-complex-data-tables.html'/><author><name>Dennis at Web Axe</name><uri>http://www.blogger.com/profile/05123030988639971556</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>3</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-16786627.post-116535815431372846</id><published>2006-12-05T14:35:00.000-08:00</published><updated>2006-12-05T14:35:00.000-08:00</updated><title type='text'>Hi Dennis!The tables in question where a represent...</title><content type='html'>Hi Dennis!&lt;BR/&gt;&lt;BR/&gt;The tables in question where a representation of data from a printed document.&lt;BR/&gt;&lt;BR/&gt;What I created with tables was an almost exact duplicate of the tables in the printed document.&lt;BR/&gt;&lt;BR/&gt;I had a meeting with the client late last week and I did discuss this with them, but the fact of the matter is, while accessibility is a matter of course for anything I produce, the audience for their products is pretty well-defined.&lt;BR/&gt;&lt;BR/&gt;You just don't see physically or visually impaired mechanical engineers!&lt;BR/&gt;&lt;BR/&gt;I know that sounds glib, but the clients customer demographics tell the story and the money has to follow that.&lt;BR/&gt;&lt;BR/&gt;As I mentioned, the new website will be standards-compliant from the ground up, but I just needed some guidance on the tables situation.&lt;BR/&gt;&lt;BR/&gt;Thanks for the input...</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/16786627/116517181757473434/comments/default/116535815431372846'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/16786627/116517181757473434/comments/default/116535815431372846'/><link rel='alternate' type='text/html' href='http://webaxe.blogspot.com/2006/12/podcast-36-complex-data-tables.html?showComment=1165358100000#c116535815431372846' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://webaxe.blogspot.com/2006/12/podcast-36-complex-data-tables.html' ref='tag:blogger.com,1999:blog-16786627.post-116517181757473434' source='http://www.blogger.com/feeds/16786627/posts/default/116517181757473434' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-16786627.post-116533304326853596</id><published>2006-12-05T07:37:00.000-08:00</published><updated>2006-12-05T07:37:00.000-08:00</updated><title type='text'>Hello Wayne. You should never have nested data tab...</title><content type='html'>Hello Wayne. You should never have nested data tables. I suggest trying the following: use header columns as well as header rows; separate your data in more than one table; simplify the content and put detailed information in hyperlinked pages.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/16786627/116517181757473434/comments/default/116533304326853596'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/16786627/116517181757473434/comments/default/116533304326853596'/><link rel='alternate' type='text/html' href='http://webaxe.blogspot.com/2006/12/podcast-36-complex-data-tables.html?showComment=1165333020000#c116533304326853596' title=''/><author><name>Dennis Lembree</name><uri>http://www.blogger.com/profile/05123030988639971556</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='10028270956873676510'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://webaxe.blogspot.com/2006/12/podcast-36-complex-data-tables.html' ref='tag:blogger.com,1999:blog-16786627.post-116517181757473434' source='http://www.blogger.com/feeds/16786627/posts/default/116517181757473434' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-16786627.post-116532521881925194</id><published>2006-12-05T05:26:00.000-08:00</published><updated>2006-12-05T05:26:00.000-08:00</updated><title type='text'>Purely from an accessibility point of view, what h...</title><content type='html'>Purely from an accessibility point of view, what happens in a situation where there are nested tables?&lt;BR/&gt;&lt;BR/&gt;Or, would you consider that a failure on the part of the developer to have to use nested tables in the first place?&lt;BR/&gt;&lt;BR/&gt;I've had to use nested tables before now for very complex product data (mechanical tolerances and tolerance ranges) and they look hideous...</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/16786627/116517181757473434/comments/default/116532521881925194'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/16786627/116517181757473434/comments/default/116532521881925194'/><link rel='alternate' type='text/html' href='http://webaxe.blogspot.com/2006/12/podcast-36-complex-data-tables.html?showComment=1165325160000#c116532521881925194' title=''/><author><name>Anonymous</name><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://webaxe.blogspot.com/2006/12/podcast-36-complex-data-tables.html' ref='tag:blogger.com,1999:blog-16786627.post-116517181757473434' source='http://www.blogger.com/feeds/16786627/posts/default/116517181757473434' type='text/html'/></entry></feed>