W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2013


From: Jan Eric Hellbusch <hellbusch@2bweb.de>
Date: Thu, 24 Jan 2013 17:48:52 +0100
To: "'Userite'" <richard@userite.com>, "'Andy Keyworth'" <akeyworth@tbase.com>, <w3c-wai-ig@w3.org>
Message-ID: <001301cdfa52$b12d9830$1388c890$@2bweb.de>
Hi Richard,

> In practice, 99% of the times that I come across <tbody> etc. it is just cluttering
> up the HTML code to no purpose whatsoever.

Over the years many people claimed THEAD, TFOOT and TBODY should be used properly, so screenreaders can deal with the data. The only thing that sort of went wrong was that when using those elements correctly, the footer is placed between header and bodies. The reading sequence was then obviously incorrect. 

Because the elements are for printers and not for screenreaders, I tried to get people to use them only for long tables and even then the sequence (head, footer, bodies) was not satisfactory. It seems that JAWS has fixed this issue since version 11. Tables marked up with THEAD, TFOOT and TBODY can be read in correct order in JAWS when using table navigation key strokes.


Jan Eric Hellbusch 
Tel.: +49 (231) 86436760 oder +49 (163) 3369925
Web: http://2bweb.de     Twitter: www.twitter.com/2bweb
Das Buch über barrierefreies Webdesign:
"Barrierefreiheit verstehen und umsetzen - Webstandards für ein zugängliches und nutzbares Internet"
812 Seiten, Dpunkt Verlag (2011)
Received on Thursday, 24 January 2013 16:49:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:47 UTC